Hi all,

Unless I've lost the plot completely, Audiosnap is ridiculously buggy and practically unusable.

I have tried using X1d, 8.5.3, 8.3.1 and all of them seem to suffer from the same, or a variation of the same suite of bugs.

I have witnessed magically appearing User markers, at times undeletable user markers, disappearing waveform view, disappearing transient pool markers..  all of which generally result in the termination of the project file.

I have restarted the same editing session about a dozen times now, and abandoned them because you cannot remove Audiosnap data in it's entirety from a project, or even from a clip - and it appears persistent through project save files also.

If it makes any difference, it's a 13 track wide drum group, about 5 minutes long at 96/24.

I've wasted about 48 hours on this and had to push the client's session out by a week, so unless there's some magic "Push this to remove bugs" button in the software somewhere, I'm about to abandon Sonar for PT10 - which I am LOATHED to do since I've been a Cakewalk user since 2000.

Google suggests that this problem has been experienced by many people, and since at least Sonar 8.5 - how is it that no debugging has been done on this?

I'm in shock.

-Tim Shackleton
-Das Bunker Studio
-New Zealand

From what I've gathered, you're supposed to ignore and not use it. And pretend that you never had the option in the first place. Then, it works fine.

Audiosnap is awful. It's really not a feature, as much as it's a gateway to a world of frustration and premature greying. It really is best to ignore it. I've found it useful a couple times for extracting timing for triggering a MIDI kick from a poorly recorded audio track. Every time I try to dig deeper than that, it drives me nuts.
 
However, if you really need a feature like audiosnap and ignoring is not an option, then I would definitely consider another DAW, as I have absolutely no faith that Audiosnap will be fixed in the forseeable future.

I feel a video coming on...........

I cannot figure out what the technical terms mean that whizz past in the videos. 

It seems to be a box of tools that you have to know in depth before you can do anything useful. Like a surgeon.

Steps that seem obvious to me do seem change something, but not in the way expected.

I have gone back to manually cutting up tracks and nudging them to the correct positions. I do not have the time.

Extracting MIDI is the only video that explains properly how to do.

The Slicing for Sampler (Session Drummer) video is OK, but then deteriorates into reading out loud the labels on the buttons, something I do not need a video for.

The next thread down includes this link, which seems pretty useful:   
[link=http://www.soundonsound.com/sos/nov11/articles/sonar-workshop-1111.htm]http://www.soundonsound.c...onar-workshop-1111.htm[/link]

 

I have tried AudioSnap for multitracked drums many times. Equal times I have failed, either because there are issues or I just can't use it properly. Now, like Savagery, I use AudioSnap only to extract kick or snare drum timing to trigger MIDI samples. Before enabling AudioSnap I save the project to a temp file because I don't want to mess my main project file with AudioSnap (it makes CWP files so much bigger and slower).

>>it makes CWP files so much bigger and slower

Holy cow. Mine jumped from 715k to 1.690k!

Good thing I have an older version to fall back on.

Thanks for the heads-up.

I want to jump in and say what a load of rubbish. You guys obviously don't know what you're doing. It must be user error.

Sadly, though I wish it were the case, I can't defend AudioSnap either. I've had some marginal success with it but the frustration of trying to get it to work as expected and the reality are so far apart that I use other programs to do this sort of work outside of SONAR if necessary.

I work very hard at not having to go there at all. It's a shame as the idea of AudioSnap is really great but it needs a really big update and stability fix that's long overdue as it is in many things eg V-Vocal.