Ableton Forum

I use both, but I think I'm left-dominant on it. Left hand plays melodies, right hand harmonizes above that.

I have a fix, but it requires Max For Live.

Hey, question... Is it possible to use the colors defined in a user's skin? (without knowing what those are) e.g., can we either send a message to activate something like "Instrument.NoteBase", or if we have to set explicit RGB values, could we maybe query against SkinDefault.py to find ou...

Your kill-switch. May it soon be unnecessary (once Ableton/Akai fixes the problem on their end) http://sadfactory.com/assets/downloads/max4live/Push_EmergencyRelease.zip It's an audio effect, so you can place it on any track. I'm not sure if it's set to automatically activate when you select the tra...

Apologies; it looks like flocked already covered the "release on disable" scenario. That works fine as-is.

Building a quick "emergency release" kill-switch device now...

I think we are wasting time to find a tricky solution. Only ableton/cycling74's developpers can help us. :cry: @greaterthanzero unfortunately it was no applicable for push_grid For the moment, manually disconnecting before you delete a device is at least a usable workaround. And we can expand on th...

I read the first posts and fixed it, until I saw, that greaterthanzero already fixed it. Thanks :) I will include it in the next pdk (push development kit) update. @yop44: Whats wrong with push_grid? Sorry, I thought greaterthanzero's post solved the grab/release control problem. If we're thinking ...

Sounds about right. With the one additional note that some retailers opened pre-orders much earlier. (I paid for mine though Guitar Center back in January)

Also of note: The touchstrip code in there* is all kinds of wacky. I jumped through a lot of hoops to provide an obvious feature that's been missing, and then didn't end up using it. Still, give that a look-see. We should talk about whether there's a more straightforward solution... *("there&qu...

Here's some progress on a more push-oriented version of polygome: http://sadfactory.com/assets/downloads/max4live/polygome64_push.zip EDIT: Here is a new version made compatible with the latest dev kit. Discard the previous one. http://sadfactory.com/assets/downloads/max4live/polygome64_push_v2.zip ...

Hacky, but solved: <pre><code> ----------begin_max5_patcher---------- 3817.3oc6cs0iiZjE94t+UTxJJ6CoGGpq.q1nU6EocmG1MqztJujDYgsocSF ZvBvSO8Dk+6acArALPUX61cwjdlQcO.FbUemq0oNmC+5s2LaY5mBymA9ifeD byM+5s2bi7ThSbS4w2L6wfOsJNHW9wlkD9T5xeY1cpKUD9oB4o2B1tK+gEEo 6V8PdQVz1pOQxtGiRhCKj2Mp7j2mlTjG84Pw4fNycJOc5tB...

Okay... triggering [live.observer] in the far-left column causes Push to relinquish control of the touch strip. This is obviously an issue with the python rather than flocked's code, but maybe we can work around it... I can rig it up to not trigger until we've activated [p push_touchstrip], but I ha...

More than that, though.. Paste [p push_touchstrip] into a new device without any other objects. The mere existence of this device on a track will kill your pitch bend. I'm poking around in there, and can confirm that grab_control is not called arbitrarily on launch. If no signal passes into the righ...

I'm having a problem with the touchstrip grabbing control without permission and not returning it properly. Or something like that. Simple example... Put an instrument on a track. Confirm that pitch bend works. Go to the next MIDI track and add any device that includes [p push_touchstrip]. It doesn'...