Editing multi-track drums is completely impossible. This needs to be addressed.

At last someone else suffers the same nightmare like me. Not to mention that when using auto detect transient in audiosnap it almost always detects the transient late, splitting it in two so when you quantize you have to go and manually fix every kick or snare hit.....
I´ve switched to PT for editing in general, it´s unbelievable retarted in Sonar PE

Soulburned
so let's clarify.  You're saying that after your timeline now has the drum tracks all split into clips for every "event", Sonar becomes less responsive?  Is this only once the action has been completed?  Is it the same experience upon closing and then opening the session fresh?  What is your CWP filesize difference (before and after clip separation)?

I'm using AS in a 'Beat Detective' way where I split the clips at the start of the Transient marker.  (Where I would then try to quantize.)  However, the moment these clips are split (hundreds to thousands, depending on the note density of the drums), the session literally just stops being responsive.  I could liken it to a person trying to play a computer game with a GPU that is severely underpowered to play the game.  CWP filesize becomes very large after the clips are split.

Soulburned
Something tells me you may want to check your drives with HDTune or similar app, and look into the SMART status to see if there are any Reallocated Sectors Pending... This means sectors that are still marked as active and available for use by the OS are failing but the data has not been reallocated to new, undamaged sectors - likely resulting in stability problems.

My drives are perfectly fine.  This behavior is only exhibited within Sonar.  As I mentioned, I can edit drums much bigger in size with more notes-per-measure nearly instantly using Reaper 5.  Pretty much every aspect of multi-drum editing in Reaper 5 is nearly instant - from clip splitting, bouncing, saving, etc.  I'm honestly quite shocked how badly Sonar runs when trying to do similiar actions.
 

Soulburned
I would suggest also opening a support ticket and submitting your problem step by step if you can recreate it every time.  It would also help to know if this happens on just that particular project of if it's across "every" (multiple) projects with different material and different settings.

It's for everything.  I've even noticed these drastic slow-downs in the PRV with a lot of MIDI information.  I'm beginning to suspect it's a coding issue.  I could make a video demonstrating this.

I can only subscribe every word Scott just said.
I7 with SSD and 16gb RAM on my side

scook
When I read about audiosnap and large cwp, I recall this thread http://forum.cakewalk.com/FindPost/2901079

that also looks like a history thing; saving flushes the history, hence the ctrl/s helping, but if the last history step was corrupted, also explains not being able to re-open some projects
 
my speculation is: there's (a) bug(s) in the both the saving and recalling of history/do entries; i think it's caused by "disconnection" between "skylight" and the underlying older codebase; i'd bet a shiny euro ;-)
 
hth

Lord Tim
** Audiosnap has a BIG problem with ghost notes and weird detections. What I tend to do is put a gate on the kick and snare track and get them extremely clean sounding (to the point of them sounding bad, but so there's a definite attack to each hit, and no noise between the hits) and the bounce THAT to a new track. You can delete the gates after that. You new guide track will have super clear hits and Audiosnap will be a million times better at detecting the transients.

Actually I tried gating an already clean kick track bouncing it to a new track. The detection becomes a bit better, but is still unusable for me. Too many signals are cutoff in the middle. After copying the pool transients to the other tracks the program became very slow, and saving the project took about 5-10 seconds.
Like the others here in the thread I still have to switch to another program to do this kind editing. Fortunetaly I have both a Platinum and a Pro Tools License.
 
Here is a screenshot of the two tracks, the original one and the bounced one. You can clearly see it's not a ghost note or poor attack problem. It's simply buggy detection.

 

I'm seeing MUCH better results than that.
 
Here's my example:
 
I've cloned my kick drum track. In the track you're getting snare and tom bleed, which you can clearly see. Both tracks are in view, the top one is the one I'll apply the gate to, the bottom is untouched.
 
First, this is how I set up my gate:
 

 
EDIT: Link to full image here so you can see the gate settings better: http://i8.photobucket.com...ample1_zpsetnoatxt.png
 
Now bear in mind that this effected track sounds TERRIBLE. But it's only there for the detection. Essentially you're just getting pops where every kick hit is. 
 
After you apply the effect, it looks like this:
 

 
When I enable Audiosnap on the tracks, just leaving it as the default threshold, I get this result:
 

 
A closer look:
 

 
Full image here: http://i8.photobucket.com/albums/a3/lordtim/SONAR/as_example4_zpsrfejr3r3.png
 
As you can see, the bottom un-gated track is terrible. Early detections, ghost notes... you name it. Even playing with the threshold won't get you much better than that, and you'll need to do a heap of manual work to make sure everything is where it should be.
 
On the contrary, the top track is dead on the start of each transient where it should be.
 
As far as saving times goes, there's not a lot you can do about that. If you're making sure your multi-mic kit is all phase coherent, you'll need to apply the transients across all of the tracks at the same places anyway, so one extra guide track is negligible as far as save time goes.
 
Now don't get me wrong, I'm not defending Audiosnap - this NEEDS to be fixed. It's a tool I've used on literally hundreds of commercial tracks over the last year or two and the less screwing around I need to do to just make it work, the better! But the gating thing REALLY helps for me and dramatically speeds my workflow up.

Cheers, man! 
 
I think the other thing that needs addressing is the manual or the tutorials in using this. Cake's Dan Gonzalez did some excellent tutorials on multitrack drum stuff including a bit of Audiosnap things, and his methods - while effective - were a little confusing, and the manual made my brain hurt trying to understand the method they prefer you to use.
 
I don't think this stuff is as hard as it appears to be, and fighting with the tools is just making the matter worse...!

It sounds like there are really two issues here:
 
1) Audiosnap's transient detection could be a lot better.
2) Sonar's clip management needs to be more robust and able to handle lots of clips without falling over or slowing down.
 
