Ableton Push support is here

[Bobby L'Avenir]

Hi Moss, have you had a chance to look at my post above? I'm still getting the same bugs with the latest version so I'm still using the older version.

Sorry, but I can not reproduce the problems you reported.

Also wanted to ask if there's a way to press the master button and have the device window pop up along with the master track being selected, I've tried shift and master but that's not it, am i missing something?
Cheers

What do you mean by "device window"? A VST device you have in the master channel? If yes, I have no control over that behaviour from the script. Opening and closing the VST window should work via the device mode.

That's a shame because it really goes crazy on my system

With my other question i was hoping there's one button (without menu diving) I could press to show the device window (alternative to pressing "D" on the keyboard) but on push? Pressing Master selects the master track but i want to select it and open the window too so i can see the plugs loaded. Does that make sense?

Cheers

[Bobby L'Avenir]

Hi Moss, have you had a chance to look at my post above? I'm still getting the same bugs with the latest version so I'm still using the older version.

Sorry, but I can not reproduce the problems you reported.

Also wanted to ask if there's a way to press the master button and have the device window pop up along with the master track being selected, I've tried shift and master but that's not it, am i missing something?
Cheers

What do you mean by "device window"? A VST device you have in the master channel? If yes, I have no control over that behaviour from the script. Opening and closing the VST window should work via the device mode.

Could you not even reproduce the octave errors i mentioned where they don't match the octaves in bitwig?

[moss]

Could you not even reproduce the octave errors i mentioned where they don't match the octaves in bitwig?

Sorry, no. You are currently the only one who reported that.

[Bobby L'Avenir]

Could you not even reproduce the octave errors i mentioned where they don't match the octaves in bitwig?

Sorry, no. You are currently the only one who reported that.

That's very strange, so let me just be clear because i've tested it again. When you click the octave button on push in drum mode the octave scale in push reads C1 to whatever? and plays that same octave in the piano roll, C1 to whatever?

I don't even have C1 in my push, it goes from octaves C-2 to Eb-1, E-1 to G0, Ab0 to B1, (then it skips to) C2 to Eb3? So you don't have that your end Moss?

[Uplay]

Hi Moss,

When pressing Clip button, there is "Accent" parameter on the right in the display. It does not increase more than 0%, but i can decrease only to minus side. I can increase the value in the Bitwig GUI on the same clip. Can you fix it if you can replicate?

[moss]

Hi Moss,

When pressing Clip button, there is "Accent" parameter on the right in the display. It does not increase more than 0%, but i can decrease only to minus side. I can increase the value in the Bitwig GUI on the same clip. Can you fix it if you can replicate?

It's already fixed in the version on GitHub.

[moss]

Could you not even reproduce the octave errors i mentioned where they don't match the octaves in bitwig?

Sorry, no. You are currently the only one who reported that.

That's very strange, so let me just be clear because i've tested it again. When you click the octave button on push in drum mode the octave scale in push reads C1 to whatever? and plays that same octave in the piano roll, C1 to whatever?

I don't even have C1 in my push, it goes from octaves C-2 to Eb-1, E-1 to G0, Ab0 to B1, (then it skips to) C2 to Eb3? So you don't have that your end Moss?

Now I see it too, strange that I did not notice before. But it is only the display who was offset by 1 octave, right? The drum notes work as expected?
I fixed the display of the drum note and also the sequencer mode on GitHub, please test. I hope that I did not break anything else.

[Uplay]

Hi Moss,

When pressing Clip button, there is "Accent" parameter on the right in the display. It does not increase more than 0%, but i can decrease only to minus side. I can increase the value in the Bitwig GUI on the same clip. Can you fix it if you can replicate?

It's already fixed in the version on GitHub.

Issue is still in version 5.01. Do you mean the fix is in 5.02?

[moss]

Hi Moss,

When pressing Clip button, there is "Accent" parameter on the right in the display. It does not increase more than 0%, but i can decrease only to minus side. I can increase the value in the Bitwig GUI on the same clip. Can you fix it if you can replicate?

It's already fixed in the version on GitHub.

Issue is still in version 5.01. Do you mean the fix is in 5.02?

Yes, get the Beta version from: https://github.com/git-moss/Push4Bitwig (Download the ZIP on the right)

[pboy]

Hi,

Pushing the Device button works fine when you line up all kinds of devices right on the track. I also get access from my Push to devices stored inside a Chain Container, by using the Push's Device button

But if storing devices into an Instrument layer Container Device the Push's Device button doesn't seem to allow access to the eight Macro knobs of the Container.

Action:
Pushing the Device button and then the upper (half sized) pad named "Macros" in the display.

Result:
Nothing happens. The logically expected functionality would be to see the display lit up with the names of the Container's Macro knobs, so you can control them from the Push's rotary encoders.

Is this "a user error", a bug or simply not part of Ableton's API? (for Push #1)

[Uplay]

Hi Moss,

When pressing Clip button, there is "Accent" parameter on the right in the display. It does not increase more than 0%, but i can decrease only to minus side. I can increase the value in the Bitwig GUI on the same clip. Can you fix it if you can replicate?

It's already fixed in the version on GitHub.

Issue is still in version 5.01. Do you mean the fix is in 5.02?

Yes, get the Beta version from: https://github.com/git-moss/Push4Bitwig (Download the ZIP on the right)

Hi Moss,

Fix confirmed. Thanks so much!
Next wish is the note nudge function in the drum sequencer like I said before... do you know ETA when Bitwig will implement the API? This is really required for making groovy pattern!

[Bobby L'Avenir]

Could you not even reproduce the octave errors i mentioned where they don't match the octaves in bitwig?

Sorry, no. You are currently the only one who reported that.

That's very strange, so let me just be clear because i've tested it again. When you click the octave button on push in drum mode the octave scale in push reads C1 to whatever? and plays that same octave in the piano roll, C1 to whatever?

I don't even have C1 in my push, it goes from octaves C-2 to Eb-1, E-1 to G0, Ab0 to B1, (then it skips to) C2 to Eb3? So you don't have that your end Moss?

Now I see it too, strange that I did not notice before. But it is only the display who was offset by 1 octave, right? The drum notes work as expected?
I fixed the display of the drum note and also the sequencer mode on GitHub, please test. I hope that I did not break anything else.

Cheers Moss, i can see thats fixed now, however i still have to use the old version as i'm still getting no use out of the arrow keys to scroll tracks. Scrolling groups is even worse, somtimes 3 or 4 presses are needed to move to the next group track ?

[pboy]

Here's another quirk in the Push4Bitwig that I haven't seen discussed somewhere else:

When you have an Arpeggiator as the first Device on a track and go in there by the Push's Devices button it works fine to adjust most of the Arpeggiator's parameters. The problem arises if you use the rotary encoder to bring down the number of patterns and then want to bring them up again. It is not possible! The encoder can not increase the number of steps.

Example:
1. Press Push's Device button
2. Press Push's "half size button" corresponding to the Arpeggiator Device.
Now you're in and the top row rotary knobs has taken on the Arp parameters.
3. Turn the knob corresponding to "Steps" leftwards.
The number of steps are now increasing.
4. Now turn the knob the other way, rightwards.

Result: The number of steps do not increase accordingly. The parameter value is stuck at the lowest value.


EDIT:
Guys, I just found that increasing the Arp Steps is not totally blocked, just terribly flakey. If pounding like crazy on the right-turn-knob it is possible to get the value to jump up to a randomly higher value.

[moss]

Hi,

Pushing the Device button works fine when you line up all kinds of devices right on the track. I also get access from my Push to devices stored inside a Chain Container, by using the Push's Device button

But if storing devices into an Instrument layer Container Device the Push's Device button doesn't seem to allow access to the eight Macro knobs of the Container.

Action:
Pushing the Device button and then the upper (half sized) pad named "Macros" in the display.

Result:
Nothing happens. The logically expected functionality would be to see the display lit up with the names of the Container's Macro knobs, so you can control them from the Push's rotary encoders.

Is this "a user error", a bug or simply not part of Ableton's API? (for Push #1)

Works fine here. Are you sure you have assigned a Macro? If you did not assign anything you will see nothing.

Uh, also make sure you used the correct button: Macros is in Fixed->Macro not the "Macros" button which shows/hides the macros on the computer screen.

[pboy]

Thanks, I'll check this ASAP.