INTERACT FORUM

More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: Matt on July 19, 2013, 03:08:19 pm

Title: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on July 19, 2013, 03:08:19 pm
Overview
MC19 adds the ability to use the JRiver audio engine from other programs that can output using ASIO.

In a third-party program with ASIO support, you will see 'JRiver Media Center 19' show up as a possible output device.  Here's an example:

(http://files.jriver.com/images/2013/asio_driver_other_program.png)

When you start playback in the other program, MC will launch and start playback in the current zone.

Playback will go from the other program, into MC, and out the configured output in MC.  All DSP processing is supported in MC.

When you stop playback in the other program, MC will also stop.

For best results, you will want to configure a small buffer size in Options > Audio to reduce latency.  Also, the latency added by convolution may be too great to make this feature useful with convolution enabled.

Real-World Use Case
There are a few real-world test cases where this might be interesting.

I will describe one I have.  I use MC as the pre-amplifier at home and connect directly to a power amplifier.  Sounds played outside of MC do not sound good, because the channel routing, levels, etc. will be wrong (by a lot) since I depend on MC for this functionality.

I also have an older Roland Piano that's connected to the system by midi.  I use a program called Pianoteq as the engine to make the piano sound.  The JRiver ASIO driver allows me to output from Pianoteq through the home sound system and get JRSS, Room Correction, and other processing.

Latency
The latency of the ASIO input, IPC, buffering, and final output is quite low.  With a fast system, the latency is low enough for piano playback, a latency sensitive operation.  If you were to use this driver for video playback, it is likely that the total audio latency will be less than the latency of a typical home theater display.

WDM Driver (help wanted)
We hope to someday create a Windows driver (WDM) of the same thing so that any program can use this.  This would open this feature up to games, web browsers, etc.  If you're a WDM audio driver programmer and would be interested in a project, please email matt [at] jriver (dot) com.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: jmone on July 19, 2013, 05:33:03 pm
I'm looking forward to the WDM enhancement as I have few apps that support ASIO directly and this change would really mean MC replaces the Windows Audio Mixer!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: kstich on July 20, 2013, 01:02:33 am
Wow, cool. Keep up the good work!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: jazid on July 20, 2013, 06:39:41 am
Wow! This looks good. At the moment I use MC via WASAPI for music. If I listen to eg. a Youtube video it is horribly loud, and I have to rush over to the amp to turn it down. Will this route the sound from the video through MC automatically without futher involvement on my part so levels remain closer to the same, and then revert to WASAPI for music afterwards? If so this is reason enough in itself to upgrade quite aside from all the other cool new stuff! Many thanks and please advise?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: JimH on July 20, 2013, 06:46:47 am
Will this route the sound from the video through MC automatically without futher involvement on my part so levels remain closer to the same, and then revert to WASAPI for music afterwards?
It is possible to do this, using "Zone Switch".  Please see the wiki topic on it.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: jazid on July 20, 2013, 07:21:40 am
Thanks for that. I am not too fast at this stuff, but as far as I can see the zones seem to refer to the output zones, is this right? I only output via USB to a single DAC. My problem is that music played using MC with the volume set appropriately is great, but if I try to watch some other content eg.youtube (which I watch in Firefox) it seems to bypass MC and output full volume to the DAC. The default file types are associated with MC but this seems to make no difference. I assume from what you are saying this can be changed but so far have not been able to find a way to do this. Please advise.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: JimH on July 20, 2013, 08:30:33 am
You can set up one zone for audio and one for video, each with its own settings, and the switch will be automatic.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: jazid on July 20, 2013, 09:06:31 am
Magic! many thanks for that Jim
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: J-a-k-e on July 20, 2013, 08:28:17 pm
Say I've got a multi-channel source like a game for instance that I want to output through my 2 channel dac, will I be able to apply dsp processing to the multi channel stream before the audio gets mixed to a 2 channel output?

I can do this at the moment with WASAPI loopback but it's a somewhat fiddly process. Once I set my asus card as the default audio device I have a zone configured with asio4all that has both my onboard sound and the 2 channel dac selected, media center effectively sees this as a 10 channel device. I also need to set the channel offset to 2, and have the output mode set on 7.1 so that I can get audio output to my dac as I see the parametric eq section only deals with the first 8 channels when it comes to channel ordering and such.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: MikeThin on July 21, 2013, 08:32:56 am
Matt,

This sounds very promising...  But will it work with REW on the waterfall analysis?  That alone would make v19 worth every penny!

Mike
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: DoubtingThomas on July 21, 2013, 06:10:47 pm
You can set up one zone for audio and one for video, each with its own settings, and the switch will be automatic.

Yes but... Zone switch does not work to automatically switch zones on an audio track by track basis from PlayingNow.

My #1 feature request for v19 is savable eq settings that can be applied on a track by track basis to help tame the OMG bass on some albums vs most of my albums.    I think of this like replay gain, but with user settable/savable eq curves.

Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: SpeedD408 on July 22, 2013, 02:37:23 pm
While we are waiting for WDM...  Would you consider adding a feature to allow loopback to be default and auto selected?  Here is how I see it working in my system (I have a Lynx setup so no WDM is available).
- set JRiver mode to Loopback
- use a web browser and the audio get routed to JRiver via the loopback method to the ASIO output to the Lynx setup.
- Flip back to JRiver and watch a TV station and JRiver would start playing and flip audio as it does today.
- Stop the TV playback and JRiver would then flip back to Loopback mode to allow 3rd party apps to play sound.

So basically have it default to Loopback mode and auto flip back and forth depending if JRiver was sourcing the audio (if yes, take control, if no, flip to Loopback mode).

I would think that would hold me over until you have the WDM driver ready.

Thanks,
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: shoshaw on August 01, 2013, 07:34:02 am
Is it possible to make MC an INPUT into a thrid party ASIO environment?  I use a ASIO environment to host many audio applications and I'd like to set it up so the MC output is available as an input into the system.

Thanks!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: JustinM on August 16, 2013, 09:35:13 am
any luck finding an WDM audio driver programmer ??
I hope this comes to fruit..
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: jmone on August 16, 2013, 03:32:04 pm
any luck finding an WDM audio driver programmer ??
I hope this comes to fruit..
+1
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: JimH on August 16, 2013, 04:02:25 pm
Not yet.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: SpeedD408 on August 17, 2013, 11:17:27 am
How about adding my suggestion as an option above.  This would at least make it easier to listen to Web browser based audio.  I'm just asking for it to be an option.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: gabeg on August 17, 2013, 08:08:26 pm
I'm not sure I'm clear how this option works.  Is this something I can use to have the media center actually process/play a file and then "serve" it to foobar to take advantage of how it streams via upnp?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: 6233638 on August 17, 2013, 10:04:01 pm
I'm not sure I'm clear how this option works.  Is this something I can use to have the media center actually process/play a file and then "serve" it to foobar to take advantage of how it streams via upnp?
It's the other way around - MC19 now has its own ASIO driver which allows other applications to send audio to Media Center.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: JustinM on August 21, 2013, 09:25:46 am
Is there a way (in Win7) to check if mc19 'Registered' its Asio driver??
My apps don't give 'JRiver Asio' as an option...
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: audunth on August 22, 2013, 01:26:33 pm
After searching around, I found a post on a forum stating you can use Winamp's linein plugin and ASIO out plugin to play sound from an application that doesn't support ASIO to an ASIO driver like the one in MC.

More info:
http://www.kvraudio.com/forum/printview.php?t=250625&start=0

Haven't tried this myself, but it seems like a possible solution while waiting for a WDM driver.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: hamsi on August 25, 2013, 01:32:21 pm
Overview
MC19 adds the ability to use the JRiver audio engine from other programs that can output using ASIO.

Does it work reverse?
Can I listen music on my desktop PC, using the MC19 on my notebook?

NotebookPC will see the JRiver servermode on desktopPC as an ASIO driver?

Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on August 26, 2013, 07:25:03 am
Hi dev team,

I've just started to play with MC 19 and its new feature the ASIO driver.
Is it expected that the internal volume is by-passed? I've played a playlist from Qobuz Desktop Player to JRiver and it was 100% loud! Once the Qobuz Player volume is set to a correct volume it's ok and really playing fine, but I was expecting that the JRiver volume will drive the whole thing which is not the case...

Configuration:
Qobuz Player ASIO -> MC 19.0.31 -> ASIO output -> RME Fireface UC

One of my goal with this new ASIO feature is to be able to use software like Room Equalizer Wizard or AudioLense to go through the JRiver Engine and check how it performs. But all these tools require recording via the same ASIO driver that the one used to generate sound. But the ASIO driver doesn't expose any ASIO input, is there any plan to, at least, make the JRiver driver pass through  the virtual ASIO input to the physical ASIO input?

Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: MikeThin on August 27, 2013, 01:58:16 am
One of my goal with this new ASIO feature is to be able to use software like Room Equalizer Wizard or AudioLense to go through the JRiver Engine and check how it performs. But all these tools require recording via the same ASIO driver that the one used to generate sound. But the ASIO driver doesn't expose any ASIO input, is there any plan to, at least, make the JRiver driver pass through  the virtual ASIO input to the physical ASIO input?

Yes indeed - I started a thread about this here:
    http://yabb.jriver.com/interact/index.php?topic=82811.0

Looks like we need to wait for the WDM version or pressure the REW authors to allow independent input/output devices. 
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: 7ryder on August 28, 2013, 02:06:47 pm
How can we defeat the MC start-up if it is not selected as a driver in other software?  I use Sony Vegas Pro for audio/visual projects and even though I have not chosen to use the JRiver engine ASIO driver (I'm using the  Benchmark_DAC2 ASIO driver which I also use in MC), MC starts up each time I start up Vegas Pro v12.  I don't want MC open, so I have to close MC manually each time and it is getting annoying.  Seems to me that this auto start-up should user select-able and not mandatory.  Thanks.

Chris
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on August 29, 2013, 01:23:35 am
Yes indeed - I started a thread about this here:
    http://yabb.jriver.com/interact/index.php?topic=82811.0

Looks like we need to wait for the WDM version or pressure the REW authors to allow independent input/output devices. 

I'm not convinced that a separated input/output option would help, I remember a discusstion from Bernt (author of Audiolense) who was explaining that the recordings are better if done via the same device.
With the already implemented support for the ASIO  Live Input, I think it would not be so difficult to extend it to allow MC to passthrough the ASIO input channels.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on August 29, 2013, 01:47:36 am
How can we defeat the MC start-up if it is not selected as a driver in other software?  I use Sony Vegas Pro for audio/visual projects and even though I have not chosen to use the JRiver engine ASIO driver (I'm using the  Benchmark_DAC2 ASIO driver which I also use in MC), MC starts up each time I start up Vegas Pro v12.  I don't want MC open, so I have to close MC manually each time and it is getting annoying.  Seems to me that this auto start-up should user select-able and not mandatory.  Thanks.

Chris

MC is the implementation of the JRiver ASIO driver, so as soon as a software iterates over the available ASIO drivers and check some informations, JRiver is loaded.
There's no other alternative except having a standalone engine or uninstalling the driver reference itself (removing the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\JRiver Media Center 19
and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ASIO\JRiver Media Center 19 seem to be sufficient)
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on August 29, 2013, 01:51:33 am
Is somebody facing the sound volume level problem I'm facing?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: 7ryder on August 29, 2013, 08:12:03 am
MC is the implementation of the JRiver ASIO driver, so as soon as a software iterates over the available ASIO drivers and check some informations, JRiver is loaded.
There's no other alternative except having a standalone engine or uninstalling the driver reference itself (removing the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\JRiver Media Center 19
and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ASIO\JRiver Media Center 19 seem to be sufficient)

Thanks for the tip, worked perfectly.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: abrise on September 03, 2013, 08:20:40 am
Is somebody facing the sound volume level problem I'm facing?
I had the same problem but it is working now with the last version. I can use Qobuz desktop and asio jriver 19 output, JRiver wolume is now working. However I still cannot have convolution or any other DSP working.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Glossie on September 04, 2013, 07:16:21 pm
 I am using a V-Link 192 USB-SPDIF converter between my laptop and DAC. When running MC18 I see both the V-Link 192 ASIO driver and MC19 ASIO driver as available devices. However when I run MC19, the V-Link 192 ASIO driver is the only ASIO driver available. I suspect this is not right. Should I not have the MC19 ASIO as an option? How can I fix this?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: 6233638 on September 05, 2013, 12:03:30 am
I am using a V-Link 192 USB-SPDIF converter between my laptop and DAC. When running MC18 I see both the V-Link 192 ASIO driver and MC19 ASIO driver as available devices. However when I run MC19, the V-Link 192 ASIO driver is the only ASIO driver available. I suspect this is not right. Should I not have the MC19 ASIO as an option? How can I fix this?
I'm guessing it's not there because there's no point in MC19 sending audio to itself.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Wungun on September 05, 2013, 10:41:44 am
this is a promising option....however, MC cant be configujred as an input thru asio...?
reason i ask, is i process my audio thru audiomulch as my setup is meant for r.a.c.e./ambiophonics.
currently i have to use virtual audio cable as my "input device" in mulch, and vac is setup as my output in MC.
and after processing, mulch sends the signal out to my soundcard.

i see i can setup MC, thru asio in mulch, but its not getting the signal...
on the output stage in mulch, MC shows 16 channels...? however in dsp/output format, its set for just 2 channels.

what i need is MC asio as my "sound in" im audiomulch, and my soundcard as my "sound out"

i notice there is a convulsion option in dsp...?
what file formets/types are supported?
thanks
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Wungun on September 05, 2013, 10:49:13 am
oops...check that. i see it accepts a wav sample for convulsion. nice!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: ashman5 on September 05, 2013, 11:59:54 am
this is a promising option....however, MC cant be configujred as an input thru asio...?
reason i ask, is i process my audio thru audiomulch as my setup is meant for r.a.c.e./ambiophonics.
currently i have to use virtual audio cable as my "input device" in mulch, and vac is setup as my output in MC.
and after processing, mulch sends the signal out to my soundcard.

i see i can setup MC, thru asio in mulch, but its not getting the signal...
on the output stage in mulch, MC shows 16 channels...? however in dsp/output format, its set for just 2 channels.

what i need is MC asio as my "sound in" im audiomulch, and my soundcard as my "sound out"

i notice there is a convulsion option in dsp...?
what file formets/types are supported?
thanks

wungun, I've used your car audio guides several times and have mimic'd your setup partially. on the software front, I was able to ditch audiomulch (for VST verision of Bidule, used inside of JRiver) and use the loopback function of MC (in place of virtual audio cable). so now i have centrafuse>MC18/19>amps. all processing is performed within JRiver. works great. haven't got into convolution yet, but hope to soon.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Wungun on September 05, 2013, 12:10:29 pm
wungun, I've used your car audio guides several times and have mimic'd your setup partially. on the software front, I was able to ditch audiomulch (for VST verision of Bidule, used inside of JRiver) and use the loopback function of MC (in place of virtual audio cable). so now i have centrafuse>MC18/19>amps. all processing is performed within JRiver. works great. haven't got into convolution yet, but hope to soon.

i guess i should be flattered :)
im outta the car PC game. Wish i would of known about JRiver before today though! lol
Cap PC is now in my livingroom lol

