Good hint @claude_g_lapalme .
And yes, please do if you have the time for it.
00:04:48 (just under 5s) EC; instantaneous FC
00:04:47 (just under 5s) EC; instantaneous FC
00:04:49 (just under 5s) EC; instantaneous FC
All three files in cache here (zipped after 3rd cycle):
VST3.zip (2.7 KB)
1 Like
With just Steinberg plugins
Dorico EC 3secs FC >1sec
vst3plugins.xml (15.9 KB)
Cubase 14 EC 2 secs FC >1sec
vst3plugins.xml (15.9 KB)
With all my plugins
Dorico EC 1min51secs FC 7sec
vst3plugins.xml (670.2 KB)
Cubase 14 EC 1min15sec FC 7 sec
vst3plugins.xml (670.2 KB)
Windows 10 AMD5950x 32G
1 Like
1st run: 25 secs, thereafter instantaneous
2nd run after emptying cache: 5 secs, thereafter instantaneous
AMD Ryzen 7 8700G w/ Radeon 780M Graphics 4.20 GHz 64Gb RAM
vst3plugins.xml (26.6 KB)
1 Like
EC: 3.75s FC: .03s
EC: 4.30s FC: .03s
EC: 4.34s FC: .03s
MacBook Pro M1Max, 64GB, Sequoia 15.2
vst3plugins.xml (61.9 KB)
1 Like
2020 MacBook Air M1 Mac OS 15.1
Total Number of Cores: 8 (4 performance and 4 efficiency)
Memory: 16 GB
Plugins: 7
Dorico 5.1.60.2187
ROUND 1
< START WITH EMPTY CACHE FOLDER>RUN 1: 0.81s user 0.39s system 49% cpu 2.416 total
RUN 2: 0.01s user 0.03s system 57% cpu 0.071 total
RUN 3: 0.01s user 0.02s system 77% cpu 0.051 total
RUN 4: 0.02s user 0.02s system 85% cpu 0.045 total
ROUND 2
< MANUALLY EMPTY CACHE FOLDER >RUN 1: 0.81s user 0.41s system 47% cpu 2.544 total
RUN 2: 0.02s user 0.02s system 84% cpu 0.047 total
RUN 3: 0.02s user 0.02s system 84% cpu 0.047 total
RUN 4: 0.02s user 0.02s system 85% cpu 0.048 total
2022 Mac Studio M1 Max Mac OS 14.6.1
Total Number of Cores: 10 (8 performance and 2 efficiency)
Memory: 64 GB
Plugins: 23
Dorico 5.1.60.2187
DORICO ROUND 1
< START WITH EMPTY CACHE FOLDER >RUN 1: 1.72s user 1.07s system 6% cpu 44.596 total
RUN 2: 0.02s user 0.03s system 85% cpu 0.055 total
RUN 3: 0.02s user 0.03s system 88% cpu 0.047 total
RUN 4: 0.02s user 0.03s system 74% cpu 0.067 total
DORICO ROUND 2
< MANUALLY EMPTY CACHE FOLDER >RUN 1: 1.40s user 0.56s system 35% cpu 5.559 total
RUN 2: 0.02s user 0.03s system 86% cpu 0.055 total
RUN 3: 0.01s user 0.02s system 85% cpu 0.046 total
RUN 4: 0.02s user 0.03s system 83% cpu 0.058 total
Cubase 14.0.5.125
CUBASE ROUND 1
< START WITH EMPTY CACHE FOLDER >RUN 1: 1.33s user 0.52s system 31% cpu 5.924 total
RUN 2: 0.03s user 0.04s system 41% cpu 0.167 total
RUN 3: 0.03s user 0.03s system 40% cpu 0.163 total
RUN 4: 0.04s user 0.04s system 41% cpu 0.184 total
CUBASE ROUND 2
< MANUALLY EMPTY CACHE FOLDER >RUN 1: 1.34s user 0.53s system 34% cpu 5.463 total
RUN 2: 0.03s user 0.04s system 43% cpu 0.163 total
RUN 3: 0.03s user 0.04s system 40% cpu 0.178 total
RUN 4: 0.03s user 0.03s system 38% cpu 0.158 total
NOTE: Forgive my near (Mac-) Terminal illiteracy, but I should mention that I ran these tests with Dorico running on the MacBook Air, but neither Dorico nor Cubase open on the Mac Studio. Is that a relevant factor, @Ulf ?
1 Like
so - tried a few things and I think Iāve crashed it.
[EDIT ugh I quit the process accidentally - it didnāt update the .xml file though.]
Dorico 5 pro
Scan 1.time: 16.13 s EC, 1.0s FC, 1.0s FC
Scan 2.time: 14.48s EC, 1.0s FC, 1.0s FC
vst3plugins.xml (58.2 KB)
Spec:
OS: Microsoft Windows 10 Home
Prosessor Intel(R) Coreā¢ i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 kjerne(r), 12 logiske prosessor(er)
I canāt remember, but I think the comp is at least 8 year old, 2016 or something.
Cubase 14 pro
Scan 1.time: 14.03 s EC, 1.0s FC, 1.0s FC
Scan 2.time: 13.81s EC, 1.0s FC, 1.0s FC
Jon
1 Like
3min30sec EC, 1sec FC
2min50sec EC, 1sec FC, similar times on 3rd & 4th run
Processor AMD Ryzen 7 3700X 8-Core Processor 3.60 GHz
System type 64-bit operating system, x64-based processor
Ram: 64Gb
Edition Windows 10 Home
Version 22H2
Installed on ā9/ā4/ā2022
vst3plugins.xml (320.8 KB)
1 Like
FYI
I rebooted and now my FC scans are taking 22-25 seconds for my full (huge) plug-in scan. It was 7 seconds before the reboot.
[EDIT 2 the 25 second scans were with procmon64.exe doing process monitoring. Goes back to 7 secs if I quit procmon64.]
1 Like
Hi @Ulf
Although I am not having any problems in Dorico right now, I am working on your instructions but running into some interesting things.
The first scan had been going for about 13 minutes and then I finally cancelled it because I was tired of staring at the command with my stopwatch waiting for it to finish. I made sure the processes were ended. Then, I instead created a simple Windows batch file script that would display the time and then run the command you provided and display the time again, to avoid having to use a stopwatch. Then I made sure the DoricoCache folder was empty and it still was, so I ran the command again with my batch file.
This time I added the āCommand Lineā column to my windows Task Manager so I could see the plugin that it was trying to scan at each step. I could see it successfully get through most of the alphabet, but it is getting stuck on the Rhodes V-Pan plugin, V-Pan.vst3.
This is a plugin that I got as a freebie that I donāt really want or use that uses a very bad copy protection scheme called CodeMeter, which I disabled because CodeMeter was preventing my Windows from updating.
It is getting stuck trying to load the plugin, presumably because CodeMeter is not actually running on my system, as I had disabled the services since I wasnāt using this plugin and my Windows could not install any updates with the CodeMeter license services running.
I do not expect it will start working on its own - I think probably I should just uninstall V-Pan and try again, and then it should complete just fine. But I wanted to check with you first to see if there were any additional things you wanted me to try.
The situation here might be more of a problem if I was not very tech-savvy and did not know how to add the command line column to the task manager to monitor which plugin it was scanning at the time. There are no popups or messages coming up from the plugin or anything of the sort - it is just silently hanging, but it is preventing the VST scanner from going any further.
3 Likes
Hi @mducharme , this is exactly the stuff Iām always talking about. This is one of the cases where the scanner just gets stuck for no apparent reason, but it hangs indefinitely and thatās when people come here to the forum and blame it all on Dorico.
Certainly, we can handle this better and we will put a time out in, so that we break off the operation after some time and continue scanning. This improvement point we already have on the list.
But go ahead now and uninstall that troublemaker and continue the scanning. Maybe there are even more of such zombies.
And thanks again for participating.
5 Likes
DORICO 5 TESTS
3 min 12.52 sec EC
2.23 sec FC
2.09 sec FC
2.02 sec FC
2 min 35.38 sec EC
1.89 sec FC
1.67 sec FC
1.57 sec FC
CUBASE 14 TESTS
3 min 31.04 sec EC
1.72 sec FC
1.63 sec FC
1.70 sec FC
2 min 50.61 sec EC
1.95 sec FC
1.65 sec FC
1.66 sec FC
vst3plugins-cubase.xml (385.1 KB)
vst3plugins-dorico.xml (385.8 KB)
Windows 11 Pro, AMD Ryzen 3900X (2019), 64GB RAM
1 Like
Run 1: 34.43s EC
1.06s FC
Run 2: 36.98s EC
1.01s FC
vst3plugins.xml (87.0 KB)
Windows 10. i5-7500 CPU @ 3.40GHz
1 Like
Iām not sure Iām doing this correctly but hereās what I see:
run 1: 3.51s user 3.18s system 14% cpu 45.076 total
run 2: 0.03s user 0.04s system 90% cpu 0.076 total
run 3: 0.03s user 0.04s system 91% cpu 0.080 total
If this is accurate then I see this for plugins:
| grep '<plugin>' | wc -l
80
vst3plugins.xml (95.2 KB)
MacBook Pro, M3 Pro, 36 GB, docked with a lot of stuff attached.
1 Like
My results for Dorico 5 and Cubase 14:
(I can send you the .xml files privately if you would like)
Dorico 5
RUN 1
1min 31sec EC
instantaneous FC
instantaneous FC
RUN 2
46sec EC
instantaneous FC
instantaneous FC
RUN 3
43sec EC
instantaneous FC
instantaneous FC
Plugin count: 186
Cubase 14
RUN 1
43sec EC
instantaneous FC
instantaneous FC
RUN 2
43sec EC
instantaneous FC
instantaneous FC
RUN 3
43sec EC
instantaneous FC
instantaneous FC
Plugin count: 185
PC / OS
AMD Threadripper 3970 / 256 GB ram / Windows 11 32H2 OS build 22631.4460
1 Like
Run 1: 4:20 min EC, instantaneous FC (tested 5 times)
Run 2: 3:29 min EC, instantaneous FC (tested 5 times)
Run 3: 3:53 min EC, instantaneous FC (tested 5 times)
676 plugins
Intel i9-9900K 3.60GHz , 64 GB, Windows 11 Pro 23H2
1 Like
wow ā¦ just wow 
1 Like
Very few VSTs on this M4 Pro Macbook, but
first run: 00:04.10 (4.10 seconds)
second run: instantaneous
third run: instantaneous
Emptied cache.
next run: 00:01.96
second run: instantaneous
third run: instantaneous
vst3plugins.xml (15.3 KB)
1 Like
Itās the number of plug-ins thatās important.
1 Like