Sparta vsts plugins work in ardour?

I just found out about these plugins

http://research.spa.aalto.fi/projects/sparta_vsts/plugins.html

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.

Since they’re using JUCE and the source code is available, they can be made to work.

However I expect that first the following issue has to be addressed:

1 Like

fantastic Robin, I keep my fingers crossed…

These plugins look very cool

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

  1. sample accurate plugin parameter automation
  2. Looping
  3. 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.

1 Like

The do now, but depending on your OS you may have to compile them from source, still, since the provided binaries depend on recent system libs.

1 Like

I m on linux! thanks , I will test them out!!

hmm it still seems to be the gui out of place… but not sure, it might be my specific configuration…

At least the font renders nicely large :slight_smile:

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

well, the plugins load and the GUI shows, I don’t have an ambisonics system to actually test it.

haha yes it s a hidpi 4k screen, this might be the cause…

I just copied there linux version from here

and followed the readme , copying the files in the vst folder etc. so no compiling!

this might be still the old version…?

No. That would not load at all.

Yes. JUCE tries to query the scale using

/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