Bidule huh?
So it creates a file to load in MC convolver? Or MC runs a convolver? Im lost...lol
Loopback?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: ashman5 on September 05, 2013, 12:48:51 pm
i guess i should be flattered :)
im outta the car PC game. Wish i would of known about JRiver before today though! lol
Cap PC is now in my livingroom lol

Bidule huh?
So it creates a file to load in MC convolver? Or MC runs a convolver? Im lost...lol
Loopback?

Loopback makes MC act like VAC. MC intercepts the audio from any DirectShow type program such as Centrafuse.

MC is also capable of hosting VSTs, and Bidule is a VST host that loads into MC as a VST...(head explodes). This allows for loading and use of multichannel VSTs like audiomulch. Works very well and keeps the processing inside of MC.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Wungun on September 05, 2013, 01:39:03 pm
Thanks for explaining that...
Found a free ambio vst plugin and loaded it straight into MC.
It'll take some tuning, but WAY less resource overhead.
I like!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on September 06, 2013, 09:52:13 am
I had the same problem but it is working now with the last version. I can use Qobuz desktop and asio jriver 19 output, JRiver wolume is now working. However I still cannot have convolution or any other DSP working.

I'm still trying to have this working, but without any luck. I use the latest version (19.0.36), I select JRiver ASIO in Qobuz desktop and play some music, the sound is not output in JRiver but directly in the ASIO driver of the sound card, the Audio Path is not showing any activity. This explain why I get full sound level.
I've seen that some logs have been added to the program for the ASIO driver, where can I found them?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on September 06, 2013, 09:54:46 am
I'm still trying to have this working, but without any luck. I use the latest version (19.0.36), I select JRiver ASIO in Qobuz desktop and play some music, the sound is not output in JRiver but directly in the ASIO driver of the sound card, the Audio Path is not showing any activity. This explain why I get full sound level.
I've seen that some logs have been added to the program for the ASIO driver, where can I found them?

