BUG: Empty pads, plugins, sample slicing to pads and keys, bogus midi data and strange behavior.
On initial pad view 16 with an empty bank and all settings at default, pad 1, 17, 33, et cetera all the way through page 8 produces note velocity NOTE ON/OFF value 127. NOTE ONs/OFFs for pads 2-16, 18-32, 34-48 et cetera produce independent midi channels 2-16 instead of a single channel and NOTE ON/OFF velocities for 100 instead of 127.
Then Inside keys of page 1-8 base key produces NOTE ON value 100. NOTE OFF value is 127. All other notes are outputted correctly but velocities are at 100. All have independent channels.
Then, move view to 64 view on page 1. Tap a pad. Velocity for all pads across all controls will either become 100 or 127. It is never consistent. Then loading a plugin first and a sample second or the other way around (I’m not sure exactly which it is) on the same pad in bank may produce Backwards note on/off velocities for all keys in that pad especially if you touched an empty pad in keys mode before loading. So note on is 100, note off is 127 for velocity.
Also slicing samples to pads or to keys sets the velocity all wrong. again another 100/127 mess.
The first impression I got in the manual since it’s one of of the things stated is empty pads record MIDI themselves. So what I did was start using them as a tool to capture midi grooves in my head when I didn’t have time to trial samples (had no samples loaded yet, no purchases, whatever) and saved these banks. Now loading a sample on an empty prerecorded pad is always messed up midi velocity or even worse, none of the midi pattern captured correctly in the first place with empty pads. Maybe do to the fact every 16 pads has channels 1-16? It’s all messed up.
It has been like this since at least 3.05 if not the very beginning? Why is velocity 100 and 127 a thing with slicing and/or empty pads? Especially the velocity when slicing. It is not good to make users have to potentially redraw a potential maximum of 64 automations per slice. Also what if a person clears the pad to keep the midi that was captured but then begins to record new Midi on that empty pad without a new sample loaded immediately or when slicing to that pad later? Guess what. Bogus midi!
I will do a video sometime when it isn’t 2 a.m and I’m not upset I had to trash my bank of mental ideas.
Would love at least an explanation to why MIDI is not really useable at all with empty white pads. It doesn’t record right on so many levels and slicing defaults to 100 velocity in automations. Who knows maybe this is the cause of a ton of other problems indirectly related users have had.