Page 1 of 1

Possible Bug? Positional Sensing CC16 Sticking

PostPosted: Mon May 30, 2016 5:13 pm
by Kabonfaiba
Hiya Dmitri!

Instead of trying to explain this in words, I thought I'd shoot a video.



I think there is a bug that is stopping the CC16 Midi data from being transmitted to host at higher hit speeds.

There is not a problem with Megadrum module in detecting the PS at higher speeds, I think it's just the transmission.

I see the LCD displaying the correct CC values at higher speeds, but as you can see the sent CC16 data is "sticking" on it's last known position after a certain interval threshold.

Any ideas?

Re: Possible Bug? Positional Sensing CC16 Sticking

PostPosted: Mon May 30, 2016 5:21 pm
by dmitri
MegaDrum will use previously calculated position if the next hit is closer then NoteOff delay. Reduce NoteOff delay to below of your hits intervals.

Re: Possible Bug? Positional Sensing CC16 Sticking

PostPosted: Mon May 30, 2016 8:48 pm
by Kabonfaiba
Well I feel stupid. Yes, that solved it! :lol:

I definitely think you should add this information to the MGM tooltip for Note off delay.

So is there a trade off to having a higher or lower Note off Delay? There must be a reason we are allowed to change it surely?

Re: Possible Bug? Positional Sensing CC16 Sticking

PostPosted: Mon May 30, 2016 9:07 pm
by dmitri
The NoteOff delay setting came first. I chose a random default value of 200ms for it. Positional sensing came later and I used it as an interval for sticking the same positional value instead of introducing another setting. You may want to use higher NoteOff delays for some percussion instruments where you don't want to cut the the sound too quickly.

Re: Possible Bug? Positional Sensing CC16 Sticking

PostPosted: Mon May 30, 2016 9:24 pm
by airflamesred
As Dmitri sais, Generally, drums will have a set length of sample and note off wil not make much difference. Something like a vibraphone, one could use it to imitate pedal, for example.