Live 12 or Bitwig 5.1

[xbitz]

^^^ the modulation method of the VCV Surge modules is the same as in Bitwig, so it's not strictly necessary to use Bitwig if there's only a moderate need for such functionality.



There are quite a few of them https://library.vcvrack.com/?query=surg ... =&license=

It's like a fair here; they have everything.
Screenshot 2024-04-02 at 21.01.47.png

Is Surge-Rack also available for Cardinal-Rack?

seems https://cardinal.kx.studio/modules but personally, I've followed Protoculture's (mr. Bitwig )module selection as outlined in this video starting from 15:30, instead of going with a distro
https://www.youtube.com/watch?v=5EkrNrWq5h0&t=753s

[liquidsound]

^^^ the modulation method of the VCV Surge modules is the same as in Bitwig, so it's not strictly necessary to use Bitwig if there's only a moderate need for such functionality.



There are quite a few of them https://library.vcvrack.com/?query=surg ... =&license=

It's like a fair here; they have everything.
Screenshot 2024-04-02 at 21.01.47.png

Is Surge-Rack also available for Cardinal-Rack?

seems https://cardinal.kx.studio/modules but personally, I've followed Protoculture's (mr. Bitwig )module selection as outlined in this video starting from 15:30, instead of going with a distro
https://www.youtube.com/watch?v=5EkrNrWq5h0&t=753s

Thanks.
I did demo Cardinal but I was busy manufacturing my Reaper workflow and I got rid of it.
Mr. CubeWig... Nice guy

[wilkins_micawber]

FL studio -> bitwig user here. Live is really charming, but I cannot stand how there is no way to experiment with modulation while saving the original state of a parameter. If you map an LFO or something to a parameter like cutoff that should have its initial position as a a default, it becomes overly difficult to see the original position or easily revert to it.

[xbitz]

^^^ https://askondo.gumroad.com/l/MetaMacroMDx

[wilkins_micawber]

Looks like you're limited to the "built in" modulators, according to the description.

[xbitz]

You can still add an isotonik modulator on top, but if you use a lot of modulators then Bitwig and Grids. https://isotonikstudios.com/product/modulat/

[SmajjL]

^^ yeah! Live 12's improvements and https://cycling74.com/releases/max/8.6.0 should give Ableton-fans hope and more future smileys
Since they allow to demo it forever without saving we can try the Ableton-way to create a Fair opinion, it is so easy to throw out comments Way to fast!
Are we seriously spoiled nowdays or what?! hehe

[wilkins_micawber]

Some ableton modulators like the stock lfo add a blue dot that moves around the original knob position. If all modulators did that, id consider using live. i wonder if it's easily possible to convert existing m4l devices into modulators instead of overtakers

Edit: but only one thing can modulate a parameter at a time. Don't think it's hard to sum signals in the situation where I realize I want to sum, so I'm going to go give live another look!

[xbitz]

^^^ I mentioned the Modulat for this reason, because of the simple binding; from AL12 onwards, it no longer requires direct connection with the target controllers, and as a modulation framework, it can aggregate modulations internally.

https://www.youtube.com/watch?v=e8vHbaIoXL0

[wilkins_micawber]

I tried Modulat, and it does allow relative modulation easily.

One difference I'm finding about ableton that is a deal breaker is the CPU usage of modulators. Adding 7 msegs (midi shapers) increased CPU use by 10-15%

Doing the same thing in bitwig contributes 0% from what I can see

[pdxindy]

I tried Modulat, and it does allow easily relative modulation .

One difference I'm finding about ableton that is a deal breaker is the CPU usage of modulators. Adding 7 msegs (midi shapers) increased CPU use by 10-15%

Doing the same thing in bitwig contributes 0% from what I can see

Plus the workflow is so much better in Bitwig

[Yorrrrrr]

One difference I'm finding about ableton that is a deal breaker is the CPU usage of modulators. Adding 7 msegs (midi shapers) increased CPU use by 10-15%

I guess it's the additional Max for Live layer. However, CPU usage from the modulators have been reduced in latest Live 12 beta currently in testing.

[machinesworking]

Workflow wise, what kills me in Bitwig as I've mentioned before is how bad the multi monitor support is. Live being only two screens, Ableton really knocked it out of the park, it's perfect.

UX is a weird thing, I think in general Bitwig is far better in the keyboard shortcut category, but multi monitor wise it's far worse.

[Yorrrrrr]

Indeed. I found Bitwig UX to be bad overall. Weird thing.

[wilkins_micawber]

One difference I'm finding about ableton that is a deal breaker is the CPU usage of modulators. Adding 7 msegs (midi shapers) increased CPU use by 10-15%

I guess it's the additional Max for Live layer. However, CPU usage from the modulators have been reduced in latest Live 12 beta currently in testing.

With the standard version, 7 instances of midi shaper gives 34% load with nothing else happening. Can't access the beta with trial account.... Wish I could see if it helps