Ableton Push support is here

[svervs]

In Beta7 the "Device on" parameter shows up on the Macros page. Is this known? A betabug?

I guess you mean the Direct mode? Bitwig told me it is intentional but I do not like it either.

That's done intentionally?
Well, I maybe wouldn't mind a new order, but this shifts Macro8 on a new page ... That's a total desaster.
I really hope they listen to you ... Will write them about this as well.

[futuresproof]

Hi guys,

Just purchased bitwig last week and im really enjoying using it with the push script. Excellent work and a big thank you to both bitwig and all scripting guys.

Unfortunatly Im having some issues with using my virusti and its plugin when using bitwig and push. Basically when you press different pads in note mode this is changing the mod matrix destinations on the synth and wrecking the patch. I think this is probably going to be sysex data thats causing the issue and was wondering if there is a way to filter this by editing the script. Im pretty new to programming (did a basic python course recently) but intent to learn a bit of javascript so dont mind playing around if someone could point me in the right direction.

Cheers

Chris

[futuresproof]

Another thing I've noticed:

When trying to fast(ish) modulations but hand using Push's encoders it seems that even if I restrict the modulation to a range of say 7 o'clock to 12 o'clock, after several repetitions the overall value moves upwards. If i was doing a filter sweep starting at a low cut off freq for example, the freq with get higher that when I started even when the knob is in the low position.

The expected behaviour would be if you moduled in the same range the results would sound the same but it doesnt.

I initially thought this be something to do with Push having encoders and not pots but then I tried the same thing in ableton, the results were more predictable like pots and therefore more usable for performance controls. Anyone have this issue? Is this a bug?

While encountering this problem (and trying to think of work around) I thought it would be nice to have an option in the script to control the "last edited parameter" with the touchstrip that way you could edit with the touch encoders and quickly be able to use the touchstrip for modulation/automation. Is this possible with the current API?

Cheers

Chris.

[moss]

Hi guys,

Just purchased bitwig last week and im really enjoying using it with the push script. Excellent work and a big thank you to both bitwig and all scripting guys.

Unfortunatly Im having some issues with using my virusti and its plugin when using bitwig and push. Basically when you press different pads in note mode this is changing the mod matrix destinations on the synth and wrecking the patch. I think this is probably going to be sysex data thats causing the issue and was wondering if there is a way to filter this by editing the script. Im pretty new to programming (did a basic python course recently) but intent to learn a bit of javascript so dont mind playing around if someone could point me in the right direction.

Cheers

Chris

I do not have a Virus so I cannot check. But the P4B script does not use Sysex. Maybe you should address this problem directly to Bitwig (support@bitwig.com).

[moss]

When trying to fast(ish) modulations but hand using Push's encoders it seems that even if I restrict the modulation to a range of say 7 o'clock to 12 o'clock, after several repetitions the overall value moves upwards. If i was doing a filter sweep starting at a low cut off freq for example, the freq with get higher that when I started even when the knob is in the low position.

I'm not sure if I understand what you wrote: Are you saying that the value "jumps" or you have to move the knob for some time to make it change?
Can you give a step by step example (what plugin, what parameter, etc.).

I thought it would be nice to have an option in the script to control the "last edited parameter" with the touchstrip that way you could edit with the touch encoders and quickly be able to use the touchstrip for modulation/automation. Is this possible with the current API?

Sorry, no. The last touched parameter is not available.

[stamp]

Hi guys,

Just purchased bitwig last week and im really enjoying using it with the push script. Excellent work and a big thank you to both bitwig and all scripting guys.

Unfortunatly Im having some issues with using my virusti and its plugin when using bitwig and push. Basically when you press different pads in note mode this is changing the mod matrix destinations on the synth and wrecking the patch. I think this is probably going to be sysex data thats causing the issue and was wondering if there is a way to filter this by editing the script. Im pretty new to programming (did a basic python course recently) but intent to learn a bit of javascript so dont mind playing around if someone could point me in the right direction.

