The All In One Source Bitwig Information & Speculation Thread

[whyterabbyt]

Problems with controller support (or at least adding manual naming, see my post above), missing multi channel support for VSTs and missing MIDI routing are not small bugs IMO

No, they're not, they're design decisions, informed by priorities, available resources, and deadlines. Like with any other software development project.

Poor decision. Isn't that what he was implying? idk.

No, he was merely doing the usual KVR bitchwhine of conflating 'they didnt do exactly what I want with every bell and whistle evar and give me a free blowjob' with 'bug'.

[spinlud]

Ehi guys maybe it's only me but i can't change size of a track in the arrangement...how do i do that?

[virtualmark]

but hopefully they have a decent report system to report any crash and unexpected behaviour?

Actually I've not had any indication of any crash report system so far. Several of my VSTs don't work, and when it scanned them it crashed the VST part a few times. Although the DAW seems rock solid, it's certainly lacking in VST support. I would love the opportunity to submit a report, yet haven't found this feature yet.

[ravasb]

I have been trying this out. It is a very well done DAW, though it actually reminds me more of Sonar than Live in a lot of ways. I gave up on Sonar because it was so buggy, so this might be a good alternative.

I give that devs a lot of credit for a job well done and wish them much success. I am still going to hold on to Live, if nothing else I could not live without MaxforLive at this point, but who knows.

Ultimately it is the musician who is the real creative force, not the DAW. Everyone needs to find their own tools. Bitwig will definitely fill that for some. It will be interesting to see how Ableton reacts.

[ZenPunkHippy]

but hopefully they have a decent report system to report any crash and unexpected behaviour?

Actually I've not had any indication of any crash report system so far. Several of my VSTs don't work, and when it scanned them it crashed the VST part a few times. Although the DAW seems rock solid, it's certainly lacking in VST support. I would love the opportunity to submit a report, yet haven't found this feature yet.

If Bitwig crashes a dialog is displayed next time it starts, with an option of sending info to Bitwig + what you were doing at the time of the crash.

So yes it's there, just not as visible (which is a good thing IMO).

[ThomasHelzle]

but hopefully they have a decent report system to report any crash and unexpected behaviour?

Actually I've not had any indication of any crash report system so far. Several of my VSTs don't work, and when it scanned them it crashed the VST part a few times. Although the DAW seems rock solid, it's certainly lacking in VST support. I would love the opportunity to submit a report, yet haven't found this feature yet.

For VSTs:

Go to Options -> Preferences -> Plugins Management.
At the bottom there is a large button labeled: "Show errors found with plugins".
Click it.
Now you get a list of non working plugins (althogh some may be unrelated DLLs).
Up on the right side you find a "Copy Errors to Clipboard" button.
Press it.
Paste that into a mail here:
http://www.bitwig.com/en/support/tech-support.html
and maybe add your system specs/OS etc.

For non-plugin crashes there should be a bug report dialogue pop up as Andy stated when you restart BWS.

Cheers,

Tom

[Echoes in the Attic]

Definitely going to sending a lot of crash reports! Getting audio engine crashes left right and cetner with plug-ins. Mainly during deleting or loading a plug-in.

[Numanoid]

Getting audio engine crashes left right and cetner with plug-ins. Mainly during deleting or loading a plug-in.

Can you sandbox 'em ?

[ThomasHelzle]

Getting audio engine crashes left right and cetner with plug-ins. Mainly during deleting or loading a plug-in.

Can you sandbox 'em ?

I would recommend setting in Preference -> Plug-In Management
"Independent processing for each Plug-in.
Only in that case all plugins are running separated and you should be able to restart them individually if one crashes.
With Global Processing 32 Bit and 64 Bit Plugins are running in two shared spaces which basically means that all 64 or all 32 Bit Plugins crash together...

Cheers,

Tom

[Echoes in the Attic]

Getting audio engine crashes left right and cetner with plug-ins. Mainly during deleting or loading a plug-in.

Can you sandbox 'em ?

I would recommend setting in Preference -> Plug-In Management
"Independent processing for each Plug-in.
Only in that case all plugins are running separated and you should be able to restart them individually if one crashes.
With Global Processing 32 Bit and 64 Bit Plugins are running in two shared spaces which basically means that all 64 or all 32 Bit Plugins crash together...

Cheers,

Tom

Yeah I found that setting in preferences. Given that they have promted that feature as the way it works, I was surprised to see that plug-ins were not automatically set to be independent by default. This makes me wonder if there is some cost to having them all checked, like a performance hit or something?

[virtualmark]

Getting audio engine crashes left right and cetner with plug-ins. Mainly during deleting or loading a plug-in.

Can you sandbox 'em ?

I would recommend setting in Preference -> Plug-In Management
"Independent processing for each Plug-in.
Only in that case all plugins are running separated and you should be able to restart them individually if one crashes.
With Global Processing 32 Bit and 64 Bit Plugins are running in two shared spaces which basically means that all 64 or all 32 Bit Plugins crash together...

Cheers,

Tom

Yeah I found that setting in preferences. Given that they have promted that feature as the way it works, I was surprised to see that plug-ins were not automatically set to be independent by default. This makes me wonder if there is some cost to having them all checked, like a performance hit or something?

Yeah I also wondered this. I left it on default as I haven't read through the manual yet, I'll probably change it to independent now.

[ThomasHelzle]

Getting audio engine crashes left right and cetner with plug-ins. Mainly during deleting or loading a plug-in.

Can you sandbox 'em ?

I would recommend setting in Preference -> Plug-In Management
"Independent processing for each Plug-in.
Only in that case all plugins are running separated and you should be able to restart them individually if one crashes.
With Global Processing 32 Bit and 64 Bit Plugins are running in two shared spaces which basically means that all 64 or all 32 Bit Plugins crash together...

Cheers,

Tom

Yeah I found that setting in preferences. Given that they have promted that feature as the way it works, I was surprised to see that plug-ins were not automatically set to be independent by default. This makes me wonder if there is some cost to having them all checked, like a performance hit or something?

I agree - I had exactly the same question in the beta
I would think that there is a small memory overhead and maybe a small performance fee too, but in my experience it was never critical and well worth the added security net. I never did an A/B test though

Cheers,

Tom

[Echoes in the Attic]

I'll be checking it on. Just didn't want to at first because I didn't think that feature would have been an option (as in "why wouldn't someone check them all?)" And, I was just a little concerned about performance already given that I could not run at 128 samples with my mac built-in soundcard. Never had a problem with that in Live, Logic or Studio One.

[tooneba]

Basically processing in several program is inefficient than doing in a single program. That's probably why it's unabled default.

[The Mantra]

First thing I did this morning is DL Bitwig demo. The installation was smooth and fast.

Initial impressions after 30 min with BW:
-It did not recognize my remote sl which is disappointing (ended up w/generic midi controller)

-PXT general (the basic push script) works fine in BW

-A quick browsing of the devices sound good (better than Live IMHO)

-The GUI feels real smooth when things move around. Its hard to describe but things load and move across the screen in a smooth way kind of like an Ipad.

-Komplete 9 ultimate seems to work, although I didn't try every single plugin.

-This Daw is NOT a live clone. I have been with Live since V5.0 and while I was able to get things going and play around, I don't feel like I know Bitwig just because I know live (the learning curve looks shallow though).

Overall It looks promising but i don't have time to give BW a serious look until later. The daw feels good enough that I can say that I would buy it if It was fully compatible with Push (PXT general is nice but only gives you basic features), or I didn't own Push
EDIT:
I'm running a digi 002 win7 64bit