It sounds like the other program isn't actually using the JRiver ASIO driver.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on September 06, 2013, 10:06:23 am
It sounds like the other program isn't actually using the JRiver ASIO driver.

That's what I was thinking after investigations, but the message from abise makes me think that he was able to do it...
I'm going to test with another player just to check.
By the way, where can I find the ASIO driver logs?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on September 06, 2013, 10:08:05 am
That's what I was thinking after investigations, but the message from abise makes me think that he was able to do it...
I'm going to test with another player just to check.
By the way, where can I find the ASIO driver logs?

It's part of the regular JRiver logs:
http://wiki.jriver.com/index.php/Logging

It will use "CJRiverASIODriver" in the log.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on September 06, 2013, 10:09:14 am
It's part of the regular JRiver logs:
http://wiki.jriver.com/index.php/Logging

It will use "CJRiverASIODriver" in the log.

Ok, thanks, will give feedback.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on September 06, 2013, 10:54:17 am
Finally after some tests on different configurations, MC ASIO driver is working fine, but when using "Qobuz Desktop" even when selecting MC ASIO as the output it doesn't work. On a computer having a native ASIO it outs directly to the sound card ASIO, on a computer without ASIO it hangs.
I'm just currious to understand why "Qobuz Desktop" expects from the ASIO driver, and what MC is not "correctly" exposing... Qobuz becoming one of the most important HD and streamed music provider in europe (they are coming in US next year), I hope we will able to solve that.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: abrise on September 07, 2013, 04:57:32 am
Finally after some tests on different configurations, MC ASIO driver is working fine, but when using "Qobuz Desktop" even when selecting MC ASIO as the output it doesn't work. On a computer having a native ASIO it outs directly to the sound card ASIO, on a computer without ASIO it hangs.
I'm just currious to understand why "Qobuz Desktop" expects from the ASIO driver, and what MC is not "correctly" exposing... Qobuz becoming one of the most important HD and streamed music provider in europe (they are coming in US next year), I hope we will able to solve that.
Sorry to have uncorrectly reported that it was working for me , i now confirm your above comment. Qobuz desktop was in fact using Asio4all when set to use jriver asio. I removed asio4all and get nothing through now .
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: duskdrums on September 10, 2013, 06:14:28 pm
Am I correct in assuming that this will not work if we use ASIO as the audio output in the playing zone in MC? If I set a new zone in MC using WASAPI event style it will work.

