Cannot Diasble AudioSnap in Sonar Platinum

Does anyone know how to turn off AudioSnap? It is preventing me from adding Dub channels at the correct latency offset from my sync track. I start recording on a channel and when I stop the transport, Sonar immediately moves the channel into alignment with my metronome sync track. This prevents me from being able to punch in new segments on the track - because the correct latency delay is then lost.
 
The Sonar Doc says that AudioSnap can be disabled with the Bypass button on the AudioSnap control panel - but that control is non-functional.

Good idea Rob; What version of Sonar are you using?

I will create a new project with only 2 tracks, record my Met into Track 1, route the signal from the DAW 1 output back thru the input of my Saffire 18i20 USB mixer to Track 2 and then record the signal. I'll let you know if I can keep AudioSnap from moving the recorded Track 2 signal.
Note: Sonar Pro seems to not allow AudioSnap to be disabled on a track that contains no clip.

Here are my AudioSnap test results with Sonar Pro V21.12 Manchester.
Opened a new project with only 2 tracks; Recorded my Met on Track 1; Routed the signal thru my 18i20 mixer back to Track 2 and recorded the Track 1 Met on Track 2.
During recording the waveform latency delay could be seen - but when I stopped that transport - Sonar again synced Track 2 to Track 1!
I verified that AudioSnap was not enabled on either track.
Same Question: How can I shut off AudioSnap and stop Sonar from resyncing my tracks!

that is not the 'audiosnap' function in Sonar.
it's the latency compensation that Sonar and probably all other DAWS have.
you can record a track on track 2 (for example a guitar track) and that will not snap to your metronome automatically unless you enable 'audiosnap' on that track manually and set the snap etc....it's a complete other function from what you're seeing with your metronome track.
When your route 1 paticular track (your metronome track) out and then back into Sonar, that will automatically allign both.
it's not an error or bug, it's meant to do that and it's not called 'audiosnap'.
there might be a setting under Preferences that let's you disable that, I don't know.
 
at least, that's how I think it is...
 
 

I didn't say DAWS automatically allign input tracks, they do allign tracks that you send out, and import back in....as what you're doing with that metronome track.
this will happen with Audiosnap enabled and disabled, it's not an audiosnap task what you're seeing.
 
just record a track and you'll see it won't lign up to your metronome.
 

Hi Brundlefly, (you da man!) if you're playing/recording a guitar track while you're listening to a metronome playing in Sonar, you wanna leave it checked right ?  Or you would end up probably with a guitar track that's playing 'before' the beat iic ?
 

Thanks Sheanes; I have recorded a number of input tracks with AudioSnap Disabled, and Sonar instantly syncs them all with my Met track when I stop the transport - which is horrible. To make matters worse - Cakewalk will not respond to my email support request.

Thanks Brundlefly; I'll try your preferences edit and report my test results.
Have you heard of Sonar force-syncing input tracks with AudioSnap Disabled?

Been doing that; with AudioSnap Disabled, new tracks still sync to Met track when transport is stopped.

this is very clearly not an audio snap issue. you can easily confirm that by trying it with a new virgin project where audio snap was never enabled (because it does not enable itself nor is it enabled by default)
 

Sheanes
that is not the 'audiosnap' function in Sonar.
it's the latency compensation that Sonar and probably all other DAWS have.

that's what it is ... and it should work in your favour as it corrects for latency in recording. if it causes adverse effects it probably means you are recording at too high latency, thus playing differently, and when latency compensated, your recordings are off => you need to try recording a lowest possible ASIO buffer sizes or use direct monitoring from your interface

Here is a video of this issue; not sure how to make a hot link of a video on this forum.
If anyone knows how to get Cakewalk to answer their support emails, please let me know.

Here is my test process:

1) Recorded click track from an external Met. fed into a Saffire 18i20 USB mixer analog input and recorded on a Sonar track. This will be the master Met/Sync signal.
2) Fed the DAW output of this signal via ASIO back to an 18i20 digital input, then mixed it to an 18i20 analog output
3) Cabled the 18i20 analog output back to an 18i20 analog input
4) Set the input of a different Sonar track to this 18i20 analog input
5) Armed the new track and started recording while playing back the Met/Sync signal. You can see that in the video. The ASIO latency is visible (approx. 100 mS) until I pressed Stop. Then, Sonar immediately shifts the new track into alignment with the Met/Sync track.

For overdub recording and editing, an engineer will need to hear the recorded/synced tracks while punching new tracks. That will be done at the system latency delay - and that latency cannot change until the track recording process is complete.

Obviously, if the DAW is syncing the track in progress with the master track - that will kill the punch-in process.

So...it would be great for Cakewalk to just tell me how to prevent the track in progress from syncing to the master track until the track recording and re-recording has been completed.

I may have to team up with Guitar Center or Sweetwater to put pressure on Cakewalk to answer my question - which I am willing to do - because Sonar cannot be used under the condition I am describing.

but actually I'm not 100% sure this 'use reported Asio latency' disabling will apply to your current metronome track, there's a small chance I'd say, that if you disable this it will only apply to new events / projects and your current metronome track will keep using this 'use reported latency'.
you'll find out :) 
 
 

Every track I record, including vocals, guitar, piano, drums, etc. will have the same 20 seconds of click track at the beginning for later synchronization - so believe me this is NOT OK!
There is no way that DAWs force input sync; this is rediculois.

Forum members: please try the test described above and give me your feedback.

I tried unchecking Use ASIO Reported Latency - and Sonar still synced the input signals. This occurred with all signals...vocals, guitar, etc.; they were ALL synced. I am finally working with Sonar TS to address this issue - which could require a software change.

I also made a number of punch-in tests yesterday - and must admit that I am impressed with the results. When track recording is stopped, Sonar moves the recorded signal left into alignment. At this point, that undesirable fact is known. What I learned is that Sonar does the same to the punch-in segment - and the results are quite accurate. That feature may not be documented. This system may be a good enough design to make working with a forced-alignment system viable.

I do have a punch-in question for the forum: has anyone experienced clicks at the punch-in and out points? That occurred during my test - and they are quite noticeable.