I meant to include that image with my previous post.
Thanks, will try and report 
MELD: it works on push standalone but I can’t assign parameters to the Matrix. Am I doing anything wrong or is it just not working. I remember trying it when in controller mode and it worked as expected
3 Likes
Known issue. Same thing with Roar. Will be fixed soon.
3 Likes
With MPE you can though, am I wrong?
Mapping velocity on release should get you there.
Or have I missed a point?
Only for parameters that are « MPE enabled » in the instrument design itself. It depends on the developer’s will in fact. Theoretically any parameter could be targeted « per note » but in reality only a few parameters are concerned usually.
Oh really? I still have to use the MPE control utility, but why can’t you configure your instrument envelope release to be targeted by this?
Really depends on the instrument. In Wavetable for instance you can (almost everything is MPE enabled) but in Drift, you can’t (fixed, very limited set of parameters that can be a target).
The MPE control midi fx is just a utility that allows to refine the curves of the incoming MPE data.
2 Likes
Oh. OK. These limitations make little sense. As everything can be targeted as a macro, I can’t see why MPE can’t be redirected to any macro 
2 Likes
Thank! It is beta, after all
Sorry if this has been discussed ad nauseam, but it’s a looong thread, and I haven’t really seen any deep comparisons on youtube…Is there anything the Octatrack can do that the Push 3 can’t? I’m thinking the performance/slider is pretty unreplacable. And I love the form factor of the Octa (size, weight, ergonomics and placement of components) and if a mk3 came, I would go to Sweden and stand in line for a week to get my hands on one.
But…the effects are really starting to show their age. The sampling rate, memory etc, likewise. The Push can seemingly sample, slice, mangle and parameter lock similarly, and has better effects, far more forward compatibility/flexibility in addition to synths, max for live etc. Not wanting to start a war here, just genuinely interested.
1 Like
But it does totally make sense. Macros can target anything but they are global and not per voice.
To make a parameter MPEable, you need to track each voice with its MPE data and process each instance accordingly.
1 Like
Yeah, that’s kind of where I’m at. I have the Push 3, but it still feels kind of quirky to me. But I’m thinking I just need to invest the time, and try to not get distracted by the bling, bells and whistles…
I’m still stumped on how to get MIDI out. My Push’s TRS MIDI’s are connected to my mioXM MIDI hub and double-checked. I create a MIDI track and add an External Device to it. Under the device’s “MIDI To” I select “Ableton Push 3 User Port” . In Settings>MIDI, I set both Input and Output to Ableton Push 3 User Port. When I tap a pad, the green arrow at the upper right of the Settings page representing MIDI output responds, but no activity registers on my mioXM. I mess with channel selection, but no dice.
I have also tried MIDI To = “ToPush”, but then the green arrow doesn’t respond. I might have thought External Port makes more sense, but it’s not an option under “MIDI To.” I tried it anyway, but the behavior’s the same. FWIW, the string “External Port” doesn’t exist in the Push 3 manual. What am I missing?
Anyway I want to thank you for this discussion because it gave me an interesting idea with m4l that will probably keep me busy for a while….
1 Like
Thanks for the heads up! I was jamming on an idea in the beta 12 last night and went to save and noticed they have disabled saving. Keep that in mind when using SA beta 12. No saving!
Edit: you can save
But the macro could accept MPE. As any MIDI parameter.
Do you have the correct polarity midi cables/adapters?
1 Like
That sounds like an activation/licensing issue, not a limitation built into the beta.
1 Like