Hey, guys.
Still trying to diagnose the VST3 plugin for Montage not being recognized by the scanner. I was wondering if it writes out logs somewhere, and / or if it can be launched in “verbose” mode to capture more diagnostic information.
Anyone have information on this?
There is this - https://owlplug.com/ - which lets you manage your VSTs.
It’s a bit wonky but might help.
Hi, I have also looked everywhere for such a log file, but haven’t found one.
So I snooped around a bit in Cubase13.exe. There is a string “-prefPath”, which also occurs in vstscanner.exe (scan client) and vstscannermaster.exe (scan master) and is apparently accepted as a command line parameter by these apps to define a Preferences file. This Preferences file could be configured and passed from Cubase13.exe to the scanner master at the start of the scanning process, thus allowing Cubase to control the scanning process.
The interesting thing is that there is also a string “scanlog.txt” in Cubase13.exe. Therefore it’s quite likely, that a log file with this name is written during the scanning process, presumably in %TEMP%. However, it may be deleted as soon as the scanning process is complete.
That said, it would be necessary to find out (e.g. with ProcMon) whether this log file is written, and if so, what’s its content.
Thanks, Phil. Appreciate the link.
@ASM, I had completely forgotten about ProcMon and other Sys Internals tools, good thought.
I did the same thing as you in terms of looking at the options on the scanner apps, but I didn’t go so far as to look into the cubase exe.
Hadn’t thought to look in %temp% and while I didn’t find any reasonable suspects for log files, I did find and delete 18GB of 57,000 tmp files dating back to 2020. Sheesh, do devs not clean up after themselves anymore?
I was looking in the Yamaha plugin folder and saw a license file that told me they developed it using JUCE. I then Googled and found some conversations on their forum in September of 2023 about a new version of JUCE causing many vst3s to no longer be recognized. It wasn’t my exact scenario, but I think there’s a good possibility that it may be a bug in the Yamaha vst caused by a bug in their dev tools. I posted to the Yamaha site, but who knows if it’ll ever get forwarded to the devs.
Still, it would be nice to have some kind of conclusive evidence of why it’s flaming out, i.e. an error log report from the scanner.
<= 