• SONAR
  • clicking on lower part of a midi/audio track SHOULDNT mute the rest of the take lanes
2015/01/27 12:27:12
orhanproject
gustabo
I read that they removing the default key bind because so many people were enabling it by accident and not realizing that they had.

Well this is funny...
They removed "o" because people hit "o" by accident while this doesnt brake anything BUT they introduce comping tool and a functionality that is hard coded and no enable/disable options and this brakes stuff by accident, and this is not only when comping mode is active but all the time, I mean clicking on lower part of a midi/audio track SHOULDNT mute the rest of the take lanes, why is this not a problem for anybody?? Nobody uses take lanes or what? I've been complaining about this for a while now. Please make it an option! It shouldnt be that hard... Or? Please respond cake people...

An example for people working in after effects (or photoshop) , imagine you have many precomps, in those precomps you have many layers, now if you click on the lower part of a layer, the rest of the layers in this precomp would mute (not visible) except the one you clicked on, crazy right? Outrageous if you ask me.
There is a solo/mute button for a reason, it shouldnt be contextual clip property like the other tools like clip fade in/fade out etc..

thank you for the headaches with this over the years cakewalk, worst part, there is no option to disable it...
2015/01/27 13:12:33
denverdrummer
gustabo
I read that they removing the default key bind because so many people were enabling it by accident and not realizing that they had.




That would be me. :)
2015/01/27 16:36:49
Beagle
orhanproject
gustabo
I read that they removing the default key bind because so many people were enabling it by accident and not realizing that they had.

Well this is funny...
They removed "o" because people hit "o" by accident while this doesnt brake anything BUT they introduce comping tool and a functionality that is hard coded and no enable/disable options and this brakes stuff by accident, and this is not only when comping mode is active but all the time, I mean clicking on lower part of a midi/audio track SHOULDNT mute the rest of the take lanes, why is this not a problem for anybody?? Nobody uses take lanes or what? I've been complaining about this for a while now. Please make it an option! It shouldnt be that hard... Or? Please respond cake people...

An example for people working in after effects (or photoshop) , imagine you have many precomps, in those precomps you have many layers, now if you click on the lower part of a layer, the rest of the layers in this precomp would mute (not visible) except the one you clicked on, crazy right? Outrageous if you ask me.
There is a solo/mute button for a reason, it shouldnt be contextual clip property like the other tools like clip fade in/fade out etc..

thank you for the headaches with this over the years cakewalk, worst part, there is no option to disable it...

what does that have to do with the issue above?  if you want to rant, do it in your own thread.
besides, cakewalk employees are not necessarily going to see anything in this thread.  for one thing this is a user forum and they don't read all the threads!
 
if you have a legitimate complaint - take it up with cakewalk directly.  ranting about it in another person's thread makes no sense.
 
