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.
 

There was a time when transient detection went wild (I suppose it still could depending on the length of the audio clip) resulting in very large project files. The only effective way to correct the problem was passing the project through the bundle process. Because bundles cannot store transient information, the project file is rebuilt fixing the bloated project. This may no longer be a problem. I have not seen a thread about large project files created by audio snap in some time.

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.

Anderton
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)

 but I've found disabling in the Inspector to be effective.
 

 
While I dont use often, so not sure its unusual, but I found having to do this more recently after opening audiosnap to quickly view an average tempo,  as posted in #19 above, i.e., audiosnap seemed to remain enabled in inspector view, although having closed it, and returned to clip view in track, I also had the message of generating transients when opening the project, and as said not being able to create a Melodyne FX region was how I found this.(until disabling audiosnap in inspector), 
 
Cheers 
 
 

Was this issue ever solved? I'm having the same problem. I have Sonar 8.5.3 and Audio Snap 2.0. One suggestion says check the inspector. Which one there are several?