Ableton Push support is here

[Collings]

Please... 64 pad Support

[TeotiGraphix]

Please... 64 pad Support

Asked for many times but right now, it would be to observer intensive and kill the script.

Mike

[yonhorizon]

First, thanks a lot for this work.
Wanted to report issues I'm having.
The device parameters of vst, can't be accessed many times, it just says "choose device layer".usually it can be fixed by adding a track with bitwig instrument, accessing its parameters, than when u go back to the vst track it allows u to go to the parameters pages.

[codec17]

Hello moss,

Question regarding to group track and his devices...
When im in device mode on my push and select a "normal" track WITH MY MOUSE on my monitor, I see in an instant wich devices/VST it got on my screen of push.
Now when i select a grouptrack (with devices) you already feel this one coming....
It wants me to select a device.. when you do that on the device in the panel of screen nothing happens, BUT when i double click on device chain in mixer it selects it.
Is this a shortcoming in the API or just not finished?
Hope it could be fixed... if not? Well life goes on..

Thnx in advance.

I strangely never tested that. Seems to be missing on Bitwigs side. I wrote a report.

Ah Thnx! I saw Volker could reproduce it...

[yonhorizon]

i dunno, wasnt we been able once to browse and select instruments from push? like in ableton? now the browse button only opens the bitwig browser.
the sequencer in drum layout, sometimes working. most of the time not working. cant see the running bar.
device parameters can be acceced 30% of the times. i wrote about it up ^

is something in my drivers\setting is wrong?

[moss]

i dunno, wasnt we been able once to browse and select instruments from push? like in ableton? now the browse button only opens the bitwig browser.

You can only select patches not instruments. You need to make sure that a device is selected.

the sequencer in drum layout, sometimes working. most of the time not working. cant see the running bar.

If you don't see the running bar the clip is not "really" selected. There is sometimes a problem with the focus in Bitwig. Click on the clip again to give it the focus.

device parameters can be acceced 30% of the times. i wrote about it up ^

Can you be more specific what's your problem here?

[pdxindy]

i dunno, wasnt we been able once to browse and select instruments from push? like in ableton? now the browse button only opens the bitwig browser.

You can only select patches not instruments. You need to make sure that a device is selected.

Is that something that we can expect to be added by Bitwig?

How about adding clips? (which could then have the instrument)

[moss]

i dunno, wasnt we been able once to browse and select instruments from push? like in ableton? now the browse button only opens the bitwig browser.

You can only select patches not instruments. You need to make sure that a device is selected.

Is that something that we can expect to be added by Bitwig?

How about adding clips? (which could then have the instrument)

The browser API is actually already capable of both but is missing the functions to open up the browser in those contexts. It's on the TODO list of Bitwig.

[pdxindy]

i dunno, wasnt we been able once to browse and select instruments from push? like in ableton? now the browse button only opens the bitwig browser.

You can only select patches not instruments. You need to make sure that a device is selected.

Is that something that we can expect to be added by Bitwig?

How about adding clips? (which could then have the instrument)

The browser API is actually already capable of both but is missing the functions to open up the browser in those contexts. It's on the TODO list of Bitwig.

I don't mind waiting for that. Thanks for the reply!

[soehngenetic]

Jürgen, do you any response from the Bitwigs, if they also have the API device direct parameter bug on their ToDo list? - I started using Bitwig in combination with Push last week and it would be really nice to have the possibility to control VST parameters via Push (and not only to reset them to the lowest possible value ). - I was hoping for the 1.3 RC2, but the problem remains there. Btw. thanks for the amazing Push script!

[moss]

Jürgen, do you any response from the Bitwigs, if they also have the API device direct parameter bug on their ToDo list? - I started using Bitwig in combination with Push last week and it would be really nice to have the possibility to control VST parameters via Push (and not only to reset them to the lowest possible value ). - I was hoping for the 1.3 RC2, but the problem remains there. Btw. thanks for the amazing Push script!

I checked in a workaround on GitHub but it works only for continuous parameters.

[pdxindy]

Jürgen, do you any response from the Bitwigs, if they also have the API device direct parameter bug on their ToDo list? - I started using Bitwig in combination with Push last week and it would be really nice to have the possibility to control VST parameters via Push (and not only to reset them to the lowest possible value ). - I was hoping for the 1.3 RC2, but the problem remains there. Btw. thanks for the amazing Push script!

I'm curious why you would even want to use the Direct Parameter mappings for VST's? By default they end up not organized well, and you have no control over the order. Common parameters that you might want to edit together end up in different pages. It's 100x way easier to edit via screen and mouse than to try to edit via Push with that mess.

Why not make your own Device mappings for the VST's you use? Sure it takes some time, but you only have to make a sensible organization once.

[moss]

Jürgen, do you any response from the Bitwigs, if they also have the API device direct parameter bug on their ToDo list? - I started using Bitwig in combination with Push last week and it would be really nice to have the possibility to control VST parameters via Push (and not only to reset them to the lowest possible value ). - I was hoping for the 1.3 RC2, but the problem remains there. Btw. thanks for the amazing Push script!

I'm curious why you would even want to use the Direct Parameter mappings for VST's? By default they end up not organized well, and you have no control over the order. Common parameters that you might want to edit together end up in different pages. It's 100x way easier to edit via screen and mouse than to try to edit via Push with that mess.

Why not make your own Device mappings for the VST's you use? Sure it takes some time, but you only have to make a sensible organization once.

+1 That's the way to go.

[soehngenetic]

Why not make your own Device mappings for the VST's you use? Sure it takes some time, but you only have to make a sensible organization once.

Thanks for this advice. As written before, I started using Bitwig about a week ago and I'm still discovering it. As a total Bitwig-noob one of my problems is, that with 1.2 some of the applications behaviour and icons seem to have changed, but the 1.2 manual still shows the ways and screenshots of earlier versions. - So I it would be very kind and cool, if you could PM me (to get not too off-topic here) a link to a tutorial or a short description how to do it. Thanks in advance.

[yonhorizon]

hello again.
big thanks moss for replying and for your work.
something weird hapenned. i formatted my pc and made a fresh windows install.
now i can browse on push. before couldnt no matter what.
the drum pad view changed its colors.
the record button , which before functioned as record clip, when clip was focused now enables arrangement record.
push still freezes when i quit bitwig.

i have the latest ableton firmware.

before i also had novation launch control connected, with that script for bitwig ( the only one ) and m-audio axiom 61, connected as generic keyboard. havent tried yet connnecting them. can it be some assignment clash ?

btw is there a way to record in session? ( the record button enables arrangement record is there a way to make it start the clip recrding ? )

thanks alot !