Making CTRLR for guitar devices, need help with latest addition RJM Overture

[verchrona]

Hi,

I have been at this Panel to control numerous Guitar devices. 4 of 5 devices work. I just got an RJM Overture pedal and did some controls for it.

The first 3 rows work perfectly with those specific units. The last row is dedicated to the RJM Overture. All the controls work perfectly. The annoying part about the pedal itself is that, everything "Drive Mode" is changed, it sends all current knob locations values. So basically, if I have the all the controls on the CTRLR Panel at noon, but the hardware is at at different settings... just changing the Drive Mode via midi will also make the Drive, Bass, Treble, Boost, Volume change values to whatever the hardware was parked at.

I figured out the solution is to: >>> everytime Drive Mode is changed via CTRLR, it reads the current values of Boost, Drive, Bass, Treble, and Volume on the CTRLR panel and also sends those values to the hardware. I wasn't able to get it working with a built-in Multi Type message.

Is this something that needs to be done with the LUA editor? Or can I somehow make the Drive Mode modulator read and send other modulators' values when the Drive Mode is changed?

This is my panel attached.

G-DEVICES (DRIVE MODE MUST SEND BOOST, DRIVE, BASS, TREBLE, VOLUME CC MESSAGES).zip

[damiensellier]

On the "drive mode" knob you set the midi message to "none", it should be set to CC.

All cc controls should work independently without interfering with each other especially if you assigned the different raws to different midi channels.
What you need is a way to read the current settings value and assign your ctrlr knobs at the right position. It's usually done by decoding a sysex message but I'm not sure if your pedal sends one. The pedal can also send CCs to update the value for 2way communication.

Are you sure the parameters reset on the pedal when you change the drive mode or when you start Ctrlr? in this case you need to disable either "modulator does not reacts to value change" or/and "Modulator does not output any value on startup".

That would be great to know if you receive anything FROM the pedal if you change parameter values or when changing a program.
If not, It will be impossible to display the current position on the Panel and you will only be able to update the value if the Ctrlr knob is changed.

Let me know
Damien

NOTE : https://www.rjmmusic.com/download-content/Overture/Overture%20Manual-1.3.pdf

[verchrona]

This is absolutely incredible. I didn't expect the code to have to be that long. I greatly appreciate you taking the time to write this code to implement with the hardware unit. It actually fixes the bug that I believe is built into the Overture pedal.

The pedal itself is rather finicky and only connects via USB whenever I'm lucky haha. What's strange about the Overture's USB driver is that once a DAW occupies its Midi ports, and even if you shut down the DAW after that, the midi ports will remain occupied until the computer is restarted. I tried this with a couple programs and it doesn't free itself after the program using it is closed.

I realized the BOOST knob actually requires the same implementation as the other 4 knobs. I went ahead and did what you did to the other knobs and applied it to the BOOST knob as well. I modified the DriveModeKeepsValues lua page only, and didn't update the DriveModeForceValues, because I was unsure what to put after "setvalue(number, true)". But I think its working without changing the DriveModeForceValues. Is it ok not to update that Lua page or does it have to be done to have the BOOST modulator behave like the Drive, Bass, Treble, and Volume?

The updated panel is attached:
G-DEVICES (BOOST REQUIRES SAME IMPLEMENTATION).zip

[damiensellier]

You're welcome!
You have 2 different scripts on the panel I posted covering both options. You should be able to work from there now that you have the different required LUA functions.
Don't hesitate to ask if you have other questions during your project.

If you prefer using a midi din 5 pin instead of USB, you can get a cheap USB MIDI cable since there's no SYSEX messages. They work fine with short compliant MIDI messages. Maybe you already have some MIDI ports on your inteface ou should try if the pedal works better with it.

Enjoy!

Damien

[damiensellier]

@verchrona

I modified the DriveModeKeepsValues lua page only, and didn't update the DriveModeForceValues, because I was unsure what to put after "setvalue(number, true)". But I think its working without changing the DriveModeForceValues. Is it ok not to update that Lua page or does it have to be done to have the BOOST modulator behave like the Drive, Bass, Treble, and Volume?

You can even remove the one you don't need.
The script is assigned when you clicked on the "Drive Mod" knob with the property pane open and go to "called when the modulator value changes" :

If you want to remove a LUA Method just open the LUA method editor, right-click the method to remove and well... remove it :)

[damiensellier]

NOTE: you can also have values you like as default for the different Drive Modes sent to the pedal with the other method. I wrote some statements if ... then for the different Modes so, depending on the Mode you switch, you can have different values set up.

[verchrona]

Ah, now I understand how choosing the script for the modulator works with the drop down menu. Thanks again for everything!