Need some ideas on what may be going on between my project, and Audiosnap.   Maybe I'm not using it correctly, but I don't remember having this problem in the past.
 
I have a new project, which so far is using an instance of Ezdrummer2, plus 2 stereo Guitar tracks panned left right, and one mono bass track, all of which where recorded live into Sonar Platinum through my Roland Quadcapture interface.  I have several Eq's, and dynamic processors insert on the various tracks and busses.  All in All, it's very basic at this point.  Sonar CPU Performance meters maybe at 15% on all 8 cores.
 
The problem.  I recorded the initial tempo at 163bpm, but I now feel that it's a little fast, so I want to use Audiosnap to change the recorded guitar and bass tracks to a tempo of 161.  Ezdrummer is still using midi at this point, so it will follow the tempo change.
 
I select all the audio tracks in the project, hit control+A to bring up Audiosnap.  Click Tempo follows Project, then using the audiosnap tempo dropdown menu, I select "From Project".  I change the project tempo to 161, and hit play, and all of the meters in the audio tracks are immediately pegged into clipping, and the audio is distorted and glitching.  If I remove Audiosnap, and change the tempo back, everything is back to normal.
 
I've never experienced this before, but it's been a while since I've used Audiosnap.  Anyone have any ideas?

Disable 64-bit Double Precision Engine in preferences. It sometimes has issues with Audiosnap stretching.

Yep....That was it.  Thanks for your response.  I just tried it with 64-bit Double Precision Engine DISABLED in preferences, and it works correctly.
 
Is this a known bug?  
 
Am I losing any performance, with the 64-bit Double Precision Engine disabled?  I've had it on for as long as I can remember.

davec69
Is this a known bug?

It is to me.     Actually, I did report it to the Bakers a long time ago (circa X1). Not a common enough problem to rate a fix, I guess.
 
I generally leave 64-bit double precision off, and just enable it on bounce/export. I've never really been able to hear it, anyway, and there have been assorted issue with it over time, though this is the only one I know of that hasn't been fixed.

Dave... if ur not going to file a bug report, I suggest re-titling the thread: "Bug in AudioSnap!  Disable 64 bit double precision engine!" Brundle... thanks for trying!
 
maybe this will get Noel's attention and get it on the list!

I'm going to try working with this feature disabled for a while, and see how it goes.   I hate to disable this feature, if it lowers available headroom.  Of course modern DAWs have such high headroom available, I doubt that it will make a major difference.     I do hope that it will be fixed though.

All you need do is bounce your AS clips to themselves, then turn 64 bit back on.
 
This only affects SONAR's internal maths computations and should make little or no audible difference

Thanks, I'll do that.  
 
I've also been seeing a higher than usual number of audio dropouts recently, so I'll probably disable it for a while to see if it has any affect on that issue. 
 
 

Bristol_Jonesey
All you need do is bounce your AS clips to themselves, then turn 64 bit back on.
 
This only affects SONAR's internal maths computations and should make little or no audible difference