The All In One Source Bitwig Information & Speculation Thread

[Robmobius]

Hmmm... BW has been pretty stable for me so far as well.

[4damind]

I am also not too keen on JAVA in a DAW, I am not sure if that is the best solution for a GUI, but I understand it had to be done because of porting to Linux and OSX.

They using the Cairo 2D open source cross-platform library which is programmed in "C" so it's not 100% Java. Same with the audio stuff.. they using PortAudio (also a open source cross-platform audio library).

[humanbeingbeing]

3. Can't get BWS and another app using audio to play together - web browser, audio player, etc. "Engine failed to connect" error is displayed until I kill all other apps/services using audio (including Adobe Flash player background services).

I've had this, it does some screwy stuff to Flash player apps in Chrome when I open Bitwig.

[Lesha]

1. No undo for VSTs

What do you mean? Like undo tweaking parameters in a VST?

2. Browser pane split in two makes no sense for VSTs, only for inbuilt effects and their presets

It makes perfect sense. And works quite well. You can store presets per VST in bitwig format that show up in the bottom pane. Also useful for bookmarks with folders and sub folders. And it's amazing for audio content, as it displays all files in a directory, including all files in sub directories. Never seen this before and massively useful.

3. Can't get BWS and another app using audio to play together - web browser, audio player, etc. "Engine failed to connect" error is displayed until I kill all other apps/services using audio (including Adobe Flash player background services).

Can't say I've had this issue.

4. When VSTs are deactivated, the CPU consumption still stays the same, so it's like muting them

Yeah I do hope they fix this one soon as well.

5. No MIDI routing

For me this has been made unnecessary due to the ability of single tracks have midi going to all devices. However it would be useful for drum plug-ins once multi-outputs is added.

6. Constantly crashing

Can't say I've had a crash since I think 1.02, sorry to hear that.

1. Yes, no undo for tweaking VST parameters.
2. Cool, I wasn't aware of that. But it still bothers me to resize it every time I want to pick a VST.

7. I forgot to add that the audio engine is still not optimized. I have tested several plugins in both Bitwig and Ableton, and Ableton is 50-60% more efficient as you can see from the number of SlickEQs I stacked together before the crackles appeared.

You can also see how each of the DAWs deals differently with latency, very nice to see it graphically (or at least the graphic implementation of latency).

[Echoes in the Attic]

True, Ableton is more efficient. CPU maxes out in Bitwig at about 75% of the mac CPU in Live with equivalent processes. Ableton did work making Live 9 more efficient than 8. I do hope Bitwig can optimize more.

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[xerxes[no]]

@ xerxes, I have no harboured ill will.. as you may notice, i edited that post out *immediately* (note there is no edit remark from kvr which shows how quick i did it) and your post quoting me was over half hour later (wow how did that happen lol?)

I was using the ipad as I mostly do, and an awesome, much missed mod once gave me advice.. to type out what i am feeling but not submit.. as the best therapy rather than get into a fight here with someone.. i do that all the time now and how I have avoided friction.. unfortunately a just cleaned ipad was uber sensitive and my finger must have literally just made the lightest contact with the submit button, which is why i immediately rushed to edit it out. That post was never meant to be seen or posted at all. It was simply thoughts I had written down to release frustration. You can edit it out if you want, but I am sure this explanation will suffice.

I hear you, no problems here. Lets go get a beer sometime when BWS is FLAWLESS and have a laugh Edited my own post too to clean things up a little. I replied while at work, so had to come back to finish it off after 20 minutes or so. Hehehe!

Looking forward to 1.06 and see how development goes.

Cheers!

[ObsoleteAcc99]

[DELETED]

[BMoore]

Not this shit again. Does mods ever learn?

[aharu]

You get more chicks and babes using Bitwig than you get with Ableton Live

[xerxes[no]]

You get more chicks and babes using Bitwig than you get with Ableton Live

LOL!

[dalor]

Demo'd Bitwig.

1) There is a a buffer problem with my Soundcard E-MU 1616m and everything sounds garbled in beyond 88khz and I tried all possible Buffer Sizes.
44.1khz and 48khz seem to work fine.

2) Akai AxiomPro61 is not working, tried the Generic MIDI Keyboard, no luck.

[woodsdenis]

Biggest WTF yet, it doesn't record pedal sustain info, it just lengthens the notes !!!! similar to convert pedal info to note length command on some DAWs. You can manually insert /edit pedal info after the fact.

[dsan@mail.com]

Demo'd Bitwig.

1) There is a a buffer problem with my Soundcard E-MU 1616m and everything sounds garbled in beyond 88khz and I tried all possible Buffer Sizes.
44.1khz and 48khz seem to work fine.

2) Akai AxiomPro61 is not working, tried the Generic MIDI Keyboard, no luck.

1.) I noticed the garbling issue the first time I ran BWS demo; however, after a bit it disappeared. I use Edirol FA-101. I'm running at 44.1 khz and 128 buffer.

Since that first time I've have not heard any sound issues. Hope that turns out the same for you.

2.) Do you mean m-Audio Axiom Pro 61 or Akai Mpk 61?
There is a script for m-Audio contributed by 4damind here (scroll down a bit past middle of page):
http://www.kvraudio.com/forum/viewtopic ... 2&start=30

If you haven't yet, it is recommended visiting the BWS forum here at KVR. Lots of useful information within

Happy Musiking!
dsan