I was wondering it just based on the fact that the main snare and kick hits (exclusing gost notes) for most of the midi grooves are at 127 for most of the hits. Not saying that there are no dynamics at all, as you highlighted there are ghost notes and some soft hits, but practically all the hard hits are at 127. So if the 127 velocity is linked to a sample that is recorded with the drummer hitting the drum as hard as he can (which would generally not happen in the middle of a drum performance) it would make sense to either adjust the sensitivity of the edrum to get a more realistic response during hard hits or to not include those extrema hard hits samples in the main articulation (those could be included in a hard hit articulation for example).
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
Yes, agree.The recommendations are not aleays consistent with whats provided in the MIDI pack so this leads me to think that either (or both):
1) The sensitivity of the eDrum used to track the MIDI should be ajusted so only ocasionally the 127 velocity is achieved
2) Drum libraries should be tracked so that the hit at 127 corresponds to a physically realistic hit of a drummer in the middle of a performance, as opppsed to hitting the drum as hard as possible (I think the SD3 core library does an overall good job on that)
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
If the MIDI is as the drummers play it, maybe the sensitivity of the e-drum used to track the MIDI should have been adjusted according to the intensity of each drummer in order to capture the dynamics in the upper velocity level for heavier generes? Not complaining about it, just thinking out loud for the sake of learning how to better use MIDI packs and program my drums.
Cheers
Josh
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
I’ve found the same thing. I bought several packs so that I could learn from them on how to make my programed drums more realistic. I’m wondering whether there was any processing of the MIDI timing and velocity data after those files were recorded or they are delivered “RAW” just as the drummers played them?
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
Thanks for your reply. Indeed, I use the invert selection trick quite often in combination with the exclude function as well . Just noticed today the bug with the exclude function (not sure why I have not noticed it before!).
I take the opportunitty to make a suggestion. It would be useful to enable a custom selection patern (e.g. select 1st and 3rd notes every 7 notes; where all those parameters may be user defined)
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
I’d be interested to know how you change the MIDI note length within SD3. I’ve been looking but have not found any place to do that. It would be really useful to shorten MIDI notes from MIDI files imported from other software (e.g. in Guitar Pro MIDI note length last until next note being played) and prevent Song block merging when humanizing due to overlap.
Reply To: Changing Midi Note Length In The Grid Editor. version: 3.3.6 Operating system: Windows 10
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
Hi, I’ve been dealing with that issue for a while. Any plans to fix it in a new update?
On the meantime I have more insights on the issue. It also occurs when apliying randomize to the grid position of the notes when:
– The note was at the begining of the song block and is moved backwards to the previous block, then the current song block will be merged with the previous one.
– The note is towards the end of the current song block being edited and the tail of the sound (eg a ringing Ride hit) would still be heard in the next song block, then the current song block would be merged with the next one.
Hope that helps!
Cheers
Check out my youtube channel https://www.youtube.com/user/joshguitarreiru
