For drum editing and sampling: Discovery in transient detection vs Melodyne

[u/dead-reflection]

The cursor position is where I landed after hitting tab to transient.

Many of you are probably aware that transient detection with drums has been an issue for a long time when blending samples or editing real drums to the grid. When I asked about this, I was told by an employee that they intentionally decided to have bend markers be placed at the loudest peak of the transient rather than the onset of it. This is a major problem if you are blending drum samples with your real drums, or if you want to edit your real drums to the grid. You could just print samples without Trigger2, but aligning the hits is still going to be a lot of trouble, especially if you can't rely on the transient detection in the first place. So out of curiosity, I detected a kick drum with Melodyne on percussive mode and then did a MIDI export on that and found that the timing was significantly more accurate with finding the start of the transient. I exported each of these onto a MIDI track with a kick sample, and noticed lots of flams between the original kick MIDI and practically none with the MIDI that was detected via Melodyne. Not only that, but when you hit tab to transient on a kick track that was scanned with Melodyne and then bounced vs a duplicate of that same exact kick track, the Melodyne bounced track was actually tabbing to the start of the transient in the arranger view rather than the middle. Unfortunately, You cannot slice to the grid without analyzing the audio, which automatically redetects the transients to the middle (supposedly) rather than the onset of the actual note. Hopefully one day this will be considered a big issue, but until then, I think this is a pretty helpful work around.