INTERACT FORUM

More => Old Versions => JRiver Media Center 24 for Windows => Topic started by: pacopericolo on September 05, 2018, 05:45:02 am

Title: ASIO In -> ASIO out
Post by: pacopericolo on September 05, 2018, 05:45:02 am

Hi,

I am trying to use the Live Play Function with ASIO input in JRiver. As the option menu already suggests, "probably you have to use a different device for input and output". Can anyone explain why? I use RME hardware (Fireface UC), which is of course full duplex ready and other software is also able to work with in- and outputs via Asio simultaneously.
However, if I try to use ASIO for in- and for output, there is no error but also no sound. If I switch output to WASAPI, it works, but this is no option in my use case.
Is there any way to make this work??

Best,
Paco

Title: Re: ASIO In -> ASIO out
Post by: mattkhan on September 05, 2018, 01:55:42 pm

You either need to have a multiclient capable driver or try to use https://www.steinberg.net/forums/viewtopic.php?t=48 instead

Title: Re: ASIO In -> ASIO out
Post by: pacopericolo on September 05, 2018, 03:00:29 pm

Thank you for this link, I will try this. But still I would like to understand technically why JRiver is "two applications", I mean, the sound goes from the driver into JRiver and then out of JRiver to the driver -> why do I need multi client capability for that? I just don't get the idea behind this kind of implementation and since the rest of the software seems to be quite well thought out this leaves me confused.

Title: Re: ASIO In -> ASIO out
Post by: pacopericolo on September 06, 2018, 02:28:14 am

And one more comment: I can use several applications with the same RME ASIO Driver simultaneously, so I think the driver is multi client capable, the problem seems to be somewhere else...

Title: Re: ASIO In -> ASIO out
Post by: mattkhan on September 06, 2018, 04:31:38 am

Technically it is just the way the app has been implemented, i would guess it is just a by product of input and output being completely separate functions.

I used to use rme and it was meant to be multiclient but I still need to use the Steinberg wrapper to get it to work, other people have found it works directly. You just have to try it out really.

Title: Re: ASIO In -> ASIO out
Post by: pacopericolo on September 06, 2018, 06:21:28 am

I have just tried the Steinberg Multiclient Driver - the server started successfully and I see the "ASIO Client" driver in some programs, but not in JRiver  ?
It's just not there  ::)

Any hints?

Title: Re: ASIO In -> ASIO out
Post by: Awesome Donkey on September 06, 2018, 06:27:18 am

One thought... is the Steinberg Multiclient Driver a 32-bit and/or a 64-bit driver? If you're using 64-bit MC24 and the driver is 32-bit only, then MC can't use it. You'd have to use the 32-bit version of MC24 in that case. The reverse (64-bit only driver with 32-bit MC24) is possible too, with the same issue.

Title: Re: ASIO In -> ASIO out
Post by: pacopericolo on September 06, 2018, 07:05:27 am

Ok, this works, thanks for helping!  :)
There is no 64 bit version of the multiclient driver, so I will probably be forced to use the 32 bit JRiver forever...
Still IMO it's a bug - or at least pretty much an inconvenience, and one that could be solved.  Other processing software (Max, Pd, Audition etc.) can do it, why can't JRiver?
Does it make any sense to post it as a bug in the "JRiver Media Center 24.0.48 -- Available Here" thread? What do you guys think?

Title: Re: ASIO In -> ASIO out
Post by: JimH on September 06, 2018, 07:15:56 am

I don't think it's a bug.  There's no harm in using the 32 bit version of JRiver.