TIXE DOPE wrote:When I used a Midi controller (Samson Graphite mf8) I would have to turn the nobs really fast and hard for it to trigger In the app and when they did trigger the parameter in the app would only go so far and then stop. And if I would try to turn the nob to adjust it the parameter would reset and go back to zero and I would have to turn it again and again. (almost like the "initialize parameter automation" function). Same with faders, any time I move a fader it resets and starts from zero no matter where the actual fader on the controller is held.
That sounds like your controller is sending relative parameter values (+1/-1) instead of absolute values (0..127).
Please check your controller configuration. There must be an option to switch the knobs from relative to absolute.
G-Stomper does only handle absolute cc values from 0 to 127.
TIXE DOPE wrote:also when play keys on a keyboard (arturia minilab) you have to hit the keys really hard and fast for them trigger, and even though you hit them very hard every time there is still a big variance in velocity from very quiet to loudest. I was hoping there would be a velocity range or a set velocity that could be preset for your keyboard.
That is actually weird.
How do the knobs react on the minilab? Same behavior as the Samson Graphite mf8?
Do you have multiple controllers connected to G-Stomper at the same time?
Try it with the minilab alone, and without any USB hub in between.
Also try another USB OTG cable + another USB cable (not all cables work well with all devices).