"Project contains edits from Audiosnap operations"? I never used Audiosnap

[T Boog]

Cheers guys. Forgive me if y'all have been asked this before but I couldn't find the answer when I searched it. 

 Why when I save as a bundle do I sometimes/randomly get this promt? I NEVER use or turn on audiosnap(to my knowledge anyway). It does seem to occur when I move/nudge audio around. Am I unknowingly losing edits I've made when it saves like this? Please clue me in. Thanks ?

[David Baay]

+1 on using Zip files to archive projects.

To disable Audiosnap on all tracks of a project where you haven't made changes:

- Ctrl+A to Select All

- Expand the Audiosnap section of the Clip Inspector on any audio track.

- Click twice to toggle the Enable option from '(Multi)' to checked and then back to un-checked.

 

[Niall]

I generally archive using Bundle files as well and I get this message occasionally. I don't think I make any Audiosnap operations but can't be sure. What exactly are they? And what sort of data might I lose by saving to Bundle? Thanks. N

[msmcleod]

All it means is that transient detection information has been stored against your clips.  Using AudioSnap is the main reason these would be created, but it isn't the only one.

Cakewalk Bundle files do not support saving transients, so it's just warning you that these will not be stored in the bundle.

If you've no recollection of editing audio transients, you can ignore this message.

Those who have spent hours editing / correcting transients should definitely not ignore this message!

Cakewalk Sonar has the new Cakewalk Zip format, which is far smaller and does support transients.   If you're concerned about losing them, don't save as a bundle - zip up your project folder instead.