Ableton Push with Bitwig

[Grizzellda]

Alright guys, don't bother saying that Push is for Ableton, because I know that.

Is anyone using it for Bitwig. It is expensive.

What are you guys using?

[pboy]

I use the Push 2 and can report that it works really well, thanks to the script by Moss.

[Rivanni]

I use the Push 2 and can report that it works really well, thanks to the script by Moss.

Same here. Also Push 3. I can even use Push 2 and 3 together, something that is not possible with Ableton Live.

[BobDog]

All the stuff by Moss is top notch and push is a great controller for BW.

It's not as good as the Live integration which you would expect, so if you are not using Live and looking to buy a controller I would recommend looking on the internet about the controllers supported by Bitwig and also looking at https://www.mossgrabers.de/Software/Bitwig/Bitwig.html

[Grizzellda]

Thank you guys, totally appreciate the feedback, keep it coming!

I will be researching this stuff. Anybody using a Novation 64 pad controller?

[voidpipe]

I am using Launchpad Pro mk3 with Bitwig... Works for me.

[Muziksculp]

Hi,

I'm planning to use Bitwig Studio 6 as soon as it is officially out of beta.

I'm interested in pairing it with a suitable controller, that offers very good workflow, and integration.

Currently trying to decide on one of these (Novation Launch Pad Pro mk3, or Ableton Push 3 ) , Which one would you recommend, and why ?

Thanks.

[Milkman]

No experience with the push.

I literally just bought (arrived about 2 hours ago) the Launchcontrol XL MK3, and am learning it as we speak. I watched some videos with BWS users controlling BWS 5 with LCXL3 and saw all I needed to see: native scripts work really well, its highly customizable and/or has great template modes, its simple (single USB C if you want, 8 rows isnt too much/too little), and cubase also has good support for it. Ive seen some people performing with it and I got fairly inspired.

Problem Im running into, which isnt a big problem:
Im using BWS 5 and beta 6. Im reading the docs for LCXL3.bwextension and it shows when the script is loaded, you should get a list of custom controls you can manually set inside BWS's controller menu, but I dont see those controls. I get a generic list of controls if I create it as a "general controller", but I dont see all the colored controls, drop down menus, etc.

Anyone else use LCXL3 on BWS, any version?

[Milkman]

Something of an update for LaunchControl XL 3 users: both steinberg and bitwig have accepted the issue I raised with them, to do with bad controller detection (Bitwig) and shift+touch controls not working to display values (Cubase, Bitwig). Both vendors are working on updates to their scripts to fix this.

[Milkman]

So as of Bitwig 6.00, the script detection issue is resolved. LCXL MK3 is no longer being detected as a generic controller and is mapped correctly. However the "shift+touched parameter" value preview feature still doesnt work for sliders, only works for knobs.

Also Ive noticed there is no way to power off LCXL3. You have to unplug USB to do this, and I dont like this at all. There is that unused "novation" button on the bottom left, right next to "solo/arm", so perhaps a long press of this can power on/off some day?

It would also be nice to see a little better basic transport control: right now you tap play to start playback, and you tap it again to stop - but this changes the playhead position to the current position, like "pause", and always continues from the new position. Maybe just a quick shift+play brings you to the start of your loop/project? Ill make this suggestion to them.

Overall Im pretty happy with this controller and it works well in cubase and bitwig. I would really like to be able to power it off though.

[kinkajou]

maybe connect the controller through a switchable AC-powered USB hub?