• SONAR
  • Draw Tool Doesn't Snap Correctly in Projects With Tempo Changes
2013/12/20 00:36:22
MakeshiftMilitia
In any version of Sonar Xx I can remember, the draw tool doesn't snap correctly in a project from the point of the first tempo change until the end.  I'm assuming the tool just continues to draw at the previous tempo.  This is kind of a deal breaker for scoring work or any other complex music with tempo changes that relies on metric automation for effects/etc.
 
I reported it as a problem through Sonar's bug reporter but it apparently didn't make it into this new update so maybe if enough people can confirm it, we can get it fixed?
2013/12/20 00:45:40
Splat
Hello,,,
 
Welcome to the forums
Could you give us clear steps to reproduce as from creating a brand new project?
Would you able to create a video as this sort of issue can be hard to get across?
 
We have another different (but slightly similar issue) here you might be able to weigh in:
http://forum.cakewalk.com/X3d-Audiosnap-wonkiness-m2952751.aspx
 
Thankyou...
 
 
P.S. What was the issue number and what is it's status? Thankyou. 
2013/12/20 01:09:00
MakeshiftMilitia
Hey there Alex,
 
The other post you linked to is an unrelated issue/problem.  I'm not going to do video recording just yet because it's so easy to reproduce:
 
1. New Project with one track
2. Insert a new tempo (let's just say 145) at bar 5
------- so far we have a project that is 120bpm through bar 5 where it then switches to 145bpm --------
3. Bring up automation for panning, volume or anything else
4. Set the draw tool to saw wave or anything else that snaps
5. Draw across the automation from bar 1 through bar 8 at 1/4 note snap (so through the tempo change)
6. Observe that at bar 4, the automation is perfectly snapped, at bar 5 and onward it has drifted off
 
You don't need to draw through tempo changes to make this happen either... start anywhere after bar 5 and the automation won't snap properly.
 
Let me know if any of that is unclear.
 
 
 
2013/12/20 01:13:01
MakeshiftMilitia
CWBRN-19135"The status of your problem report has updated to "Submitted to Development" with the following notes:

This is confirmation that your report is officially on file with our development team. At this time we do not require any further information from you to research the nature of your report. Should we require further information we will contact you using the email address you have provided in your report."

 
I'm pretty sure I reported it months ago but I can't remember honestly.
2013/12/20 01:13:43
Splat
OK thanks... haven't got time to repro as I gotta go, maybe another forum member can chirp in.
 
A screenshot or two might be good to demo what happens (if you want to create more impact with your post)....
 
Thanks...
2013/12/20 13:33:35
MakeshiftMilitia
Anybody willing to test this out?
2013/12/20 13:42:44
Splat
I tried this, I guess I'm still not getting it. I'm probably doing it wrong, your steps are pretty good but I suspect if I had a screenshot of (6) it might help me.
2013/12/20 16:16:08
MakeshiftMilitia
In this screenshot I followed the steps I outlined above... tempo change at bar 5.
 
You can see in bar 4 (in the green bounding box), before the tempo change there are 4 saw waves across 4 beats... perfectly synced.
 
In bar 5 (the yellow bounding box), you can see there are 3 and 1/3rd saw waves across 4 beats... no longer synced.
 
Why is this bug a problem?
Let's say you were scoring Iron Man 4 and you had many tempo changes across a project to hit all of the action.  You get to bar 67 and need to do some SWEET dynamic wobble bass (slightly sarcastic).  You draw in your waveforms to modulate your cutoff and then you realize you are **** out of luck when it doesn't sync.  Now you have to do a bunch of extra work to get around the bug (or change your creative vision), you miss your deadline and you get fired.
 
That's why this needs to be fixed.
 
 

2013/12/22 15:30:56
MakeshiftMilitia
C'mon, someone on these forums has to write or record music with tempo changes and draw tempo-synced automation
2013/12/22 17:47:36
Splat
Well I'm fairly clueless to be honest but this is what I did, it's taken a while to work this out (really need to baby spoon me here):


1. New Project
2. Insert audio track
3. Arm and Record audio track (say 10 bars worth).
4. Insert a new tempo (let's just say 145) at bar 5
------- so far we have a project that is 120bpm through bar 5 where it then switches to 145bpm --------
5. Bring up automation for panning, volume or anything else
6. Set the draw tool to saw wave.
7) Set event draw duration to 1/4
8) Set snap to whole note.
9) Draw across the automation from bar 1 through bar 8 onwards....

I get the below image, note the leadup is a straight line, however I drew it from bar one and the line got created.... No idea....
 
Anyway here is the image, does this prove anything...?
 


What is missing from these steps otherwise?
 
 
(this is reminding me of http://www.photoshoptroll.com/  , however it's real and I'm the stupid person )
 
 
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account