Einige Plug-ins blockieren einen Scan

Which syntax is needed for the entries in BannedPlugins64.txt?
Something like "WAVESTATION (VST)" as shown in the Scanner.log or only "WAVESTATION" seems not to work.

Ok, this works:
C:\Program Files\Steinberg\VSTPlugins\KORG\WAVESTATION.dll
 

I couldn't find the BannedPlugins64.txt file in the path mentioned above for Windows, but managed to find it in C:\Program Files\Cognitone\Audio\Resources

Not sure if it's right to update that file directly but it did allow me to skip a couple of plugins that were causing issues.

For the record, I achieved (at least temporary) satisfaction here by copying the contents of the Synfire-written file BrokenPlugins64.txt into 

C:\Program Files\Cognitone\Audio\Resources\BannedPlugins64.txt 

This did successfully cause the constant re-scan of the reported broken plugins on every startup to cease.

After this, there were still a few stragglers, plugins that never made it into BrokenPlugins64.txt, but which were continuing to delay Synfire's startup.

I captured a screenshot of the announcement of the stragglers,

then found those plugins and manually added them to BannedPlugins64.txt.

As of 20251229, my BannedPlugins64.txt file has 25 lines in it.

C:\Program Files\Steinberg\VstPlugins\iZBreakTweaker.dll
C:\Program Files\Common Files\VST3\AAS Player.vst3
C:\Program Files\Steinberg\VstPlugins\iZVocalSynth2.dll
C:\Program Files\Common Files\VST3\Steinberg\Dark Planet\Dark Planet.vst3
C:\Program Files\Vstplugins\UJAM\VD-DEEP.dll
C:\Program Files\Vstplugins\Triebwerk\Triebwerk.dll
C:\Program Files\Vstplugins\Loom_x64.dll
C:\Program Files\Vstplugins\UJAM\USYNTH.dll
C:\Program Files\Vstplugins\UJAM\VD-HOT.dll
C:\Program Files\Vstplugins\UJAM\Virtual Pianist.dll
C:\Program Files\Common Files\VST3\Piano V.vst3
C:\Program Files\Common Files\VST3\Steinberg\Hypnotic Dance\Hypnotic Dance.vst3
C:\Program Files\Common Files\VST3\Steinberg\Symphonic Orchestra\Symphonic Orchestra.vst3
C:\Program Files\Common Files\VST3\Steinberg\vstviewer.vst3
C:\Program Files\Common Files\VST3\Steinberg\VST Connect\VST Connect.vst3
C:\Program Files\Common Files\VST3\Steinberg\HALion Sonic SE\Halion Sonic SE.vst3
C:\Program Files\Common Files\VST3\Steinberg\HALion 5\HALion 5.vst3
C:\Program Files\Common Files\VST3\Steinberg\Triebwerk\Triebwerk.vst3
C:\Program Files\Common Files\VST3\USYNTH.vst3
C:\Program Files\Common Files\VST3\VD-DEEP.vst3
C:\Program Files\Common Files\VST3\VD-HOT.vst3
C:\Program Files\Common Files\VST3\Virtual Pianist.vst3
C:\Program Files\Common Files\VST3\Steinberg\Groove Agent.vst3
C:\Program Files\Common Files\VST3\Steinberg\Padshop.vst3
C:\Program Files\Common Files\VST3\Overloud\TH3-64.vst3

FWIW, UJAM and Steinberg plus were the primary offenders.

At this moment in time, I have Synfire starting up without any obvious hangs or reported plugin errors.

The files in BrokenPlugins64.txt should not be scanned again unless you run a scan with the reset option. Moving them to BannedPlugins64.txt bans them permanently no matter how you run a scan