I just got the Sensel Morph and have set it up with the piano overlay MPE to use it with my modular system via the Expert Sleepers FH-2.
I noticed there was something not quite right about it and figured out that it is the Velocity response. When I hook the Velocity output (mapped to output 2 of the FH-2) to an oscilloscope, it shows that it can’t go lower than approximately 3V, even if I set the Threshold in the SenselApp to 0 (I’ve also tried 10). Everything else (aftertouch and slide) responds perfectly between 0-10V.
I have tested the FH-2 with the Roli Seaboard Block and there is no issue with the FH-2 - it responds to velocity between 0-10V.
Is this a particular issue with my unit? Have I set it up incorrectly? Can it be fixed with an adjustment in the firmware code?
So I have noticed this problem seems to exist when using software (like the Roli Equator) and also in any software on the iOS on my ipad so it seems like its to do with a setting on the Morph. Is it possible to allow users to adjust the sensitivity range (it would also be great to be able to adjust the sensitivity curves for all parameters).
+1 for sensitivity curves. Threshold is good, but doesn’t help how hard you need to hit/press to get higher velocity notes. I need to practically beat on the piano overlay to get any velocity over 100. So, I end up needing to either adjust every curve setting in my DAW, or add plugins to do it, which is inconvenient.
If threshold is set to 0-3, aftertouch works perfectly but velocity is too hard. I can’t hit soft velocity like 0-50.
I currently set threshold 4, velocity works a bit better but of course aftertouch threshold is high.
Is this being looked at? Because its definitely a bug. Every other parameter is 0-10V. Just the Velocity is 3V. This is disappointing.
The only reason I bought the Sensel Morph is because I was told in the demo videos about its higher resolution and sensitivity in mpe, and its versitility in being customisable. Now that I’ve bought it I find that the firmware settings are somewhat limited.
Does anyone know how to revert to a previous version of the firmware? I want to see if maybe this problem didnt occur in previous versions.
+1!!! Waiting hard for velocity/ sensitivity curves for music production overlay. For Fingerdrumming is this feature absolute necessary. Hope there is something in the pipeline…
Hi @Ebee. We don’t have any updates to offer at this time. Thanks for your continued patience, we will certainly make an announcement once this is addressed.
Bump.
It’s been over a month since this issue was last mentioned.
Has the issue been acknowledged? It it being assessed? Is a fix in progress?
This is a showstopping issue for an otherwise amazing device!
We’re currently hiring support to help with issues like this. I can’t give a precise estimate but we are completely aware of the request and will be working to address.
@Ebee Thank goodness that’s not the case! He’s still very much here doing great work. We’re hiring support to work directly with him in North Carolina.
Hi, could I get an update on any progress being made to address this velocity issue? Testing this out, the lightest touch on the morph registers a 16 value in midi with the Threshold set to 0.
I came to post about this issue too and found this thread. The SenselApp should have curves for everything, like the Roli software has.
But more basic then that, the velocity response needs to go from 0 to 127. That fact that it doesn’t is simply a bug that needs to be fixed. If I rest my fingers on the Morph and gradually press down until it registers a note, the lowest velocity I can get is about 32! If I carefully try to tap a note really gently and quickly then I can get down to about 16, but this is not reliable. Generally the lightest I can do with normal playing is 32 or 25% velocity.
Besides the low velocities, the high velocities are reached too easily, in my opinion. When I view the pressure in the Visualizer I see that the force I use to get full MIDI velocity is only about 1/5th of what the Morph is capable of reading, and maybe 1/3 or 1/2 of what I could reach if I really hammer single notes when playing. (It is harder to achieve the same pressure levels with multiple contact points, playing chords.) I suppose you want to leave some headroom for aftertouch? I don’t know how that all works. Anyway, different people would obviously have different preferences for this but I figure if it was set up so that the velocity response was about 2/3 of what it currently is, then it would partly solve the problem with light notes and then you wouldn’t reach full velocity so easy.
The ultimate solution is to have editable curves, but at minimum fix the low velocity bug and have an overall sensitivity setting with a high range that users can set to their preference. And it needs to be a general setting for the Morph, not attached to individual notes!!!
