To be honest, looking at the data, I don’t see where the problem is.
The M4 driver can be selected and the audio engine seems to accept it, and there is nothing unusual to be seen in the logs.
I have a couple of questions:
Does MIDI input via the M4 work in Dorico?
Dorico tries to wire it’s audio output to the M4’s Out 1/2 ports, is that where you expect audio to come through?
When the M4 is selected in Dorico and you start playback, when you open the HALion Sonic SE editor window, is there any metering activity going on in that window? Especially have a look at the top middle of the window, as that shows the metering of HALion’s main output.
What if you open Dorico’s mixer window, is there any metering going, especially on the right most, the master channel?
Yes, MIDI from the M4 works in Dorico.
No, I don’t see any metering in the Dorico or Halion SE mixers.
Yes, my monitors our plugged into outputs 1 and 2.
One (related) observation for you. When I adjust volume on my menu bar or touch bar, I must make sure the appropriate output (built-in or M4) is selected. There’s a part at the end of the troubleshooting video that recommends unchecking that attenuation check box. But I suspect many users are just adjusting the wrong volume. Anyway, that’s a separate issue - just thought I’d point it out.
I did not have that updated driver - “improved support for Cubase” - but do now.
No change. Diagnostics attached.
One thing I notice is that in the Device Setup… dialog, when I switch to Built-in I get a brief spinning beachball as though CoreAudio is thinking, and the Stereo Output dropdown then reads “1,” but when I change to M4, there is no beachball and the drop down changes immediately to “Out 1, Out 2”.
Thanks again for the data. Odd enough though, the logs look all totally fine and there is nothing that suggests that it would not work properly, so - honestly - I’m running out of steam.
May I ask you to download the Cubase Elements 30 day trial (Try Cubase now for 30 days | Steinberg) and see how that goes?
Otherwise I can only offer doing a remote session via TeamViewer, VNC or Zoom so that you can share your screen and we can have a look together.
I cleaned off some space and installed Cubase Elements. I was able to get it to play through my M4 and monitors.
I’ve attached screen shots of the Studio Setup dialog.
If that doesn’t trigger additional ideas, I’m open to a Zoom session. I’m in Seattle.
at least good to hear that it works with Cubase. But strange enough, then it should also do with Dorico, because Dorico’s audio engine is derived from Cubase.
Let’s have a Zoom session then. I’m an early bird and get up at 6, so we could start 6:30am, which is 9:30pm in Seattle, if that suits you.
Please send mail to ‘u dot stoermer at steinberg dot de’ and we’ll arrange for the details.
I had this same problem with my M4. Audio in all other apps (including Cubase) worked fine, only Dorico had a problem. The only way I could find to resolve it (on Mac) was to use an aggregate device. See this thread:
Interesting post that I missed. Arrg! I bought an M4 recently and, in fact, they have released new drivers today, along with new Firmware.
The M4 does work in Cubase and Wave Lab for basic audio chores, however, the M4 does not provide a ping delay (latency) for using it in the Ext Efx loop in Cubase 11 (or any other version of Cubase to date). It (the Ext Efx loop) seems to work with Motu’s DP software but not Cubase. I’m on a Win10 PC, btw, and I will add that the M4 seemingly performs all other audio tasks without issue. Too, it does not shut Cubase down while using the Ext Efx loop, it just will not produce the ‘ping’ number.
Moving on, using Wave Lab Pro 11 and trying to again use the Ext Efx loop feature in WL, it’s a complete fail. If you connect things correctly (EXACTLY AS YOU WOULD IN CUBASE) it will either freeze or turn WL off. Also, an odd thing about WL vs. Cubase is that the list of M4 connections (in/out channels) in WL looks quite different than it does in Cubase. It is said that Motu uses the same 8 channel DAC in the four channel M4 that they use in their typical 8 channel interface so I guess that this could somewhat help to explain what WL creates in it’s connection list? However, this said, the Cubase program channel list is more straight forward looking, and, more importantly, while not working perfectly (lack of ping in the Ext Efx loop), it will not crash or lockup Cubase. Actually, this behavior makes me wonder if the algo that creates the WL channel list is responsible for the WL Ext Efx fail? I have to think this is possible; that the channel sorting algo has confused the program as it tries to sort the M4 channels. ??
Which brings me to my last question: Why is it that two programs under the same Steinberg banner offer two very different ways to connect the same interface?
Yes, but the M4 post and the friendly Steinberg poster who took some interest in the OP’s initial problem made me feel that I was in the right place. And actually I see the post as more M4 oriented than the particular Steinberg program. However, if I’m in the wrong place with my M4 comments I’m sorry.
First I’d like to reply to Derrek: Actually no, I only monitor the Dorico forum, which is already enough time consuming among all the other tasks I have to do.
Now to the question of mr.roos: The thing is, Cubase and WaveLab have code wise not very much in common. WaveLab was for many many years the product of a single programmer and it was just sold under the Steinberg brand. It’s only since recently that Steinberg is taking over the development, but the code basis is still from the past. I don’t want to go into detail, but I hope you now understand why they behave differently.