Print

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

[gtgray]

I have seen this come up before with a couple of builds of MC16, it usually was fixed in the next build.

Trying to start a Video from Standard View get :

"Something went wrong with playback"

"Failed to connect audio renderer to audio decoder."

I assume you all know what this one is...  

HDMI bitstreaming... Denon AVR-591 Nvidia HDMI Audio..

[gtgray]

No help here apparently.. this must be happening to others as well.

[JimH]

We're aware of a couple of similar problems.  One with MOV files that aren't Apple's.  One with 3gp files from a phone.  These should be fixed shortly.

[CountryBumkin]

I have seen this come up before with a couple of builds of MC16, it usually was fixed in the next build.

Trying to start a Video from Standard View get :

"Something went wrong with playback"

"Failed to connect audio renderer to audio decoder."

I assume you all know what this one is...  

HDMI bitstreaming... Denon AVR-591 Nvidia HDMI Audio..

I seem to recall having this problem a while back when my Audio was not setup properly. i can't recall the exact issue now.
Are you using WASAPI Event style?

[gtgray]

I seem to recall having this problem a while back when my Audio was not setup properly. i can't recall the exact issue now.
Are you using WASAPI Event style?

Yes, but it occured with direct audio as well.  I just updated the to last/latest version of 16 and I see the same thing. I have recently updated my Nvidia driver. I am running 285.38

[gtgray]

Yes, but it occured with direct audio as well.  I just updated the to last/latest version of 16 and I see the same thing. I have recently updated my Nvidia driver. I am running 285.38

I see there is a later version just released that is WHQL, I will give that one a shot but I believe the HDMI audio driver piece is the same.

[gtgray]

I see there is a later version just released that is WHQL, I will give that one a shot but I believe the HDMI audio driver piece is the same.

The WHQL version 285.62 behaves the same.

[Matt]

Could you describe your settings for Options > Audio, bitstreaming, and DSP Studio?  Red October Standard?

Does audio-only playback work?

Thanks.

[gtgray]

Could you describe your settings for Options > Audio, bitstreaming, and DSP Studio?  Red October Standard?

Does audio-only playback work?

Thanks.

Audio -Direct Sound.... have also tried WASAPI Event Style
Device Denon Amp
HDMI Bitsteaming
Music files play fine
Red October HQ with filters
Hardware Acceleration
Default Video Render automatic

Playback Method J River Video Engine
Source Filter Automatic
LAV CUVID Decoder
madVR

Been run LAV CUVID and madVR along time.

[Matt]

Try Red October Standard and no bitstreaming.  Does that work?

[gtgray]

Try Red October Standard and no bitstreaming.  Does that work?

No, I did uprade another PC to the latest version of 16, but not 17 and it works.

[gtgray]

So are there any more suggestions? This PC still doesn't work, and I would like to upgrade at the discount but since installing I am broken on 16 and 17 on this box.

[fitbrit]

Audio -Direct Sound.... have also tried WASAPI Event Style
Device Denon Amp
HDMI Bitsteaming
Music files play fine
Red October HQ with filters
Hardware Acceleration
Default Video Render automatic

Playback Method J River Video Engine
Source Filter Automatic
LAV CUVID Decoder
madVR

Been run LAV CUVID and madVR along time.

Did you try WASAPI (not event style) too? Try a low e.g. 10 ms buffer.

I notice you're using HQ with additional filters. Can you try standard and HQ without the additional filters; I don't see why you'd need them, and by specifying additional filters, you're probably running older versions unless you manually upgraded to the newest ones like MC does automatically, give or take.

[gtgray]

Did you try WASAPI (not event style) too? Try a low e.g. 10 ms buffer.

I notice you're using HQ with additional filters. Can you try standard and HQ without the additional filters; I don't see why you'd need them, and by specifying additional filters, you're probably running older versions unless you manually upgraded to the newest ones like MC does automatically, give or take.

I can try WASAPI event/ no event.. tried your buffer suggestion.. I have tried Red October standard it did not help. So that eliminates the additional filters variable. I can set it to the most basic settings avaialable and I still get the error. I set it everything to automatic  and to the most basic setttings...... no go.


I literally have tried everything and I get no playback at all all, just the failed to connect audio redender to the audio decode. WMC works, MPC-HC works, PowerDVD works. MC 16 and 17 don't on this box, 16 did for a long time. I am at a loss.
 

[fitbrit]

I'm sorry that there may be some repetition here. I think I just remembered how I fixed this issue myself a couple of months ago.

In options>audio, what is the audio device in output mode settings?

In options>video>advanced, what is the audio playback device.

If the former is "denon amp", make sure the latter is also "denon amp", and by that I mean that it's actually the same device, not "windows default" or "same as device used in audio".

[gtgray]

In Audio
Output Mode is:
WASAPI
the output device is :
Denon-AVAMP-1 (Nvidia High Definition Audio)

In Video Advanced
Audio Playback Device is:
Denon-AVAMP-1 (Nvidia High Definition Audio)

[fitbrit]

