I've been playing w/ audiosnap in Splat. Set markers on a raw 8 bar drum clip (not Cakewalk content). Quantized. Set to follow project tempo. Reset tempo. Now it brings down Sonar if I look at it. Anyone else having issues w/ audiosnap?

1) Try turning up your interface buffers... if that doesn't help try increasing your Read/Write cache
 
2) Revert back to an earlier version of the project (before you started using AS)
 
The reason I say this is because I've had the same types of issues (albeit in the original audiosnap... haven't tried the new version) and I'm pretty sure it was partially because I was driving the system harder than my latency/buffer settings could handle. Once the project started getting wonky it just became more and more corrupted the more I tried to screw with it.
 
So just keep in mind you are doing some pretty intensive stuff when using AS (especially if you are editing all 8 tracks at once) so you want to give your system all the power you can to succeed.
 
Cheers.

Sorry... read that as 8 tracks instead of bars for some reason. Still might want to try from scratch with more buffers.
 

I have not seen a problem with Audiosnap, and can't reproduce one now using Quantize followed by Clip Follows Project on several tracks of multitrack drums. In general, I would say buffer size and CPU load should have no bearing on stability. My guess is that Audiosnap is not directly responsible for the crash - at least not by itself.

It was clip follows project - quantize - then a tempo change from 152 to 130. I also messed w/ a couple of the markers. But I'm sure it's not that easy to reproduce as my guess is it's something deep in the bowels of audiosnap.

Notecrusher
It was clip follows project - quantize...

You stated the reverse order in your original post, but I tried it both ways, moving markers as well, and still don't see a problem. Are you saying this is repeatable for you? If so, you should submit the project the Bakers to troubleshoot.
 
 

The order doesn't matter it's the tempo change you missed. But I suspect the best way to crash audiosnap is to stress it hard.
 
The first time Sonar crashed the problem reporter crashed too, lol. I sent them two subsequent crash reports.

I did make tempo changes after enabling Clip Follows Project; just didn't mention it.

When you quantize does it quantize all the detected transients? Not here. Just some of them. And yes strength is at 100%. Also some markers won't move or stretch as I tell them to. This tool has been buggy and unstable from the start, why can't time stretching just work like in other DAWs? GRRRRR!

While I can admit that AS is not the most intuitive feature and it takes some work, I would never consider it buggy.