Oops, I switched steps in my description 
. Late evening and sleep incumbent! I should have said “search for new engines in order to toggle Vavra”.
Thanks @jofemodo
Hi,
i tried to skip the sudo and move the deb into the /usr/local/lib/lv2, as well as into the /usr/lib/lv2 and installed it from those places. The .so file ended up in the /usr/local/lib/lv2 folder.
I then tried to “search for engines” in all these cases, but it will just not show up 
Reboot does not help either.
I’ll wait and see what is coming in the future. With Osiris on thins thing, i’m happy as a small child close to christmas anyway 
Hi @ledan! This is very close to my own feelings, the first time I saw Osirus and OsTIrus showing up on the Zynth 
.
I recommend you place the .deb and launch sudo dpkg -i in the lv2 folder directly, after:
cd /usr/local/lib/lv2
I am not sure that the .deb contains all the appropriate directions, to point at the right lv2 directory, and anyway it doesn’t break anything to do so, even I don’t know if it is actually required.
All best regards
Hello @dsp56300, @jofemodo and all those concerned!
Just to make a recap, of the current state for DSP563xx emulators integration in the Zynth, it seems that - as of now and on an updated staging Oram - there is a full OsTIrus/Osirus dictionary of CC parameters visible in the chain, but they don’t reflect the values of the currently selected preset.
Maybe, the parameters feedback between the UI and the emulator engine is not (fully) implemented yet.
Any news on this? (or have I missed some recent updates?).
Thanks, all the best!
My Osirus is still missing all the presets.
An interim status on the subject of parameters and multimode would be nice.
Do you mean @highsiderr that your Osirus installation doesn’t show any preset banks?
If so, that should happen automatically on the current staging Oram (not in stable, where the plugin has to be compiled from source and the presets generated through CLI afterwards).
Regards
I rebuilt the image and reinstalled everything.
Now osiris also has its presets.
Osirus and Ostirus do not display their own parameters with the new LV2 host. Is this due to the MidiCC script?
No. It seems the Osirus and Ostirus plugins doesn’t have good symbols for the property parameters. All parameters seems to be parsed with the same symbol “_”. I will check if it’s a TTL issue or a parse issue.
Regards,
1 Like
It seems that the symbol name styling doesn’t works with jalv. I’m not sure if this is LV2-compliant:
plug:_13_0_82
Lilv seems to only take the first “_”. When parsing a get this:
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Channel Volume
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo1 Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo1 Symmetry
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo1 Keyfollow
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo1 Keytrigger
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Osc1 Lfo1 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Osc2 Lfo1 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 PW Lfo1 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Reso Lfo1 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 FiltGain Lfo1 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Rate
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Balance
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Shape
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Env Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Symmetry
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Keyfollow
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Lfo2 Keytrigger
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Shape Lfo2 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 FM Lfo2 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Cutoff1 Lfo2 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Cutoff2 Lfo2 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Pan Lfo2 Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Patch Volume
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Transpose
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Key Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Unison Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Unison Detune
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 16 Unison Pan Spread
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Panorama
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Unison Lfo Phase
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Input Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Input Select
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Chorus Mix
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Chorus Rate
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Chorus Depth
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Chorus Delay
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Chorus Feedback
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Chorus Lfo Shape
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Delay/Reverb Mode
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Effect Send
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc1 Shape
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc1 Pulsewidth
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc1 Wave Select
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc1 Semitone
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc1 Keyfollow
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Shape
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Pulsewidth
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Wave Select
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Semitone
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Detune
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 FM Amount
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 5 Osc2 Filt Env Amt
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 5 FM Filt Env Amt
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 5 Osc2 Keyfollow
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 5 Osc Balance
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Sync
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Filt Env Amt
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 FM Filt Env Amt
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc2 Keyfollow
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc Balance
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Suboscillator Volume
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Suboscillator Shape
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Osc Mainvolume
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Noise Volume
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Ringmodulator Volume
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Noise Color
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Cutoff
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Cutoff2
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Filter1 Resonance
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Filter2 Resonance
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Filter1 Env Amt
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Filter2 Env Amt
DEBUG:zynthian_lv2.get_plugin_ports: Got property parameter with symbol _ => Ch 2 Filter1 Keyfollow
I suspect LV2 symbols can’t start with “", or at less, lilv doesn’t recognize symbols starting with "”. @dsp56300, could you change code to generate better names for the symbols, ideally not starting with “_”?
Regards,
BTW, @dsp56300, could you generate a reduced TTL with just the symbols for channel 1? If not, i would cut the current one. Until we have the full multi-timbral integration, we don’t need all channels parameters and having a reduced TTL will reduce load time.
Regards,
Hi @jofemodo
I don’t know if my remark is relevant, but, in optimising the current TTL manifest syntax, please take care not to break the temporary multi-timbral usage workaround for Osirus/OsTIrus (arming a chain with the synth, building a multi-channel layout in VNC, saving preset, adding Midi chains with the synth chain as target Midi output).
All the best!
Have you tried to select “All MIDI channels” for the Osirus synth chain?
Regards
Do you mean @jofemodo, creating an Osirus chain that receives Midi on all channels?
My current workflow is that a DSP56300 instrument chain is set on a given basis Midi channel, with a multi preset created in VNC and saved in the snapshot. All remaining channels are reached by Midi chains set on the other channels of the multitimbral patch.
Regards!
I’m not sure if this was already mentioned somewhere and I missed it, but on the new stable release when you load a preset in Osirus or OsTIrus the Zynthian parameter contols all start at their minimum (fully ccw) rather than reflecting the actual values loaded from the preset. This also means that the actual loaded value jumps to the Zynthian control’s value as soon as you make a change. Sounds fantastic and works well otherwise, though, just like the hardware.
Hi @LagoonCity,
Yes, it is known and acknowledged by the devs that, in Stable and for the time being, there is no bidirectional feedback of parameters, between the code of DSP563 plugins and the Zynthian UI.
I believe that this is more or less resolved in Vangelis/Testing, and expected to be merged in Oram Stable at a coming release point. I seem to remember that the current limitation in Stable (all preset parameters set to 0/full CCW on preset reading by the UI) is due to the incomplete or lacking integration of JUCE, a widespread framework for audio plugins coding.
1 Like
Thanks, I thought I had seen it earlier in the thread but didn’t have any luck finding it for whatever reason.
I’ve been following the JUCE integration discussion a bit because of the issue with Airwindows Consolidated parameter names not updating dynamically, since that’s near the top of the list of things I’d like to run on the Zynthian in the future.
2 Likes
I just noticed that when I save a preset for Osirus from the Zynthian UI, some parameter changes in the effects section aren’t saved properly. For example, I was working on a patch that had the delay time set all the way down at 3 with the feedback set relatively high. When I save a preset, the delay time gets reset to around 500ms (guessing by ear) and the feedback is returned to zero. I’m not sure if any other parameters are changing elsewhere in the patch - those are the immediately obvious ones.
The Zynthian apparently reloads the preset after saving, because the parameter changes are audible (but not reflected in the UI) immedately after the save is complete, as well as being in the saved preset when I load it manually.
I suspect this is because the effects are global in the Virus C, and isn’t exactly a bug but I wanted to put it out there in case. EDIT: I made some obvious changes to parameters within the voice (oscillator pitch, filter cutoff) and confirmed that they are saved normally. As far as I can tell it’s only the state of the global effects that isn’t being saved.
Any News from @dsp56300 ?