Bitwig Studio 5.3 Beta Out Now (New drums and a step sequencer)

[Korg Supporter]

[M1st]

I think we'll all agree when I'll say that Cubase won, and it's over for Bitwig...

[ChanceB]

I think we'll all agree when I'll say that Cubase won, and it's over for Bitwig...

Not all of us

[kmonkey]

I think we'll all agree when I'll say that Cubase won, and it's over for Bitwig...

It sounds like someone thinks big about himself And most of the times it's the ones most insecure about themselves

[M1st]

It was a reference to the other thread from this month, and it was meant as a joke. Happy bitwig user over here, couldn't care less about DAW wars

[xbitz]

btw. this is where Bitwig's modular advantage comes into play. Unlike Ableton Live, while the output of MIDI processors doesn’t appear in the piano roll, the result isn’t baked into the clip. Currently, AL struggles to at least make previous phases retrievable during MIDI editing, but once the MIDI clip is closed, the modifier chain is lost, leaving only the final result. In contrast, Bitwig produces a non-baked output, allowing both the source and the processing to remain editable.

MIDICap also works as it should


Cubase, AL, whatever

[pdxindy]

It was a reference to the other thread from this month, and it was meant as a joke. Happy bitwig user over here, couldn't care less about DAW wars

It would be great if the hierarchy was finalized and discussion could end...

I like the new Drum Devices and especially, the new Grid Modules - Pitch Shifter and Frequency Shifter.

[Dalle]

btw. this is where Bitwig's modular advantage comes into play. Unlike Ableton Live, while the output of MIDI processors doesn’t appear in the piano roll, the result isn’t baked into the clip. Currently, AL struggles to at least make previous phases retrievable during MIDI editing, but once the MIDI clip is closed, the modifier chain is lost, leaving only the final result. In contrast, Bitwig produces a non-baked output, allowing both the source and the processing to remain editable.

MIDI effects in Live work the exact same way. The new piano roll MIDI tools in Live 12 are a different thing. Both have their use cases.

[xbitz]

^^^ But why would I use devices in Live when the ones embedded in the piano roll are so much more convenient, as long as I don't close the clip editor...what needs to be solved in Live is to preserve the modifier chain... till it Bitwig is better

[Dalle]

^^^ For the same advantages you just said Bitwig has?

[xbitz]

^^^ Bitwig wins the device-based competition because of the Note Grid, while Live wins due to its embedded tools in the piano roll—if the used tools were preserved. But for now, they aren't; to be continued when they are.


Or if you look at voice stacking, Bitwig is a very special kind of beast—it has its own niche, but at least it reigns supreme there

sick

[stoopicus]

Days after I bought Stepic, and I’m not even mad

[stoopicus]

It was a reference to the other thread from this month, and it was meant as a joke.

It was a good one, I literally loled. That other thread was so damn KVR.

[apoclypse]

^^^ Bitwig wins the device-based competition because of the Note Grid, while Live wins due to its embedded tools in the piano roll—if the used tools were preserved. But for now, they aren't; to be continued when they are.


Or if you look at voice stacking, Bitwig is a very special kind of beast—it has its own niche, but at least it reigns supreme there

sick

I'm not sure Bitwig "wins" because of Note Grid when Ableton has M4L. Not only does M4L work as midi effect devices and generators, but it also now works in the PR. So the argument is if Bitwig has midi or generative devices, so does Ableton. A lot of them in-fact.

I still prefer the way they are implemented in Bitwig, but I wouldn't call it a "win" when M4L can do so much more than Note Grid.

[apoclypse]

Anywho. I want to see what they do with 5.4 and the supposed arranger and piano roll updates before I even consider updating Bitwig. I'm still on 5.0.