Print

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

[tbng]

It's an old problem for me.  At times in the past I've had difficulty getting JRiver to find the device to which it was attached via HDMI, mandatory because I listen to many surround recordings.  It used to be with a Meridian HD621 HDMI interface.  Now, it's the Trinnov Altitude 16.  For three weeks following installation, JRiver and Trinnov were happily married.  Then, the Trinnov decided I no longer needed sound and went mute on all sources.  Since it is nothing more than a Linux-based computer, I pulled the plug and turned it back on.  Voila!  Sound returned on every source - but not JRiver.  JRiver no longer recognizes the Trinnov as a device, and my music server has been rendered mute.  I have made no changes to JRiver settings other than to buffering (an issue discussed elsewhere here), and all of those were installed and working before this problem began.  Multiple reboots of both machines have accomplished nothing nor does swapping HDMI cables.  It doesn't sound like a JRiver problem, but maybe someone can make a suggestion.  So far, all Trinnov has to say is "Nous ne parlons pas anglais."

Could JRiver's network player get around the HDMI nightmare?

[JimH]

One of your other applications may be set in Exclusive mode.

[fitbrit]

When you unplugged the Trinnov, MC may have changed the sound device associated with the zone you usually use with the Trinnov. With the Trinnov turned on, go into Options> Audio in MC and check that the Trinnov is the right audio device. Many other issues would produce some kind of error message.

[Fitzcaraldo215]

It's an old problem for me.  At times in the past I've had difficulty getting JRiver to find the device to which it was attached via HDMI, mandatory because I listen to many surround recordings.  It used to be with a Meridian HD621 HDMI interface.  Now, it's the Trinnov Altitude 16.  For three weeks following installation, JRiver and Trinnov were happily married.  Then, the Trinnov decided I no longer needed sound and went mute on all sources.  Since it is nothing more than a Linux-based computer, I pulled the plug and turned it back on.  Voila!  Sound returned on every source - but not JRiver.  JRiver no longer recognizes the Trinnov as a device, and my music server has been rendered mute.  I have made no changes to JRiver settings other than to buffering (an issue discussed elsewhere here), and all of those were installed and working before this problem began.  Multiple reboots of both machines have accomplished nothing nor does swapping HDMI cables.  It doesn't sound like a JRiver problem, but maybe someone can make a suggestion.  So far, all Trinnov has to say is "Nous ne parlons pas anglais."

Could JRiver's network player get around the HDMI nightmare?

It is really a Windows problem.  So, there is nothing JRiver can do.  You need to first make sure Windows "sees" the Trinnov properly in Windows Sound.  Make it the default device and exclusive, if you need to.  Then, JRiver ought to be able to use it as its output device setting.

I used a Gefen HDMI Detective+ to permanently solve my HDMI issues.  There is a 4K version for around $100.  It is always on, powered via HDMI, so Windows always sees it and does not attempt to mess with the output settings.  The Trinnov or any other receiving device behind it can be off or on, but Windows is buffered from that by the Gefen.  So, Windows never gets confused.

[fitbrit]

It is really a Windows problem.  So, there is nothing JRiver can do.  You need to first make sure Windows "sees" the Trinnov properly in Windows Sound.  Make it the default device and exclusive, if you need to.  Then, JRiver ought to be able to use it as its output device setting.

I used a Gefen HDMI Detective+ to permanently solve my HDMI issues.  There is a 4K version for around $100.  It is always on, powered via HDMI, so Windows always sees it and does not attempt to mess with the output settings.  The Trinnov or any other receiving device behind it can be off or on, but Windows is buffered from that by the Gefen.  So, Windows never gets confused.

I second this recommendation for those who want no hassles and are willing to pay for that.

[tbng]

"You need to first make sure Windows "sees" the Trinnov properly in Windows Sound.  Make it the default device and exclusive, if you need to.  Then, JRiver ought to be able to use it as its output device setting."

Interesting comment.  I am surprised to see that computer sound does not even offer HDMI as a playback device.  That seems to explain the dead output on HDMI except that I've never used anything but HDMI.  I'm really confused.

[fitbrit]

You said you have swapped HDMI cables. Have you tried using a different HDMI input on the Trinnov?

[tbng]

I checked Windows/Sound in the control panel and to my surprise there is NO offering for an HDMI sound driver.  Given that I've been using HDMI exclusively for audio since I starting using JRiver and that I have sound for the first three weeks of Trinnov ownership, I am going to presume there was a driver installed.  Now, there is none.  Whatever caused the Trinnov's sound problem apparently also erased the HDMI driver on the music server computer.  Doesn't make a lot of sense, but I don't know what else to conclude.

[alglove]

It could be that Windows knows that the HDMI output is there, but is hiding it from view because it thinks it is disconnected. In Windows/Sound in the Control Panel, right click on the white background and put checkboxes next to "Show Disabled Devices" and "Show Disconnected Devices".

[Fitzcaraldo215]

I checked Windows/Sound in the control panel and to my surprise there is NO offering for an HDMI sound driver.  Given that I've been using HDMI exclusively for audio since I starting using JRiver and that I have sound for the first three weeks of Trinnov ownership, I am going to presume there was a driver installed.  Now, there is none.  Whatever caused the Trinnov's sound problem apparently also erased the HDMI driver on the music server computer.  Doesn't make a lot of sense, but I don't know what else to conclude.

I seriously doubt there is a special driver for the Trinnov.  HDMI audio is part of the PC driver for video, either for the GPU or integrated on the mother board with Intel.  But, HDMI video also makes HDMI audio available to Windows Sound.

HDMI exchanges information with the receiving device via an EDID handshake, including the name of the receiving device.  No handshake, no audio or video.  So, typically you will see the name of the receiving device listed in Windows Sound as if it were a unique driver, but it isn't.  It is just HDMI audio with the device name obtained from the handshake.  Mine lists it as "Gefen" because my Gefen HDMI Detective+ device is what it sees as a result of the handshake.

If Windows Sound is not listing your Trinnov and the advice in posts above is not helping, likely something is going wrong with the HDMI handshake establishing connection.  That could be a cable or HDMI port malfunction on the PC or the Trinnov end.

You said you have already tried other input sources and cables to the Trinnov.  I assume that was to the same Trinnov HDMI input port.  If not,check that.  Do you have another HDMI input device, like a monitor?  Try connecting that directly to the same PC HDMI port to check the output port on the PC.  Sound isn't necessary. This is just to check that the HDMI handshake is taking place and that the PC's output port is good.

Also, turn on sequence is often the culprit.  You have tried rebooting, but try it once more.  Everything off, reset then turn on the Trinnov, then the PC.  Check Windows Sound to see if the Trinnov is listed. Make sure it is the default output device.  Normally, this turn on sequence should work. Sometimes we get lost in testing or do inadvertent things. 

Do these before you call your dealer or Trinnov.  They will want to know whether these basics work or not.

You are not the first and you will not be the last to encounter the tricky monster of HDMI in Windows.