If you right click on your device and then choose lock to control surface, that does the trick... I use it with mine!

Cheers D

@S4 Actually that doesn't work I tried it, at least in the larger full on hub which has other gui elements. Also that's a bad workaround as I wish for the device not to disable other APC40 Features when it's disengaged / off. Much like the CS Step patch, when the device is engaged a section of the controller should be taken over and it's functionality in Live turned off, then returned when the device is disengaged.

I put the full patch in this upload so the ultimate effect of the Blue Hand can be seen. If the Blue Hand locks to this device it even messes it up itself. One knob will turn other knobs etc. They need to be stored and automated so i can't hide the gui from Live.

I really just want to make it look like an APC40 or 20 parameter/button has been MIDI mapped and have it behave like that, totally disengaged from the control surface features.

I don't expect anyone to dig through this huge patch, but I'm sure someone has dealt with this and am including for reference.

thx all

I can;t look as i'm at home but have you ordered your live.objects that are automated and stored starting at 1 (with no 0's) that should sort out the knobs turning other knobs problem.....

Have you looked at max4live.info at the wiki for disabling the APC40's functionality....

Cheers D

Have you looked at max4live.info at the wiki for disabling the APC40's functionality....

this I have not done I'll take a look thx.

As far as the ordering, no I haven't done that but You'll see it's not something I want to do... 4 of the knobs are just display of the LFOs and I don't want them mapped to anything but they need to visualize