I can´t get OSC to work.
On the elk-pi I started (over SSH and Ethernet) the JX 10 Synth and its running fine with MIDI keyboard working.
Then I started Open Stage Control (Mac OS) like described here.
The “send” IP then is prefilled with the local adress of the elk-pi.
Though I didn´t change anything in the Sushi config I left the port as is (24024).
After loading the template, there are errors shown in the debug window.
Might be Open Stage Control not digesting the hostname as passed in that way.
First advice from your log would be to use elk-pi.local as hostname instead than mind@elk-pi.local (it’s a simple UDP connection so there’s no authentication needed). If this doesn’t work, try to use the board’s full IP address as reported by ip a or ifconfig.
You can debug incoming OSC connections with oscdump without launching SUSHI, e.g. launch:
$ oscdump 24024
inside the RPi and you should see incoming messages.
First advice from your log would be to use elk-pi.local as hostname instead than mind@elk-pi.local (it’s a simple UDP connection so there’s no authentication needed).
This didn´t work.
The IP adress seems to be 127.0.0.1. Shown in ifconfig, if I´m not wrong.
oh yes. That worked.
oscdump on port 24024 gets messages.
As you might have thought, I´m fairly new to many of those things. I´m a poor beginner but really appreciate your support for newbies like me.
Thanks!!!
I have the same experience as @andrakar. I started oscdump on the RPi, and started Open Stage Control on my Linux VM. Using mda_jx10_vst3_open_stage_control_gui.json as the session file, I was able to see messages on the RPi when I use oscdump 24024. For example, when moving the cutoff knob, they look like this:
e1a77c42.561d10b1 /parameter/synth/VCF_Freq f 0.050000
e1a77c42.58a7d672 /parameter/synth/VCF_Freq f 0.100000
e1a77c42.6584901c /parameter/synth/VCF_Freq f 0.150000
e1a77c42.b498915b /parameter/synth/VCF_Freq f 0.190000
However, when running sushi on the RPi, with the config file ~/config_files/mda-vst3-configs/config_mda_synth.json, there are no changes when controls are moved while I’m playing my MIDI keyboard.
I suspect the problem is a path/name mismatch. This is from /tmp/sushi.log:
I edited the mda_jx10_vst3_open_stage_control_gui.json file, and changed the “address” key value in the “JX-10 Elk Controller” tab section from “synth” to “jx10”, and now the control is working.
Hi @rcohen,
thanks for the detailed analysis and yes, indeed that was the issue, the processor name in the SUSHI JX10 config was different between the VST 2 (synth) and the VST 3 version (jx10).
We’ll uniform this in the next update.
Currently the way to check OSC paths is the one you showed by analyzing the system logs, we have ready to deploy a new system that will dump all the plugin information to a separate file, including OSC paths and that should make these debug activities easier.
Currently, something like that is only available with gRPC but we have in the backlog to implement something like a simple “OSC echo” message that could do that.
If you’re only using Open Stage Control to change parameters you can save the state in Open Stage Control itself but it won’t be synced if you e.g. change a parameter through SENSEI or MIDI.