Hi,
So I’ve got 8 tunes ready for a live hardware set in about a week.
The Zynthian is being the primary sound module, for running the virus & VirusTI models, along with linuxsampler and dexed.
The problem that I have, is that I want to change the patches on the virus synths per-song, but I can’t find a way to make it work.
I have 8 zs3 subsnapshots, one for each tune, and while this will load the right names onto the zynthian screen, it doesn’t change the patches on the synths in the VNC view, and so the sound doesn’t change. My understanding of the zs3 feature is that it captures all loaded parameters?..
If I try the full snapshots, this does basically the same, but takes a minute or two(!) to reload all the instruments & effects… Not good for a live situation.
My sequencer/groovebox is a Polyend Play+ which is also sending PC’s to my TR8 for kit selection. Actually, there are 2 x play+ devices so I can have a continuous hour of music!
What I would really like to do, is have the 8 patches I have set as favourites in the virus gui, to respond to midi program changes so that I don’t have to reload anything. As if it were the actual hardware.
Is this possible?..
Thanks,
Sean
i think the problem is related with the MIDI parameters. Let me find a solution so you can gig.
Please, send your snapshots to test.
Regards
2 Likes
001–2 overnight stopover.zss (233.1 KB)
Thank you.
Here’s the full zss. I’m not sure how to get the individual zs3 lists out?
But changing the patches in the first 2 channels should give you an idea.
My plan B is have a laptop connected with the vnc session open.
1 Like
Before I forget.
Zynthian is Oram 2506.1
Osirus is 1.3.20
OsTIrus is 1.3.15
luckily, this is not going to be needed.
regards
1 Like
I think the actual problem might be that I can no longer select the patches for the virus synths from the zynth ui(?)
It was working fine a couple of weeks ago.
So I had discovered what might be an issue with the arpeggiator on the VirusB going out of sync with the incoming midi clock.
I attempted to resolve this by (locally on the device via a git pull of the github code) updating the plugin builds (from 1.3.22 which ran fine, to what turned out to be 1.4.5, which suffers from overloads).
After that didn’t work, I copied the plugin files from my zynthian-dev device which got me back to the versions mentioned above.
At some point in that process, the zynth ui stopped allowing me to change the virus patches.
I’ve tried the regenerate_lv_presets.sh script but that didn’t help.
Hi @gadg3ts !!
Preset selection works OK in my side, although saving/restoring ZS3 with modified MIDI parameters could cause trouble. I would save as new presets from the native GUI and would use the saved preset without any param modification.
Also, i’ve fixed a bug (in vangelis branch) that was causing problems when loading ZS3 containing presets tagged as “favorite”. I noted you had some like this in your ZS3s.
Please, try re-saving your ZS3s, specially those using presets marked as “favorites”.
Anyways, i don’t think it’s a good idea to have instances of Osirus and OsTirus at same time. This engines are very CPU hungry and you probably get XRuns. In general, i woulnd’t have running simultaneously more than one instance of the DSP56300 emulator.
All the best,
2 Likes
Aha! It’s fixed!
Thank you.
I had already made presets for virus emulations in the native (vnc) ui, but I wasn’t sure how to use them.
So I removed all of the “favourites”, and then found the “native” presets in the bank labelled “none”.
Now, I can switch between the 8 zs3’s and I get the correct sounds 
I am now ready for my 1-hour live set next Sunday.
Which is actually the event for which I bought the zynthian (last year) in the first place.
Having run both of the emulators at the same time over the last few months, they’ve been pretty stable for me.
I think the issues with the crackling, which has now gone, would have been because the zynthian was probably overheating, as the underside of the case yesterday was pretty hot to touch.
Combined with the UK’s recent heatwaves, everything was overheating!
Today, after letting it cool down properly overnight, it has been fine.
I have also set the latency of the emulators to 2 in the native ui - this has stopped, or at least reduced, the xruns I was seeing in the debug log. The sounds coming out of the box seem fine.
Later, I will likely run each emulator on a separate zynth - once I’ve built a box for my “zynthian-dev” box which is currently just a pi5 mounted on the back of a 7" screen.
Thank you for the pointers.
3 Likes
Just as a postscript.
The zynthian ran brilliantly in the performance.
The only challenges were that the 1010music bluebox decided to not work for its first pair of inputs (so I had to do some last minute replugging), and relying on the stage monitors for hearing myself (instead of using my headphones where I know what it’s supposed to sound like!) was probably a bad idea.
On the other hand, I’ve got the multitrack recording of the bluebox to mix better.
and the bluebox decided to work again properly once I got it home!
Thanks,
Sean
3 Likes