turning off patchcord reassign feature
-
LaotzeSunHammer
- Posts: 89
- Joined: Fri Oct 02, 2009 6:59 pm
turning off patchcord reassign feature
I noticed that M4L includes a new feature to where you can hover over an inlet to turn the inlet blue and move the connecting patchcord to another place. I find this more annoying than helpful, how do you turn it off? Can't find anything in the prefs.
-
jackaperkins
- Posts: 8
- Joined: Wed Nov 04, 2009 8:28 pm
Re: turning off patchcord reassign feature
I was wondering this too. It's great when I want it but I find sometimes i grab the wrong cable when a lot are crossing in a small space.
Re: turning off patchcord reassign feature
i actually broke two patchers without noticing with this.
GREAT feature when i want it.
TERRIBLE when i didnt realize i used it.
maybe a modifier key to use it for the clumsy among us?
GREAT feature when i want it.
TERRIBLE when i didnt realize i used it.
maybe a modifier key to use it for the clumsy among us?
-
olivierseb
- Posts: 230
- Joined: Sun Dec 11, 2005 8:52 pm
- Location: FRANCE
- Contact:
Re: turning off patchcord reassign feature
this will be a Max 5.1 featureSurreal wrote:i actually broke two patchers without noticing with this.
GREAT feature when i want it.
TERRIBLE when i didnt realize i used it.
maybe a modifier key to use it for the clumsy among us?
I also had to get used to it, but this is a real time saver, no more need to delete a patch cord then draw a new one.
a tip: click on the cord (on the middle) itself to get the blue dot
olivier

MacBookPro17", mac OS 10.6.2/RME FF400 & FF800
http://www.olivierseb.com
Max for Live training sessions in Paris @
http://www.apaxxdesigns.com/
Max for Live training sessions in Rennes @
http://www.intouchmedia.fr
Re: turning off patchcord reassign feature
i would strongly agree that this should be a optional behavior. i'm actually afraid to do patching in complex patches with this new feature. I've spent a lot of time (albeit, limited to a little over a week of playtime) correcting problems that occurred from the dynamic re-routing--most especially (and dangerously) when i had no idea it had happened until the patch was broken.
jake
jake