Strange One - Studio Pro v8.1.2 - Plugin Scanner crash with Scaler 3?

[Vocalpoint]

Been tracking an oddball scenario with Studio Pro v8.1.1 and now v8.1.2 specifically with Scaler 3.3.x.

Over the last couple of weekends - I finally completed a brand new (from bare metal) digital audio workstation with Windows 11 25H2 and a clean install of everything - one by one. When I got to the Scaler install last week - I noticed some oddball messaging appearing in Event Viewer - that was both interesting and alarming at the same time.

The readout looks like this:

A very specific "crash" of the Studio Pro plugin scanner when taking a run at the Scaler 3,vst3 plugin. This issue is recorded in Event Viewer and then the scan happily finishes it's run and Studio Pro opens normally.

Now - not only is the crash of the "plugin scanner" (of all things) not normal - it's the fact that Studio Pro seems to "allow" this plugin to pass the gates for entry into the app - even after all this nonsense has occurred.

I always thought that the plugin scan had a defined purpose - one that establishes a baseline for entry INTO the app space and if a suspect plugin comes along - this scan was supposed to identify said dodgy plug-in and automatically blacklist it.

In this case - not only does the scanner bottom out and die - the plugin that caused it to do that seems to get a free pass to continue on into the app space - to potentially wreak more havoc.

I would have never noticed this IF I wasn't specifically testing each plugin of mine via clean install.

This is the only plugin (out of 146) that I have active right now that is doing this. So I am unsure whether this is a Studio Pro issue exclusively OR a Scaler 3 issue.

One thing that "might" absolve Studio Pro - is this exact same thing happens in Native Instruments Komplete Kontrol (ni-plugin-info.exe) application as well:

I am in contact with the Scaler folks - but for those using Scaler 3 (And/or Komplete Kontrol v3.5.4) out there now (specifically the VST3) - can anyone check Event Viewer for anything similar to the above?

Would love to know if it's just me - or something a bit more wide spread....

Cheers

VP

 

[BobF]

VP - I've been running this new machine, Win11-latest for a few months now along with Scaler3.3 and FSP-latest. I have zero events for either in the logs. I updated Scaler to 3.3.1 today and the rescan didn't generate any events. Yes, VST3 ...

Maybe there is a place to look for events that is unknown to me

 

[Vocalpoint]

VP - I've been running this new machine, Win11-latest for a few months now along with Scaler3.3 and FSP-latest. I have zero events for either in the logs. I updated Scaler to 3.3.1 today and the rescan didn't generate any events. Yes, VST3 ...

Maybe there is a place to look for events that is unknown to me

Bob

Much appreciated and VERY valuable info.

Could be something going on here - and maybe only here - then.

But IF there was an issue with Plugin Scanner - wonder why it only shows itself on this specific plugin?

I will continue my analysis.

VP

 

[BobF]

Bob

Much appreciated and VERY valuable info.

Could be something going on here - and maybe only here - then.

But IF there was an issue with Plugin Scanner - wonder why it only shows itself on this specific plugin?

I will continue my analysis.

VP

Scanner reports 251 plugs here. NI, Native, IK, IL, Scaler, toontrack, XLN, Waves, Nomad Factory, etc with zero errors scanning. I doubt seriously that there is a problem (distributed) in the scanner.

I would look for disk errors in Event Viewer and maybe do a clean uninstall/reinstall of Scaler

 

[Vocalpoint]

Scanner reports 251 plugs here. NI, Native, IK, IL, Scaler, toontrack, XLN, Waves, Nomad Factory, etc with zero errors scanning. I doubt seriously that there is a problem (distributed) in the scanner.

I would look for disk errors in Event Viewer and maybe do a clean uninstall/reinstall of Scaler

Agreed. The scanner comes back 100% clean on 145 of my plugins - it's #146 it does not like.

I submitted a support ticket to Fender with analysis, dmp files, screencaps etc. We shall see if they come back with anything.

There is something going on here since NI's Komplete Kontrol scanner is also kicking back a very similar error.

I will find it.

VP

 

[sintil8]

Bit of a Wildcard suggestion, what happens if you run Scaler 3 as a stand alone?

Does it run outside the DAW OK...

If I recall NI used to suggest running Maschine and KK in stand alone, after updates, whether that is still the suggested thing I wouldn't know !

Regards