DSP563XX emulation plugins

[dsp56300]

Sounds fine.

Can I query the directory for the presets somehow or shall I hardcode the path for now?

I noticed that subdirectories are not supported, so I’d chose a directory like this:

/zynthian/zynthian-data/presets/lv2/<pluginName>_<romName>_<bankName>.lv2

that okay?

[jofemodo]

It would be better in this one:

/zynthian/zynthian-my-data/presets/lv2

Regards

[ledan]

I’m sorry if that answer was not for me. But if it was indeed, then no, not a full fledged Zynthian, but an rPI with IQ-Audio hat running the latest stable 64-bit OS

[Aethermind]

Any progress @dsp56300 with integrating OsTIrus presets lists and parameters exposure in Zynthian?

Unfortunately, I don’t have the technical coding skills to help in any way in this process, but this is my practical suggestion, whatever time you and the Zynthian Labs deem apt for the Oram inclusion of a fully working Virus TI emulator:

• It is not really required to expose each synthesis value, of the myriad available on the Virus signal path. Once the plugin stability with VNC visualisation is sorted out, as well as the single/multi modality, this operational mode could be used only to do in-depth sound design, while presets tweaking and on-the-fly adjustments could be done on a selected gamut of parameters on the Z’s UI, depending on the chosen patch.

I am aware that Virus TI offers more than just plain old-school VA synthesis, also encompassing FM, cross-modulation and wavetable, and thus potentially requires different editing layouts for specific patches. I guess that this could be solved with some kind of categorisation, that sets a certain limited number of parameter groups to be exposed.

Just my idea, of how this could be managed and presented.

All best regards

[dsp56300]

Yes, if you pull and compile the latest version from source, presets are generated upon initial load of the plugin. Presets are written to the folder

/zynthian/zynthian-my-data/presets/lv2

It looks like this:

However, they are not picked up by the Z GUI immediately. You have to load the plugins once, then do:

regenerate_lv2_presets.sh http://theusualsuspects.lv2.Osirus
regenerate_lv2_presets.sh http://theusualsuspects.lv2.OsTIrus

And then load the plugins again so that they show up.

[jofemodo]

Fantastic @dsp56300 !! It’s my turn now!!

[infinitymodular]

@dsp56300

regenerate_lv2_presets.sh http://theusualsuspects.lv2.Osirus
regenerate_lv2_presets.sh http://theusualsuspects.lv2.OsTIrus

Forgive my ignorance, but where is that shell script?

… nevermind … found it.

[wyleu]

@infinitymodular

Forgive my ignorance, but where is that shell script?

… nevermind … found it.

This is getting to be quite a flock, I’m collecting here.

[Aethermind]

Just great @dsp56300

Thanks: I very much look forward to recompiling OsTIrus from source, and enjoying the presets directly onboard the Zynth!

It will be also an opportunity to verify if the occasional audio system inconsistencies on my Pi5 were due to the VNC GUI visualisation.

[Aethermind]

C’mon @jofemodo, do your spell and give us OsTIrus with exposed synthesis parameters on the Zynthian!

[infinitymodular]

well done @dsp56300 … this works beautifully. Also all previous issues with crashing when modulating and using vnc are gone. Not sure who fixed it, but “LEGEND”!

[highsiderr]

For now you can use @Riban midi cc send device to control Ostirus.

Send Midi CC+PrgCH?

Example. Mixer Channel 1 is the channel with the Ostirus plugin in multimode. Mixer Channel 2 is a normal midi channel without plugin. Mixer Channel 3 is the same. Now you can send midi notes from channels 2 and 3 to channel 1. Ostirus (in multimode) receives these and assigns them to its internal channels. An Ostirus instance now plays 3 different presets. 1 Bassline 2 Pad 3 Lead Unfortunately you can’t control them at the moment and a preset has to be selected via VCN because there i…

Virus Ti MidiCC

