DTS-HD - TRUE-HD passthrough seems to have stopped working upgraded to KODI 17.6
#1
Hi all - thanks in advance. I've seem to have lost passthrough of HD codecs on KODI. Although i'm not/can't 100% link it, it seems to have occurred following my known last update to KODI-17.6. However i have been using it for a couple of weeks but its the first time i've noticed movies with HD codecs are not working and that was the last change I can remember doing. DTS-HD and TRUE-HD don't work. DTS, AAC etc all work fine.

standard upgrade i followedConfusedudo apt-get update
sudo apt-get upgrade

&& also did
sudo apt-get dist-upgrade

I have searched the forums trying to find similar recent posts but most seem relevant to issues with new hardware and kernel updates, they don't seem to be the same issue as i don't see the same ouput in the debug logs - in fact i don't see anything indicating errors in kodi logs, seems to be working fine from KODI point of view.

logfile - (1st 512KB) - https://pastebin.com/VPFWk3sc
Logfile - (at time of selecting movie): https://pastebin.com/2DmSruVW
new FULL logfile following reboot - debug enabled - (disabled pulse audio in /etc/pulse/client.conf) - https://pastebin.com/EHMyvJjs
Hardware: Intel NUC D34010WYKH - i3 - HASWELL.
AVR: Yamaha VX-R673
Ubuntu 14.04 (Kernel: 3.13.0-137-generic)
Kodi 17.6 Git:20171114-a9a7a20

I realize I am using ubuntu 14.04 as base system but this all did work previously and "if possible" I really wanted to avoid rebuilding/upgrading the OS (just in the hope upgrading to recent release will fix it - but certainly will if it's confirmed issue with 14.04). Primarily because I have other services running on it which i'm reluctant to go through hassle of troubleshooting when they "break". But this has been working and wonderfully stable for some time.

If there is any direction for me to look into that'd be great, KODI logs indicate ALSA is being used.

Kind regards
Adrian
Reply
#2
Please always include the FULL debug log file. We prefer to have all the puzzle pieces.
Reply
#3
Apologies - I've tried to include FULL logfile but it was too large for PASTEBIN (1809KB) . So i've included the first 512KB and plus the existing DEBUG snippet when i clicked the movie. If you still require a complete FULL log i'll have to paste in clumps.

Thanks for looking though.

regards
Adrian
Reply
#4
The issues I see here have nothing to do with kodi. Seems "something" fucked up while upgrading. From the looks, we try to open the device the way it should be 8 channels / 192 - but it fails, it does not say why and we fall back to NULL Sink. Please try LibreELEC 8.2 from USB stick and verify.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#5
I've manage to get it working - I think the issue is around PULSE audio - so don't think I've solved the issue but worked around it.

I noticed after you said post FULL log - there was an ERROR

13:58:39.446 T:140030726875136   ERROR: PulseAudio: Failed to connect context
13:58:39.446 T:140030726875136  NOTICE: PulseAudio might not be running. Context was not created.

So decided to disable pulse in /etc/pulse/client.conf [autospawn = no] . rebooted 

It still didn't seem to work and the log entry about PulseAudio was still present but can see in the logs were successfully detecting my AVR and passthrough capabilities.

I decided to just re-check passthrough settings in KODI AUDIO menu (as I had been messing with them previously, to try and get this working) - this time I noticed KODI has detected my YAMAHA AVR as a HDMI device - (previously it's always been denoted something along lines of "HDA intel, hdmi #0" ) - now it's "HDA intel, YMH RX-V673 on HDMI" . This has always HDMI dev #0 btw just never seemed to have shown up as YMH device in KODI.


Anyway ensured passthrough device was the YMH RX-V673 and it's all working fine again.

regards
Adrian
Reply
#6
Thanks Fritsch, yeh i've suspected something to be wrong with underlying OS rather than KODI but know idea what to look at, plus reserved about doing full upgrade.

Obviously there is a difference now in the log output and device is initialized correctly - no idea if this related to me disabling pulse or coincidence of reboot, I will have ago at putting pulse config back and see if it reverts.

https://pastebin.com/7CMtNwZd

Thanks again for looking - appreciated.
Reply
#7
This would suggest all perfectly fine:

Quote:
  1. 15:21:16.617 T:140663450486528   DEBUG: CActiveAESink::OpenSink - ALSA Initialized:
  2. 15:21:16.617 T:140663450486528   DEBUG:   Output Device : HDA Intel
  3. 15:21:16.617 T:140663450486528   DEBUG:   Sample Rate   : 192000
  4. 15:21:16.617 T:140663450486528   DEBUG:   Sample Format : AE_FMT_S16NE
  5. 15:21:16.617 T:140663450486528   DEBUG:   Channel Count : 8
  6. 15:21:16.617 T:140663450486528   DEBUG:   Channel Layout: RAW,RAW,RAW,RAW,RAW,RAW,RAW,RAW
  7. 15:21:16.617 T:140663450486528   DEBUG:   Frames        : 1024
  8. 15:21:16.617 T:140663450486528   DEBUG:   Frame Size    : 16

The rest you cut away - no idea.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
DTS-HD - TRUE-HD passthrough seems to have stopped working upgraded to KODI 17.60