Audio Snap changes not saving

You're sure you're opening the right version of the project? And I assume you're not saving as a CWB bundle file, because that warns you that Audiosnap info will not be saved.

So, I've began editing the track again, this time the saved edit re-open successfully. 

Good deal. Hope it holds up. Definitely not SOP to lose AS edits.

It's doing it again, and more. 

chilldanny: I'm unfamiliar with 'apply edits and commit to audio' this may be my main problem.

Please explain if you get a chance.

Thanks!

This BUG is really annoying. About 8 hours of audio snap tweaking is shot.

All I'm doing is saving the AS edits done in a previous session and re-opening the project. My edits only include moving transient markers - nothing more.

Tried exporting the track after saving AS changes and it saved it as a non-audio snap file in its original state minus AS edits.

Tried highlighting the file in Sonar and activating my external audio editor to capture the AS edits. It opens the file in its original state minus the AS edits.

I have a backup archive of previous versions where AS was saved (10 hrs ago), and opening it at this time doesn't display the edits from AS.

Sometimes the transient markers disappear in part of the audio file. So like for measures 1 to 6 the transients display. For measures 7 & 8 the transients don't display.

Similar to the transients not displaying, the actual wav file rendering disappears for certain measures but the audio still plays sometimes. Other times the audio breaks up and fizzles away into static.

Sometimes only the first or second transient markers allow me to move them, the rest of the markers are not editable. I have to close the project and reopen it, or re-launch Sonar to edit other transient markers, then they become the defacto marker to be edited.


Rebooting the computer doesn't solve the issue. Reinstalling Sonar doesn't fix the issues.

The usability of Audio Snap over long periods of time deteriorates for a single project. Overall behavior is very inconsistent.

Sometimes it works as expected for a few days or 2 weeks, then it goes awry.

Thanks, brundlefly. I'll read up on what you suggested to try and get it sorted.

Ok, Was trying to Export. Found the right click > Bounce now.

Thanks, rbowser

Ack, bouncing the track doesn't retain any of the edits done in AS.

This sucks. After I invent a work around and calm down I'll email tech support and let them know of this.

DJSur


Sometimes the transient markers disappear in part of the audio file. So like for measures 1 to 6 the transients display. For measures 7 & 8 the transients don't display.

I haven't had my edits disappear, but I've seen what you've describe above in a few projects of mine.  I don't trust Audio Snap, so I do as suggested and bounce as soon as I'm done. 
 
What's funny is that Bitman opened up a thread earlier today with a link to a video of a guy who made a Beat Detective clone application for Reaper.  I tried to follow the same steps he performed in it (which are doable in AS), but the results were horrible.  Lots of static noise that sounded like my drum loop went through "The Glitch.  The guys' program did a MUCH better job than Audio Snap!!!  How can a random guy create a Beat Detective clone for Reaper that works better and easier than AS?  I honestly don't get it.
 
Here's the link if you want to check it out: http://forum.cockos.com/showthread.php?t=66434
 
 
EDIT:  To add link to video.

a nice trick to have in mind is this:

every time you've finished editting with audio snap, duplicate this track and then bounce to track only the duplicate one and then save the project and exit sonar. so next time you open the project, if the edits are lost in the original one, you'll have a bounced one with all the edits applied. but if you haven't lost the edits in the original one, delete the duplicate one and continue to work. repeat the same procedure before saving and exiting though!

Vallhagen


This wont help you much: I just post to say that i have had my issues with Audio Snap too, both version 1 and 2.

After som time of editing, some markers may disappear or spantanous (yes!) timestretching can appear on a clip. It's just strange, buggy and unreliable. Sad to say that, cuz when it works i really like it.

...and i dont really like "workarounds" like "use only on short clips, and hope it will work", "bounce often" etc... It saiz nowhere in the specs that you shall do that. I think an option like AS shall be able to handle a - say - full map of a played drumkit, maybe 12 tracks, and line them up and quantize a full song.

well well... no this wasnt a helpful post. Cheers anyway :)

I agree with you on trying suggested 'work arounds' - that's not really an acceptable resolution in my opinion.
"Designed to work on small clips" - this statement to me says: We're not inclined to make this any better, just use it like we say. 
I've been trying to use AS again on a recent project, using smaller clips. To be perfectly honest, the project is shot and I threw it away. I don't need the stress of messing around with it all again.

Thanks,

-D

ve taken to freezing the tracks I've applied AS to because when I bounced them and then went back to my as tracks the markers had moved. I've not tried unfreezing them yet to see if the transient markers are still in the same place so I can't confirm this as a full workaround yet.

Looking back over this thread, I think part of the problem is understanding the difference between relocating a marker in the clip, and stretching audio by moving a marker. When you bounce a clip, any stretching you've done is applied, and Audiosnap is turned off. When you re-enable Audiosnap on the bounced clip, SONAR sees it as a new clip, and will re-calculate the transient marker locations.


So, for example, suppose you have a clip that needs quantizing, and you first add, disable, and adjust the locations of some markers as needed so that they accurately represent the actual audio transient locations. If you save the project at that point, it should open back up with all your marker adjustments intact. If you then quantize it to 100%, the audio will stretch, and all the markers will be shown exactly  on their respective beats.


But at soon as you bounce it to render that stretching permanent with an offline algorithm, Audiosnap will be turned off after the rendering, and when re-enable it, the transient marker locations will be re-calculated. And since transient detection is often a little wonky, a lot of markers may now show up early of late,  the spurious markers you disabled before will be back, and the missing markers you added will be gone. But the audio itself will be right on with maybe some small deviations from perfection due to the way the stretching algorithms work to minimize distortion and phase errors while getting the transients as close to the target at possible.


Because all your transient-editing work is lost, and you may have missed something, or otherwise dislike the results, it's highly recommended to clone the edited track and bounce the clone to clips, or bounce the track to a new track, rather than bouncing the clip in place. Hitting Undo immediately after bouncing will also get you back to the edited state, however.
  
So the moral of the story is: If you want to preserve the locations of transient markers that have been re-located without stretching audio, do not bounce the clip!. SONAR should retain those edits on saving, and in my experience it usually does, but there are occasions where either the way the markers are stored or simply the graphical display gets fouled up. This has improved  over the last several versions, but continues to be a problem. So bouncing partial edits might be a good a good idea, but you should bounce to a new track rather than bouncing the original clip.

I'll need to clone all the tracks I want to AS and archive the sources. Then do the transient work to each track

 
Just keep in mind that the cloned audio clip isn't really a separate file until you've bounced it. Initially, it's just an additional pointer to the original file. SONAR stores AS info independently of the clip, so you can conceivably have different AS states on different tracks referencing the same audio file. As soon as you bounce/freeze or apply effects to any track using a shared clip, that track is going to get its own independent file, and the original file will remain "unmolested". So there's no danger in working with unbounced clones, but it's good to understand what's going on in the background.