Michael Canavan wrote: ↑Thu Dec 30, 2021 12:13 pm
CharlzS wrote: ↑Wed Dec 29, 2021 10:18 am
iTrensharo wrote: ↑Wed Dec 29, 2021 9:24 amIf DP or your plugins update, plugins can disappear again, and you're back to square one. The recent DP 11.03 update has completely broken it for me, to the point that I've uninstalled and just won't bother with it. It's far too much work. There aren't enough hours in the day for me to mess with this anymore.
I can't speak on Waves, specifically, as I don't use their plug-ins.
Sorry to hear your troubles, but this has not been my experience. I have never had a plug disappear. As far as validation across different machines, I have three VST2 plugs that do not validate on two different machines. One machine is an i7 laptop and the other is Xeon workststion. UVI DrumReplacer and the Korg MonoPoly and Korg ARP Odyssey fail on both architectures and all the other VST2 validate with no issues - Izotope, Softube, Korg, Flux, Arturia, McDSP, NI, VSL and Toontrack. I run all the Korg VSTis in VEP anyway, so no issue. There are some issues with VST3 - a few single plugs from multiple vendors (McDSP 6030 Comp, Massive X, a couple of IZ Neutron plugs) do not validate, but that's pretty much it. The plugs are consistent across both PCs. Stuff not validating is not unique to DP. None of my Softube VST3 plugs validated in Studio One (that may have been remedied by an update, but I have not revisited it). The Waves (PSP, etc.) issue was something completely different and unique to how DP was handling the video. Since you're not using those then no issue. You might want to give one last look at how/where the plugs are installed.
It's definitely a configuration issue IMO. The fact you're not experiencing the issue points towards some problem other than a global issue, i.e. it's a rare bug that he caught with his particular software configuration, or VST folder location. It's too late to get iTrensharo to do this but the culprit if it isn't a folder location permission type issue, is likely an errant VST. It's definitely possible to have a VST hose the validation process.
Lol. No. This is a funny read. Excuse me.
1. Contacted support. They [told me they] have gotten other reports of users having the same issue.
2. Not a configuration issue. Has nothing to do with any of that. These plugins do not fail to show up or work in any other Audio/Video application on either of my machines - and I have replicated the issue on two separate machines.
3. All of my plugins are installed in the system directories.
4. It's an issue MOTU is aware of, and I am not the only person who has reported it to them. I'm guessing the M-Audio ASIO Driver working with
literally everything on my system
EXCEPT DP11 is also a configuration issue, too?
C:\Program Files\Steinberg\VstPlugins and
C:\Program Files\Common Files\VST3 are both default system folders for VST2 and VST3 plug-ins. If an application cannot reliably function with plug-ins installed in those locations, then that application is broken, AFAIC.
%ProgramFiles% is a protected directory on Windows. Only Administrators have Write Access by default, but anyone can Read from %ProgramFiles%.
Therefore, it's easy to check for permissions issues, considering:
A. Any subdirectory of %ProgramFiles% inherits its permissions de facto, and
B. Any Files within %ProgramFiles% or its subdirectories inheret its permissions de facto.
So, %ProgramFiles%\Steinberg\VstPlugins has the same permissions by virtue of inhereting from Steinberg, which inherits from %ProgramFiles%
DAWs only need Read Access to this directory, which the system grants to any user or application by default, unless the administrator of the system changes this himself (which is likely to break more than just ONE DAW on the system). As a result, the easy check for permission errors is simply to do File -> Open in Digital Performer and navigate to C:\Program Files\Steinberg\VstPlugins and C:\Program Files\Common Files\VST3 within that dialog. The File Open Dialog will be running with the permissions level of the Digital Performer DAW (the application that opened the dialog).
If the Open Dialog can navigate to those directories without a UAC Prompt or Permission Denied error, then ... the permissions issue does not exist.
Again, the DAW only needs READ access to access those locations. You'd have to be running DP on a very limited account, probably with additional - group policy-imposed limitations to have issue with that. I am not.
Lastly, and most unremarkably, it should be known that user applications run by default under the permissions of your user account - so really, checking this in DP isn't REALLY necessary. If you can go to those locations in File Explorer, then any application you launch should be able to read from them without issue.
An errant VST is likely to cause issue in at least one other host. I have tried several to see if I could get any of those that trip up the validator to choke...
Cubase
Studio One
Cakewalk by BandLab
Sound Forge Pro
WaveLab
Samplitude Pro X4 (Known for flaky VST3 Support, so a nice stress test for them)
DaVinci Resolve Studio (Newly added VST3 Support, not even that robust... but works as expected)
This does not happen. They "just work." The issue is certainly not the VST Plug-ins.
In any case,
the issue has been reported by other users, as I have been told this directly. So, they are aware of it. It's probably just a hard issue to fix, given the manner in which they support VST (by going through their MAS system, while many other DAWs support them directly) and how inconsistent it can be in terms of presentation.
1. What plug-ins Pass and Fail the validator is completely inconsistent across different machines, and even across VST Cache Clears on the same machine.
2. Updating a plug-in can push it from Pass -> Fail and vice versa, due to automatic Re-Validation when DP sees the change.
3. The Re-Validation can cause the plug-in to disappear from all plug-in choosers (again).
This means that someone at MOTU can look at a Windows system there and see something that appears to be working properly, while the end user is seeing different behavior. Whatever validation process they are using for VST is not reliably consistent, and this will make it a royal PITA to troubleshoot and find/target/fix any issues therein.