I just gave this a try, seems a lot better for responsiveness on the Thunder overlay's top row. I'd need to try it more to see if it is fully fixed but it is certainly a ton better. Took too long but I am glad it has been updated. Thanks a lot
I definitely struggled with both issues and this update is a nice improvement. The lower velocity range is a lot easier to reach in a way which feels natural, but the upper limit is reached a little too easy (talking about threshold 10). Can't complain too much overall, this was a good update. Thanks.
Thank you for the kind words! We're really glad you're finding it useful. Appreciate your note on the upper limit, this is exactly the kind of feedback we need to continue improving the experience.
The firmware version is already up to 0.19.298. It required multiple updates to get there. I just kept pressing the red Update button until it finally went away and the Firmware version was reported as 0.19.298 (Up To Date).
Ah, sorry to hear it didn't just go through the first time! Glad it finally got there. If anyone else is having this issue, please feel free to reach out to support@sensel.com
This update does not address bluetooth issues. It is very much on our radar though and we plan to address it in the future. We really wanted to get some of these improvements out there, but there are still many things we are working on! Appreciate your patience.
This seems to not work correctly in Bitwig. For VSTi I have to set Bitwig's PB range to 24, while instrument is set to 48 to get it working. Bitwig's devices are always behaving bad.
I just checked Sensel Morph controller script which is shipped alongside with Bitwig. This is version 1.1.3. You can find setUseExpressiveMidi(true, 0, 24); slapped all over the place. So I copied controller script, made new version of it and replaced all setUseExpressiveMidi(true, 0, 24); to setUseExpressiveMidi(true, 0, 48); and it finally works correctly. @Sensel you should fix your controller scripts :)
You can download a fresh script from github.com/sensel/sensel-controller-scripts. Click on the IO panel (bottom right of bitwig, with 2 stacked arrows) to access the options for the script. You can set the bend range to "48" with a toggle.
@Neraremas: I should add, we 100% agree with you that it's poor UX and non-intuitive. We unfortunately had to implement it that way to include it in this update. And it also gives us an opportunity to get feedback on the new velocity scaling, which we'll then use to refine it and create a long-term solution that's more intuitive - where you can choose your velocity scaling and activation threshold independently. Thank you for taking the time to leave your feedback. 🙏
@@SenselInc Independent velocity scaling and threshold would be really nice! Ideally also the option to set up custom response curves. Sometimes an exponential or logarithmic response would be much more practical for example, especially when used with a modular synthesizer.
Hey! The new pitch bend method works for any overlay, including the Buchla Thunder. It quickly settles to the note of the area under your finger, which is an improved experience.
There are no plans to release a grid overlay at this time, but this can be done with our overlay designer! Some folks have been kind enough to share their designs in our forum: forum.sensel.com/t/12x6-linnstrument-mpe-grid/639
Since threshold 10 has been redefined to mean threshold 3 with improved scaling, does that mean that all controls currently assigned to threshold 10 (before the upgrade) should probably be reassigned to threshold 9? Or does the change only apply to controls that employ scaling? In other words, do on/off state buttons have new behavior with threshold 10? Currently on my Buchla Thunder overlay I set all the top control buttons to threshold 10 to minimize the likelihood of accidently activating them.
Thanks for reaching out. Yes, you'd want to set them to 9, otherwise they're activation threshold would act as if it was at a 3. The improved scaling setting is an inelegant workaround, so apologies for that.
@@SenselInc Thanks for the prompt reply. Hopefully you will have a new release of the software to go along with another firmware upgrade that gives proper control of the velocity scaling, whether it be at the control level, or global level. Currently I work around the problem within Vital by using a non-linear remap of all modulations. But it must be set or copied for each affected modulation. Hopefully this update will eliminate the need for the remaps.
I just gave this a try, seems a lot better for responsiveness on the Thunder overlay's top row. I'd need to try it more to see if it is fully fixed but it is certainly a ton better. Took too long but I am glad it has been updated. Thanks a lot
Thank you for the feedback! We're glad it's an improved experience so far. Agreed, we wish we could have pushed this out sooner.
I definitely struggled with both issues and this update is a nice improvement.
The lower velocity range is a lot easier to reach in a way which feels natural, but the upper limit is reached a little too easy (talking about threshold 10).
Can't complain too much overall, this was a good update. Thanks.
Thank you for the kind words! We're really glad you're finding it useful. Appreciate your note on the upper limit, this is exactly the kind of feedback we need to continue improving the experience.
Very very nice Sensel does it again
thank you!
Great so much better thanks!
Very glad to hear it!
The firmware version is already up to 0.19.298. It required multiple updates to get there. I just kept pressing the red Update button until it finally went away and the Firmware version was reported as 0.19.298 (Up To Date).
Ah, sorry to hear it didn't just go through the first time! Glad it finally got there.
If anyone else is having this issue, please feel free to reach out to support@sensel.com
Does this firmware address any of the Bluetooth issues? It's barely useable on MacOS for mpe
This update does not address bluetooth issues. It is very much on our radar though and we plan to address it in the future. We really wanted to get some of these improvements out there, but there are still many things we are working on! Appreciate your patience.
This seems to not work correctly in Bitwig. For VSTi I have to set Bitwig's PB range to 24, while instrument is set to 48 to get it working. Bitwig's devices are always behaving bad.
I just checked Sensel Morph controller script which is shipped alongside with Bitwig. This is version 1.1.3. You can find setUseExpressiveMidi(true, 0, 24); slapped all over the place. So I copied controller script, made new version of it and replaced all setUseExpressiveMidi(true, 0, 24); to setUseExpressiveMidi(true, 0, 48); and it finally works correctly. @Sensel you should fix your controller scripts :)
@@JazJazgot Thank you for catching this. Speaking with the team to see how we can best address!!!
You can download a fresh script from github.com/sensel/sensel-controller-scripts. Click on the IO panel (bottom right of bitwig, with 2 stacked arrows) to access the options for the script. You can set the bend range to "48" with a toggle.
We will update the installers soon.
@@SenselInc Thank you! This was quick!
So "10 (High)" *really* means the threshold is 3 but with new velocity scaling? What kind of insane UX is that? Who came up with that?
It's certainly a work around!
@Neraremas: I should add, we 100% agree with you that it's poor UX and non-intuitive. We unfortunately had to implement it that way to include it in this update. And it also gives us an opportunity to get feedback on the new velocity scaling, which we'll then use to refine it and create a long-term solution that's more intuitive - where you can choose your velocity scaling and activation threshold independently. Thank you for taking the time to leave your feedback. 🙏
@@SenselInc Independent velocity scaling and threshold would be really nice! Ideally also the option to set up custom response curves. Sometimes an exponential or logarithmic response would be much more practical for example, especially when used with a modular synthesizer.
I'm curious how the pitchbend change will effect the Thunder?
Hey! The new pitch bend method works for any overlay, including the Buchla Thunder. It quickly settles to the note of the area under your finger, which is an improved experience.
@@SenselInc I'm using a midi to CV converter (Shuttle Control), any idea of what CV range we should be setting?
Please tell me will Morph be able to support midi 2.0 in the future?
Hi Matt
Did you add the ‘missing’ midi note zero for vst keyswitching?
Unfortunately we could not get to it for this update, but we have not forgotten about it!
Are there plans for such a grid overlay anytime soon?
There are no plans to release a grid overlay at this time, but this can be done with our overlay designer! Some folks have been kind enough to share their designs in our forum: forum.sensel.com/t/12x6-linnstrument-mpe-grid/639
@@SenselInc A grid overlay would be fab especially for us Ableton users that have Push/launchpad etc, would be a natural nice addition.
@@thegoony 100%. It's something we'd love to do. And thanks for your suggestion - we've added it to our tracker.
Velocity is still hard to use.
Please add the ability to set min/max midi CC values.
Thanks for the feedback Forrest!
Thankfully, the update affects the lift scaling in the same manner as velocity - much nicer.
Excellent, we are very happy to hear it's been a nicer experience!!!
Since threshold 10 has been redefined to mean threshold 3 with improved scaling, does that mean that all controls currently assigned to threshold 10 (before the upgrade) should probably be reassigned to threshold 9? Or does the change only apply to controls that employ scaling? In other words, do on/off state buttons have new behavior with threshold 10? Currently on my Buchla Thunder overlay I set all the top control buttons to threshold 10 to minimize the likelihood of accidently activating them.
Thanks for reaching out. Yes, you'd want to set them to 9, otherwise they're activation threshold would act as if it was at a 3. The improved scaling setting is an inelegant workaround, so apologies for that.
@@SenselInc Thanks for the prompt reply. Hopefully you will have a new release of the software to go along with another firmware upgrade that gives proper control of the velocity scaling, whether it be at the control level, or global level. Currently I work around the problem within Vital by using a non-linear remap of all modulations. But it must be set or copied for each affected modulation. Hopefully this update will eliminate the need for the remaps.
You sound like Jeremy from Red Means Recording 🙂
We will definitely take it!
unfortunatly, Sensel Morph is down, now, in 2022.
Maybe coronavirus i guess, so i guess Sensel will be back soon
Unfortunately the morph is discontinued. Announcement here morph.sensel.com/blogs/news/sensel-morph-sunset
@@SenselInc LoL !