This is not 100% ideal, as I am using an ASUS card which require sample rate etc to be set in the ASUS control panel unless you are using ASIO. It isn't a deal-breaker, however, as any audio i'm likely to be playing through external programs are not high sample rate files (fidelify, for example). But i wanted to check to make sure that the behavior whereby MC loads and tries to play an IPC named file but no sound comes out is the expected behavior.

Also, if this is the case, I will create a new WASPI zone used only for the ASIO engine. Any suggestions on what to put as an expression in zoneswitch to ensure that the waspi zone is activated when using the engine and not activated otherwise?

Thanks!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: JimH on September 10, 2013, 06:25:33 pm
This feature is ASIO input, not output.  So you can still use ASIO in MC normally.  This feature just makes MC's audio engine available to another program that supports ASIO, so that it can output to MC's engine.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: duskdrums on September 12, 2013, 08:43:00 pm
Yeah, sorry, I was unclear. The problem I was having was when using the feature to go from fidelify --> (ASIO feature) --> MC --> (normal ASIO setting in MC) --> Asus Xonar STX. If i use the feature to go from fidelify to MC but then change my output method to WASAPI, then the Ipc file "plays" fine and I get sound from fidelify to MC and then out to the sound card. But this is not ideal because using WASAPI to control the Xonar STX means that I do not bypass the settings panel for the Xonar (which can be bypassed when using ASIO as the output method in MC).

