Ableton Push support is here

[futuresproof]

How about the issue with the Virus?

I had a play around with this and found that they same thing happens using standard midi cables if the virus is set to use polypressure as one of the midi control "Page" options in edit mode. If you set "Page A" to controller data and "Page B" to sysex it works as normal. The trouble is you cant seem to change this setting when the plugin is used.

I tried converting ploy pressure to CC in the push script but it just set the CC and the poly pressure so a filter in the script might be the way to go. I might try using midiox and some virtual midi ports to filter this out to be sure.

[futuresproof]

I guess the "problem" is that the knobs are also sensitive to speed, which means that the value inc/decs faster if you move the knob faster..

Hi moss thanks for taking the time with this.

Do you think this is an API/Bitwig issue and is it worth reporting? The reason I ask is that the controller functions perfectly within Ableton and the automation is not trying to pull away from you as you write it. At the moment I find push pretty useless for recording automation into bitwig.

I hope this is fixable as I love all the other functionality you have in the script.

You can adjust the value to your liking in Config.js by changing the value of "Config.fractionValue".

Cheers I will have a play with this.

[pdxindy]

I purchased Bitwig recently and am exploring the 1.2 beta and using my Push (using latest github script).

In Ableton, if I put a vst synth in an Instrument Rack and map parameters to the rack macros, the 8 Push knobs automatically work and the 8 macros are immediately available to tweak while playing.

I've not been able to figure out how to do a similar setup in Bitwig. Is this possible?

[stamp]

How about the issue with the Virus?

I had a play around with this and found that they same thing happens using standard midi cables if the virus is set to use polypressure as one of the midi control "Page" options in edit mode. If you set "Page A" to controller data and "Page B" to sysex it works as normal. The trouble is you cant seem to change this setting when the plugin is used.

I tried converting ploy pressure to CC in the push script but it just set the CC and the poly pressure so a filter in the script might be the way to go. I might try using midiox and some virtual midi ports to filter this out to be sure.

Solved!
Download the latest ableton demo, set up the push as control surface in preferences. It should update your firmware. When done press and hold the user button set aftertouch treshold to 127. Exit ableton.

Now your push pads won't transmitt any aftertouch data. You can still send aftertouch with the ribbon if needed in BS.
It's a workaround but at least you can use your Virus.

Cheers

[moss]

I purchased Bitwig recently and am exploring the 1.2 beta and using my Push (using latest github script).

In Ableton, if I put a vst synth in an Instrument Rack and map parameters to the rack macros, the 8 Push knobs automatically work and the 8 macros are immediately available to tweak while playing.

I've not been able to figure out how to do a similar setup in Bitwig. Is this possible?

There's no need to wrap it in an Instrument Rack (but you can). The VST already has 8 Macros. You can select the Macros by pressing the Device button than select "Fixed" and then Macro. Watch my Tutorial video about devices ( ).

In Bitwig it is better to map/arrange the controls in Parameter Pages. If you are using 1.2 Beta, right click on the plugin and select "Edit panel mapping".

[futuresproof]

Solved!
Download the latest ableton demo, set up the push as control surface in preferences. It should update your firmware. When done press and hold the user button set aftertouch treshold to 127. Exit ableton.

Cheers

Great work stamp! Works fine for now.
Cheers.

[futuresproof]

Anyone tried using the mapping mode in 1.2 beta to map the push touchstrip to a macro?

When i try this instead of receiving the midi CC that you set in push4bitwig it maps the note c-1.

Plugins that that have midi learn work fine I just cant map in bitwig

[pdxindy]

I guess the "problem" is that the knobs are also sensitive to speed, which means that the value inc/decs faster if you move the knob faster..

Hi moss thanks for taking the time with this.

Do you think this is an API/Bitwig issue and is it worth reporting? The reason I ask is that the controller functions perfectly within Ableton and the automation is not trying to pull away from you as you write it. At the moment I find push pretty useless for recording automation into bitwig.

I hope this is fixable as I love all the other functionality you have in the script.

It is not just a speed issue.

When I turn one of the macro knobs back and forth repeatedly, the value for the knob keeps increasing. I tried increasing slowly and decreasing quickly and the knob value still kept incrementing. Approx 9 back and forth twists and a knob that started at 0 is now at about 50% when it should be at 0

[moss]

Anyone tried using the mapping mode in 1.2 beta to map the push touchstrip to a macro?

When i try this instead of receiving the midi CC that you set in push4bitwig it maps the note c-1.

Plugins that that have midi learn work fine I just cant map in bitwig

Try if it works when you select Push as the only midi input and not All.

[EpikureeR]

Hey there, just wondering,
is it possible to have bitwig scroll down when you scroll down with the controller in session view?
I have really scene intensive projects and would love the focus to switch automatically.

EpikureeR

[codec17]

nevermind...

[sl1914]

I downloaded the latest script for Push today.
When I try to use it with 1.2 beta 10 Push locks up quickly, usually I can play notes less than 30 seconds and then it freezes.
I have to restart Push and Bitwig to make the controller work again for a short moment.

[pdxindy]

I downloaded the latest script for Push today.
When I try to use it with 1.2 beta 10 Push locks up quickly, usually I can play notes less than 30 seconds and then it freezes.
I have to restart Push and Bitwig to make the controller work again for a short moment.

Do you have the latest firmware from Ableton?

[pdxindy]

I purchased Bitwig recently and am exploring the 1.2 beta and using my Push (using latest github script).

In Ableton, if I put a vst synth in an Instrument Rack and map parameters to the rack macros, the 8 Push knobs automatically work and the 8 macros are immediately available to tweak while playing.

I've not been able to figure out how to do a similar setup in Bitwig. Is this possible?

There's no need to wrap it in an Instrument Rack (but you can). The VST already has 8 Macros. You can select the Macros by pressing the Device button than select "Fixed" and then Macro. .

In Bitwig it is better to map/arrange the controls in Parameter Pages. If you are using 1.2 Beta, right click on the plugin and select "Edit panel mapping".

Thanks for your help!

[sl1914]

Do you have the latest firmware from Ableton?

It should be the latest.
I never had these freeze problems before beta10.
And it doesn't freeze in Live 9.2.