KVR Audio

Sailor16 · Post by **Sailor16** » Sat Jul 14, 2018 7:43 pm

I have a friend who used to yell at Bitwig because it was so long in "beta stage" before 1.0 was finally released. Then all of the sudden the same friend switched perspective and started praising Bitwig. But today he's again back at hating Bitwig, not really sure why. My guess is that there's this tipping point when reality hit my friend and made it clear that it's not about the tools, it's about his talent and skills. If my friend can't do whatever he wishes to do with simple means, no amount of gear, plugins, DAWs or DAW features will do it for him either.

On topic, version 2.4 seems very interesting!

deastman · Post by **deastman** » Sat Jul 14, 2018 9:00 pm

I currently use Bitwig, Live, Cubase, Reason, and Logic (let’s not mention Sonar!). I’m thrilled with each new release of every DAW, and I use each one for its strengths. Worrying about their weaknesses is a waste of time IMHO.

xbitz · Post by **xbitz** » Sun Jul 15, 2018 10:26 am

just share it, looks cool

SLiC · Post by **SLiC** » Sun Jul 15, 2018 10:46 am

Yes, BWS is the only DAW I have used that truly embraces touch screen (with specific modes/layouts and keyboards for touch use), I am using it very successfully on my MS Surface.

putoff · Post by **putoff** » Sat Jul 21, 2018 10:13 pm

Can I resurrect the the VST3 issue?

Ableton really should support it for one. It's not even at VST3 anymore, they have moved onto VST 3.5 in 2011! They are further behind than before.

However, I have experienced buggy VST3 plugins. Scaler was one of them, as well as VPS Avenger, where the initialized state of the program was literally unusable compared to the VST2 version. I think that VST3 might be the successor everybody wants, but VST2's have less bugs. I'm not fully convinced with VST3.

That being said, you can load VST3 into Ableton Live using Stagecraft Universal Plug. I never see anybody mention this but it's always a relevant point. You can also use it to load AU into VST hosts and other kinds of shenanigans.

pdxindy · Post by **pdxindy** » Sat Jul 21, 2018 11:39 pm

Back on topic... Bitwig 2.4 beta 1 is available for download

marmess · Post by **marmess** » Mon Jul 23, 2018 10:37 pm

Can someone let me know if this new version solved the issues with MPE? On paper yes, but is it good also in practice? I might do the upgrade if it's worth it.

pdxindy · Post by **pdxindy** » Mon Jul 23, 2018 11:22 pm

marmess wrote:Can someone let me know if this new version solved the issues with MPE? On paper yes, but is it good also in practice? I might do the upgrade if it's worth it.

What issues are you referring to?

marmess · Post by **marmess** » Tue Jul 24, 2018 3:10 am

Right, I haven't been clear.
I was talking about the ability to work with instruments who can deal with Voice per channel. Problem being Midi channel are reassign to an other numbers.

In Logic (or mainstage), it's possible to reassign CC74 to CC2 and the value is sent by channel. Is that possible with Bitwig 2.4?

Other option, copy-paste 2 vst tracks and filter the instrument channel input to create a "fake" MPE instrument. Is it working well inside one track right now?

pdxindy wrote:
marmess wrote:Can someone let me know if this new version solved the issues with MPE? On paper yes, but is it good also in practice? I might do the upgrade if it's worth it.
What issues are you referring to?

Winstontaneous · Post by **Winstontaneous** » Tue Jul 24, 2018 4:29 am

deastman wrote:I currently use Bitwig, Live, Cubase, Reason, and Logic (let’s not mention Sonar!). I’m thrilled with each new release of every DAW, and I use each one for its strengths. Worrying about their weaknesses is a waste of time IMHO.

Unless you start a project one you don't like it and need to finish it.

I love Logic's Drummer, Alchemy, and other native FX/synths but hate everything else about it, especially its instability with 3rd party AUs, broken PDC, automation and mixer. Still I use it, but most of the time I export as audio ASAP.

I know what you mean though, I use Live/Logic/Reason/Audition for what they do well and don't expect them to be something they're not.

pdxindy · Post by **pdxindy** » Tue Jul 24, 2018 4:51 am

marmess wrote:Right, I haven't been clear.
I was talking about the ability to work with instruments who can deal with Voice per channel. Problem being Midi channel are reassign to an other numbers.

In Logic (or mainstage), it's possible to reassign CC74 to CC2 and the value is sent by channel. Is that possible with Bitwig 2.4?

Other option, copy-paste 2 vst tracks and filter the instrument channel input to create a "fake" MPE instrument. Is it working well inside one track right now?

Bitwig is still strictly following the MPE protocol.

Only VST synths that can use CC74 and Pitchbend of +/-48 fully works.

Bitwig 2.4 now has full midi channel support. So that is an important step.

marmess · Post by **marmess** » Wed Jul 25, 2018 3:03 am

Ok, it sounds a little bit better but everything it's still not versatile.
What about MPE automation, have they added a pen tool to edit the recorded curves? It's a pain not having this option.

pdxindy wrote: Bitwig is still strictly following the MPE protocol.
Only VST synths that can use CC74 and Pitchbend of +/-48 fully works.
Bitwig 2.4 now has full midi channel support. So that is an important step.

pdxindy · Post by **pdxindy** » Fri Jul 27, 2018 3:17 pm

marmess wrote:Ok, it sounds a little bit better but everything it's still not versatile.
What about MPE automation, have they added a pen tool to edit the recorded curves? It's a pain not having this option.

pdxindy wrote: Bitwig is still strictly following the MPE protocol.
Only VST synths that can use CC74 and Pitchbend of +/-48 fully works.
Bitwig 2.4 now has full midi channel support. So that is an important step.

In 2.4 beta 2, Bitwig added ability to set Pitchbend range per device. Anything from 12-96

I just tried it with Bazille (which is still +/-24) and it works as expected. So that limitation is resolved!

Bitwig 2.4 announced