I have selected a clip, opened Audiosnap and selected "Clip Follows Project", get this error:
 
Invalid measure and/or beat.
 
The tempo required for that location is out of range.  Please remove some tempo entries in the tempo view around the desired time or enter a correct measure and beat."
 
Open tempo map, there is a steady line at the project tempo, nothing that I can remove.
 
Ideas?
 
(Wont let me upload pic)
 
Project tempo is set at 185.  Metronome and audio clip are aligned in time.  After dismissing error, track gets truncated and plays at a ridiculously fast speed.
 
Floowing directions here:
 

 
 
 
 

Any way to post links or pics?  Bought this expensive software, forum should allow this.

Does the same thing when opening a new project, importing a single wav, and following directions in link.
 
There were no tempo changes, at beginning its set to 120.

200bpm
Any way to post links or pics?  Bought this expensive software, forum should allow this.

Not sure one has anything to do with the other.

You can post pictures here by embedding them.
 

 
As to AudioSnap, as I've said before it's a complex piece of software that requires user input. There is no simple one-paragraph answer or I would give it to you. You also need to understand tempo maps. Any answer I could give would simply reproduce the documentation and provide the links you would find by searching on: sonar audiosnap tutorial
 

Users can only post a picture or link after a number of posts.  I think it's 25 but I'm not sure.

I talked to tech support.  The X3 documentation for what I am doing was not correct. He showed me the right way, but he advised to bounce then archive any audiosnap tracks as keeping AS tracks open could corrupt the project.
 
I will make some more posts to see if it allows me to post links.  
 
Bouncing is taking hella long time for a 5 min track; hope the result sounds good.

This happens when you do exactly what the error is telling you... entering an invalid measure or beat for the tempo you have selected. That means if you are trying to enter say the 4 beat of a measure before the 3 beat and the project can't accommodate it by altering the tempo map (which would mean you would have a serious tempo speed up at that point) Sonar will throw the error. You basically cannot bend the confines of traditional musical time theory.
 
This is a little tricky with Sonar in the sense it will count silence at the start and end of a clip in how it counts beat or measure and sometimes will jam multiple measure in a tight space at the start of a clip where the silence is so you have to make sure the beat 1 of measure 1 actually starts at beat 1 of measure 1 and that the rest of the first measure lines up with appropriate beats up until the next measure. Otherwise you will eventually run out of valid beats/measure as you approach the end of the song.
 
You also have to be very aware of what the actual time signatures are as your song moves along and be sure that you are not entering beat/measure markers at the wrong spots or the whole thing will screw up.
 
You can keep an eye on your progress with the Tempo View. If it is a song that has been recorded with a reasonably even tempo the line in the tempo map will be more or less straight. If you screwed up there will be drastic spikes and valleys on your tempo map.
 
 

How long is "hella' long"? Bouncing a single track should not take very long. Mine bounce in a few seconds. Post your system specs, interface model and what you have your buffers set at.
 

And yes. I've had projects go completely to arse when saving projects with active audiosnap tracks. Audiosnap needs a revision. Hopefully it will happen in X4.