Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JBHERTZ]

Hello,

I have resorted to using parallels with my Mac mini to load windows 10 so that I can use the WDM driver to link Roon to JRiver.

The issues seems to be that I must run the insider preview in order for this to work with Macs new M1 CPU.

No devices show up in audio outputs. Works fine on my other 2 PCs running regular non-preview editions.

Any suggestions? Are the devs working on getting JRiver to work with the new insider previews?

I have attached some screenshots.

[JimH]

I wouldn't expect WDM to work under Parallels.  Sorry.

[JBHERTZ]

Because of the insider build? Or it wont work because of virtualization? The later makes no sense.. software running on windows OS should have "no idea" its a virtualized session. Unless the software has a bug.

[JBHERTZ]

What about the ASIO driver then? That would work fine. But its not showing either.

[Hendrik]

ASIO driver are not actually "drivers" in the classical sense. They are just a defined interface ASIO-aware applications look for to talk to each other. It does not actually go through any Windows driver functionality.
If it doesn't show up in another ASIO application, then it might not be enabled or installed properly.

[JBHERTZ]

Well, I testing installing parallels on a Mac Book Pro with a Intel CPU and windows 10 regular build not insider and the WDM driver works fine. Doesnt seem like the issue is with parallels but between the insider preview (required to run M1 CPU in parallels for now) and JRiver. Can a developer look at this to ensure the issue wont make it to the public build?

[JimH]

Well, I testing installing parallels on a Mac Book Pro with a Intel CPU and windows 10 regular build not insider and the WDM driver works fine. Doesnt seem like the issue is with parallels but between the insider preview (required to run M1 CPU in parallels for now) and JRiver. Can a developer look at this to ensure the issue wont make it to the public build?

That's not something we'll look at now.

[Awesome Donkey]

It's probably related to running a Windows 10 Insider build which are known to be buggy and sometimes unstable.

I wouldn't be surprised if JRiver doesn't support running Media Center on the Insider builds of Windows 10. So, you might be stuck unfortunately.