PUSH - lock to control surface issue
PUSH - lock to control surface issue
Does anyone know of a way to make PUSH utilise the - lock to control surface - option in the same way as the APC40 does?
What I want is to lock PUSH to a particular track or device on the track and for that devices buttons/controls to remain available on PUSH even if I change focus in Ableton (to say - the master track)
The main use for this is for things like -
Switching my main mix between mono and stereo using a utility on the master bus, whilst checking the effect a particular plugin on a different track has on the mix - this requires me to turn a device on and off on 2 tracks at once (i used to control one device with the mouse button and one with the buttons on the APC40). Unless I'm missing something PUSH only allows you to change devices on one track at a time as once you change focus in ableton the focus changes in PUSH too (and vice versa)
Thanks in advance.
What I want is to lock PUSH to a particular track or device on the track and for that devices buttons/controls to remain available on PUSH even if I change focus in Ableton (to say - the master track)
The main use for this is for things like -
Switching my main mix between mono and stereo using a utility on the master bus, whilst checking the effect a particular plugin on a different track has on the mix - this requires me to turn a device on and off on 2 tracks at once (i used to control one device with the mouse button and one with the buttons on the APC40). Unless I'm missing something PUSH only allows you to change devices on one track at a time as once you change focus in ableton the focus changes in PUSH too (and vice versa)
Thanks in advance.
-
- Posts: 362
- Joined: Fri Apr 17, 2009 1:17 am
- Location: Edmonton Alberta
Re: PUSH - lock to control surface issue
9.1.6b2 uses a lock to control surface, but I haven't found a way to do it right from PUSH.
current solution: right click on title bar of device, click 'lock to control surface (PUSH).
Would really like to be able to control this from push.
Or better yet, be able to toggle between pre-set 'locked' devices. so, semi-locked device rotation...
current solution: right click on title bar of device, click 'lock to control surface (PUSH).
Would really like to be able to control this from push.
Or better yet, be able to toggle between pre-set 'locked' devices. so, semi-locked device rotation...
-
- Posts: 1134
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: PUSH - lock to control surface issue
You can disable "follow selection" (or something like that), in your Preferences.
You can also use ClyphX and set up a lock to device function the way you want.
You can also use ClyphX and set up a lock to device function the way you want.
-
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: PUSH - lock to control surface issue
Yes, but this is for clip playback only though.Valiumdupeuple wrote:You can disable "follow selection" (or something like that), in your Preferences.
True, but this....You can also use ClyphX and set up a lock to device function the way you want.
...would be much better.Would really like to be able to control this from push.
Or better yet, be able to toggle between pre-set 'locked' devices. so, semi-locked device rotation...
I like the second sugesstion too.
Not all racks are equally important in a live situation. It would be cool to have a mode where less important ones could be skiped.
-
- Posts: 1134
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: PUSH - lock to control surface issue
Easy to do with Clyphx for M4L...TomViolenz wrote:True, but this....You can also use ClyphX and set up a lock to device function the way you want.
Would really like to be able to control this from push.
Or better yet, be able to toggle between pre-set 'locked' devices. so, semi-locked device rotation...
-
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: PUSH - lock to control surface issue
What is?
And I know my way around clyphx just fine, but I don't think it should be used as a continued excuse for Ableton to be lazy and not implement better solutions to problems that quite obviously exist.
And I know my way around clyphx just fine, but I don't think it should be used as a continued excuse for Ableton to be lazy and not implement better solutions to problems that quite obviously exist.
Re: PUSH - lock to control surface issue
This plus we shouldn't have to rely on PXT Live and PXT General.TomViolenz wrote: And I know my way around clyphx just fine, but I don't think it should be used as a continued excuse for Ableton to be lazy and not implement better solutions to problems that quite obviously exist.
-
- Posts: 1134
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: PUSH - lock to control surface issue
http://www.maxforlive.com/library/device/1940/m4l4cxTomViolenz wrote:What is?
Inside this example device you've got all informations on how to "connect" M4L with ClyphX. Then you'll just need to grab a button or whatever controls on Push (I use the 2nd footswitch input) and use it to trigger to ClyphX action (can't remember its exact name).
But I agree on your point btw.
-
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: PUSH - lock to control surface issue
So this would override the function that is normally triggered from that button?!Valiumdupeuple wrote:http://www.maxforlive.com/library/device/1940/m4l4cxTomViolenz wrote:What is?
Inside this example device you've got all informations on how to "connect" M4L with ClyphX. Then you'll just need to grab a button or whatever controls on Push (I use the 2nd footswitch input) and use it to trigger to ClyphX action (can't remember its exact name).
But I agree on your point btw.
I guess that could be semi usefull with a useless buttons like TapTempo.
But I don't want to have M4L running in the backround for something as fundamental as Lock-to-device.
And for something more eleborate, like the proposed "switch only between certain racks" You'd need quite a few more buttons and would have to make that preselection with clyphx actions in its Usersettings.txt.
That is a pretty horrible workflow.