Audiosnap question: can you edit clip maps on multiple clips?

Actually, I'm pretty sure you can't, so I guess my question is, once you DO edit the clip map on a clip, how do you apply those changes to all the tracks in a project? I want to quantize a multi-track to the grid, but SONAR's initial guess was way off. Now that I've fixed the problems on the best track for reference how do I replicate?

Yah, but I don't want to tempo map the project, I want to quantize them to a hard grid (so I can do other tempo related functions later). But most of the clips have long gaps of silence since they're multitrack parts that don't appear through the whole song. I can get SONAR's tempo close, but since the performance was recorded without a click it's not exact, and I don't know how to apply the changes to the other tracks. 
 
As an experiment, I tried to do this in Reaper and Live last night. I didn't expect to succeed fully but I did confirm that it's not easy-peasey in other DAWs...which I suppose is comforting in some weird way. 
 
Surprised there's not a good example of how to pull this off, it seems like a pretty common problem if you get stems from a live band that you want to do a dance remix for. First you want to quantize the whole thing to a grid and then you can sequence and manipulate tempo globally (like adding accelerandos and whatnot). 

I found this interesting thread last night. I'm going to try and use this method (maybe some variation on it) to see what happens:
 
http://forum.cakewalk.com/Audio-Snap-2-multi-track-drums-quantize-in-phase-m1921825.aspx
 

Uh, maybe I'm not reading it right.
 
If you set the project to follow the clip, SONAR just inserts tempo changes so that it's measure boundaries line up with the existing audio. I'm talking about defining the measure boundaries and than having SONAR stretch the audio so that it's mapped measure boundaries line up to where they would at the project tempo in time. So the grid would be, er, all the measures would be the same real-time length as if it had been quantized (which it has), but so that ALL the tracks are quantized the same way, with the measure break info coming from the one track's clip map. (does this make any sense? :-)
 
As for your second answer, I'll go look that up!
 

What you want to do can get very complicated and may take multiple attempts to get right, but you're on the right track (no pun intended). Basically its a three-step process (four, including the final bouncing of clips to render the stretching):
 
1. Set the project timeline to match the audio of your reference track using Set Project From Clip as Karl described. You have to do this so that SONAR knows where the timing irregularities are that you want to eliminate.
 
2. Select all the clips, including the reference track, choose the Autostretch option from the dropdown to the right of Clip Follows Project, and then Enable that on all tracks.
 
3. Now you can alter or delete any or all of the tempos in the timeline and SONAR will stretch/compress all the clips equally to conform to the new tempos or to a single, initial tempo if that's what you want.
 
The level of precision you use in the first step will determine how tightly everything is "quantized". In theory, you could bounce the stretching, and then do additional quantizing of individual tracks at higher resolutions as appropriate, but I think you're likely to get bad artifacts from stretching more than once. As it is, you may not like the results you get. The less you mess with the tracks to get them where you want, the better.  A lot depends on the nature of the content. Also, once all your tempo changes are done, it's important to select each clip individually and Bounce to Clip(s) to render the stretching permanent using the most appropriate "Offline" algorithm in the Audiosnap Palette for that clip's content.
 
All that said, here's the bottom line: It's going to be a ton of work, and I don't think you're going to like what you get. It were me, I'd stop after step 1. That will give you a grid that you can use to add or replace sounds while maintaining the original ebb and flow of tempo. And if an individual part has wonky timing, you can quantize specific parts of specific tracks to tighten them up against other parts without changing the overall tempo variation.
 
EDIT: Oops. Stepped away form a half-finished post for a bit, and see you've come up with an alternate strategy in the mean time.

The Drums Production webinar is how I learned to use Audiosnap across multiple tracks for anyone who is interested. They keep it limited to drums and I had to modify the procedure to use it across an entire set of tracks (a whole band) but the methods shown got me going. I insert my own Transient Markers across tracks using Snap to Grip (moving/disabling/deleting any auto detected markers that are in the way) to get the general song tempo in order then switch to the more traditional methods to correct individual timing issues on beats or late/early starts/stops on other instruments. It takes two passes to do this (one for general tempo correction them a second to line the individual parts up).
 
Audiosnap however is very quirky and awkward in X2 doing even simple stuff so doing it across multiple tracks just multiplies the weirdness. You will likely want to make sure your system is set to handle the serious processing loads involved (turn up your buffers). I've been told it is more stable in X3 which would be great. It's a neat tool when it's working properly. When it's not it is fist through monitor infuriating.