INTERACT FORUM

More => Old Versions => JRiver Media Center 24 for Windows => Topic started by: wmupchurch on April 20, 2018, 09:58:42 am

Title: Media Center no longer appearing in DAW (recording software)
Post by: wmupchurch on April 20, 2018, 09:58:42 am
I have used JRiver as an audio 'device' for many years with Presonus Studio One.  I installed MC24 and uninstalled MC23 today.  In my audio device list in my DAW, I used to see 'JRiver Media Center 23' (or whatever version I was using), but now I see no listing.  Studio One automatically identifies devices so there is no way that I can find to force add MC24, but I don't think that's the issue.  I suspect that the MC24 install came with some default setting that doesn't let it appear as a device.  Any idea what settings those could be?
Title: Re: Media Center no longer appearing in DAW (recording software)
Post by: JimH on April 20, 2018, 10:16:56 am
You probably had the WDM driver active in the older version.  The wiki has a topic on the WDM Driver:

https://wiki.jriver.com/index.php/WDM_Driver
Title: Re: Media Center no longer appearing in DAW (recording software)
Post by: wmupchurch on April 20, 2018, 11:16:28 am
Thank you!  I have enabled WMD and changed my audio setting Options-->Audio-->Audio Device is not "Default Audio Device.  I also rebooted, but JRiver MC24 is still not showing up as a device.  Any other items to check?
Title: Re: Media Center no longer appearing in DAW (recording software)
Post by: Awesome Donkey on April 20, 2018, 11:18:48 am
Could try this: Make sure MC24 is closed, then find a MC24 shortcut, right click on it then select run as administrator (when prompted, allow it). From there, repeat the steps of enabling the WDM driver then close MC24. Start MC24 normally (not as administrator) and see if it appears now.

If it's still not showing up, possibly because of this: https://yabb.jriver.com/interact/index.php/topic,114531.0.html
Title: Re: Media Center no longer appearing in DAW (recording software)
Post by: wmupchurch on April 21, 2018, 11:15:36 am
I tried it with run as administrator stuff, but it didn't work.  It could be a driver signing issue as mentioned in the thread you linked.  I'm not willing to disable the setting recommended so I guess for now, I'll forgo using JRiver and us ASIO4ALL.  Thanks again for your help and perhaps sometime in the future either Microsoft will lower the complexity and cost barrier or JRiver will get updated.  I'll just try again after a few of the next updates come out.