Thank you for taking a look, @Ulf . No more issues here, fortunately. Hope you have a great one!
I will check but I think I completely deleted it.
Doing things with the Shared Components folder was all that I did in the last portion of troubleshooting. At first I had tried restarting Dorico like 5-10 times, each time “continue to wait” for a few minutes every time it popped up and eventually giving up and “terminate”. Rebooting did nothing - happened again a few times. Found this thread and reinstalled the update, but that did nothing, led to me starting Dorico, “continue to wait” for a few minutes, then terminate, and retrying that process another 5 times. Still nothing.
Then after all those tries I renamed the shared components folder, trying again to start, it immediately started correctly. At that point I renamed the shared components folder back. Since I knew it would cause the problem again, I tried to delete things from the Shared Components folder, so I found these old VST transit things and I know VST transit was discontinued, so I deleted those, and also this ancient DLL file from 2013 for eucon. So then all I had left in the Shared Components folder was something from wavelab (a new file installed this year) and the Halion Sonic SE subfolder, which had a few dll files from 2022 and a few other files inside it. When starting Dorico with just those two things left in the Shared Components folder, it didn’t start again with the same problem as before. So I terminated the startup in the dialog and then deleted the Halion Sonic SE subfolder from inside Shared Components. Then I started it again and it started correctly.
Thanks a ton @mducharme for reconfirming. Because that means my fix is not good enough, so I need to have a look again at it.
Thank you Ulf for helping me.
I’ve attached the zip file of vstscanner
Let me know if I can do anything more.
vstscanner.zip (1.3 MB)
Hi @psmk31452 , thanks for the data. What I can immediately see in the debugger that your vstscanner has loaded Bohemian Cello.vst3, so most likely it is hanging in there.
If you go to C:/Program Files/Common Files/VST3 and temporarily move that Bohemian Cello out there, e.g. to the Desktop; then kill all processes with VST in the name and the Dorico app as well. If you then try to launch Dorico again, does it behave better then, not hanging indefinitely?
Thanks a ton
Thanks again, Ulf.
I’ve moved the Bohemian Cello out of the Common Files/ VST Folder.
Now to kill all processes with VST in the name and the Dorico app as well…is this done in the Task Manager?
And you mention to kill all processes with VST in Dorico also…how is that done?
Sorry, I’m in unchartered water with this.
By the way I also have a Behemian Viola and a Bohemian Violin, should I leave those alone?
I copies the VST Boehmian Cello to my Desktop and then went back to delete the Bohemian Cello VST from the Common Files/VST Folder and I get the message,
File In Use
“The action can’t be completed because the file is open in VST 3 Plug-in Scanner”
Close the file and try again
Yes, you would kill those processes via the Task Manager but to make it simple a reboot does also do the job… The pros among us use Process Explorer for that but its up to you.
Same problem so I’ve added the new VSTScanner files
vstscannermaster.zip (1.3 MB)
I’m getting somewhere.
I tried to open Dorico again but this time I deleted the Bohemian Viola and the Bohemian Violin.
Then Dorico was hanging on some iZotope plug-ins. Everytime izotope does updates on their plug-ins their installer installs even the older VST’s and even Cubase Blocklist them.
So, I then deleted the iZotope plug-ins and Dorico opened right up.
Now that means Great News but also begs the question…how do open Dorico with my 3 Bohemian VST’s?
The Cello, the Viola and the Violin?
Any suggestions?
Have you checked for updates of the Bohemians?
I will do that.
I thank you for all of your help, Ulf.
I owe you a beer.
You are more than welcome.
And the list is getting longer, see Shout-out to ULF! - #4 by Ulf
Hello! UIF!!
I have another bug related to the audio engine and I will send you a diagnostic report!
Can you check it for me?
Hi @Yoshiaki_Watanuki , thanks for the data.
Contained is 1 crash dump of the audio engine and running that through my debugger shows me a crash some where in the operating system code. Basically the audio engine was idling around when suddenly the crash happened. Must be corrupted memory or so, because normally it would not crash in such location.
What were you doing at that time? Was there anything particular that you did?
Thank you for verifying this!
The only other time I was operating Dorico I was running Google Chrome!
When you say the memory is corrupted, do you mean physically?
My PC is old, so maybe it is.
Hi @Yoshiaki_Watanuki , no, if physically corrupted memory, it would give you crashes all over the place, also in other applications.
But memory corruptions can happen in software as well, when some code or module overwrites memory when for example using a wrong index to a memory location. These problems are most difficult to find and eliminate. But as I said, this is just an assumption, because otherwise I can not explain an application crashing at that particular location.
Other than that I can not say at the moment. So we have to keep an eye on it and please report again if you get crashes.
Thanks!
I understood!
I will continue to verify the operation!