I'm in...
 
Regards,
Dan
 

I too do this many times and agree there needs to be a lot of work done on this workflow. I also agree with Lord Tim about gating the guide track and also thank him for the detailed info. 
 
I thought I might also add a few random tips that I sometimes use that might help someone. 
 
- I find that quantizing without splitting works pretty well if you have very minor adjustments to make. If you have larger or more difficult problems it causes problems for me, so splitting becomes necessary.
 
- If you split and have lots of splits, yes saving and working with the data becomes really slow. As you put things back together they are not as slow any more. It would be nice to be able to select a section and work on it, but AS ONLY works on the entire track. So to work on a section, you have to split it somewhere (say at the end of the 1st verse) and copy that to another track. Then you can split/work on that section and "bounce to clips" to put them back together. Then copy that back to the original track, select the next section and do the same.
 
- I also sometimes use melodyne to quantize. Even Melo essential does a much better job of this than sonar. However, since you don't have multitrack, you have to align everything in a track to the grid, then do the same for other tracks to maintain alignment. If you have a pretty accurate track, this actually works better for me than doing it with audiosnap.
 
- Sometimes I'll use both. Split a group of tracks at beats 2 and 4 ONLY and align those to the grid on 2/4. This gets everything pretty close, but the beats in between are some times a bit off. Now bring those into melodyne one track at a time and quantize. Render those and bounce to  create clean tracks.
 
- Drum replacer can also act like a gate. Use DR to replace a kick track and it eliminates all the bleed just like a gate does.
 
- If you're not going to keep the track in the final, then don't worry about pops/clicks. Sometimes the final intent of my work is to create midi tracks from the part and trigger AD2. If I'm doing this, say for a kick track, then I can work on the original kick and not worry about the artifacts associated with splitting or moving around hits as they won't wind up triggering a note anyway.
 
- Another thing I've posted about that I wish would be changed is the behavior of grouping when you use AS to split. If you have all your tracks in a group, split them with AS, the result is that all the clips are still in one large group. What we really need is for each vertical slice of clips to be in a separate group as that's the way we want to work with them. If you split manually that's what happens. So if I'm going to only split on the 2/4 snare hits and maybe a few other place, then I sometimes create a group of the tracks and split them manually with the split tool. It's time consuming, but more accurate and everything winds up in the correct grouping structure. 
 
 
That's a short list of the top of my head. I'm also considering purchasing the studio version of melodyne 4 which does multitrack. Their method of working with "blobs" is better than the idea of working with transients. However, at the moment we would still be using it stand alone to edit multitrack drums and exporting/importing the finished tracks to sonar.
 
gabo
 

Once you do have the markers all quantized together, you *can* double click one and it selects all of the tracks with the markers that fall on the same beat... well, in theory. That works about 80% of the time, and other times it either selects none, partial, or grabs markers around the ones you're trying to select. Pretty annoying!
 
One good thing about the transient smart tool is it's easy to left-mouse drag around the markers you want to select and select them all. If you've quantized the track, just turn your project snap on and you'll be able to drag them to the nearest beat quite easily.
 
But I do agree, if you've got everything locked together, one marker should move the others by default when you drag it around.
 
Since I don't use the split method, I don't find any slowdown at all. In fact, if you check out the specs in my signature below, you'll see I'm running a pretty low powered laptop for my recording computer, and even worse, my audio drive is a USB2 external drive. But I'm getting very acceptable performance out of it, even on really big projects.  I'd expect that to change really fast if I decided to split at each transient, though! That would likely bring my machine to its knees!

Some time ago I posted some features for editing drums, maybe you agree with some of them:
 
- Tab to transient: Works wonders with individual tracks but starts to fail when tabbing with grouped clips, that´s really annoying
- Group clips: I wonder why when tracks are grouped if you select one track and make a split it doesn´t make a cut in all tracks, that slows a ton the workflow when cutting tracks to edit them to the grid so it doubles the steps to make a cut for all the tracks grouped.
- Grid lines: The only way to change the resolution of the grid is by enabling SmartGrid, but everytime you change the zoom it changes its resolution. A way to set the grid lines to your prefer resolution will be a major improvement
- AudioSnap: (This one has been address perfectly by Scott in this original post) Those who work professionaly need to speed up our editing time. Now audiosnap is the only way to edit multitrack drums ala BeatDet way. Your select your markers, merge them and cut. So far so good. Now it comes the bad part, the session begins to slow down, if you ever dare to save the session it will take maybe 10 minutes and 300mb size. That´s really bad and why I mainly switch to PT for that.
- Strech clips only works with one track at a time. So if you´re trying to strech your 20 drums tracks for some cymbal bleed you have to do it one by one :(
- Enable a quick quantize button that will move to the selected grid without having to set the parameters in the quantize menu, like you do on PT, just press a key and move. Bang!!
 

brundlefly
What you want to do is select all clips, and Apply Trimming to destructively apply the slip-edits, and then disable Audiosnap on all the clips, either using the AS Palette or the Audiosnap section of the Clip tab in the Track Inspector.

I'll give this a shot and see how it goes, thanks for the advice!