Ableton Push support is here

[TeotiGraphix]

Funny enough, I have been using Ableton lately for a couple things and the Push. There is something funky happening because even in Ableton the lights when playing notes mess up.

I really don't know if there is any correlation, just thought I would mention it.

Mike

I have not noticed any problems with the lights while running Ableton, though I have been using the Beta version. Not sure if there have been any firmware updates to Push that have contributed to the problem.

Yesterday, I set up a Linux box and ran the Push with the 7.22 P4B script, also without any light problems.

Its looking OS specific, but could also be some other wierd conflict going on. Maybe Microsoft are slowly bugging my system to force me to return to Win 10 </tinfoil-hat>.

Anyway I'll continue using one of the dusty old scripts that work.

I haven't tried the latest script, been doing other things but I will try today. With Ableton it was intermittent, need to actually see if/when it does it again, maybe I was hallucinating and the pad lights were just flashing.

Windows 7, Microsoft will have to tear it out of my hands. My dev computer is staying Windows 7 until I feel like I want something that has bugs and crashes, unlike Windows 7 that gives me no problems and I have massive things installed.

Mike

[ceasless]

So I'm feeling a bit dense here, I didn't see it on the the FAQ and I didn't see it in the videos explaining the new navigation in Push 2: how do I access custom parameter pages? I am able to see the 'Common' mappings, but can't seem to be able to figure out how to switch to other parameter pages.

Is this what belongs in the 'Parameters' section, which is NYI due to missing API as moss mentioned in his Push 2 navigation video? I never really bothered with this on my Push 1 but wanted to turn over a new leaf with the new hardware. Yet success remains elusive..

[Lukree]

Have been using Live again after getting Push 2 and decided to give Bitwig a go for a change. It looks and works wonderfully - until it doesn't... There is something weird happening, when I play notes on a track it suddenly jumps to another track. And this keeps repeating on other tracks as well. Anyone else has any similar hiccups? My setup is pretty complex with hardware synths, elektron overbridge etc so I haven't managed to isolate the problem yet.

[moss]

So I'm feeling a bit dense here, I didn't see it on the the FAQ and I didn't see it in the videos explaining the new navigation in Push 2: how do I access custom parameter pages? I am able to see the 'Common' mappings, but can't seem to be able to figure out how to switch to other parameter pages.

Is this what belongs in the 'Parameters' section, which is NYI due to missing API as moss mentioned in his Push 2 navigation video? I never really bothered with this on my Push 1 but wanted to turn over a new leaf with the new hardware. Yet success remains elusive..

On the Push 1 you pressed Device twice. With the Push 2 I moved the changing of the parameter categories to the "menu buttons" over the display. These were the 2nd row buttons on Push 1. This functionality is now also available on the Push 1 (2nd row buttons), so you do not have to open the Device display first.

[ceasless]

So I'm feeling a bit dense here, I didn't see it on the the FAQ and I didn't see it in the videos explaining the new navigation in Push 2: how do I access custom parameter pages? I am able to see the 'Common' mappings, but can't seem to be able to figure out how to switch to other parameter pages.

Is this what belongs in the 'Parameters' section, which is NYI due to missing API as moss mentioned in his Push 2 navigation video? I never really bothered with this on my Push 1 but wanted to turn over a new leaf with the new hardware. Yet success remains elusive..

On the Push 1 you pressed Device twice. With the Push 2 I moved the changing of the parameter categories to the "menu buttons" over the display. These were the 2nd row buttons on Push 1. This functionality is now also available on the Push 1 (2nd row buttons), so you do not have to open the Device display first.

Hi moss,

Unfortunately I'm still stuck. The top buttons give me 'Fixed' and 'Direct' ('Parameters' doesn't engage, and you've mentioned before the API is missing). I do not see any way to page through the different Fixed sections, nor do I see any way to page through the 'Direct' parameters. For the custom Parameter Pages I have added in Bitwig's 'Device Panel Mappings', I don't see anything.

