I don't know if I didn't install pvst in the right way, but when I clicked on the about button I always had the new version number in a galaxy far, far away ...
Yeah i didn't update the main pvst dll so no new version number visible, i compiled only the pbuzz.dll. Too lazy .
Thanks a lot for still updating your indispensable loader, but after installing b33, all plugins (vst, vst3, buzz, ladspa, dx) appear as unknown in my index and a lot of them do not load anymore when i click on them. What's wrong?
I'm seeing the same problems as thOke and HerrFornit - all VSTs duplicated as "Unknown" Instruments and Effects. When I do a full rescan from Global 2, PVST still sees everything as an Unknown dll.
Loading a 32-bit VST will work the first time, no matter which version (effect of instrument) I choose, though they will not necessarily behave correctly when choosing an instrument as an effect or vice-versa. Then, after restarting Buzz, any VST that was added in the previous session appears as a third correctly indexed version, which works, along with two Unknown versions, which no longer work. When trying to add either of the Unknown versions, the error dialog indicates that it is looking for a file in my 64-bit folder, even though the real plugin is in my 32-bit folder. Interestingly, Buzz seems to know the real location of the VST, as shown in the path when selecting it in the Machines tab, but PVST is looking in the wrong place.
64-bit VSTs don't work at all. They show up as effects and instruments, and neither one works.
I reverted to b31, and everything works fine again, though the scanning process took a loooooong time (I have too many VSTs, I guess).
One thing I noticed with the b33 version was that on startup, there was a lot of disk activity for CompatTelRunner (I think that was the name) accessing files in my VST directories but none for scan.exe, and startup didn't take nearly as long to complete.
I'm using 32-bit buzz, so the version that I used was the 32-bit installer. The trojan result is probably a false positive, but even if it's real, that wouldn't be the cause of any issues I had with the 32-bit version of b33.
I've seen plugins show up as both instruments and effects before, when I had PVST incorrectly installed. I think at that time, I had neglected to copy the bin64 folder from the zip, figuring "oh, those must be the files for 64-bit Buzz, so I don't need those." But of course, those are the loaders for 64-bit VSTs in 32-bit Buzz, so all my 64-bit plugins would show up twice (and of course not load). I think that's maybe just what happens whenever the PVST scan finds a plugin it can't identify - it will show up as both instrument and effect until you actually load it. Then the next time you start Buzz, it will show up correctly because PVST knows what it is.
O.k. Nathan I read your Post. Well if you also use 32bit loader it might be a false positive. Perhaps Frank Can fix it somehow.
But somehow the loader is dumb. I've made a complete rescan and it says 194 unknown dlls and this seem to be all the old vst and vsti I have in my vst folder. Even after use of some synths, restarting, rescanning the loader says they are unknown and they appear twice as effect and generator. Not a single machine is recognized, also no decision if 64 or 32 bit. The only way to get it to work is to load a Plugin and in the menu choose scan for new, restart Buzz and so on, then the loader works, but every Shell scan or full rescan shows every vst as effect and generator.
So finally it doesn't seem to be useful anymore to have a vst folder scanned, o.k. I know in most cases what type of machine the vst is but it looks strange ....
Well I hope Frank can explain why this is so ...
Just one further addition: this time the Version number appears in the losder, but to be honest, in this case I prefer a working loader without the correct Version number ...
-shell vsts support now instruments and effects in one dll
why is this?
There are shell plugins like the Waves one that contain both instruments and effects in one dll. Previously the instruments form Waves always showed up as effect in pvst, that's not the case with the new version.
Thank you, it is working now in the 32-bit Version of Buzz!!
...but the scan.exe in the bin32 folder of the 64-bit version is still detected as a virus here.
Thank you for the response Thoke. I have both files 32 and 64 bit version recognized as a trojan. I Scanned with a usb-virus-stick of a Well known german Computermagazin. 2 of four Scanners see a problem.
Could this hopefully false positives be the reason why the scan.exe files were not copied in the beginning...
I Trust Frank if he says that bis programming environment is clean, ' 'cause I remember what a crap it was with Avira and btd custom stepseq, before Ixix cleaned the false positive.
So I will give it a go ...
5 minutes later: the 32bit version of Polacs loader seems to work very fine here, before I had around 190 unknown plugs and now only 12 the Rest are sorted very fine in all kinds of vst and some Shell Plugins.
Everything seems to be fine, so thank you very much so far Frank ...
-shell vsts support now instruments and effects in one dll
why is this?
There are shell plugins like the Waves one that contain both instruments and effects in one dll. Previously the instruments form Waves always showed up as effect in pvst, that's not the case with the new version.
Thanx for explanation.
After reinstalling the recompiled version, I thought It's the same behaviour (doubling generator/effects). After Full rescan it looks good !!
@Buzztler/theOke I had no virus or bug problem here with the x86
Win10x64 1809, WinDefender. (no Cloud/sample upload)
Malewarebytes, no Problems.
The heuristic search of Avira was used to produce false positives, that's one of the reasons why I changed to Win Defender, since it's detection rates are improved.
On my Win7x64 laptop, I am still using Avira.
Thanks for the new version Polac ! My guess is scan.exe uses some type of compression packer which antivirus heuristics hate as they're usually a good medium for malicious code to be obfuscated into.