Playback issue with M2TECH hiFace Two on Windows 11 requiring disable/enable workaround (ref#U5DSJC)

Support
1

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Both streaming and local* *library* music are affected.

Do you encounter any playback errors with the "System Output" Zone?

· I don't have a System Output available, but I'd like to keep troubleshooting

How is the affected Zone connected to your RoonServer machine?

· Cable (USB, HDMI, SPDIF, etc.)

Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?

· Connected directly to my RoonServer machine

Does the device show up at all in Roon Settings -> Audio?

· Yes, it shows up there, but it isn't Enabled

Does the "Enable" button unlock the Zone?

· I pressed Enable, but the Zone remains disabled

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· 2025-01-27 about 8-11

What are the make and model of the affected audio device(s) and the connection type?

· M2TECH hiFace Two USB connection

Describe the issue

Roon server with Windows 11.
M2TECH hiFace Two connected via USB to the Roon server. ASIO driver selected. After restarting the system, the device is visible, but music cannot be played through Roon. When pressing play, it returns to stop. It doesn't play music. In Roon / Audio, you need to select disable, then enable. After that, playback works correctly until the next system restart.

Describe your network setup

The network does not affect the error.

2

Hi @Piotr_Szulowski ,

Before using the device in Roon, are you using it as an output on another app? Due to the nature of ASIO, it is always in exclusive mode and can only be controlled by one app at a time. I wonder if something else is locking control.

3

Hi @noris
I am describing the situation in detail. After restarting the computer, I go to the Windows sound settings and can play the test sound. The device works normally. However, I cannot play sound through Roon. I have to disable and re-enable the output in Roon for it to work.
Additionally, it has worked fine for many years. It only recently stopped working for an unknown reason (a Roon update, perhaps?).

4

HI @noris
I noticed another fact. If the WASAPI output for the same device is active during a system restart, I can’t reproduce the error. If WASAPI is disabled, ASIO randomly fails to work.

5

Hey @Piotr_Szulowski,

Thanks for the update - let’s see if refreshing your RAATServer database may help.

You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

  • Create a Backup of your current Roon database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the Roon App to generate a new RAATServer folder

Let me know if you’re still running into issues afterward. Thank you! :pray:

6

Hi @benjamin
Creating the RAATServer folder helped for a few days, but unfortunately, the problem has returned.

7

Hi @Piotr_Szulowski,
Okay thanks for letting us know. I think our developers will need to take a closer look at this. I’m going to submit a ticket with them for this case. Once we have some next steps for you we will let you know here.

10

Hi @Piotr_Szulowski ,

Do you have any issues when using the WASAPI driver, with ASIO enabled or disabled?

Are you able to confirm if the issue happens on another PC, or just on the current Windows 11 one?

11

Hi,
I have no issues with WASAPI output, regardless of whether ASIO is active. I prefer ASIO output due to its better sound quality.
I don’t have another PC to run such tests.

12

Hey @Piotr_Szulowski,

Thanks for the update!

If possible, can you ensure that the latest drivers for the M2TECH hiFace Two are installed? If the issue continues, consider reinstalling the drivers to address potential corruption.

It also may be worth getting in touch with M2TECH directly - it’s important to note that M2TECH has indicated potential compatibility issues with first-generation products on Windows 11, as stated on their support page:

“With Windows 11 this is generally not possible.”

That said, using the WASAPI driver might be a more reliable solution longterm.

13

Hi @benjamin
The first thing I did before reporting the issue was reinstalling the device drivers.
The second thing: Foobar and ASIO output work.
The third thing: I have the second generation of the device, which is compatible with Windows 11 – see point 2.
The only issue I’m experiencing is the inability to play through Roon when WASAPI is inactive in Roon.
That’s why I’m reporting the issue to Roon.

15

Thanks for the follow-up @Piotr_Szulowski. While our team investigates further, it may be worth reinstalling the ASIO drivers on your Roon Server machine and see if the same issue occurs.

We’ll follow up with more information once our team has had the time to review your case in further detail. Thank you for your patience in the meantime! :+1:

17

Hi @Piotr_Szulowski,
Sorry for the long delay in getting back to you. The developers want to compare logs WASAPI disabled and with it enabled. Can you get us timestamps for both states?

18

Hi @daniel
2025-03-07 18:44 Wasapi disabled - can’t play.
2025-03-07 18:49 Wasapi enabled - can play.

19

Hi @Piotr_Szulowski,

Thank you for the precision - we’ve identified the issue. At 18:44, RAAT is initiating a setting for both ASIO and Wasapi, despite the latter being disabled.

We’ll reproduce in-house to determine if this is a RAATServer bug or an issue with device announcements. In either case, we’ll share more information as soon as possible.

21

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.