No longer applies - I split the topic out so that orhanproject can get help with his problem.
2015/01/27 16:53:57
Anderton
orhanproject
BUT they introduce comping tool and a functionality that is hard coded and no enable/disable options and this brakes stuff by accident, and this is not only when comping mode is active but all the time, I mean clicking on lower part of a midi/audio track SHOULDNT mute the rest of the take lanes, why is this not a problem for anybody??

 
Because that's not what happens when I use comping, therefore it's not a problem. But I may not understand exactly what your problem is. When you shift+space bar to start playing a clip, and use the arrow keys to navigate (as you're supposed to do with speed comping), all muting and soloing happens transparently and automatically. It doesn't matter where I click, nothing else gets muted.
 
Maybe you could start a thread about this specific issue that explains it in more detail? 
2015/01/27 17:17:03
Grumbleweed_
I used to the think the O key was a nightmare when I was young and naive. When I grew up and realised how clever it was it made a huge difference to my mixing. It does make sense to have a button light up to show that you are in offset mode but I think I'll do the key binding as I regularly use it.

Grum.
2015/01/28 02:53:53
orhanproject
Beagle
orhanproject
gustabo
I read that they removing the default key bind because so many people were enabling it by accident and not realizing that they had.

Well this is funny...
They removed "o" because people hit "o" by accident while this doesnt brake anything BUT they introduce comping tool and a functionality that is hard coded and no enable/disable options and this brakes stuff by accident, and this is not only when comping mode is active but all the time, I mean clicking on lower part of a midi/audio track SHOULDNT mute the rest of the take lanes, why is this not a problem for anybody?? Nobody uses take lanes or what? I've been complaining about this for a while now. Please make it an option! It shouldnt be that hard... Or? Please respond cake people...

An example for people working in after effects (or photoshop) , imagine you have many precomps, in those precomps you have many layers, now if you click on the lower part of a layer, the rest of the layers in this precomp would mute (not visible) except the one you clicked on, crazy right? Outrageous if you ask me.
There is a solo/mute button for a reason, it shouldnt be contextual clip property like the other tools like clip fade in/fade out etc..

thank you for the headaches with this over the years cakewalk, worst part, there is no option to disable it...

what does that have to do with the issue above?  if you want to rant, do it in your own thread.
besides, cakewalk employees are not necessarily going to see anything in this thread.  for one thing this is a user forum and they don't read all the threads!
 
if you have a legitimate complaint - take it up with cakewalk directly.  ranting about it in another person's thread makes no sense.


I'll make a new thread, sorry for hijacking this thread :)
2015/01/28 03:39:31
orhanproject
Anderton
orhanproject
BUT they introduce comping tool and a functionality that is hard coded and no enable/disable options and this brakes stuff by accident, and this is not only when comping mode is active but all the time, I mean clicking on lower part of a midi/audio track SHOULDNT mute the rest of the take lanes, why is this not a problem for anybody??

 
Because that's not what happens when I use comping, therefore it's not a problem. But I may not understand exactly what your problem is. When you shift+space bar to start playing a clip, and use the arrow keys to navigate (as you're supposed to do with speed comping), all muting and soloing happens transparently and automatically. It doesn't matter where I click, nothing else gets muted.
 
Maybe you could start a thread about this specific issue that explains it in more detail? 


Thanks for answering Craig

I'll make a new thread but for now Im going to reply hou here (sorry for hijacking thread again)

"When you shift+space bar to start playing a clip, and use the arrow keys to navigate (as you're supposed to do with speed comping)"

Yes, when doing this speed comping its all fine, it works as it should BUT my problem is when you don't do speed comping, the "click on lower area of midi/audio clips" behaves the same way as in speed comping, which for me shouldnt be like that... This is my problem because you are still in "sped comping mode" all the time... And can easily mute clips if tou are not super carefull with where hou click while doing arrangements on the song...

Don't know if this made it clearer but I'll try to do a new thread and make a videoclip...
2015/01/28 03:40:47
orhanproject
Sorry for double post (I'm on the phone)
2015/01/28 07:37:39
Beepster
@orhanproject... You can change from comping mode to Sound On Sound and/or use one of the other tools instead of the Smart Tool. Pretty sure the first will stop the auto muting and the second will definitely stop the muting. You can just set whatever dedicated tool works best for whatever it is you are doing then set it to the Toggle Tool keybinding and bouce back and forth between the Smart Tool and whatever you choose. Of course you can also cycle through any of the tools with the F keys at the top of the keyboard.
2015/01/28 09:09:28
orhanproject
Beepster
@orhanproject... You can change from comping mode to Sound On Sound and/or use one of the other tools instead of the Smart Tool. Pretty sure the first will stop the auto muting and the second will definitely stop the muting. You can just set whatever dedicated tool works best for whatever it is you are doing then set it to the Toggle Tool keybinding and bouce back and forth between the Smart Tool and whatever you choose. Of course you can also cycle through any of the tools with the F keys at the top of the keyboard.


Beepster, I tried changing to sound on sound and the other modes, still acts the same, thats what I mean, you cannot change this "lower clip click mute rest take lanes "behavior... Its on all the time...
I know I can change between move/select tools but the this method adds up alot of extra clicks to the workflow. Smart tools works better overall except I get this "lower part midi/audio clip click mutes rest of take lanes" behavior with it... Hmm..
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account