OK.
Last thing before I run out of ideas for now: How is the Windows audio playback device configured? If the default deveice is the Denon, go into properties, supported formats:
Do you see TrueHD, DTS-HD as well as DD/AC3, DD+/EAC3 and DTS?
If yes, I'm stumped.
If no, try a different HDMI cable (assuming that you installed new nVidia drivers already).

[JimH]

In Audio
Output Mode is:
WASAPI
the output device is :
Denon-AVAMP-1 (Nvidia High Definition Audio)

If you haven't done so, try the tests from Windows Control Panel/Sounds to make sure Windows thinks it can play the format successfully.  If it doesn't work there, it won't work in MC.

I had a similar problem once with an ATI card and it took updating the driver to get Windows to see some of the 5.1 formats.

[gtgray]

OK.
Last thing before I run out of ideas for now: How is the Windows audio playback device configured? If the default deveice is the Denon, go into properties, supported formats:
Do you see TrueHD, DTS-HD as well as DD/AC3, DD+/EAC3 and DTS?
If yes, I'm stumped.
If no, try a different HDMI cable (assuming that you installed new nVidia drivers already).

First you have to understand this is a working installation for everything but JR MC.. All the formats show supported in playback devices. I get HD audio and the other formats in the other playback environments. An the multichannel formats work in the other players. Just to keep a reality check on this I did a clean install of the drivers. I can't run, the latest driver because it has a bug that prevents a good number of the newish video cards from displaying any video in WMC. WMC is required to view my Ceton. As much as I would like a divorce from WMC until someother Media Center environment supports cable card tuners WMC is vital.

There is nothing wrong with my HDMI cable, if it can pass HD audio and video for other playback environments. This was working in 16 for a long time until one of the most recent updates. Something changed in the code base and it is common to 16 and 17

[JimH]

Just to confirm...

Are you running 17.0.22?

Are you able to test with a device other than the Denon?

[Matt]

In Video Advanced
Audio Playback Device is:
Denon-AVAMP-1 (Nvidia High Definition Audio)

This bypasses the JRiver audio engine, which might cause the problem.

Instead, select Options > Video > Advanced > Audio playback device > Same as device used in audio playback (the default).

[JustinChase]

This bypasses the JRiver audio engine, which might cause the problem.

Instead, select Options > Video > Advanced > Audio playback device > Same as device used in audio playback (the default).

^^^  This worked for me a few months ago.  Your Audio looks to be setup correctly, so video "using the same device" will use this setup, and as Matt said, will send thru the MC engine.

It seemed "wrong" to me, like it would be better to be specific on both places, but this change has mine working since months ago.

good luck

[fitbrit]

Yeah, it's the opposite of what I was suggesting; I couldn't quite remember how I fixed my problem.

[gtgray]

This last suggestion worked for me, finally. But wait before I loose your attention. I have run into something else new and very weird. It only happens in MC17, playing the same content as MC16.


I have been running this Sandy Bridge for about 4-5 months. Intel H67 Media Board, GT 545. When I run an HD MKV derived from a  Blu-Ray playing back DTS HD Audio DTS HD MA. I am getting a voltage errror on the 12V line. So something you are doing in 17 is pulling a lot more voltage than the same content on 12v. I would be inclined to say I have a hardware problem, but in the whole time I have owned this box I have never seen an error message on hardware from the Intel Desktop Utilities. It seems the 12V line is being pulled down to almost 11v (11.08) when playing this content. Same content with LAV CUVID and MadVR is not pulling the power supply down. Everthing plays fine but the health monitoring is sensing the 12 volt line is dropping in MC 17.

I will troubleshoot the hardware, but I don't get what is going on in MC 17?

[JustinChase]

This last suggestion worked for me, finally.

good news!

Same content with LAV CUVID and MadVR is not pulling the power supply down.

I won’t pretend to have any idea what’s causing the power drop you’re seeing, but I’m curious about what other program you’re using to test this…

MPC-HC?

[gtgray]

MC 16, PowerDVD, MPC-HC.

I mean it seems like a legitimate low voltage warning. I just have never seen one on this machine before now, when I just got MC 17 working. Thanks to everyone for use the same as, suggested above. That setting also got MC 16 back working.

MC 16 playing the same content does not cause the 12 volt line to drop. Nor does anything else. Beats me. Either there is sometihing in 17 putting extra load on the PSU, or there is something in 17 interfering with the intel utilites. If 17  is creating extra load it could be revealing a hardware fault that had not been seen before. I don't have any choice now. I will have to put another PSU in the box. If I continue to see the error. I have another GPU of the same type available. If I do both those things and the low voltage warning continues and only in version 17 we would need to look deeper.

I might get a meter on a 12v line and see if the intel utilities are correct. I can't imagine they are not.

[gtgray]

The crazy part about this, the system only uses about 75 watts playing back HD stuff and that is total system with the Nvidia GPU going.

[JimH]

I can't imagine how any piece of software could cause a voltage drop.  It could peg the CPU and the disk, but management of hardware resources has to occur much lower than the application level.

Please copy and paste to a new thread on the Hardware board here.  I'll lock this now and declare the original problem solved.  Let me know if you need it opened again.