What’s the latest on presets please? In Zynthian I only see the default preset. I can see them in the VNC engines window and play in single and multi mode. Is it possible to make them visible (in single or multi mode) in Zynthian presets? (running Oram Staging version). In any case thanks for your work here - it’s amazing to be able to run this in Zynthian, and particularly in multi mode.
Hi @3tree,
AFAIK the presets should be already fully visible and selectable since at least two major Oram releases. I suggest you switch in webconf > software > repositories (or version) to Oram Stable 2502, wait 15 secs for newer OS releases to be shown, select Oram Stable 2502.1 (or 2502.2 if available), update Zynthian in webconf or onboard, reboot.
You should now see a series of ROM banks. populated with lots of presets, both on Osirus and OsTIrus chains.
Regards 
Thanks for your guidance. I’ve done this, but there are no presets shown in Zynthian, only in the GUI (engines view). Also, Osirus hangs on ‘Adding Processor’ and doesn’t load. UI log reports
Feb 24 21:50:24 zynthian startx[1061]: WARNING:zynthian_gui.busy_thread_task: Clients have been busy for longer than 30s: {‘add_processor’}
Hi @3tree !
Could you explain the steps you followed to install the ROM file?
Also, we would need the “context”. I mean, software version, zynthian hardware, etc.
Regards,
1 Like
Hi @jofemodo
It’s a custom build. Here’s some details from the web interface.
Raspberry Pi 5 Model B Rev 1.0
Audio: [Custom device]
Display: [Pi 7 Touchscreen Display 800x480 (inverted)]
Wiring: [MINI_V2]
Profile: [v5]
SOFTWARE
zyncoder: [oram-2502.1]
zynthian-ui: [oram-2502.1]
zynthian-sys: [oram-2502.1]
zynthian-data: [oram-2502.1]
zynthian-webconf: [oram-2502.1]
rom installed originally directly in the plugins folder and then latterly via web ui (when problems persisted)
Difficult to say, but probably the problem was you tried to install by hand. You ALWAYS have to install ROM files using the webconf, so the LV2 presets can be generated properly.
I recommend you check this folder:
/zynthian/zynthian-my-data/presets/lv2
to see if presets has been generated, perhaps partially, for the Osirus or Ostirus engines. If so, remove all preset folders for these engines. Then, try to upload the ROM file again and wait until the process is finished. It could take some time to generate the presets.
If it doesn’t work, you should consider the possibility that the ROM file you are using is not well supported or it’s damaged. In such a case, we couldn’t help you too much with this, sorry.
FYI, i’ve recently verified the ROM install procedure and i’m pretty sure it works OK.
Regards,
1 Like
Yes that folder contains preset folders - lots of! So I should remove those, and the manually added rom files, then start again from the web interface per your advice above?
Yes. This is my advice.
Regards,
1 Like
Tried this and failed, then disabled the engine, re-enabled and repeated and it worked. Thanks for your advice.
2 Likes
Is there any known issue with OsTirus causing midi in to fail? Not sure on the correlation vs causation but it seems like when running 2 or more instances of OsTirus midi stopped working. Might just be a coincidence but after a fresh zynthian install it happened again today. Will do some more tests but interested if this resonates with anyone else?
On mine (pi5, 8gb, no overclocking) two instances of OsTIrus puts the CPU load pretty high and three is completely out of the question, constant xruns if it loads at all. Maybe you flew too close to the sun and something crashed?
Good to know, same spec as mine. I guess you can workaround two+ in multimode anyway.
1 Like
Hi @LagoonCity and @3tree 
I warmly recommend using OsTIrus in the current interlocutory multi-timbral mode, instead of arming different tracks with more instances of the same engine. Such a plugin arrangement would get close to the physical calculation limit of the Pi5 four cores, while in multi mode a much smaller computational overhead is entailed.
In order to work with OsTIrus in this way, you should:
-
Create an instrument chain with OsTIrus, setting its Midi In as Channel 1
-
Create as many more MIDI chains (not instrument) as the remaining channels of your multitimbral setup, not exceeding 3-4 channels per Zynthian unit, at a manageable sample buffer size (certainly not 128 but 256 or 512, which is more than adequate for sequencing purposes in terms of actual latency).
-
Set the Midi Out channel of the newly created Midi chains as channel 1, that is the first chain with the active OsTIrus engine.
-
Enable VNC, and create a multichannel Midi performance patch on the native GUI in webconf, connecting the Z to an external computer.
-
Save the multi preset on the OsTIrus native GUI on VNC.
-
Save the snapshot on Zynthian.
-
Disable VNC and reboot, in order to preserve precious CPU resources.
-
Play or sequence multitimbrally your OsTIrus patch. In this way, you can obtain several Midi channels from just one instance of the emulator engine in multi mode.
Best regards!
2 Likes
That’s the plan, I just hven’t set it up yet, been mostly using Helm, Mimi-D and SO-666. When I first got the Zynthian I checked how many OsTIrus instances I could load before I got xruns, to get a feel for how much I could run on the Pi 5 (first one above 4 I got). It hasn’t found a place in my workflow yet, though.
Thanks a lot for the explanation. I’ll give this a go.
1 Like
DSP56300 are already version 1.4.1 with 1.4.2 already in beta and coming soon. As much as I can say, they are working well on the Zynthian. Maybe it is time to update? 
And maybe add the released XENIA and VAVRA?
1 Like
I would say: it is just about time 
Unfortunately, I have not yet understood how to make the presets and controls of Xenia and Vavra visible in Zyngui, so I’m no help with this, sorry.
These two are especially interesting, as Waldorf offers everything for download on their own website:
Microwave (Xenia)
and
Micro Q (Vavra)
1 Like
As far as I can tell, the Vavra and Xenia integration is yet to be undertaken, and the overall situation should be more or less in the state of this November 2024 post:
Speaking of integration, in latest Oram Stable 2502 Osirus and OsTIrus apparently read the parameter values for presets as numerical remarks, but fail to register them in the graphic ring representation of rotary encoders. Any progress with this in testing @jofemodo?