Disable Audiosnap?

I'm a longtime Sonar user, and this may seem like an ignorant question (and it is...), but I can't seem to figure out how to disable audiosnap on tracks. I know there's a button in the Audiosnap window: "Enable/Disable Audiosnap on Selected Tracks". Here's what's happening:
 
I want to use Audiosnap on 1 track, so I select that clip and turn on the Transients tool. It takes awhile, and gives a message to wait until transients are created. It then creates transients on ALL tracks, including those that are archived. Not sure why it does this, but okay....
 
So, I select all the tracks except the one I want to work on, and click the "Disable" button, and the transient markers on all the other tracks disappear. Fine, so far.
 
If there are a lot of tracks in the project, Sonar begins to be sluggish, because Audiosnap is still enabled on all those tracks, even though there are not markers anymore. I can turn off the Transient tool, and when I save and close the project, sure enough... when I reopen it, Sonar gives the message that transients are being created, and voila! ALL the tracks again have markers.
 
How can I simply work on ONE track, without all the others being involved? I know I'm missing something fundamental here, but I just can't figure this one out. Thanks.
 
--john

Thanks, Steve. Will check that. I see that there's no icon that actually tells you whether global snap is on or off, but I did find it in the flyout menu on the snap-to-grid icon. All these years of using Cakewalk stuff and I'd never noticed it before. Thanks again. Hopefully, that'll do the trick. 
 
best,
 
-john

I hate to belabour this, but it's maddening.... Still can't figure out how to actually TURN OFF AUDIOSNAP. Here's another example:
 
I just opened an existing project and it gave me the message "generating transients....". Once it finished, the project opened up and looked normal. The Transient Tool was OFF. There was no sign of any transients or markers on ANY tracks at all. How the heck do you tell if it's on, and which tracks it has worked on? I'm stumped...
 
Also, the Snap To Grid tool was turned off, and when I opened its dialogue box, the "Audio Transients" box was not checked.
 
How do you get Audiosnap to JUST GO AWAY? How do you select a track (or region) and "remove audiosnap", or "remove all transient markers"?
 
I feel like a complete moron for not figuring this out yet. (help....)
 
--john

I don't use audiosnap very often, I find it easier to just do it over if there is an issue. however if memory serves me correctly the only way to stop that message of generating snap markers is to bounce the track to clips. I could be wrong though.

You can get the "generating Transients" message even if you have never used audio snap... I do. I haven't used audio snap on any currant projects I'm now working on , but even today I had that message on one project. To me it is just the computers CPU dogging it a bit to re-draw the audio images. 

When I think of it, I bet I get that message on a project that I hit Shift A by mistake instead of Ctrl A. Shift A opens Audio snap, and I close it right away, but this makes sense.
Thanks for solving my mystery too! So your right, it's embedded somewhere, I wonder if clearing that "Aud in" or the "picture cache"  would help?  I'll try it next time I get the message. 
I have never performed either of those operations but it seems a common suggestion. 
 

I’ve run relatively high track counts with multiple plug-ins inserted in the effects bin and transient markers displayed on every track without any issues.
 
I am guessing so I may very well be wrong but, if you haven’t moved any of the transients on a particular track, it doesn’t process that track during playback.
 
Also, there are two modes of processing, (1) an on the fly process and an (2) off-line line process.  The on the fly process is supposed to be easy on the CPU and shouldn’t consume massive amount of processing power but, you may hear some anomalies that will go away in the final mix-down.  The off-line process is CPU intensive and happens during mix down.
 
My suggestion is to move the transients around to your heart’s content on your track of interest and then mix just that track down by itself (bounce to track or export).  Save your project with a different file name and delete the original track (to avoid confusion) ... and see what happens.
 
Out of curiosity are you running 32 or 64 bit (I am assuming 64 bit based on the 12 gig of RAM).

Good Day,
 
I haven't read through all these posts fully, but I recently had an issue with audio snap remaining enabled in the inspector window under clip/audiosnap, after having enabled audio transients in track to quickly look at the approximate tempo of a random recording, and then returned to clip view, I noticed it because later I couldn't invoke Melodyne on a clip, and found audio snap enabled in inspector/clip/audiosnap was preventing Melodyne FX region being available, not sure this is same issue but I dont believe Ive ever had to do this before until recently. Anyway not sure this is any help, but an experience I had recently.  
 
Cheers 

Caa2
I am simply asking if there is a specific reason that saving as .bun flushes out the audio snap litter.

It appears to offer a very effective solution for times when the obvious procedures do not help. I am going to try it but I would like to understand the idea in detail rather than relying on a simple cause and effect assumption.

Thank you.

Just going from memory, I don't think the compressed BUN format supports the state of audiosnap transients,  possibly because it predates it.   Never tried with looped Acidized waves...

I use AudioSnap a lot and don't have this problem. Not sure what version of SONAR the OP is using but there have been AudioSnap improvements over the past couple years. What about this...
 

1. Select All
2. Go to the Inspector, Clip tab, Audiosnap
3. Uncheck Enable (if it says Multi, click to see the check box)

 
That doesn't solve why the OP gets transients on everything, which shouldn't be the case. There's always the ".bun flush" but I've found disabling in the Inspector to be effective.
 

I recall there were issues with bloated project files due to Audiosnap, primarily related to using Split Beats to Clips. But I don't recall that disabling Audiosnap via Clip Properties was ever ineffective, only that saving as a Bundle was a convenient way to dispose of AS markers, especially when a project became unmanagebly sluggish due to AS marker bloat.
 
But rather than starting with Select All, I would start with Edit > Select > All Audiosnap/Slipstretched to avoid problems with toggling the property when some clips have it enabled, and some don't.