Audiosnap Crashing? - I think I've found out why.........

Now that I'm doing more work with live bands I've been using Audiosnap more and more recently, mainly for extracting tempo maps and up until today haven't had many problems. However... today I've had more crashes in a morning than I have in the last 18 months, many more in fact - and all when editing the clip map of a clip.

Having decided it couldn't possibly be a bug because I'm a fanboi and X1 doesn't have any I've done the same thing many times without a problem before, I started looking for reasons and it seems to be tied in with the audio clip editing before using Audiosnap.

I was deleting a large chunk of data from the start of a project and then dragging the resulting shortened clips forward in time to the project start. The 'magic' cure for going from a "crash city" Audiosnap experience that would have made me tear my hair out (if I had any), to a smooth "work as advertised" experience was to bounce the clips after the editing. If only I discovered that four hours earlier.

Anyway, point of the post really is to find out whether others have had a similar experience and/or alert others to a tip that has certainly worked for me.

I made that procedure my standard way of doing things since Audiosnap came out and it served me well.  I basically ported the process from V-Vocal with the attitude that once something is fixed and sounds good then commit to it and move on.  If you are not sure about your edits then make copies of the unedited tracks, archive them and hide them in case you need them.

I'm of the opinion that all transient detection is a bit flakey to some percent.  I think that in this area the Reaper transient detection feature contains a few more controls to make the artificial intelligence of the detection part of the program better than the SONAR implementation.  But that is not to say that you can't work Audiosnap and make it do what you want if you are willing to do a little manual adjustment of the transient markers.  I think all transient detectors are going to require that.  Even Toontrack's Drum Tracker requires a tweak when the dynamic ranges are not well defined.

I am suspect that the issue with crashes with Audiosnap is the sapping of the computer resources by the process.  It's my hunch that each change is held in RAM in case you undo the process during playback because the crashes just feel like the same kinds of things that happened when I started loading mega drum sample libraries in Superior Drummer and would crash SONAR when I starved it for memory.

I think that bouncing to a clip frees up memory and removes the possibility of running into this situation.

FBB how the heck did you figure that out? If you didn't know that already it looks like a very fine job of detective work to me. Great tip too.

Inspector FFB at your service!

Thanks for the post.

Rim