Of course, one issue is that in the .ttl file there is a parameter definition for each parameter for each ‘part’ of Osirus, so it’s the number of parameters (something like 300 or so) times 16, so unless something is done to structure this, it will be an inordinate amount of parameters. But I suppose that given the proper naming structure, something could be done in similar ways to the way when loading multiple ZynAddSubFX chains, there is only one instance of the plugin, and the parameters get routed accordingly.
Thank you for this.
Unfortunately, on a fresh Zynthian install with the Vangelis update and everything running well, it is not possible to upload any ROM file successfully.
regarding Vavra and Xenia, Waldorf has made available both the factory presets and the ROMs on their website. Does this still prevents us from having the factory presets in Zynthian?
I can post the links if you are ok with that.
Many thanks for all the amazing work and hope your recovery is proceeding nice and smooth.
I have switched to vangelis, but the presets for Vavra and Xenia are not in the presets directory. Is there anything else I need to do to add them? Also, although I can upload roms for Xenia, the upload for Vavra is not working - it says it is uploaded but it is not displayed in the web interface, and the plugin does not work. Where should the rom files be installed to in the directory structure?
Is there something special that needs to be done to get the modwheel to work with Osirus? The bend wheel and aftertouch work fine, but the modwheel CC does not seem to be getting through.
Hi @ricard, have you checked that the presets you are testing the modwheel with are programmed in a way that makes them reactive to CC1? (LFOs, cross-mods, filters cutoff, etc.)
No, it’s a good question; the Virus can be a bit daunting with all its capabilities.
But what I did was start up the Osirus UI in VNC, and set up a mod routing from the mod wheel to the filter cutoff. There was no response when I moved the mod wheel, but if I changed the routing source to bend wheel or aftertouch, the filter cutoff audibly responded accordingly. So my conclusion is that while other controllers work, the mod wheel does not. I didn’t test any other CC controllers though, so I don’t know if it was specifically the mod wheel (CC1) or CC in general.
Ok. Here it is:
zyncoder: vangelis (e903d39)
zynthian-ui: vangelis (3ce1900)
zynthian-sys: vangelis (eac724c)
zynthian-data: vangelis (8b55ea8)
zynthian-webconf: vangelis (7a43686)
In Webconf choose Software->Engines
In the tab MIDI Instrument scroll down the list until you find Osirus and set the mark.
Reload Webconf by clicking the Zynthian icon on top left. (Already tried with reboot, but outcome is the same.)
In Webconf choose Software ->DSP56300
The page shows the etire list of all possible DSP56300 emulators, not only the one that has been activated. In Oram, only the previously activated emulator would show.
All file fields show none, as expected, when nothing has been uploaded yet.
Choose Upload Osirus ROM file. A new window opens, Drop files here or click and choose, either operation will result in showing the filename underneath the ant-lined area.
Press UPLOAD.
A Progress bar runs through, looks like it does not reach the end before the black window closes and the previous page shows up like this:
Note, the Osirus filename field still shows none. I’ve checked the binary with the pulled chip. It works perfectly in Oram, but in Vangelis it does not.
The Osirus can be added in Instrument Chain, but it does not work and has no presets. In Oram, it has presets and it works.
fresh burned last stable Oram and then updated to Vangelis
I remeber this issue has been in the past and then was resolved, so I gues this time is the similar cause. I can not find the revision when this happened.
