Vaporizer 2 Wavetable Linux/Win/MacOS Synth Open Sourced

jofemodo · February 9, 2026, 2:04pm

Done!

harrylnorris · February 12, 2026, 11:11pm

Any plans to make the presets visible in the current release of ORAM?

Thanks,

Harry

hannesmenzel · February 13, 2026, 4:20pm

Hi @HansR , I think you told me that already in another thread. I think I recall you’re somehow symlinking zynthian-my-data to your usb stick unter /media.

Can you tell me if it causes any problems on screens were you can select any data from usb drive and the user data folder alike? Like the soundfont selection screen for example?

HansR · February 13, 2026, 7:09pm

Hi @hannesmenzel

The recipe is here

Until now I did not have any problems with this solution.

I formatted the drive (64GB ) as NTFS, because FVAT caused trouble. The NTFS drive also makes it very easy to copy files to and from the device in Windows. If you are Linux user, perhaps it’s better to make an EXT4 partition on it.

It shows up as usual in webconf but that is (and always was) unreliable for file management:

The webconf File Browser works fine, the drive shows up twice, once as /media/root/ZYNTHIAN and once as my-data

On the Zynthian itself I see no difference with the original situation:

I’ve done speed comparisons in the past, and if I remember correctly, there was a slight speed drop on an RPi4 (about 20-30%) and none on an RPi5. That’s of course dependent on the speed of the stick.

It is a fairly safe solution. If you copy the complete zynthian-my-data to the USB drive and rename it to zynthian-my-data-old before you create the symlink, you can revert this simply by deleting the symlink and renaming the old directory back.

Disclaimer: @jofemodo once told me this is not tested nor supported by the devs, so try this at your own risk.

Kind regards,
Hans.

hannesmenzel · February 13, 2026, 7:58pm

Seems like it also need to update the engines database after installing. Regenerating the presets does this:

(venv) root@hannes-zynthian:~# regenerate_lv2_presets.sh https://www.vast-dynamics.com/plugins/VASTvaporizer2
Regenerating LV2 presets DB: https://www.vast-dynamics.com/plugins/VASTvaporizer2 ...
Generating Vaporizer2 LV2 presets ...
Error parsing native preset '/usr/share/Vaporizer2/Presets/AT Ambience 1.vvp' => reference to invalid character number: line 765, column 16436
Error parsing native preset '/usr/share/Vaporizer2/Presets/BA Control the Future.vvp' => reference to invalid character number: line 769, column 16512
Error parsing native preset '/usr/share/Vaporizer2/Presets/GT MPE Guitar.vvp' => reference to invalid character number: line 769, column 16511
Error parsing native preset '/usr/share/Vaporizer2/Presets/BA Creak Bass 2.vvp' => reference to invalid character number: line 769, column 16511
Error parsing native preset '/usr/share/Vaporizer2/Presets/SY Acid MPE.vvp' => reference to invalid character number: line 765, column 16442
Error parsing native preset '/usr/share/Vaporizer2/Presets/PD Marimba Lift MPE.vvp' => reference to invalid character number: line 769, column 16511
Error parsing native preset '/usr/share/Vaporizer2/Presets/BA FM is the Phuture.vvp' => reference to invalid character number: line 769, column 16511
Error parsing native preset '/usr/share/Vaporizer2/Presets/PD Bladerunner Lift MPE.vvp' => reference to invalid character number: line 765, column 16511
Error parsing native preset '/usr/share/Vaporizer2/Presets/PD Bladerunner MPE.vvp' => reference to invalid character number: line 765, column 16511
Error parsing native preset '/usr/share/Vaporizer2/Presets/VC Vaporizer.vvp' => reference to invalid character number: line 878, column 414767
INFO:root:Workaround took 13s
INFO:root:Command took 13s
Running Flag Actions from '//zynthian/zynthian-sys/sbin/regenerate_lv2_presets.sh'...

Anyway, great sounding synth!

