Feature request: velocity-dependent notes

[dmitri]

I'm not really understanding why to handle this in megadrum and not just in the PC? This is already very common in many samplers.

This is what I suggested in my first reply. I don't want to waste MegaDrum MCU internal resources for something which is not really useful.
So is this "velocity layers split" function needed/wanted or not?

I'd like to keep the alt note feature for use with L/R articulations.

If implemented, this new function won't break any existing functionality so you'll be able to continue using layering the way you do it with alternative/pressroll notes.

[ignotus]

I'm not really understanding why to handle this in megadrum and not just in the PC? This is already very common in many samplers.

Maybe in many but not in all - for me and for others it means using another application to remap the midi data. I know, it's not really that hard, but if it could be done in MD, it would simply make things easier.

This is what I suggested in my first reply. I don't want to waste MegaDrum MCU internal resources for something which is not really useful.
So is this "velocity layers split" function needed/wanted or not?

If it'll hog resources that might be better used for other improvements, then I'd say forget it - but I thought it wouldn't have an impact? Either way, now I know how it can be done by other means I understand if you'd prefer not to implement it.

[dmitri]

If it'll hog resources that might be better used for other improvements, then I'd say forget it - but I thought it wouldn't have an impact?

It won't have immediate impact since there are still spare bits/bytes in the already allocated config structure. It's just if I use these spare bits/bytes for this function now, then for any new (more useful?) feature I will have to expand the config structure which may make Atmega644 based MegaDrum unlucky.

[ignotus]

It won't have immediate impact since there are still spare bits/bytes in the already allocated config structure. It's just if I use these spare bits/bytes for this function now, then for any new (more useful?) feature I will have to expand the config structure which may make Atmega644 based MegaDrum unlucky.

Hmm... as the owner of an Atmega644-based MD (I already upgraded from an Atmega32 a few years ago) I think I might prefer to hold out for something more critical that couldn't be done with the PC... I've done some testing using qmidiroute and it does the job nicely, and a couple more clicks when setting up my kit isn't going to kill me

[airflamesred]

Ok, I shall be moving to Kontakt next month, and has been pointed out this stuff can be done elsewhere, so lets see what crops up.

@Mbira I don't know whether your older post got resolved but I found this
http://www.vi-control.net/forum/viewtopic.php?t=34135

[dmitri]

I understand that the conclusion is that it can be done in a PC and not a functionality which should be implemented in firmware.
Good that I didn't start implementing it
It was a nice discussion so if anyone has any other features requests, don't hesitate to post them in the forum!