Win10 preventing VST export
Posted: Wed Jun 17, 2020 3:20 pm
Hey,
Since a few days I'm struggling to export/create/render a very simple plugin in VSTi.
AT first, I thought it was because of my bad programming skills ...
I tried my exported VSTi in Acid (which is my main DAW), in FL (last version 20.something, updated last week), no cubase ( I own a old version, so I did not install it when I switched to WIN10), but no luck... each time the plugin is considered as failing...
So I also tried the exportation with FS 3.06, didn't work... FS 3.08... same deal... Still thinking it comes from a bug inside my schematic... So last resort...export with alpha... and then... I got that...
The plugin finally loaded after this 10 sec scan... (but was not working because of the rendering with alpha )
Weird thing is that I didn't get this message with export from 3.06 or 3.08...
But I'm pretty sure it was the same thing that prevented my VSTi to be recognized as valid...
So I don't know how to work around this...
Maybe it's the name I gave to the plugin (DTfPMF) that looks really like a virus name that generates this WIN10 behaviour.. I don't know...
It probably comes from a recent WIN10 update, as I've switch to WIN10 2 years ago, and was never confronted to this before...
I've looked to the page linked to the message, and seriously... put me to thinking.. this is becoming too much...
If working on your own machine becomes such a PITA because of all these security barriers, I think I'm gonna give up...after all these years...
here is the page link:
https://docs.microsoft.com/en-us/window ... -antivirus
As anyone encountered the same issue?
One last word... Just stick to XP and push at max the time you'll switch to WIN10... really... This OS is a real nightmare... I miss so much my WIN2K machine
Since a few days I'm struggling to export/create/render a very simple plugin in VSTi.
AT first, I thought it was because of my bad programming skills ...
I tried my exported VSTi in Acid (which is my main DAW), in FL (last version 20.something, updated last week), no cubase ( I own a old version, so I did not install it when I switched to WIN10), but no luck... each time the plugin is considered as failing...
So I also tried the exportation with FS 3.06, didn't work... FS 3.08... same deal... Still thinking it comes from a bug inside my schematic... So last resort...export with alpha... and then... I got that...
The plugin finally loaded after this 10 sec scan... (but was not working because of the rendering with alpha )
Weird thing is that I didn't get this message with export from 3.06 or 3.08...
But I'm pretty sure it was the same thing that prevented my VSTi to be recognized as valid...
So I don't know how to work around this...
Maybe it's the name I gave to the plugin (DTfPMF) that looks really like a virus name that generates this WIN10 behaviour.. I don't know...
It probably comes from a recent WIN10 update, as I've switch to WIN10 2 years ago, and was never confronted to this before...
I've looked to the page linked to the message, and seriously... put me to thinking.. this is becoming too much...
If working on your own machine becomes such a PITA because of all these security barriers, I think I'm gonna give up...after all these years...
here is the page link:
https://docs.microsoft.com/en-us/window ... -antivirus
As anyone encountered the same issue?
One last word... Just stick to XP and push at max the time you'll switch to WIN10... really... This OS is a real nightmare... I miss so much my WIN2K machine