Only 189 pages of parameters, yikes.

jofemodo · February 13, 2026, 8:19pm

190 x 4 = 760 parameters.

If you edit 110 parameters a day, you could end in one week only

But i must say the IA is very good and fast editing TTLs. She only needs some wise guidance.

Regards,

hannesmenzel · August 1, 2026, 9:13pm

I did a quick and dirty ttl for this. Parameter ordered according to the original plugin param ids, groups, adjustments in the mod matrix. It’s waiting in an old PR.

If anybody knowing this synth better has any proposal, go ahead!

jofemodo · August 1, 2026, 10:29pm

i was not aware of the PR. i will check It ASAP.

Thanks

hannesmenzel · August 1, 2026, 10:38pm

The vaporizer ttl is new. The old pull request contains other ttls as well, and also this.

jofemodo · August 2, 2026, 8:51pm

Fantastic @hannesmenzel !

The PR is already merged in vangelis.

Thanks a lot for these custom TTLs. They are a great contribution and improve a lot the usability of the affected engines. Specially the Vaporizer2 that, until now, was almost impossible to adjust without using the native GUI. Now you can find the parameter you want to modify and do it from the zynthian UI. If you combine this with the “chain controllers” , you can easily select and make accessible the few parameters you want to modify while playing/sequencing.

All the best!

hannesmenzel · August 3, 2026, 9:03am

Great. This is just a first draft, so feel free to adjust. I actually don’t know the synth well and only used the parameter names for grouping. You can imagine there was some regex find&replace involved with 755 parameters.

Btw. we talked about the auto naming of pages with more than 4 parameters. I actually would vote for p.N because in the current state it looks odd if you have e.g. LFO 2 1, LFO 2 2, LFO 2 3 and so on. I mean, I could rename these to LFO A, B, C.

jofemodo · August 3, 2026, 4:20pm

Of course. I can’t imagine managing this with the “notedit”

Yes. Please, rename them as you propose.

Regards,

hannesmenzel · August 3, 2026, 4:44pm

I’ll do this, but it’s not quite an optimal solution, since this differs from the original plugin UI layout.

Maybe we find a solution for distinctively displaying page numbers that can be recognized as such (like explicitely call it a page or at least give it a distinction with font colors for example).

hannesmenzel · August 3, 2026, 5:45pm

Sorry, I have a noob problem, since my noob workaroud editing ttl’s (edit on zynth - update for letting the ttl being passed from the zynthian-data location to the actual location - test) doesn’t work anymore, because update of course pulls the repo version. All other suggestions (regenerate_engines_db.sh, restart service, reboot) didn’t work.

So I’m stopped here until I learn this git checkout magic, but didn’t find a good explaination. (Well, I found this…):

So if anybody can give me a short hint how to (non-destructively) switch between zynthian repo and fork I’d be very thankful.

hannesmenzel · August 3, 2026, 9:44pm

OK, done for today with this. While trying to ssh with vscode to my zynthian I somehow managed to almost destroy my studio PC by associating my windows machine .exe with vscode completely (all exe opening with vscode, including explorer, taskmgr, cmd, powershell, regedit and so on) and I only got out of this mess with the help of my wholeheartedly hated Claude AI. Meanwhile solved the vscode problem by enlarging the /tmp partition…

Will try another day.

EDIT: Btw: could we probably make the size of /tmp larger by default in the image? I read it’s recommended to revert changes here after a done task, but this seems to be a repeating issue through different use cases (installing vscode on zynthian, compiling plugins on zynthian and others).

riban · August 4, 2026, 5:44am

I had to increase /tmp to 400MB to install vscode server. Zynthian uses /tmp for many things, including webconf downloads, clippy warped audio, etc. The size of the tmpfs mount is a limit, not a quota, so if we increased /tmp mount to 500MB then it would solve a lot of these issues but not take up that actual space until required. I suggest we increase the tmpfs to a larger size, based on the available RAM, e.g. 20% of RAM.