The All In One Source Bitwig Information & Speculation Thread

[SadPuppyBlues]

Just showing up to voice my appreciation to the beta testers who shared some info, Tom especially.

Thanks guys. It was cool hearing about it.

[pdxindy]

Just showing up to voice my appreciation to the beta testers who shared some info, Tom especially.

Thanks guys. It was cool hearing about it.

+1

[audiohouse]

Hi Tom,

I noticed on your screenshots of BW, it has high DSP usage, and you dont have many tracks.

Do u feel BW is efficient in using DSP/CPU? Or it gets clogged very easily...?

Btw thanks for the screenshots and info. BW is looking good.

[ThomasHelzle]

Thanks a lot guys for the appreciation
It actually IS a lot of work to get those answers to you and write up all this stuff - especially for things I hadn't tested myself before or areas that aren't totally mine. English not being my first language doesn't help either

I just need a break - and that need isn't related to the "creative elements" on the thread - I'm not so easy to frighten off.

I thoroughly enjoyed the cat pictures actually and my comments were never pointed at those or the merry fun, only at the very aggressive tones in some Bitwig threads and ridiculous remarks like "how Bitwig brought all this onto themselves" - which is totally beside the point IMO:

If you think about it: When Bitwig will come out, they can be sure to get quite some attention, half because of an interesting product and half because of all the hype - everybody interested in Live-like-DAWs should have heard about BW by now and be at least curious.

In marketing, any attention is good...

...but only if you can present a product fit to back that up, otherwise it can collapse fast.

I have a good impression of BW so far and think I will go for it, but YMMV of course.

But this is also why I try to relativise some of the anxiety and expectations.
When People expect a tool at 1.0 to blow everything else out of the water, the tool can't do anything but fail that test.


To address some of the remarks:

- That screenshot may have created a spike in itself by being taken and I had several 2D and 3D programs running at the same time. I have no problems with the performance of BW here, I don't think I encountered crackles or dropouts so far.

There are quite a lot of BWs Polysynths in the project (on many pads of the drum machine for instance are instances of that), 1 Kontakt, 1 Kruudster, 1 Harmor, in the layer test track there is a BW FM4 and a BW Organ together with several effects like the great ladder filter in multiple instances and then there is Jamstix on one track, which is a bit on the spikey side. With all this running, my CPU is at 8-10% for Bitwig.

- I use a 6 core i7 overclocked to 4.1 Ghz and 32 GB Ram running windows 8 pro x64. Audio Interface is a Presonus Firebox at 48kHz/4ms latency (lowest possible setting when driver is set to high CPU use).

- No Nebula here.

- Not sure about the Midi handling myself, but that may not be finished or I miss something (wouldn't be the first time).

More to come later this week when I have gathered more knowledge myself


As for more betatesters:
For an unreleased software, too many betatesters are actually more in the way than helpful.
If the noise goes over a certain threshold, you can't hear anything anymore, nor think clearly.
As frustrating as it is for some, I think they do the right thing - and of course you can say that I have it easy to say that and be totally right...

Cheers,

Tom

[IncarnateX]

Hi all
Sorry to have kept you waiting with regard to the Bitwig release. There have been some minor drawbacks and we had to simplify the code a little.
However, it is soon to be released and tested. Here is a sneak peak:



Cheers

does it has PDC?

Not at present. But we may be able to add it in the upcoming update, which will already be released in 2018.

[IncarnateX]

.....

[trimph1]

[hibidy]

That was a nice break for all of us.........wasn't it?

Now where is it! I blame my tools for my problems and only bitwig can save me from posting all the time!!!!!??????!!!!!!111111!!!!

[codec_spurt]

That was a nice break for all of us.........wasn't it?

I enjoyed it. It's good to take time out. Reconsider things. Look for new cat pics..

[hibidy]

No new cat pics for now, just reading. And an occasional pop-in.

[The Mantra]

Here's a tough one

I understand that Bitwig has VST3. Does it support the "VST expression" like Cubase?

Specifically, I own Halion Sonic and want to know if I will be able to edit instrument articulations in the automation lane like you can in Cubase.

If VST expression is not explicitly supported, is there any way to manually map articulations to Bitwigs per note automation with VST3 plugins?
If this is the case I might consider finally cashing in on that Halion symphonic orchestra coupon I got from Cubase 5.

I realize that it's unlikely that a beta tester would coincidentally have VST expression compatible plugins, but I figured i would go ahead and ask.

Shout out to Tom and all the beta testers for being so patient and generous.

[Bathrobe]

Note expression came with vst 3.5 if i'm not mistaken.

Not likely that bitwig supports vst 3.5.

But they seem to have their own version of note express that maybe works with any
vsti not only vst3.5 vsti's. See their last video for that.

[ThomasHelzle]

Here's a tough one

I understand that Bitwig has VST3. Does it support the "VST expression" like Cubase?

Specifically, I own Halion Sonic and want to know if I will be able to edit instrument articulations in the automation lane like you can in Cubase.

If VST expression is not explicitly supported, is there any way to manually map articulations to Bitwigs per note automation with VST3 plugins?
If this is the case I might consider finally cashing in on that Halion symphonic orchestra coupon I got from Cubase 5.

I realize that it's unlikely that a beta tester would coincidentally have VST expression compatible plugins, but I figured i would go ahead and ask.

Shout out to Tom and all the beta testers for being so patient and generous.

That's what I thought as well, but I got confirmation today that Bitwig 1.0 initially only comes with VST 2.4 support.
The Note-Expression/Microediting was developed independently from VST 3.5 (and actually before the latter came out) for the internal synths.

Sorry if I should have created a different impression before.

Cheers,

Tom

[Echoes in the Attic]

On the subject of folder tracks, I found this post while googling on the interwebs:
https://www.facebook.com/bitwig/posts/444328925606001

Facebook user "Bitwig" said that not only are there folder/group tracks but that they can be nested inside other group tracks. Ableton only allows one grouping, no sub groupings.

Is this confirmed by beta testers?

[ZenPunkHippy]

There are "Group" and "Ungroup" options on one of the menus, and it's referenced in the manual list of key commands, but it seems to be disabled at the moment.

Peace,
Andy.