Sorry for being dense.

EDIT: In other words, I am able to see the 'Common Controls' under Fixed and the first page of params under 'Direct'. I'm missing how to move to other pages (like 'Envelope Controls' under Fixed), and especially whether or not my custom Parameter Pages will be accessible.

[moss]

EDIT: In other words, I am able to see the 'Common Controls' under Fixed and the first page of params under 'Direct'. I'm missing how to move to other pages (like 'Envelope Controls' under Fixed), and especially whether or not my custom Parameter Pages will be accessible.

You need to press the Page Left button.

[ceasless]

EDIT: In other words, I am able to see the 'Common Controls' under Fixed and the first page of params under 'Direct'. I'm missing how to move to other pages (like 'Envelope Controls' under Fixed), and especially whether or not my custom Parameter Pages will be accessible.

You need to press the Page Left button.

Amazing! This gives me easy access to the 'Fixed' sections. This is going to be a game changer.

I'm still feeling a bit stupid though. Are the custom pages supposed to show up as "first class citizens"? Or under the 'User' section? Nothing shows when I press 'User' on a device with almost 20 parameter pages associated with it, though.

Also feeling curious: What functionality will eventually live behind the 'Parameters' heading in the main device view?

[ceasless]

EDIT: In other words, I am able to see the 'Common Controls' under Fixed and the first page of params under 'Direct'. I'm missing how to move to other pages (like 'Envelope Controls' under Fixed), and especially whether or not my custom Parameter Pages will be accessible.

You need to press the Page Left button.

Amazing! This gives me easy access to the 'Fixed' sections. This is going to be a game changer.

I'm still feeling a bit stupid though. Are the custom pages supposed to show up as "first class citizens"? Or under the 'User' section? Nothing shows when I press 'User' on a device with almost 20 parameter pages associated with it, though.

Also feeling curious: What functionality will eventually live behind the 'Parameters' heading in the main device view?

Ok, got it. Looks like I select 'User' and then select 'Device'! Then I have access to all the parameter pages. The font is too large to really see the page names nor the parameter names. One of the benefits of the custom parameter mappings is getting to use something more sensible than the crammed VST name, so that's a small improvement that would be really useful, at least to me.

Actually, looking more closely I'm not sure that the custom names I've added to the parameter pages are being used at all. The pages reflect the right params though.

[ceasless]

Alright, back with what I hope will be the last question for a while. One of my main motivations for getting the Push 2 was to have Polyphonic Aftertouch with decent pads. I felt like I was trying to stab my fingers through the Push 1 pads. The Push 2 pads are much nicer, but... 'Pressure' modulation does not seem to do anything anymore. I've dialed it into 'Pitch' at extreme settings on the PolySynth and am not observing any change in pitch nor any visual modulation indicators. The controller preferences for Push 2 are set to send Polyphonic Aftertouch as Polyphonic Aftertouch. Am I missing something here? I searched the Github wiki in hopes of avoiding popping in with more questions, but didn't find any reference to what I'm seeing.

[ceasless]

Alright, back with what I hope will be the last question for a while. One of my main motivations for getting the Push 2 was to have Polyphonic Aftertouch with decent pads. I felt like I was trying to stab my fingers through the Push 1 pads. The Push 2 pads are much nicer, but... 'Pressure' modulation does not seem to do anything anymore. I've dialed it into 'Pitch' at extreme settings on the PolySynth and am not observing any change in pitch nor any visual modulation indicators. The controller preferences for Push 2 are set to send Polyphonic Aftertouch as Polyphonic Aftertouch. Am I missing something here? I searched the Github wiki in hopes of avoiding popping in with more questions, but didn't find any reference to what I'm seeing.

