If I close a project by closing the window, sometime the starting page will not appear. I had to end Dorico in task manager. Then when I try to start Dorical again the loading screen got stuck on “wait for audio engine initialization”.
Also I can only hear from the left channel on my laptop.
After Dorico crashed twice I finally could open Device Control Panel. I guess it is a bug. Let me know how to give you the dump if you are interested.
I need to configure windows sound. I am using Windows 11 BTW.
In Sound Settings - Speakers I selected audio format 16bit, 44100Hz. Turned audio enhancement off.
Back to Dorico Device Setup, Stereo Out dropdown is empty! After tried to select different items in the ASIO driver dropdown, Stereo Out dropdown suddenly has Speakers item. I think this is a bug. Now I have sound from both channels.
Thanks for the data. The contained dump files show an already known issue in regards to the MediaBayService. You have HALion Sonic 7 installed which uses a new shared MediaBay component. There is an own MediaBayService process running which HALion Sonic connects to using some client software which somehow cannot connect to the server process. We are still evaluating and trying to find the cause of it.
In the meantime, as a workaround, you could uninstall HALion Sonic 7 and revert back to 3.5 (and change back to 7 once we solved the issue.)
We are sorry for the inconvenience and apologize.
I checked back with the @Ulf and @dspreadbury and here is a first workaround to keep HALion 7 or HALion Sonic 7 installed (Windows only, I can provide a Mac version on request):
To prevent any SteinbergMediaBayServer restart problems, here is a (zipped) bat file that starts it once and keeps it running. It needs to be unzipped and executed once after system start, before starting Dorico (you can put it anywhere you like, e.g. on your desktop and execute it from there):
I just figure, since there is no problem with the version of HALion SE released with Dorico 4, I’ll just sail on using that until Dorico 5 comes out, at which time I am confident that HALion SE 7 will be smoothly integrated into the package.
I’m also having big problems with last Dorico SE update, crashing after closing a project,
(quite everytime if I open 2 project and close one of them)
I can’t go back to free old Halion (not authorized?),
other problem: select all, copy and then paste in another project, chord symbols disappear (if I try to put a new one I see the copied one exists but it’s invisible in score)
Running the bat file seems to have improved my situation immensely.
Many thanks for figuring this out and sharing!
Before running this:
I could start with a fresh boot and run any single project in Dorico with Sonic/HALion 7. Even stuff saved way back with version 1 of Dorico that used Sonic 2 initially was not a problem. Plugin states/parameters/etc…all perfectly preserved as they’d last been under Sonic 2/3/HALion 5/6…whatever.
Upon opening a ‘second project’, if I allowed the new project to take over the playback engine, I’d get hangs and crashes. It could even happen in projects that weren’t using any obvious form of HALion (perhaps the metronome track still uses some hidden form of HALion?).
If I attempted to close that initial project, Dorico could freeze (not sure if it ‘crashed’ or just got hung up in a state of waiting for a hand-shake that never came?). Killing off Dorico by the Task Manager wasn’t enough. Killing the Steinberg VST engine this way would usually leave the ASIO drivers and all in a state that nothing could use them (reliably) again without rebooting the system. At first I thought using ASIO Link Pro could be the problem so I removed that and still had problems with direct connections to hardware with native ASIO drivers (M-Audio Delta 1010 PCI, and Tascam 1200 USB interfaces).
Since running this bat file…I’ve had a few smooth Dorico sessions with several projects open under each of my audio interfaces…as well as when using ASIO Link Pro. The time required for Dorico to ‘swap out’ the sounds involved is reasonable (and I have some pretty big [tempting fate for trouble] templates, using both VST3/VST2 instrument and effect plugins from multiple vendors in some projects).
Is there a similar bat file that stops the media bay server, or is it something small and sleepy enough when not being used that we’d might as well just leave it running all the time?
I just ran into exactly this problem, Dorico was not responding anymore, it didn’t show the Hub again and so on. After killing the MediaBayServer and start it via your command line it works fine again.
So from what I see here I think this MediaBayServer is a perfect candidate for a Windows service, because a manual restart is pretty cumbersome and can lead to the problems we see here.