Trapezoid
Max Output Level: -90 dBFS
- Total Posts : 14
- Joined: 2005/12/25 17:32:13
- Status: offline
Automation Write records inaccurately
I turn on Automation Write, hit play, and play with a parameter. As it's recording, it sounds the way I want it to and seems to be writing the nodes correctly:  Then as soon as I hit stop, the nodes automatically quantize:  The result played back sounds awkward, especially for fast, rhythmic effects. Is there any way to prevent Sonar from deleting all my beautiful, nuanced nodes?
|
Kalle Rantaaho
Max Output Level: -5 dBFS
- Total Posts : 7005
- Joined: 2006/01/09 13:07:59
- Location: Finland
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 05:50:06
(permalink)
And you don't have Input Quantize (or anything similar, if such exists in X-series) on?
SONAR PE 8.5.3, Asus P5B, 2,4 Ghz Dual Core, 4 Gb RAM, GF 7300, EMU 1820, Bluetube Pre - Kontakt4, Ozone, Addictive Drums, PSP Mixpack2, Melda Creative Pack, Melodyne Plugin etc. The benefit of being a middle aged amateur is the low number of years of frustration ahead of you.
|
gswitz
Max Output Level: -18.5 dBFS
- Total Posts : 5694
- Joined: 2007/06/16 07:17:14
- Location: Richmond Virginia USA
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 10:43:35
(permalink)
You can control the precision of this quantization. I know there's a setting somewhere but I can't remember where. Preferences somewhere... Scook, do you know where it is?
StudioCat > I use Windows 10 and Sonar Platinum. I have a touch screen. I make some videos. This one shows how to do a physical loopback on the RME UCX to get many more equalizer nodes.
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 11:43:14
(permalink)
There is a variable in AUD.ini which automatically thins recorded automation called AutomationDecimationMSec. The default is 50 milliseconds.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 11:51:51
(permalink)
I tried changing those values from 2 to 1000 ms in X2 (what's on one of my laptops), and didn't see any difference in the on-screen graphic resolution. I tried saving the config file and closing/opening Sonar to adopt the changes. I'll try later with X3.
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 12:02:43
(permalink)
It has nothing to do with "on-screen graphic resolution". AutomationDecimationMSec removes nodes from recorded (not hand drawn) automation. At least that is my understanding. I don't believe it is documented anywhere.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 12:10:23
(permalink)
I was indeed doing fader automation, but whether I moved the fader with decimation at 2ms or 1000ms, I didn't see any difference in what was drawn onscreen. Perhaps the resolution changes internally and the graphic always gives a rough representation? I'll try on X3 and see if there's an audible difference between the two extreme settings, regardless of what shows up on screen.
I couldn't find any documentation anywhere either.
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 12:20:04
(permalink)
I don't know what the allowable range is for the variable. It may not even work in the X series. FWIW, I just did a quick test with values 20, 50 and 100. They looked the same to me. I don't have a pre-X series version installed to test.
post edited by scook - 2014/05/18 12:31:03
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 12:41:13
(permalink)
There was a similar thread a few years ago http://forum.cakewalk.com/FindPost/2071724 It gets into discussing the AutomationDecimationMSec midway through the second page. I mostly hand draw automation so it is not an issue.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 13:56:06
(permalink)
Okay...I did some tests by generating white noise and doing automation with 2ms and 1000ms decimation. In both cases, the automation graphic indicated a minimum time of around 40ms between nodes. I used Sonar's onscreen faders for automation, moving them as fast as I possibly could - so fast it would definitely be unmusical unless you wanted a really fast random tremolo effect. The following screenshot shows what happens when you render the tracks with the volume automation. It's clear the volume curves follow the automation graphic curves. Give how fast the changes are (the timeline is set to milliseconds), it would certainly seem that Sonar's automation resolution is about the same as what human perception is capable of discriminating. As to whether the automation decimation parameter serves any useful purpose, I have no idea but it doesn't seem to make any difference. 
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Automation Write records inaccurately
2014/05/18 14:08:09
(permalink)
Yea, this is pretty much my results too. I did find a post where Noel describes the variable http://forum.cakewalk.com/FindPost/35571 The description appears different than my understanding of the variable.
|
rir1
Max Output Level: -89 dBFS
- Total Posts : 93
- Joined: 2004/11/04 15:34:20
- Status: offline
Re: Automation Write records inaccurately
2014/07/09 22:10:32
(permalink)
Anderton
I tried changing those values from 2 to 1000 ms in X2 (what's on one of my laptops), and didn't see any difference in the on-screen graphic resolution. I tried saving the config file and closing/opening Sonar to adopt the changes. I'll try later with X3.
seems like you know about mix automation - I've posted elsewhere - I finally installed X2 (had 8.5) - I've never had trouble with automation, but it seems in X2, I had automation on one track, and had trouble with the fader data being recorded - finally it did on one track; then I went to do some volume adjustments on another track and it doesn't record the automation; I have the track write enabled and read enabled, as usual - do I need to disarm the write enable on the other track? Never had to before - all I know is I'm not getting automation data to record on the 2nd track, and don't know why I should be having this trouble - if you have any ideas I appreciate it. I'm hoping it's just some little thing I need to fix - thanks.
|