Oh that’s awesome that you got it (mostly?) working.
I kind of just hacked it together just to make it work for my setup, with hopes that it’ll be possible to do in Cubase eventually, so the code isn’t very neat.
It doesn’t work properly with relative settings unfortunately, due to how I am handling the logic about not receiving MIDI feedback. Basically I check to ensure that the value I send is the value Cubase thinks the parameter is, and this wont match up well with relative values. It does work, just a bit imprecise.
It is definitely made for absolute values.
Definitely keep us up to date if you think of any clever ways to work it out.
At least before the .50 update, there was no way of scaling controllers that send relative values. They were always scaled as being 7bit values. That made me start using the API instead. But still I haven’t been able to get the encoders jitter free. Especially with fast encoder movements.
Ohh right of course.
Yeah I made an adaption to handle encoders and faders without jitter, but relative is not as easy to manage.
I am more concerned with the Midi Remote Editor bugs with sending incorrect and extra values not being fixed with this update.
Any word on if this bug is something that is nearing a fix? It’s really frustrating to not be able to make use of the MIDI Remote Editor, since it does look so nice, and is easy to use. But at the moment it is unfortunately entirely useless for any control that requires MIDI being sent back to it.
I’m using Lemur and I wanted to set it up to Midi Remote.
The irritating thing about Midi Remote is that it refuses to allow you to change your MIDI Input/Output Ports once you’ve set them. Right now, I’m experiencing the same thing you are - alot of jittering and lagginess. I have a feeling it’s to do with some MIDI feedback loop of some kind.
If you use a MIDI monitor and monitor what messages get sent and received it’ll become a lot clearer.
There are issues with feedback, delayed messages, and also there is a rounding bug causing some values to never return the correct value (I have documented my findings and I do believe Steinberg acknowledged it some months ago, but I can’t recall by now).
I am a bit surprised we’ve not heard or seen anything regarding this, and I really hope we won’t have to wait for the next paid release of Cubase to get this fixed…but on the other hand… by now I’d be okay paying as long as they can assure us that the Midi Remote will be usable.
Hi guys, does anyone know when using a controller is it possible to reset a plugin parameter to default value by pressing the encoder switch? I’m sure this used to work but don’t see that behaviour at the moment.
I did this by mapping both knob and button of a push encoder to the parameter, and setting the button min and max values to 50% (or whatever you want your default to be). And it must be in jump mode.
Worked in this case, but I don’t think there is a generic set to default for quick controls etc. Maybe it can be done in a script.