Ableton Forum

What is your Push grid showing? the standard note grid? or no led colors.

Make sure your Push is turned on, before adding the m4l device.

"Push control, when" does exactly, what it says. If you select the m4l device or the track, containing the m4l device (depending on your selected option) the custom grid should show.

its Just showing the standard grid. The track is selected.

Bumper

Okay, could you please try out these two m4l devices?
http://florianzand.de/push/m4l_devices/tests.zip

Test 1: What happens with the Push grid, if you activate the toggle?
Test 2: What happens with the Push grid, if you add the m4l device to your track? What is the message box showing?

Thanks!

Hi flocked - thanks for the work on this!

The polygome device works fine on Live 9.0.2, however it doesn't (showing just the normal grid as Dchild describes) in the latest beta (9.0.3 b3)

Here are the results for the tests under 9.0.3b3 (and between brackets the result under 9.0.2)

Test 1: top left pad flashes, maybe red but happening very fast so not 100% sure, then stays lit in dark red. If you deactivate the toggle the top left pad stays dark red (9.0.2: grid disappears to leave a blank grid, reappears when the toggle is deactivated )

Test 2: nothing happens to the grid, Push message box shows under the left knob PshCntrl DvcSlctd (9.0.2: grid disappears as in test 1, message box shows same as in the beta, grid reappears if I turn the knob to PshCntrl Off and disappears again if I switch to track or device select mode)

So it sounds like it's a beta issue...

Thanks !

Good work!

Regarding the closebang issue, try freebang, I had better results with this object in M4L.

Thanks for your help.

Yes, it seems, that 9.0.3 breaks the "call grab_control" message. I contacted Ableton about it.

@Siege: Freebang isn't working either. The both send a bang, but just to late.

hi flocked - when using the push_grid device to grab the pads to generate midi notes when pressed, i seem to be getting a slight bit of latency that is not present when using push in native live mode to play the same instruments. is this just an inherent limitation to using M4L? or is there something I am missing? thanks!

Thanks Flocked for this awesome work!

I have a question. Is there a way to release control before deleting a device. Because one a device using push_grid deleted the is no way ti use pads again.

regards

@yop44, you'll need to add another patch to reclaim control if you delete the original patch without releasing control.

lo.key wrote:@yop44, you'll need to add another patch to reclaim control if you delete the original patch without releasing control.

Thanks, but I'm not sure that's a handy solution...

yop44 wrote:Thanks Flocked for this awesome work!

I have a question. Is there a way to release control before deleting a device. Because one a device using push_grid deleted the is no way ti use pads again.

regards

As is noted on the site and in the readme, this is a bug with Max For Live and closebang.

yop44 wrote:

lo.key wrote:@yop44, you'll need to add another patch to reclaim control if you delete the original patch without releasing control.

Thanks, but I'm not sure that's a handy solution...

agreed. the 'handy' solution is not to delete the patch in the first place, as the docs spell out.

Yes, as stated in the bug list, it is definitely a bug and shouldn't be the default behavior. It would be stupid to require the user all the time to remember deactivating the device before deleting.
Maybe some m4l developers can find a solution. - If you connect closebang with the "release_control" message in a push control object, nothing happens, because the bang never receives/triggers the message. Is there another way/walk around? Maybe some way to slower the deletion?

coleb: Are you sure that you get a lag? Is it only if you have the max editor open (which makes all push objects much slower) or general?

yop44: Currently you need to deactivate the device or the push control in option menu.

flocked wrote:Yes, as stated in the bug list, it is definitely a bug and shouldn't be the default behavior. It would be stupid to require the user all the time to remember deactivating the device before deleting.
Maybe some m4l developers can find a solution. - If you connect closebang with the "release_control" message in a push control object, nothing happens, because the bang never receives/triggers the message. Is there another way/walk around? Maybe some way to slower the deletion?

coleb: Are you sure that you get a lag? Is it only if you have the max editor open (which makes all push objects much slower) or general?

yop44: Currently you need to deactivate the device or the push control in option menu.

have you played around with deferlow ? this deals with message prioritisation and helps quite often.

Deferlow isn't working. Why should it work? It makes sending the "release_control" message slower.
But thanks for your input