IMHO, If you like to play with the latest improvements and features, for sure it’s better/safer to change to staging or testing than tweaking stable by yourself to get the new features on it.
Staging is quite stable. All changes in Oram staging have been already tested in Vangelis so it’s not normal that staging gets totally broken. It could be partially broken (some feature broken) at some point, but in such a case, it would be fixed very fast.
Regards,
Alright @jofemodo! It looks like someone has to take the plunge, and switch to Staging Oram one of his beloved Zynths 
@ledan, I suggest you do the same, to have Osirus and OsTIrus automatically installed and configured. If you don’t manage or want to do so, just drop me a message in pvt and I will send you the compiled components of Osirus, but please keep in mind that this is an advanced tweak which, according to slight system or hardware differences, might result in a stable OS becoming unstable 
.
All best regards
You will enjoy staging
I think i am already (?) because i have a DSP56300 section in the meny that also shows my rom that i uploaded via winscp earlier. Its also visible in the UI (VNC).
So now its just a matter of getting some sound out of it.
my main page states:
i’ll pull down the test image (2024-09-23) just in case
Excellent then!
Either your compiling routine had already went well, or now that you have effectively switched to Oram staging you can see the implemented DSP56300 options 
Have a very good virusing!
Tbh, i don’t know how i managed to get that menu in place Aethermind 
But now i pulled the last test image (which btw, started with working video right away on my cleaned/formatted sd-card (??!)) and doing the vangelis upgrade now. Very exciting.
Thx for all your good help gentlemen.
edit.
and it works 100%
I will pick up some active cooling for the rPI tomorrow (it seems to be needed) in order to adjust up the frequencey a bit on the CPU
Btw, is it possible to add custom banks to Osirus? As i own the Rob Papen Analog soundbank, it would be a thrill to use that on Zynthian as well.
Answering this myself
It works absolutely great using the import tool also for 3rd party sysex banks.
This is flipping great while i “did” have to rename the extension from “MID” to “mid” in order for the UI to see it (as it came that way from the purchase), its really not an issue as Linux is quite case-sensitive. This is awesome.
How well do the other three work under Zynthian?
Just great!
Hi @Kirtai!
If you mean “the other DSP56300 emus”, I haven’t had the chance to try Vavra and Xenia on the Zynthian, not to mention Nodal Red which not only is still in a developmental and testing phase, but going by the words of @dsp56300 is probably beyond the computing capabilities of a Pi5.
It seems that Vavra works straight away with the available Aarch64 LV2 plugin, I will test it. Let us see if also Xenia functions already on the Zynth (don’t know if this would possibly be a fortunate coincidence, or the devs upstream have updated the latest releases to what they already know the Z requires to make them run).
Nodal red does load up, but suffers from underruns/overloads so it’s very crackly.
On the other hand, on a more powerful desktop machine, it does sound exactly like the hardware that I have next to me… 
Yes indeed @gadg3ts!
I also have the original hardware and Nodal Red installed on a desktop machine, and they - holy moly - sound practically identical, if we take out from the equation the unavoidable coloration of the four DACs, which in the desktop unit not only are of top quality but also run at the rather unusual resolution of 4 bit and 96 Khz, meaning high waveform bandwidth with low aliasing in the upper range at the expense of slightly less amplitude dynamic (the sample frequency can be replicated anyway, setting the audio interface duty cycle). Using effectively Nodal Red 2X on the Zynth is obviously quite out of question, at least for now (waiting for what Pi6 will possibly bring us in the future!).
I have installed Vavra and Xenia from .deb packages, and they (mostly) work out-of-the-box in Zynthian.
In my case, only the latter loads presets and plays them correctly, at normal CPU clock and without apparent xruns issues, but with only one chain activated. [Edit: if I leave it loaded inactive, after a while it goes in red warning mode, maybe due to a logging problem, like OsTIrus used to do before being optimised at code level].
Presets obviously don’t show on the Zynth and aren’t saved with the snapshot, but are only selectable temporarily on VNC. Also, the plugin only works in single mode. Still a long way to go, before even beginning to be usable in a real scenario. Nevertheless, the engine already sounds as wonderful as it does on other computer platforms. [Edit: also, let us remember that this engine is a testing software like Nodal Red, for the time being, with restricted access to selected members of the DSP563XX emulation forum, thus we should not mention them further until they are released in beta to the wider public ]
As for Vavra, I have not managed to make it load presets and produce sounds coherently (maybe something with the patch folders), and it seems to me a tad less stable than Xenia as it stands.
Anyway, while this feels like a good start for the prospect of having the whole DSP56300 arsenal onboard, the integration priority is justly focused on the beautifully-sounding Osirus and OsTIrus for the time being.
All best regards
Yes, best to wait for an actual release before doing much integration work. The reason I asked about them is that I only have a Pi4 atm but will be getting a Pi5 soon, so thanks for the testing.
Please correct me if i’m wrong, but as i understand it (using for example Vavra as an example, and the explanation given here: MiMi-d - creating a new software synth for Zynthian - #21 by riban)
all that is required is to issue a sudo dpkg -i debfile (which will in that case end up in the lv2 folder from what i can see), then do the “search for …” in the software->engines and/or potentially a reboot and it should be visible?
I tried it but Vavra is not shown in the listing of plugins 
I’m running “Vangelis” on the rpi5 and have Osiris working.
That’s exactly what I did, without the sudo, 4 days ago.
Some of the sound files downloaded from Waldorf in that zip do not work and produce a deadlock when trying to load them, but most of them just work.
Same is for the other plugin, some sounds load, some not.
It would be so nice if someone with a better understanding of the Zynthian system could help to integrate this properly, also because ROMs and sounds are published by Waldorf for free. Missing that opportunity would be shame.
Also, leaving such a precious task to some noob like me, would certainly just be a waste of time and produce more problems than benefit.
This is indeed the procedure that I followed to explode the plugins files, carried by a Debian distribution format (.deb), in the usual directory of the LV2 plugins.
As for the presets, downloadable from the Waldorf legacy instruments support pages, they are all a matter of hit-or-miss, with some locking the synth engine and some not.
Since the focus is now on fully integrating Osirus and OsTIrus, with complete recall of parameter settings and presets saving in the snapshot, I would suggest to leave aside the other DSP56300 engines for the moment, if not for testing purposes.
As they stand now, they are unreliable, not optimised and hardly usable in a real context: let us entrust @dsp56300 and @jofemodo with the required steps to integrate them, when the time is mature to do so. I am pretty sure that this is in the plans, and that there is a definite interest in also providing these further and valuable engines on the Zynthian!
All the best
Remember to place the Aarch64 LV2 deb package in the lv2 folder (/root/usr/local/lib/lv2) before installing it, otherwise Zynthian will not be able to see it as an available engine. Moreover, do not forget to activate/toggle Vavra in webconf, before searching for new engines
All best luck!
You must search for new engines before seeing the new engine in the list, so you can’t enable before. If you see the plugin, no need to search again
Regards,