Have other people not had problems using the new feature when they also use ASIO out to their output device? That is, can others use both the ASIO input feature and ASIO as their output device? 
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: hamsi on September 18, 2013, 06:14:14 am
Does it work reverse?
Can I listen music on my desktop PC, using the MC19 on my notebook?

NotebookPC will see the JRiver servermode on desktopPC as an ASIO driver?



May I listen music through my desktopPC's speaker, when I play on my notebook by choosing the ASIO driver (JRiver audio engine) of desktopPC?

I want to get rid of zones, different libraries and mediaserver.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: eddyshere on September 18, 2013, 06:57:51 am
Any news on the wdm version of this ? This would be very helpfull for external bluray players such as tmt i use for full menu support with MC and an asio DAC...
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Krunchy on October 02, 2013, 01:53:38 am
Can you give examples of programms supporting asio that could go by jriver?
I still don't get the use of this new fonctionnality.

Thanks!
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: giantpopples on October 05, 2013, 05:52:13 pm
I use this feature with the squeezelite app which emulate a squeezebox device on a PC.
It can play music files up to 192/24 and integrates perfectly with other squeezebox products for multiroom audio.

Since this small app is ASIO compatible, I see MC as available output and all my music comes through MC engine with the distance/crossover settings.

Since my audio card is better than my pre amp (I use an Asus Xonar HDAV card on an Emotiva UMC-1 processor), MC allows me to use my PC as a pre amp and the sound is much better  :D

Just have to figure out how I can keep this function when I watch videos, now when I do so it kinds of disconnect the squeezelite app.
I saw someone talking about different audio/video zone on MC, maybe I'll look into it.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Wungun on October 07, 2013, 06:49:41 am
If you wanted to play media on WMP or Foobar, you can output it to MC before the soundcard to make use of its audio engine/ filters/DSP. for example....
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Krunchy on October 07, 2013, 09:20:46 am
Thanks for your replies!
As i'm using my laptop for both internet and "audiophile music", i was interested to have sound through jriver from other programs, and not only media or audio programms.
I might be wrong, but since jriver 19, i can have directly sound from an internet video to my amplified system (with usb dac)
Before i had to check the asio driver, or worse, the windows system, to make it work.
So...am i stupid or this is thanks to the new audio engine of JRiver?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Lonx on October 14, 2013, 08:07:21 pm
Since switching to JRiver, my Onkyo receiver is now clear of any EQ or room correction settings and all sounds well. However this presents another problem. I also run TV and PS3 via optical spdif to the receiver, which now sounds flat and unbalanced. I can fix the TV issue with a tuner card and currently trying to decide which one.

The Playstation routing that I want to do is -

PS3 (DTS/DD) -[Optical]-> HTPC -> JRiver ASIO (PEQ, Correction etc.) -[HDMI]-> Receiver

* If I was to put something in my HTPC with spdif input (I have an old M-Audio 192 (with asio drivers) lying around which would work after converting optical to coaxial), would it then be generally possible to route via the JRiver ASIO driver for processing and output?

* AverMedia H727 TV tuner card also has a HDMI input however I've been told it will only capture stereo audio. Not sure if it can do pass-thru to JRiver ASIO - which would be ideal? I emailed them but received a fairly standard copy+paste response from their product info, and I may not have been clear enough in my questioning. Obviously I do not intend to route PS3 video via PC, only the sound so using spdif makes more sense.

* Another option is to run an external DAC, pass analog inputs to HTPC... but this is getting ridiculous to retain surround sound with Gran Turismo ;)

Surely I'm not the only one with external devices with Optical/HDMI outputs that we want to route (with surround audio) via the PC to use the great processing features of JRiver? I know latency may also become a distinct possibility when trying to do this, but its worth a try. Thoughts or suggestions would be awesome, thanks.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Neco on October 15, 2013, 12:57:17 pm
Has anyone used this to produce upscales of Stereo sources to surround?   I'm hoping its possible and someone has a workflow to demonstrate it.

I've been wanting to do this for a long time, and was going to actually post a thread, until I noticed this one.  It seems like it should be possible?

When the original audio source is of decent quality (high bitrate AAC / FLAC etc)  the surround upscaling is so astounding that I've left it permanently enabled for 2 channel sources.   I've never found another utility that really gives the same sound or quality as MC's upmixing.

So being able to produce dedicated tracks I can archive would be nice.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: HiFiTubes on October 22, 2013, 03:06:09 am
Does this ASIO allow PCM2DSD at 2XDSD?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: thediscman on October 23, 2013, 06:37:14 am
Does this ASIO allow PCM2DSD at 2XDSD?

