dcumpian

Bristol_Jonesey
No I don't think it will.
 
Envelopes always assume priority over fader positions, at least that's how I'm seeing it.

Well, that's kind of a bummer then...
 
Dan

Indeed but it makes sense considering that's what happens at the default values anyway.
 

RehabRob

sausy1981
Hi guys, a little annoyance of mine is when I'm automating I can never remember where the fader was before I started automating. I always try to remember the number but I forget as soon as I start moving the fader as I'm concentrating on the automation. I do my automation with my mouse and I was wondering if I can set something up before I start automating so when I release the button of my mouse the fader returns to where it was before I started the automation. Thanks Guys,
Andrew

 
am I misreading or isn't this what "touch" mode in automation is about???
 
https://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=Automation.04.html
 
Touch
Touch mode overwrites any existing automation data for the currently armed parameter only when the parameter is moved with the mouse or a MIDI controller. Automation writing stops when the parameter is released, and the parameter returns to any previously automated position. This mode is useful if you want to update a previous write pass, appending new automation data only where desired. When using a touch-sensitive MIDI controller, new automation data will only overwrite existing automation data when you physically touch a control.
 

I think sausy just wants to know the original value before the envelope was written for reference but that is a good point to know if it somehow fits into what's being attempted.
 
Snapshot automation might be another potentially useful tool depending on the application.

Maybe...... if you let your actual project start at measure1 and have empty clip(s) with the desired fader positions (snapshot) on measure0 then rewind to the beginning will recall those settings....then start automation recording from measure1.
Haven't tried that one yet though....

Hi guys, Thanks for all the replies, thats why this forum is great.. I do always have a pen and paper in front of me when mixing but I was hoping I wouldn't have to look away from the screen just to remember the number of the original fader position. The snap to current would kinda work as when your finishing the automation move just do a quick double click and that might do the trick. But the touch control is something I will look into, sounds like that might be what I was looking for. It's not really a big issue, just something that would speed up workflow a bit for me.
Thanks for the help guys, gonna try and see if snap to default works and I'll look up touch control.
Cheers,
Andrew

Pretty sure James had it nailed when he said "the first node on the automation envelope will tell you where you started"
 
Before you even start moving faders in Write mode, the fader has a definite start position. This value will be written as a node as soon as the transport starts, and the fader will return there when you rewind to where automation starts.

Yeah, I rely on the start and end points for reference. If there are no appropriate reference nodes in the area being automated I add them. Sometimes I might even make notes about things I need to recall either in the text areas provided by SONAR or a method that worked before SONAR, paper and pen. There may be a more sophisticated way but I have not bothered to research the subject.

Yeah I might just use a reference node at the end of where I'm automating, Put it in before I start the pass and hopefully let go of the mouse before I reach it. The snap to current does kinda work, I can set the current position as the snap point and just as I finish the pass a quick double click will bring the fader back the touch mode as far as I can discern is for midi only so not applicable in my situation.
Thanks guys,

sausy1981
 Put it in before I start the pass and hopefully let go of the mouse before I reach it.

Define a loop on the timeline and have it end just before the reference node.

Cool, seems like there's a couple of ways to get what I want done, so I'll just use the quickest when I try them out.