The mystery deepens... Using first Usine Hollyhock and then again in MIDI Monitor on OS X, I only see messages for Note On/Off. I've confirmed with my MPC that at least key aftertouch should be displayed in the monitor. Frankly I would expect all MIDI messages to appear here, so I wonder if it's something else...

Am I crazy? Is pressure/polyphonic aftertouch working for other Push 2 owners?

[moss]

Alright, back with what I hope will be the last question for a while. One of my main motivations for getting the Push 2 was to have Polyphonic Aftertouch with decent pads. I felt like I was trying to stab my fingers through the Push 1 pads. The Push 2 pads are much nicer, but... 'Pressure' modulation does not seem to do anything anymore. I've dialed it into 'Pitch' at extreme settings on the PolySynth and am not observing any change in pitch nor any visual modulation indicators. The controller preferences for Push 2 are set to send Polyphonic Aftertouch as Polyphonic Aftertouch. Am I missing something here? I searched the Github wiki in hopes of avoiding popping in with more questions, but didn't find any reference to what I'm seeing.

The mystery deepens... Using first Usine Hollyhock and then again in MIDI Monitor on OS X, I only see messages for Note On/Off. I've confirmed with my MPC that at least key aftertouch should be displayed in the monitor. Frankly I would expect all MIDI messages to appear here, so I wonder if it's something else...

Am I crazy? Is pressure/polyphonic aftertouch working for other Push 2 owners?

I tested it too now and it seems that Push 2 does only send Channel Aftertouch?! I also checked the Ableton manual and tried it with Live but there does not seem to be an option anywhere where you can switch to poly aftertouch. Unless I am overlooking something I will need to change this to plain Channel Aftertouch support for the Push 2.

[ceasless]

I tested it too now and it seems that Push 2 does only send Channel Aftertouch?! I also checked the Ableton manual and tried it with Live but there does not seem to be an option anywhere where you can switch to poly aftertouch. Unless I am overlooking something I will need to change this to plain Channel Aftertouch support for the Push 2.

On the one hand, it feels good not to be crazy. On the other hand, this dropping of polyphonic aftertouch might just drive me crazy anyway! How could they drop such a feature? Clearly if the pads are able to contribute to channel aftertouch, they each have individual pressure sensors that could (nay, should) be sending individual pressure data.

Do the aftertouch messages show up in your MIDI monitor, moss? I'm not seeing them on my side, and doing aftertouch modulation in a plugin like Massive didn't seem to have any effect when I was using it in Usine. I will try a few other places, but if you are seeing messages and I am not then this thing is getting returned ASAP.

EDIT: Nevermind, it does send channel aftertouch. Verified in Live and then in Usine once I realized that I have to stab the pad with my finger with what I would call significant pressure to get it to trigger. All CA messages. I just assumed that they weren't taking anything away from the previous Push, just adding more sensitive pads.

Maybe they don't want it to work better in Bitwig than Live and they are waiting for a firmware update to coincide with Live 10...

[moss]

EDIT: Nevermind, it does send channel aftertouch. Verified in Live and then in Usine once I realized that I have to stab the pad with my finger with what I would call significant pressure to get it to trigger. All CA messages. I just assumed that they weren't taking anything away from the previous Push, just adding more sensitive pads.

Yes, that's why I simply did not test that.

It is now implemented and you can test it if you get the version on GitHub.

[goatgirl]

I have tried some more commits on github to see when the pad lights became a problem.

Last commit to work:
Dec 6, 2015
Push4Bitwig-6d16f624a3e3ff7e8d3476a9c0094e5e8504184e

First occurence of lag issue:
Dec 29, 2015
Push4Bitwig-4645f069a4e7a038e8deb9cdb91d61ec08d693d6

Updated findings

Lights ok with nothing on the track

Lights response is delayed when you add a device such as polysynth to the track. The more notes that are played, the longer the delay becomes.

[goatgirl]

Also when the delayed response occurs, it appears to be affected by note length as the delay is more noticeable with a series of longer note presses than shorter notes.