would they work in ardour? I know ardour has very advanced possibilities for ambisonics setups via ambdec etc… but this would be a great addition I think.
Would this also cause a problem? I thought Ardour required flexible block sizes now.
“the plug-ins support sampling rates of 44.1 or 48kHz, and block sizes that are a multiple of 64 or 128 samples”
That sounds like they use some stock convolution engine. This can probably be addressed if needed.
This has always been the case
It’s only used for
sample accurate plugin parameter automation
Looping
Varispeed
Assume a cycle of 1024 samples
(1) Process 567 samples, change parameter, process remaining 457 samples. This is done per plugin (not the whole session) [4].
(2) When reaching the loop point, run for 123 samples, loop-locate, process 901 samples. – This happens session-wide (all processors).
(3) is new in Ardour6. When you play at speed 125%, Ardour runs for 1024 * 125% = 1280 samples and resamples the result to output 1024 samples. This likewise affects all processors of the session.
so in summary: don’t automate the plugin, don’t loop, don’t vari-speed.
–
[4] LV2 plugins can ask to ignore this sample-accurate automation: http://lv2plug.in/ns/ext/buf-size#coarseBlockLength . LV2 plugins could also use time-stamped event-sequences instead of classic parameters. VST3 also offers time-stamped changes.
Is that self-compiled version or their binary? Do you perhaps have a HiDPI screen or a multi-screen display with effective large resolution which may trigger the plugin to scale up?
I did local-compile using the JUCE project (not cmake) and that works
/usr/bin/dconf read /com/ubuntu/user-interface/scale-factor
/usr/bin/gsettings get org.gnome.desktop.interface scaling-factor
…and falls back to use a scale-factor depending on display’s DPI. There does not seem to be an easy way to override this. Also JUCE assumes that the host “knows” about the scale factor. The relevant code is