Yes, I assumed that "Playback will go from the other program, into MC, and out the configured output in MC.  All DSP processing is supported in MC." meant that PCM2DSD at 2XDSD would be supported, but it would be nice have that confirmed.

Also, I would very much like to route 2-channel SPDIF audio from 2 external devices (TiVo, Blu-Ray player) into MC with this new feature. I have a small form factor PC with no expansion slots, so some kind of external, ASIO, USB soundcard with 2 SPDIF inputs is what I (think) I'm looking for.

It looks like this might work: http://www.creative.com/emu/products/product.aspx?category=610&pid=18388

But I have no idea. Is anyone else routing external SPIDF *into* MC19?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: guido310 on October 24, 2013, 12:19:31 am

I use an hauppauge Colossus that has spdif and can capture Ac3 audio, it works

Since switching to JRiver, my Onkyo receiver is now clear of any EQ or room correction settings and all sounds well. However this presents another problem. I also run TV and PS3 via optical spdif to the receiver, which now sounds flat and unbalanced. I can fix the TV issue with a tuner card and currently trying to decide which one.

The Playstation routing that I want to do is -

PS3 (DTS/DD) -[Optical]-> HTPC -> JRiver ASIO (PEQ, Correction etc.) -[HDMI]-> Receiver

* If I was to put something in my HTPC with spdif input (I have an old M-Audio 192 (with asio drivers) lying around which would work after converting optical to coaxial), would it then be generally possible to route via the JRiver ASIO driver for processing and output?

* AverMedia H727 TV tuner card also has a HDMI input however I've been told it will only capture stereo audio. Not sure if it can do pass-thru to JRiver ASIO - which would be ideal? I emailed them but received a fairly standard copy+paste response from their product info, and I may not have been clear enough in my questioning. Obviously I do not intend to route PS3 video via PC, only the sound so using spdif makes more sense.

* Another option is to run an external DAC, pass analog inputs to HTPC... but this is getting ridiculous to retain surround sound with Gran Turismo ;)

Surely I'm not the only one with external devices with Optical/HDMI outputs that we want to route (with surround audio) via the PC to use the great processing features of JRiver? I know latency may also become a distinct possibility when trying to do this, but its worth a try. Thoughts or suggestions would be awesome, thanks.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: millst on December 16, 2013, 11:02:06 pm
Does this work with linked zones? I didn't have any success.

-tm
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on December 17, 2013, 04:45:19 pm
Does this work with linked zones? I didn't have any success.

No, sorry.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: millst on December 17, 2013, 05:49:58 pm
Ok, can probably work around it. Is there any plan to make it work?

-tm
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on December 17, 2013, 06:07:27 pm
Ok, can probably work around it. Is there any plan to make it work?

Not in the short term, because it would require a fundamental change to how linked zones work.  Currently linked zones are each playing a copy of the same thing.  This is good because it allows DLNA, but it also creates limitations like this.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Bjorn on December 31, 2013, 05:17:34 am
I really hope WDM Driver is something we will see in near future. It's absolutely necessary if a HTPC is going to function as a proper media player without using an external surround receiver/processor. The other option is to have all programs incorporated into JRiver, which I assume isn't possible. With the upcoming nanoAVR, we can also combine a HTPC with an external unit like Playstation 4 in a surround setup. Just too bad there aren't enough channels for active cross over too. Always something missing......
http://www.minidsp.com/aboutus/news

Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on January 15, 2014, 06:14:23 am
How many ASIO channels are exposed? I'm trying to connect with AudioLense with a 5.1 configuration, and it is claiming that the number of channel is incorrect.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: gappie on January 15, 2014, 06:27:01 am
How many ASIO channels are exposed? I'm trying to connect with AudioLense with a 5.1 configuration, and it is claiming that the number of channel is incorrect.
I don't know about audiolence. but it seems like mc is exposing 16 channels (I checked via reaper)

 :)
gab
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: mojave on January 15, 2014, 08:48:53 am
How many ASIO channels are exposed? I'm trying to connect with AudioLense with a 5.1 configuration, and it is claiming that the number of channel is incorrect.
I just tried several channel configurations with Audiolense including 16 channels and none of them work with the JRiver ASIO driver. I think this is an issue Matt will have to fix when he recovers.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: millst on January 15, 2014, 09:33:29 am
ASIOInit returns 16 output channels and 0 input channels. I've only tried working with the first 6 (5.1 input).

-tm
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: gappie on January 15, 2014, 11:58:50 am
here the asio driver works, even with 16 channels :) . but I must have mc open in on way or an other. otherwise the loading of mc takes to long and I get an error.

 :)
gab
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: rlebrette on January 15, 2014, 02:17:47 pm
I just tried several channel configurations with Audiolense including 16 channels and none of them work with the JRiver ASIO driver. I think this is an issue Matt will have to fix when he recovers.

Not sure that's a JRiver problem, we've to discuss this with Bernt.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: SoBizarre on February 07, 2014, 02:49:27 pm
Hi,

I was trying out JRiver MC, and specifically the ASIO driver I was interested in. I wanted to route all the computer audio through the MC, so I could have for example crossfeed in Spotify, Youtube and such, and with the help of Hi-Fi Cable/ASIO Bridge it worked very well. Basically I've had very few problems:

