Ableton Forum

This isn't exactly a bug, in that it's working as designed, but functionally it's problematic if you do any custom max for live stuff with Push.

Aftertouch/channel pressure needs to be diverted through the control path. e.g. When I grab the button_matrix, it should divert the channel pressure messages as well. Having them continue to go through while the matrix is doing other things is causing me problems with my max for live stuff.

Can I get a confirmation on this? I can't get it working but I might be missing something.

I think it's a bug. There was a problem with the button_matrix not being grabbed/released properly, which I thought they had fixed, but it sounds like there are still some issues. Don't freak out, your Push is fine. Submit a bug report.

between the beta and the current release version, some of the push controller numbers changed. that's why you're having problems. some of the devices in the kit will need new arguments (e.g. "control_surfaces 0 controls 13" might be "control_surfaces 0 controls 14" now). learn to...

Yeah, we're on the same page, lo.key. Don't know how the hell to use it, though.

I know I'm trying to do things that are beyond my knowledge, but it's fun. I love poking about with this stuff.

Yeah, I tried that like an hour ago. There were bits of the test file I tried that it couldn't do. It's probably a later version of Python.

Gah, it appears to be more complicated. It's not just that I haven't got the syntax right above, but also that I can't insert any modifications in the remote scripts successfully. Like, including just opening the push.py and inserting a single character in one of the comment lines. Any modification ...

I guess the other issue is whether my proposed method would refresh the controller properly (i.e. with a selected device change only, without toggling the track or what have you). I have no idea how to read the script to determine if that's the case, so any advice on that front would be great as well.

I want to modify the push script so that I can toggle a step sequencer on or off for a particular track, whether it's a drum rack or no. One way that occurred to me to do that would be to modify the script not so it queries the track about the existence of a drum rack, but only whether the selected ...

I'm relieved to see this isn't about rocket-propelled grenades.

It's also worth mentioning that at some point the control list changed. So if you're doing any max for live stuff, e.g. the button matrix changed from control 71 to 135.

Right now, we don't seem to be able to delete MIDI CC recordings the same way we can other automation (hold delete and touch the knob). I'd like the same thing (well, wiggle the knob in this case) for outboard MIDI gear. e.g. hold delete and move your filter cutoff knob to erase filter modulation on...

I'd like to have the velocity sensitivity de-coupled from aftertouch sensitivity. They need independent settings, IMO.

personally, i see this as a feature, not a bug :] For those of not viewing it as a feature, it's unfortunate because it means that for all drum racks, you can't play more than the 4x4 grid of notes without scrolling, and for all instrument racks, you can't step sequence. It would be nice to be able...