Just trying to save a bit of time. Instead of selecting a disabled transient, right clicking, selecting Disable, moving it, right clicking then disabling it again I would like to...
 
Select disabled transient(s), hit a key binding to enable, move the marker, hit a keybinding to disable it again.
 
Looks like I'm going to be doing this action hundreds if not thousands of times so just getting that extra couple steps out of the way will be enormously helpful.
 
Thanks.

There are quite a few autosnap functions in the track view area of keyboard shortcut dialog. Might need to roll your own bindings though.

Transient Markers.....
 
Pain Staking!!!!
 
 

@scook... Yes, I'm thinking it may come to that. I've got a workflow happening now but I'm going to take a look at the shortcut preferences tomorrow. Now food and rest. Cheers.
 
@markyzno... Very much so. I am in full on wax on/wax off mode right now. I hope this all works as planned. :-/

Also, depending on zooming in and out the markers go all haywire....
 
I had to produce an album recently where the drums were really badly tracked so some drum replacement therapy was the order of the day.....Boy oh boy did I have to focus on getting those transient markers correct....as I say, painstaking.
 
Transient Markers functionality could certainly be improved for later updates/versions of Sonar.

markyzno
Also, depending on zooming in and out the markers go all haywire....
 
I had to produce an album recently where the drums were really badly tracked so some drum replacement therapy was the order of the day.....Boy oh boy did I have to focus on getting those transient markers correct....as I say, painstaking.
 
Transient Markers functionality could certainly be improved for later updates/versions of Sonar.

I found X2a got rid of SOME of the annoying graphical glitches with transients so although they still flicker a bit it is still usable (at least on my system). However I saved a project in the middle of working with the tracks set to transients, shut down and the next day (yesterday) the project was completely unusable.
 
So yes... Cakewalk definitely needs to figure out why the heck this feature is such a wonkfest. That or maybe you just can't walk away from a session involving transients.

Is it possible that you are working on too large a section of the project at a time?

Well it's an approximately 2 and a half minute song and I am treating it as one clip (well one clip for each track). There is also a second version of the song in the same project I intend to raid for comping/replacing bad parts but I hadn't touched that set of clips. This is however one of the shorter songs I'll be doing this to. Like I said all was well until I closed the project, shut down and reopened it. I'll be starting from scratch today. I just need X2 to remain stable long enough to make it through until rendering. I'll be leaving the system on with the program running if I can't make it through an entire project in one session. Otherwise I'll be trying X1. Cheers.

Beepster
 wonkfest