1. As mentioned in posts above, some programs (e.g. JACK i was experimenting with) can't connect to JRiver ASIO. I think the problem lays in fact that it doesn't expose any input channels. See the difference between JR ASIO and ASIO4ALL:

(http://i.imgur.com/dPkdjDH.gif)

Anyways, since ASIO Bridge connects without a problem, I consider it a non-issue, really.

2. The second problem(?) though, could possibly have some negative impact on sound quality. MC's ASIO clock seems to drift quite a lot compared to ASIO4ALL:

http://i.imgur.com/sIvgrUn.gif

http://i.imgur.com/sxSKY9E.gif

I looked it up, and supposedly this sample rate deviation causes some audible cracks. Again, I'm not TOO worried, since I'm getting occasionally pops and cracks caused by heavy computer activities, plus when I was a kid, I had a mono record player with piezo cartrige and a bunch of scratched, worn-out records, so I'm no stranger to cracks ;D , but it would be good to know what do you have to say about it nonetheless.

3. There was another thing I don't quite understand. I recon the only way to have web browser videos in sync with audio, is to output in WASAPI non-exclusive (anything else causes video to be out of sync by the amount of the buffer you set). But even then, live playback latency is not compensated for (shouldn't MC just report to Windows a buffer increased by the amount of the latency?). Am I missing something here?


Now the REAL problem: $$$. I believe MC is fairly priced for what it is (a fully featured media center). But for someone like me, who basically is only after a DSP engine, the price is a little hard to swallow. Not to mention the fact that one needs quite a few third party programs to make it work:

You need obviously Hi-Fi Cable/ASIO Bridge (or equivalent)
You need a utility to hide the above (and the MC) in system tray upon Windows start.
In case you have (like me) a laptop with non-configurable media keys, you might need a volume control utility (like the excellent VolumeČ) after you change default audio device to Hi-Fi Cable.

Now, it was mentioned here that you are working on proper WDM driver, which would allow to easily set MC as default sound device in Windows, and still be able to use MC itself without any problems (right now it's associated with a lot of hassle), and maybe slowly migrate from other programs (Foobar and PotPlayer in my case). Off course it would be great if there was something like standalone DSP engine with Windows driver available for purchase for substantially less than $50, but I don't think there is a market for such product, unfortunately. So, the question is:

Any news on WDM Driver?  :)
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: mojave on February 07, 2014, 03:07:19 pm
Any news on WDM Driver?  :)
The Hi-Fi Cable/ASIO Bridge is currently the lowest latency available way to route audio through JRiver, but you can also use File > Open Live > WASAPI loopback. Matt, JRiver's CTO, has been in the hospital (http://yabb.jriver.com/interact/index.php?topic=86462.0) and he is the one working on the WDM driver. I don't think it will be released for a while yet.

I can't remember if it affects latency with the ASIO Bridge, but you could try adjusting Tools > Options > Audio > Advanced > Live playback latency.

If using the WASAPI loopback, you can set it as a preset in Playing Now. My family just clicks the preset button before starting playback of any other computer source audio and it will playback through JRiver's engine just fine.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: millst on February 11, 2014, 04:56:11 pm
In regards to the clocking, I've noticed something I don't quite understand about the ASIO input. I've been using it to input 48kHz sound and the buffer switch callback generally happens every 5-6ms, which is expected. However, about 10% of the time it is triggered after only 1ms.

That's problematic for me since I might not have data ready that soon. I've worked around it by sleeping in the callback until there is some data. MC seems to tolerate it, but I doubt it's ideal (is it slowing the audio output to compensate?). There definitely seems to be some jitter between the two, which I don't see that when directly outputting to a sound device via WASAPI.

-tm
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: bblue on June 26, 2014, 05:47:41 pm
Overview
MC19 adds the ability to use the JRiver audio engine from other programs that can output using ASIO.

In a third-party program with ASIO support, you will see 'JRiver Media Center 19' show up as a possible output device.  Here's an example:

