I feel you @ledan. The SN2 was possibly one of the most advanced VA engines ever created.
On top of that, you owned the best hardware version of this marvel machine, with 48 multitimbral voices contained in an imposing three units rack. Notwithstanding some notorious issues with faulty encoders, which can be fixed rather easily, you objectively should have kept this amazing artefact of electronic engineering. But as we know, life not always advises for the best. Testimony to the exceptional features and power of this instrument, is that Novation never attempted to reissue this synthesiser, either as a new hardware or a software implementation of it.
Hi @Barrett, to be honest, your reported behaviour of Ostirus on Zynthian is quite unexpected. Reliable patch recall was implemented about more than a year ago.
Just in case, have you saved or overwritten the snapshot containing the emulator upon switching off the system?
That’s great news! I’m new to the environment and user error is waiting for me at every step.
I have some reading on the wiki.
Right now if i load up the synth engine, and use the vnc gui to select a new patch, it works great but if i save a snapshot or reboot the engine will not load the patch that was in use.
Hi! If I recall correctly, you should save a snapshot (a mixer configuration of tracks with loaded processors) after having selected a preset on VNC on the native interface, for Zynthian to recall the patch on the ensuing startup and mixer state loading.
Anyway, there’s no longer need for viewing the synth interface on VNC, since the factory banks of Ostirus presets are selectable directly on the Zynthian interface.
Hi Paolo, this is a strange behaviour.
I recently installed a freshly flashed Oram Stable 2025-11 on a new Pi5 Zynthian build, enabled Osirus and Ostirus on webconf, uploaded their ROMs through the related menu option and searched for engines and presets. Everything worked straight away, and all the factory preset banks were visible, selectable and recalled with the snapshot.
On which ZynthianOS version are you? Could you maybe publish your Webconf splash screen?
Should everything else fail, you might try to regenerate the presets from terminal.
The first obvious port of call that comes to my mind is making sure that you have duly searched for engines, then presets, in the Engines tab of webconf. After that a reboot is due.
The second and more substantial source of potential issues, if I read your words correctly, could be that you have kept on SD the ZynthianOS previously used on a Pi4. Zynthian makes a number of adjustments, code inclusions/exclusions and optimisations on first boot, for the OS to run appropriately on a specific hardware configuration.
Thus, I would consider a backup on webconf, either full or just the Library tab, of your relevant data and snapshots, and a fresh burn on SD of the latest Zynthian version of your choice.
I am not seeing presets in Osirus with Access Virus C ROM after running regenerate_lv2_presets.sh http://theusualsuspects.lv2.Osirus (which restarts the UI).
Are you on Vangelis @riban for this specific installation?
My Osirus ROM banks were misteriously gone for a while, then - after a regeneration procedure and a given update - they were back again, alive and kicking.
Besides, it took a bit to realise that now CTRL/PRESET shows patches when bold-pressed, and not double-touched.
I am on vangelis. I have regenerated presets and rebooted (several times). I know how to access presets and only see “Default”. I am fully up to date on vangelis updates.
[EDIT] An, as if by magic, it appears! I now have the presets and banks. I did another update, scan and reboot then they appeared. Remember to press preset button twice to reach the banks which shows the ROM banks. Thanks Mr Benn.
Could there be a new arisen incompatibility, regarding the consolidated Osirus presets format in Zynthian and recent Vangelis kernel changes? Is maybe @jofemodo aware of a similar issue?
As a matter of fact, my two TUS emulators integrated in Zynthian work nicely now with Vangelis, but I too experienced their sudden rebirth, after regenerating presets and searching again in webconf.
Further to this, and without a logical reason, it also occurred to me to be confused at times by the dynamics of the PRESET button pressure sequence.
