INTERACT FORUM
More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: InflatableMouse on April 19, 2014, 11:38:01 am
-
I was going to play with Netflix and route its audio through MediaCenter, but now I find this ASIO driver is nowhere to be found on my system?
I'm running the latest from the beta board. I read in another thread that sometimes MC needs to be run as Administrator. Under Tools/Options/Features I unticked ASIO, closed MC, started it as Admin and ticked it again. Said it needed to restart so I did, as Admin. Box is still ticked but where is this ASIO driver?
I was under the impression this ASIO driver would be under playback devices, so I could tick it as system default?
Also, I'm not sure on the next steps involved. I asked this before and received a nice answer from mwillems (http://yabb.jriver.com/interact/index.php?topic=86687.msg592813#msg592813), but I'm not sure if anything has changed since.
Thanks!
-
ASIO drivers are only available to applications which support ASIO.
You will need something like ASIOBridge (http://vb-audio.pagesperso-orange.fr/Cable/) if you want to pass audio through a WDM device into Media Center.
-
But shouldn't the (virtual?) device be available under playback devices, or be visible in MC itself?
Thing is, I don't see it anywhere. In mwilllems' response he said to create a new zone and make a loopback, I don't see how to do that either.
-
But shouldn't the (virtual?) device be available under playback devices, or be visible in MC itself?
No, an ASIO driver will not be listed as a WDM device (windows control panel) and it doesn't make sense for Media Center to be able to play audio to itself.
-
But shouldn't the (virtual?) device be available under playback devices, or be visible in MC itself?
Thing is, I don't see it anywhere. In mwilllems' response he said to create a new zone and make a loopback, I don't see how to do that either.
Mouse, my instructions were for using WASAPI loopback, not ASIO. WASAPI loopback requires an extra audio device you're not using to act as a "dummy" default audio device. Then JRiver steals the input from that default audio device. MoBo sound is what most folks use. You can then (using my directions) set up a system where JRiver can effectively feed itself sound through the two zone method.
To get the same thing working with ASIO, you need an external program like the ASIO bridge mentioned above.
Does that make sense?
-
Never mind, I was able to fix it another way with a tip from Mojave. Thanks!