Problem
Ein Plug-in weigert sich zu scannen und blockiert den Scanvorgang scheinbar auf unbestimmte Zeit.
Ursache
Manche Plug-ins scheinen eine sehr lange Zeit damit zu verbringen, etwas zu tun und dann nicht mehr zurückzukehren. Sie können den Lizenzstatus prüfen, versuchen, eine Verbindung zu einem Server herzustellen oder was auch immer. Manchmal öffnet ein Plug-in ein Dialogfenster, das vielleicht verdeckt oder anderweitig versteckt ist, so dass du es nie beenden kannst.
Lösung
Gedulde dich und warte 3 Minuten, dann schließt der Scanner das Plug-in aus und fügt es der Datei BannedPlugins64.txt in /Bibliothek/Application Support/Cognitone/Resources (Windows: C:\ProgramData\Cognitone\Resources) hinzu.
Wenn du das Scannen aller Plug-ins von Grund auf wiederholen möchtest, kannst du das jederzeit tun. Wähle einfach die Option Alle scannen (zurücksetzen), bevor du einen Scan startest.
Comments
Sa., 09.09.2023 - 14:56 Permalink
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
Mi., 28.02.2024 - 00:06 Permalink
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.
Mo., 29.12.2025 - 15:07 Permalink
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.
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.
Mo., 29.12.2025 - 19:25 Permalink
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