Ok, so I've figured out many ways around this, but since Platinum is suppose to have a new algorithm for audiosnap and transients I thought I would give my 2 cents on this. 
 
This works better than before, but still needs a lot of improvement. Here's the major thing I think should work a lot better. Transients on things with very clear transients, like drums, don't seem to work quite right. Let's take an example. 
 
If I have a Kick track. For my recordings this is the easiest thing to discuss, I get a lot of isolation from a mic I put inside the drum. There are very clear kick events, VERY CLEAR. 
 
If I could draw a line on the clip view, I could very easily position a line and say "everything above that line is a kick hit or what I would call a transient" and it would be 100% accurate and easy to do. 
 
However, when I turn on transients, and play with the threshold slider... There will be clear kick hits that don't get identified while there are very very small things (who knows what) that do get identified. No matter how I adjust the threshold I can't get 100% accuracy on the kick hits. 
 
Why is this so hard to get right? Individual drum tracks should be the easiest "no brainer" case for transients and audiosnap and it should be 100% correct.
 
I do this on every recording I make as I always layer kick and snare and mix, so making this work better would really help my workflow.
 
gabo

I'm afraid I have to agree completely. I think people have mentioned before that it works a lot better if you really clean up the track first, I suppose processing it with a gate or something. But I can totally reproduce this behavior - something with a very clear transient will not get detected or will be detected way before it actually starts, etc.

Yes, forgot to mention the "way before" or "way after" cases. There are always some of these and it's easy to reproduce as it happens every time.
 
My method of dealing with it is to gate it, tweak the gate to get short spikes, freeze the track, and then drag it to a midi track. Then I unfreeze the original track and remove the gate. That works well, but why should I have to do all that every time I make a recording?
 
gabo

Hi gabo,
Yep, I have to agree as well...in fact, AS is still one of the things that is (IMHO) most lacking in Sonar. Between weird transient detection, insertion of transient markers at quarter-note intervals (CWBRN-31368) and clunky workflow on multi-track editing, I'm still exporting drum tracks to a different DAW that I, *ahem*, "don't fear" for drum editing.
 
Sonars pros still outweigh the cons for me, but AS still could use some real work.
 
Dean

What DAW do you use for drum editing? Is it a windows DAW? I might try the same if you've found one that works better. 
 
I have been a Sonar user for many years and will continue, but if I could export drum tracks to something that works much better and then bring them back, I might give that a try. 
 
gabo

Hi gabo,
It's generally considered mildly bad form to directly reference a competitors product on the forum. I'll PM you.
 
Dean

Yea, sorry for that Razor. 
 
Wow, after reviewing, Sonar really does have a lot of work to do to make multitrack drum editing competitive.
 
We really need to try to put some pressure on Cake to get this sorted out.
 
gabo

If you have specific steps to repro from a new project, that's easy enough to follow for somebody who hasn't used this functionality before, please create a thread in problem reports forum.

Record any significant stretch of audio, preferably multitracking with several mics. Turn on AudioSnap. Observe.