https://discourse.zynthian.org/uploads/short-url/n19oFVTw6K8XQ16v2kumBuRrrV9.pdf

[Aethermind]

Thanks @highsiderr

This is a useful addition to the current OsTIrus implementation!

EDIT: I had not followed the development of this new advanced Zynthian feature. Therefore, of course, thanks to @riban

[highsiderr]

Thanks @riban for Program this…

[Lumm]

Thanks for your great idea @highsiderr

[dsp56300]

That was due to logging to stdout, which corrupts the internal Z communication. Also, I recently got back to the DSP emulator and optimized it a bit. It should run better now

[highsiderr]

The presets for bank a and bank b are missing in my Zynthian Osirus.

[jofemodo]

Hi @dsp56300 !

I just noted that when building & installing, some scripts are installed in raw “/usr/local”:

[17/18] Install the project...
-- Install configuration: "Release"
-- Installing: /usr/local/./virusTestConsole
-- Up-to-date: /usr/local/.
-- Installing: /usr/local/./start_IndiArp_BC.sh
-- Installing: /usr/local/./start_Impact__MS.sh
-- Up-to-date: /usr/local/./virusTestConsole
-- Up-to-date: /usr/local/.
-- Up-to-date: /usr/local/./start_IndiArp_BC.sh
-- Up-to-date: /usr/local/./start_Impact__MS.sh
-- Up-to-date: /usr/local/lib/lv2//Osirus.lv2
-- Installing: /usr/local/lib/lv2//Osirus.lv2/dsp.ttl
-- Installing: /usr/local/lib/lv2//Osirus.lv2/manifest.ttl
-- Installing: /usr/local/lib/lv2//Osirus.lv2/ui.ttl
-- Installing: /usr/local/lib/lv2//Osirus.lv2/libOsirus.so
-- Up-to-date: /usr/local/lib/lv2//OsTIrus.lv2
-- Installing: /usr/local/lib/lv2//OsTIrus.lv2/dsp.ttl
-- Installing: /usr/local/lib/lv2//OsTIrus.lv2/libOsTIrus.so
-- Installing: /usr/local/lib/lv2//OsTIrus.lv2/manifest.ttl
-- Installing: /usr/local/lib/lv2//OsTIrus.lv2/ui.ttl

I mean these files:

• /usr/local/./virusTestConsole
• /usr/local/./start_IndiArp_BC.sh
• /usr/local/./start_Impact__MS.sh

This is not very nice. Could “/usr/local/bin” be a better place?

BTW, i’m currently working in the firmware file manager that would generate the preset list automatically when uploading a new firmware file.

Thanks!

[Aethermind]

Hi @jofemodo and @dsp56300

I have just installed Osirus and OsTIrus compiling from source with:

git clone --recurse-submodules GitHub - dsp56300/gearmulator: Emulation of classic VA synths of the late 90s/2000s that are based on Motorola 56300 family DSPs
cd gearmulator
cmake --preset zynthian
cmake --build --preset zynthian --target install

And tried to generate presets with:

regenerate_lv2_presets.sh http://theusualsuspects.lv2.Osirus
regenerate_lv2_presets.sh http://theusualsuspects.lv2.OsTIrus

After adding the respective ROMs in the plugins’ folders, searching for new engines in webconf > engines and flagging Osirus and OsTIrus to activate them (with reboot), I can see the new plugins in the Z (latest Oram, V 5.1 with Pi5) [SOLVED but no presets show in the UI of the related mixer chains.]

As a contextual detail, I noticed through an SFTP server on my LAN connected external computer that LV2 plugins are not anymore in:

root/usr/local/lib/lv2

but instead in:

usr/local/lib/lv2

Is this correct @jofemodo?

[EDIT: I might be misled on this, by the directory tree representation in the SSH server, since there seems to be a /root under /root]

Thanks, and have both a bright Sunday!

[le51]

Just To be sure : right now, this engine has To be compiled from source for using it with Zynthian ?