Print

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

[lucretius]

I use this driver to send audio from other programs to JRiver Media Center. However, since MC25, it does not work -- I get an error message:

Windows cannot find 'C:\Program Files\J River\Media Center 25\Media Center 24.exe' .

How do I get it to point to 'C:\Program Files\J River\Media Center 25\Media Center 25.exe' ?

[RoderickGI]

Not sure, but try disabling the ASIO Driver Feature in MC25, rebooting the PC, and then re-enabling the ASIO Driver Feature.

"Options > General > Features > ASIO Driver"

[lucretius]

That doesn't do it.  Somewhere a pointer (where it's located exactly, I do not know) was set to look for file name "Media Center 24.exe" instead of "Media Center 25.exe".  This should be a simple fix.

[RoderickGI]

Okay, I was hoping that may simply fix file associations and get things working again.

You will need to fix file associations yourself, manually, by the sound of it. But you haven't provided enough detail to be sure exactly what you are doing. I don't use the ASIO driver, so that leaves me at a disadvantage. But if you are trying to play a file to an application, and it still points to MC24, then you need to change Windows so that it points to MC25.

Search for "Default Apps" in Windows, then select either default apps by file type, or default apps by protocol. Change the default Music and Vdeo player as well, if you want.

[lucretius]

Okay, I was hoping that may simply fix file associations and get things working again.

You will need to fix file associations yourself, manually, by the sound of it. But you haven't provided enough detail to be sure exactly what you are doing. I don't use the ASIO driver, so that leaves me at a disadvantage. But if you are trying to play a file to an application, and it still points to MC24, then you need to change Windows so that it points to MC25.

Search for "Default Apps" in Windows, then select either default apps by file type, or default apps by protocol. Change the default Music and Vdeo player as well, if you want.

I went through the registry and I deleted all references to Media Center 24.exe.  That did not do it. However, I downloaded the latest iteration of J River Media Center (25.0.31) and the problem disappeared. I can now use the "J River Media Center 25" ASIO driver to send audio from other programs to JRiver Media Center. I wish developers would either note such fixes in the release notes or otherwise reply to the message here that the fix is in.  Thanks to all!

[lucretius]

For some reason I am getting the original error message again:
"Windows cannot find 'C:\Program Files\J River\Media Center 25\Media Center 24.exe". I thought that was fixed. I am perplexed.

[Awesome Donkey]

Sounds like an antivirus issue.

[Hendrik]

It should work if you make sure that MC25 is already running when trying to play content through ASIO. It only fails if it doesn't find a running MC and then tries to start it - using the wrong name.

I've fixed the issue in the driver, so that should also be resolved in a future build.

[lucretius]

It should work if you make sure that MC25 is already running when trying to play content through ASIO. It only fails if it doesn't find a running MC and then tries to start it - using the wrong name.

I've fixed the issue in the driver, so that should also be resolved in a future build.

Thanks a million!

[MarcR]

Hendrik, all,

Happy MC user since many years, having used audio inputs from ASIO soundcards, and from Windows apps via the WDM driver, all fine.
But with HiRes streaming coming up these days, for getting the HiRes directly into MC, I now really need to have the JRiver ASIO driver working.
I have tried to use it since MC19, now using MC23 on Win10, but still have the following trouble, which I presume is still valid for MC25:

I cannot get the ASIO input driver to work with several apps that can output to ASIO, like:
- HiResAudio's streaming app: it crashes once starting to play to the JRiver ASIO
- Voicemeter: it keeps flashing red the output when selecting it to be JRiver ASIO, indicating it does not work as expected
I do get it to work however in 2 channels at 32bit/192kHz or any other frequency from Pianotec 6, although there it starts going on/off in a loop when trying to select more then 2 channels as an output config towards JRiver ASIO.
But this proves at least that in some configs it does work fine (be it somewhat sensitive to reconfigs).
The HiResAudio streaming app as well as Voicemeter and Pianotec all do connect fine directly to the ASIO driver of my Exasound DAC directly too (but then I miss MC's features like room correction, multi-channel conversion, zones, etc.).

So what can be the mismatch with most apps and the JRiver ASIO driver?
Are there JRiver ASIO driver limitations to bit depth, frequency, number of channels or buffer size that may be violated by these apps?
Or might the input apps expect some responses from the JRiver ASIO driver that they do not get?

Is there any configuration that can be fiddled with at the MC side (apart from options/general/ASIO driver yes/no)?
Any way to monitor what is going wrong?
(In some cases MC does switch to ipc, but only achieving sound in Pianotec, as said.)

I read here that one driver setup bug was fixed by Hendrik (as in the MC25 release notes 25.0.34 (5/2/2019) "1. Fixed: The JRiver ASIO driver did not work properly because it was still referring to MC24 in one place."), so I made sure manually that any registry keys for older MC versions where removed from Windows Registry, did a clean reinstall, restarting machine, etc. but the problems persist.
I expected that of course, given that Pianotec does get something through the JRiver ASIO driver, so the problem must be inside the communication ongoing between the external app's input process and the JRiver ASIO driver process. Everything surrounding it seems to work ok.

Would expect many people to start using this for HiRes streaming into MC, so an important feature, I would think, that presumably would have matured since MC19.
(Could go through a DLNA client to JRiver Media Server, but that I find a very involved work-around...)

Any insights welcome... thanks in advance.

[JimH]

Please try MC25 and report any problems.

[MarcR]

Did what you suggested, JimH:
Installed MC25, restarted machine & closed MC23 and its media server, then started MC25 fresh without importing anything from MC23.

This gives me practically the same issues:
- Pianotec now finds ASIO "JRiver Media Center 25" and can play on it, as before, but:
- HiResAudio's streaming app and Voicemeter still cannot play to ASIO JRiver, which remains having the name "JRiver Media Center 23" btw. Both do start ipc on MC25 (without sound, as before).
- The very first time I attempted to play something on the HiResAudio streaming app, MC25 prompted an error, proposing that it would change a setting (where are those in the MC UI?) from 16 to 2 channels input, as that is what the input app indicated (at 32 bit and 96kHz). I clicked yes on that, but the originating app crashed in teh mean time.

So it appears nothing is different from what I had with MC23.

BTW, as the default output for this new MC25 install is still on the default (Windows) Direct Sound, the different output stage appears to have no influence on the problem (my MC23 instance was configured to go to an Exasound DAC in the result reported before).

Any logging I could do for you perhaps?
Or any setting that may have impact?

[JimH]

DSP Studio > Output Settings.

[MarcR]

Yes indeed, just discovered that.
So that has nothing to do with the input problem, just the conversion within MC to the Direct Sound output (which I did indeed not have when connecting to my DAC).

So problem remains identical in MC25.

[Matt]

I just tried Voice Meter and it tries to output 16 channels and Media Center doesn't currently support that.

I'll make the next build just ignore any channels over 8, so at least it will start working / routing the first eight channels.

Please try once the build is available.

[MarcR]

Thanks for looking into the issue, Matt.

FYI: In some other thread on the ASIO driver topic I saw once, someone suggested that MC would actually be asking for 16 channels, as a reason for other programs trying to deliver that... not sure how that works, but I do know that anything I have thrown at the ASIO driver just was 2-channel material (from standard 44.1/16 to 192/24).
Voicemeeter and certainly HiResAudio's streaming app would never want to output 16 channels by themselves, I guess.

Hope you guys can demystify the apparantly 'not so waterproof ASIO API spec'.