(http://files.jriver.com/images/2013/asio_driver_other_program.png)

When you start playback in the other program, MC will launch and start playback in the current zone. [emphasis added]
Playback will go from the other program, into MC, and out the configured output in MC.  All DSP processing is supported in MC.

When you stop playback in the other program, MC will also stop.

This is a really nifty but a little dangerous capability.

Sorry to bring back this old thread but I would like to know if there has been any changes in the behavior described above, especially where I underlined it?

I set up Foobar for ASIO out to MC 19 and did some tests.  If MC is not already running, it does come up in the player zone associated with a local device output.  However, if MC is already running and playing in a different zone (one not associated with a local device output), it will cause the running zone to block, and from then on MC will not respond to any further input.  You have to kill MC and JRService and start over.

Before this lock up occurred, I was able to play to the local player zone, if it was already selected, even if another non-local zone was active.  After the lockup described above, MC would no longer pass audio on the local zone (Wasapi USB), but it didn't block.  It looked like everything was running fine, but there was no audio.  Further testing revealed that it would pass audio if the bitrate sent was the same as it was set when the above lockup occurred.  It isn't MC, it's something that happened to the Wasapi driver during that lockup, as other devices outputting to the same driver, behaved the same way.

The only cure for this was a system reboot.

Is there a way that the target zone (currently playing) is not messed with if it is already active?  And that the status of any other active zone not have any effect on the local play zone?  This all just needs to be more bulletproof.

Perhaps I did something stupid or assumed too much, but I don't think these events should ultimately cause a reboot to be necessary, or an active stream interrupted.

--Bill

Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on June 27, 2014, 08:42:20 am
I set up Foobar for ASIO out to MC 19 and did some tests.  If MC is not already running, it does come up in the player zone associated with a local device output.  However, if MC is already running and playing in a different zone (one not associated with a local device output), it will cause the running zone to block, and from then on MC will not respond to any further input.  You have to kill MC and JRService and start over.

I can't reproduce this.  I leave it playing in a zone and it stops playback and starts playing the ASIO input.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: bblue on June 27, 2014, 03:03:38 pm
I can't reproduce this.  I leave it playing in a zone and it stops playback and starts playing the ASIO input.

Hmmm.  That's interesting.  I'll repeat on 147 just downloaded.

Why should it stop playing on the active zone (one not associated with the local playback device) in order to play ASIO on the local zone (one that is associated with the local playback device)?  Or do you mean while playing on the local playback zone, you sent ASIO from another source to it, and that replaced (superceded) what was originally playing?  If the latter, should it do that or just report the device as in use (or ignore the request)?  I would think it should honor existing paths, only using one if it really is available.  ?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on June 27, 2014, 03:48:51 pm
Hmmm.  That's interesting.  I'll repeat on 147 just downloaded.

Why should it stop playing on the active zone (one not associated with the local playback device) in order to play ASIO on the local zone (one that is associated with the local playback device)?  Or do you mean while playing on the local playback zone, you sent ASIO from another source to it, and that replaced (superceded) what was originally playing?  If the latter, should it do that or just report the device as in use (or ignore the request)?  I would think it should honor existing paths, only using one if it really is available.  ?


The bigger mystery is the hangs you were reporting.  I'm hopeful they won't happen with the latest, but let us know.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: planetearth411 on August 20, 2014, 11:12:14 am
New to JRiver and trying out the MC 19.   I'm using Windows 8.1, Lenovo ThinkPad with dual Pentium 2.53ghz and IFI Nano IDSD DAC (supports 1x,2x,4x DSD via ASIO).

Using latest Foobar, I can choose output "JRiver MC 19 ASIO" and send either a WAV or FLAC 16 bit/44khz file to MC 19, where I then have MC19 output 2X DSD stream to IFI Nano DAC (DAC supports 1x,2x,4X DSD natively).  Seems to work great.   However, when I choose 4X DSD stream in MC19, the audio is choppy.  I've tried playing with the various buffer settings without success.   

Listening to the 4X DSD choppy audio, sounds pretty amazing... is there anyway to get rid of choppiness?   Any help greatly appreciated.  Thank You. 
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: Matt on August 20, 2014, 11:27:46 am
New to JRiver and trying out the MC 19.   I'm using Windows 8.1, Lenovo ThinkPad with dual Pentium 2.53ghz and IFI Nano IDSD DAC (supports 1x,2x,4x DSD via ASIO).

Using latest Foobar, I can choose output "JRiver MC 19 ASIO" and send either a WAV or FLAC 16 bit/44khz file to MC 19, where I then have MC19 output 2X DSD stream to IFI Nano DAC (DAC supports 1x,2x,4X DSD natively).  Seems to work great.   However, when I choose 4X DSD stream in MC19, the audio is choppy.  I've tried playing with the various buffer settings without success.   

Listening to the 4X DSD choppy audio, sounds pretty amazing... is there anyway to get rid of choppiness?   Any help greatly appreciated.  Thank You. 


It's possible that increasing buffering in Options > Audio > Device settings could help.
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: planetearth411 on August 20, 2014, 09:20:21 pm
Thanks.   It seems Tools/Audio Device/Advanced/Live Playback Latency affects the choppiness.  It's less choppy at the max setting of 500 ms.. is there a way to set a higher live playback latency?
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: torgny on November 07, 2014, 08:18:17 am
Hello there.  I am using 20.0.33 since a few days back and the new J River Media Center 20 for ASIO output but am unable to redirect the sound from the internal loudspeakers to the UBS -- how can the connection between ASIO and physical device be changed?

Keep up the good work // TG
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: BryanC on November 07, 2014, 02:10:19 pm
Hello there.  I am using 20.0.33 since a few days back and the new J River Media Center 20 for ASIO output but am unable to redirect the sound from the internal loudspeakers to the UBS -- how can the connection between ASIO and physical device be changed?

Keep up the good work // TG

Options->Audio->Audio Device
Title: Re: NEW: JRiver audio engine as an ASIO driver
Post by: LocutusEstBorg on January 23, 2015, 04:07:31 am
I want to set up the following chain:
Dirac Audio Processor (Default Windows playback device / 7.1 channel) > JRiver ASIO Driver (8 channel) > ASIO sound card (9 channel)

I want to perform bass management in JRiver for stereo subwoofers as follows:
Front L, Side L & Surround L > Sub 1
Front R, Side R & Surround R > Sub 2
Centre & LFE > Sub 1 + 2

If possible, do some kind of time and level alignment to the subs as well.