I am trying to generate MIDI notes from a kick drum track so that I can layer a sample from Session Drummer to beef up the sound. I am using X2 Producer.
 
In general, X2 works great, but sometime the transient is well ahead of the actual kick drum hit and I can't explain why. There's just a tiny bit of mic bleed. Why does it get it right so often, but then goof up other times? FWIW, when wrong, the transient is always early, usually in the 10 - 30 tick range.
 
If I don't manually check every drum hit / transient, I get occasional flams because the audio transient (and therefore generated MIDI note) is ahead of the actual kick drum hit.
 
I know I can manually move the transients to right spots before creating the MIDI notes, but are there settings somewhere that would let me tweak how audio transients are identified? I would say 95% are close enough for rock and roll, but it's that 5% that takes forever to find and fix (basically checking every drum hit in the whole track).
 
Here's a photo of what is going on. Note the transient is well ahead of the drum hit, enough for audible flamming. The MIDI note generated by AudioSnap is on the track below.
 

Happened so often for me I gave up on Audiosnap.

Hi
 
Did you find out how to fix it ?

Sometimes depending on the settings of audio snap, the transient will go where the transient begins, just like the picture you provided. The marker is set perfectly to where it begins. If you look at your picture, You'll see a flat line and then when the audio starts, that is where that marker begins. The transient is actually lined up perfectly to where the audio begins. To get it to the peak, you may have to move them manually to get it there or adjust some settings like the threshold and beats.
 
CJ

garry
In general, X2 works great, but sometime the transient is well ahead of the actual kick drum hit and I can't explain why. There's just a tiny bit of mic bleed.
 

 
That bleed is your answer. Audiosnap can't tell the difference between a kick transient with bleed (or maybe beater noise?) preceding it, and some other instrument with a slow initial attack. You wouldn't want to have that attack separated from the transient in other circumstances so the transient marker is placed to include it.
 
In the absence of a built-in Audiosnap parameter you can set to ignore signals below a certain level, the workaround is to destructively gate a copy of the track (Process > Remove Silence works well for this) and extract MIDI from that gated audio.

I have the same issue, the workaround I use is...
Insert a noise gate plugin in the kick drum track and check the threshold for not loosing any kick hit.
Process the plugin and delete it.
You will see that the kick hits are perfectly cuted (no Little line before the hit)
 
After that, engage audiosnap on the new procesed clip and the transients are perfect.
 
Daniel
 
 

How is it that the "threshold" control doesn't take care of this?

Threshold is for including/excluding markers based on peak amplitude. It has no affect on marker placement.

would bee god if that had a threshold control to , so it didnt trigger the markers to fast

Like on the pickture , its almost no sound before the transient hits

brundlefly
Threshold is for including/excluding markers based on peak amplitude. It has no affect on marker placement.

Right, thanks. In that case I agree with Lydmann.
I'll try the gating thing, though it still seems weird to me AudioSnap's algorithm doesn't handle this more intelligently. Many other solutions seem to.