Well then, It really feels like I will have to venture in Vangelis lands with one of the Pi5s…
Missing escapes, I should have taken care upfront. I pushed a fix
When opening a preset on the Zynthian UI, it shows all midi cc with value zero.
Did I do something wrong or is this feature not yet there to show the cc values, or is it just impossible, because the emulator does not send the values?
I’m more into electronics than into software, so I’m still climbing up that learning curve…
Yes. This is the expected behavior because we have no MIDI CC feedback from the plugin.
Anyway, remember this “MIDI CC control interface” is just a “hack” until we have the LV2 controllers fully integrated. When this is ready, controllers will take the right value when loading presets, etc.
All the best,
Don’t worry, we all are.
As is often the case the Dutch have recognised the peculiar routes we take …
I’ve never heard that term, but it immediately reminded me of Living With Complexity by Donald Norman - a fantastic book about human-centered design that talks about this exact phenomenon in one of the early chapters.
EDIT: that Elephant Talk clip reminds me of Fripp’s League of Gentlemen stuff, you can really hear the influence his collaborations with David Byrne had on him.
Hi @jofemodo
I couldn’t find the midi map for the Virus C but finally found one for the Virus A. It is my understanding that the A and C midi maps are similar. I used it to have AI generate a config file. I’m sure there are many parameters that could be deleted from this, but I left them anyway. You can delete anything in it not suitable for zynthian.
Osirus.py (6.0 KB)
Blockquote
Thank you @ronsum, for stepping in on the topic of CC dictionaries for the Virus emulators.
I have been very busy lately, thus I have dropped this self-appointed task a bit
I own a TI but haven’t installed OsTirus on zynthian because I dont have a pi5 yet. I’m wondering if I should go with a 4GB or 8GB to use OsTirus. Any suggestions?
Going from what I read around, and until the Raspberry Foundation officially releases a firmware fix, it seems that, quite strangely, the 4 Gb version sports slightly to openly higher computational performance, under certain circumstances and depending on the kind of code and RAM usage involved.
Take this with a grain of salt, because the consensus is not unanimous, and the random access memory consumption when complex waveforms are calculated polyphonically is relevant anyway. The current hypothesis is that differences in computational behaviour would depend on SDRAM type and related chunks paging size, between the 4 Gb and 8 Gb variants.
Just now I’m playing the first notes on Vavra. Interestingly enough, installation of DSP56300Emu-1.4.0-Linux_aarch64-Vavra-LV2.deb was easy and it shows up after Scan for Engines and so on. I can load and manipulate presets in VNC, but I can not get the preset list to show up on theZynthian, same with CC list.
Now, Waldorf actually give all the files, System and Sounds for free download.
https://waldorfmusic.com/legacy-micro-q-series/
The sound is Waldorf.
So could this be included?
How to go on to make this fully work?
Appreciate it
I restarted with a fresh image, installed “ninja-lib”, cmake, juce (+ all dependencies) and went at it again (my device is the pi5 w. 4GB).
i do get a killsig at juce_gui_basics.cpp but the compilation continues anyway. Lets see where it all lands (fingers crossed)
Hi @fussl!
That is quite surprising indeed. I knew that Vavra was on the todo list for potential Zynth integration, but only after the Osirus/OsTIrus integration was completed and assessed. I did not expect the normal Aarch64 Debian plugin to work as it is straight away, thus I neither tought to try it on Zynthian (but I use it on PC/Mac and it sounds amazing!).
Maybe I will have a go in the weekend
Best regards
Hey @ledan
Another measure of caution, before compiling Osirus and OsTIrus from source: be sure to delete via SFTP the previous plugin installation(s) in:
/usr/local/lib/lv2/…
I just recompiled both synths on my V 5.1 and noticed that, by not cleaning the OsTIrus and Osirus directories in the lv2 folder, I ended up in an infinite building loop. Just remember to put again the related firmware files in place, and to regenerate the presets thereafter (albeit I am not even sure if this step still has to be done, with the latest code from source: anyway, it does not harm, and it worked for me).
All good luck and best regards!
Thx mate, i appreciate it
yeah, i made sure that there were no residue from earlier lv2 somewhere from your recommendation (there were none). Its not crucial either (as i have the hardware already + the VST of this great plugin), but “of course” ( ) i wouldn’t mind having it on the rPI either (that is a super-cool concept). I’ll stay patient i think and see how it all pans out.
A big thank you for all your great input and contributions in general here. I’m sure there are more people than myself who appreciate it
On a general note. Would it be possible to be “cheeky” enough to enquire if anyone has a fairly newly compiled .so and .ttl of Osirus to share (i presume they could be dropped onto a suitable “/usr/local/lib/lv2” subfolder and then do the rescan activity?
Why not simply change to staging or testimg?
Regards
No problem @ledan,
That can be easily done I think, unless there is a tight upload size limit in this forum that I haven’t had the chance to run into! I will drop the .so and .ttl files here.
Many thanks for your kind words mate! .
I am slowly building my abilities in this IT environment on the solid foundations of the skilled people ready to help who I found here, trying to bring in exchange my personal experience and standpoint to this lively community.
All best regards
Hi @jofemodo,
I was considering to switch to staging Oram on one of the two Pi5 Zynthians, but I am a bit wary because at the moment I am using them combined for an OsTIrus-based musical project.
Vangelis/testing would be a bit too adventurous in this context, but I installed it on the V4 and am exploring it with great enjoyment so far!
Best regards