HI, i wonder if anyone can enlighten me on audiosnap's tempo changes. I know how to change tempo to match an audio clip, but could anyone explain to me why it doesnt alter the tempo so that is regular throughout the track? I know why it does it, due to transients being different lengths etc, but I always assumed that (so long as it was a regular type of track) that the tempo should always be the same. As an example, if i match tempo to an audio clip, then play it with, say, a regular session drummer, simple drum track, when you listen to it, the drums speed up and slow down. Surely this is not what a regular tempo should be?
I've spent hours trying to get my head around audiosnap, but this part of it just does my nut in. Can anyone tell me why they have designed it this way? All I want is regular tempo to match my audio.
Cheers, John.

I personally never found it will work as promised. It does exactly like you are saying and it jumps all over the place. One would figure that a song played with a nice even tempo would only require a few changes but it goes berserk and will jump from 120bpm to 241bpm and crazy stuff like that. 
What gave me the best results was to play along with the track while tapping the tempo and recording a hi hat. Crank the velocity up to 127 and bounce to a audio track, then extract the tempo from that. But it was hit and miss. 
I try real hard to start all projects with the tempo set ahead of time. The only exception is live recordings. With those I just have to be a better musician and play in time with the midi overdubs. But I am soooo used to cheating with MIDI keyboard parts it's hard not having the beat/measures line up. 

Thankyou for your reply. At least i'm not the only one then. I've looked at forums and tutorials and videos, yet i haven't seen (what i would imagine would be a glaring problem, however it could very well be me that's the glaring problem!)this featured. Can anyone else throw any light on this please? If only to preserve my sanity!

Can anybody help? Not just for me, but to save anyone else from all this wasted time. Any advice is Much Appreciated :0)

I thought I gave you the answer, what other info are you looking for? 
There's nothing more to it, you sound like you understand how it works and found out like all of us that it is flawed. 

Try to record all further projects using some sort of click or better yet a basic drum track, if there are going to be drums in a final mix all recordings must start there. 

Build yourself a collection of templates that have a few different drum patterns that work for your style of music,,, even if it's only a hi hat. 
I have mine divided into midi tracks for each drum part, Kick, snare and hi hat. so I can then rebuild a full drum track latter on. 

Cheers John, i appreciate you replying to my message. I'm just finding it difficult to believe that they've made this incredibly complex piece of equipment, but that it doesn't really do the most important job expected of it. I guess you're right, there's no replacement for playing the stuff in time. The way i've done it before is to record ,say a long repetitive guitar part, in chunks, and groove clip each chunk. This has always worked in the past, and sticks completely to tempo. It's just that audiosnap seemed like a panacea for adjusting bits and bobs. I'm off to practice! Cheers for your help, John :0)

Well I don't think it's possible for anyone to play in perfect time. Sure , we can be so close but never to the clock,s resolution. 

And that brings up to topic of not worrying about it. If you can't "hear" timing imperfections then all is good. 

I don't use the clock when recording pure audio music as in my bluegrass band, which has no drums, or our live band with drums.That makes for the best recordings that sound natural. 

But if I'm going to be the one all by myself building a song with midi parts then it will have to start with a clock pulse. Otherwise it will slowly build into a mushy mess of timing.  I find that even two musicians playing together will have better timing than one. 

I recently had this problem when importing Pro Tools sessions where the tempo was unknown (nope, OMF doesn't carry in tempo from originating session).  This is kind of a no brainer feature that I hope the Sonar team addresses.  Other DAWs do it on the fly in about 2 clicks.

This kind of makes collaboration between teams with different DAWs difficult.  Of course having the original tempo information solves the problem at the import step (you can type it in manually) but in the real world, that's not always possible because you just get handed stuff electronically and don't always have immediate access to the originating session author.