Please add Organteq and maybe other commercial plugins too

[IFW-SPS]

Just adding this request as a vote for eventually adding Organteq officially to Zynthian.

I think other commercial plugins (if at all available and working) may be interesting as well to make Zynthian the all-in-one solution, as RPi will no doubt get faster and more and more viable as a laptop replacement with each new iteration of the hardware.

Thanks in advance for your consideration.

[riban-bw]

I have installed the Organteq 2 LV2, which works but is suboptimal:

• Does not expose any parameters so sound design must be done with native GUI, e.g. in VNC.
• Does not expose any presets so preset selection must be done with native GUI.
• Takes a long time to initiate which results in zynthian timeout. No audio or MIDI is routed. (Routing will be correctly made if another chain is subsequently added / removed.)
• Takes a long time to change presets / build pipe emulation. (This seems to be reduced on subsequent reselection of the preset (may be cached) but reverts to slow selection if organ is restarted.)
• Appears in the "Synth" group, not the "Organ" group.
• High CPU usage (approx. 30% on each and every core). This isn't too bad but worth noting.
• Without further integration effort, the individual divisions / manuals are not mapped, e.g. can't drive from seperate MIDI keyboards.

I also manually run the native (non-LV2) version and it behaved broadly similar to the LV2 plugin. I suspect the slow start is due to it building its pipe model each time. I cannot see a way to save that for fast start-up. Maybe Modartt would consider adding such an option.

It is a nice organ emulation with lots of configuration options. If someone wants to make it work they can do so manually, albeit with the above limitations. I am not currently convinced that there is sufficient benefit to be had by exherting the effort to integrate into zynthian. There are likely to be few users paying for Organteq (which does not have a lower cost option like Pianoteq does) who are not already satisfied by Aeolus.

It would probably take someone with the approriate programming skills (not that much), enthusiasm and time to implement this. You may find the current core developers lack the latter two of those and hence integration is unlikely in the foreseeable future. Sorry!