Thanks Derrek, and Daniel! And thank you for the welcome.
Ahh, I see! I’ve been using the BBCSO Discover playback template. If I revert to HSSE, or switch to NotePerformer, it is much quicker.
I’m a software engineer at one of the big tech companies, so please forgive me for throwing out some ideas while I think through this! Hopefully this is helpful:
It looks like Dorico is actually trying to wrap-up the VST loading for the first instance (or it’s doing something else) before it will let me save, close, or open another project. I just tried going from a BBCSO project to a Silence project, and it does indeed hang, so I don’t believe an activation button would help unless it allows the original VSTs to continue loading. It’s probably a stretch, but the blue-sky solution would be to allow multiple instances of Dorico to load their VSTs simultaneously, right? (I’m guessing that’s a much larger architectural discussion.) If that’s not possible, it might be better to have an interrupt on VST loading. The VSTs are currently loading on a background thread, if I’m not mistaken – which is a great user experience – but there’s a semaphore/lock on the main thread when you try to save, close, or open another project. Perhaps during or after each individual VST loads, it would be worth checking-in to see if the UI or project state has changed? If the user wants to interact with something that requires the audio engine, or they need to switch projects, Dorico could pause or abort the VST load at that point.
By chunking, there would still be some input lag, but it would probably remain under the ‘magic’ 10 seconds. In short: since activation takes a long time, it should be a cancelable task.
Steps to reproduce:
- Load a project using the BBCSO playback template
- Within a few seconds, save or close, or load another project that has the Silence playback template
- System hangs
Is there a way to file a detailed bug report with the team, or is this the best way to provide feedback?