IK Multimedia Pianoverse is BLOCKED by S1 7.2.3

[shanabit]

Hey fellas, this is the ONLY plugin that is showing up in the BLOCKED LIST. I have Reset the blocklist and re-scanned plugins a few times. S1 blocks it every time.

I ONLY have VST's running in S1 on my M1 Mac running Tahoe 26.2 with AU disabled. Both Cubase 14 and Reaper 7 load it just fine so it kind of narrows it down to S1, just not sure how to fix the issue? Thanks for any help. I think it would be the same in the new StudioPro as well. IK is all current as well.

 

[dean.winter]

Sorry you're having problems. Potentially not much help, but it works here on Windows. I know you mentioned you re-scanned, but did you remove plugin settings first? That usually gets me sorted when stuff like that happens.

Dean

 

[shanabit]

I deleted them again for a second time and it seems to have taken. Thanks for the help

 

[Lukas]

Don't forget that plug-ins on the Blocklist usually mean that these plug-ins crashed during plug-in scan. So it's always worth a try re-scanning the same plug-in. If the crash persists, then you should reach out to the plug-in developer.

 

[shanabit]

Don't forget that plug-ins on the Blocklist usually mean that these plug-ins crashed during plug-in scan. So it's always worth a try re-scanning the same plug-in. If the crash persists, then you should reach out to the plug-in developer.

Thanks

 

[Davey]

Don't forget that plug-ins on the Blocklist usually mean that these plug-ins crashed during plug-in scan. So it's always worth a try re-scanning the same plug-in. If the crash persists, then you should reach out to the plug-in developer.

Scaler 3 is hit and miss to scan and I think it's just the length of time it takes to initialise rather than an all out crash.
Of course S1/SP can't really tell the difference between those things. All it can see is that it asked the plugin to initialise and it hadn't done it in a sensible timeframe. From the scanner log it looks like S1/SP has a timeout of about 12 seconds. When it scanned successfully it looked to be taking typically 9 or 10 seconds so uncomfortably close to that timeout. All it takes is one of those fun random Windows background tasks to hog the CPU/Disk for a wee while and you are over the limit.

I don't know if the VST spec specifies the max times but maybe there is scope to increase that timeout a little. Or have a second scanning function that you could call "slow scan the awkward buggers" or something. Once it has scanned it is fine because the data is cached.