Cheers

Chris

I do not have a Virus so I cannot check. But the P4B script does not use Sysex. Maybe you should address this problem directly to Bitwig (support@bitwig.com).

Hi guys,
I've reported this behaviour in december last year. Really sad to see it's still there. This is the only reason I'm still on Ableton.
@ Futuresproof are you using the beta?

[futuresproof]

I'm not sure if I understand what you wrote: Are you saying that the value "jumps" or you have to move the knob for some time to make it change?
Can you give a step by step example (what plugin, what parameter, etc.).

Hi Moss,

I'll try and get a video or something done at the weekend to try and explain better.

Cheers

[futuresproof]

@ Futuresproof are you using the beta?

Hi stamp

Yeah I'm on beta 7 and using the push script from github. Do you have the same issue with the Virus and other Midi controllers or keyboards? Think I'm gonna try that next.

@Moss If the issue is not sysex it will probs be Poly pressure/ aftertouch as it seems the issue does not happen if you just tap a pad lightly however if you press down hard the changes are made.
Is there any way I can temp filter out Poly pressure being sent from Push via the script?

I'm just trying to find out what the issue is so I can report it Bitwig and Access.

Cheers guys.

Chris.

[moss]

@Moss If the issue is not sysex it will probs be Poly pressure/ aftertouch as it seems the issue does not happen if you just tap a pad lightly however if you press down hard the changes are made.
Is there any way I can temp filter out Poly pressure being sent from Push via the script?

There's no filter but you can select to convert it to CC values in the settings.

[stamp]

Yeah I'm on beta 7 and using the push script from github. Do you have the same issue with the Virus and other Midi controllers or keyboards? Think I'm gonna try that next.

Hi futuresproof,

I didn't check if it happens with other controllers. Push is my only controller at the moment.
Let me know if converting polypressure to CC helps!
+1 for an option to filter polypressure.

Thanks!

[moss]

+1 for an option to filter polypressure.

I added it to my TODO list.

[stamp]

+1 for an option to filter polypressure.

I added it to my TODO list.

Good news! Thank you Moss!

[futuresproof]

Hi moss,

I created a video to try and demonstrate the issue I have with the encoders, its not great but I hope it helps:

https://drive.google.com/file/d/0BwiDLX ... sp=sharing

Basically I am moving the knob only a small amount and returning to what should be 0 or a value near to 0. If I move the knob 25% of the way I would expect to the macro or controller value to be 25% everytime. What appears to happen instead is that the value does not return to 0 but instead adds the next turn to the previous one resulting in the overall value increasing over time until it reaches 100%. I have done the same thing in ableton in which case a turn of 25% on the knob results in a value of 25% on the control no matter how many times or how fast you are turning the knob. You can return to 0 every time.

I have been playing around since doing the video (doing the same thing but slower) and it seems if you turn the knob clockwise by half a rotation then back again (so your thumb is in its starting position) you do not come back to zero as you would expect.

I also feel that the range or resolution of the encoders may play a part in this as I have to turn the knob several times to cover the full range and find it a bit cumbersome to do automation. Is there any thing I can edit to change the resolution so that range of the knob is more comfortable?

Anyway let me know if this explains it or not or if you have an issue with the video.

@stamp/anyone else, Please can you see if you can replicate this?

Cheers

Chris.

[stamp]

@stamp/anyone else, Please can you see if you can replicate this?

Sorry but I don't have a license.
How about the issue with the Virus?

Cheers

[moss]

Basically I am moving the knob only a small amount and returning to what should be 0 or a value near to 0. If I move the knob 25% of the way I would expect to the macro or controller value to be 25% everytime.

I see now what you mean. 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. From the video I get the impression that you move it fater when you move it to the right than to the left (completely normal).

I also feel that the range or resolution of the encoders may play a part in this as I have to turn the knob several times to cover the full range and find it a bit cumbersome to do automation. Is there any thing I can edit to change the resolution so that range of the knob is more comfortable?

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