Kodi does not play flac 192khz files

Hi,

I have a X96Max+ Android box with display and 4/64 configuration.
I installed the latest stable CoreElec 9.2.5 and that works fine from sd card.
I connected the optical out of the X96Max+ to my optical in of my yamaha htr 3072 surround receiver that has a build in dac capable of 384/32. I have my flac files on a NAS. When I put the settings in Kodi to play 192 flac files that doesn’t work. When I put the settings in Kodi to 96 the 192 flac file plays on 96.
Question is if it is possible to make this work.

Many thanks

Are you sure your Yamaha will accept 192kHz on the S/PDIF port (optical)?
The DAC in the Yamaha may be capable of handling 384kHz / 32bit but on which interface? HDMI? USB?
The S/PDIF optical interface would normally handle 192kHz maximum and only 2 PCM channels or compressed multichannel like AC3 or DTS. I had a look at the user manual of your receiver where it states:

Digital Audio (Supported frequencies: 32 kHz to 96 kHz)
• Optical x 1
• Coaxial x 2

The HDMI section supports:
• DSD 2-ch to 6-ch (2.8 MHz)
• PCM 2-ch to 8-ch (Max. 192 kHz/24-bit)
plus the usual DD and DTS variants.

Why do you think it supports 384kHz?

Hi,

I also have connected an old Asus O’play HD2 via optical out to my htr3072 receiver and with that old device I’m able to play the 192 file, the receiver shows it on his display. With my X96Max+ Coreelec box when i put the Limit Sampling Rate to 96khz it will play the file.
So in short yes my yamaha receiver is able to play 192khz flac files but not at this moment with Coreelec. I also seen somewhere via a google search someone with another android box but with libreelect installed who had the same problem but when switching to another device tree he was able to play 192khz files. Maybe the device tree i’m using has problems ?

But why does the user manual for your device (HTR 3072) state that 96kHz is the maximum rate on the digital S/PDIF interface??? On HDMI it supports 192kHz, though. Some kind of handshaking problem I think. Are you sure the Yamaha model number is correct? What does your user manual say?

This is indeed strange. But the yamaha I have is the Yamaha HTR-3072 (RX-V385). If you look for the specifications on RX-V385 on https://usa.yamaha.com/products/audio_visual/av_receivers_amps/rx-v385_u/specs.html you see that is says DA Converter - Burr-Brown 384 kHz / 32-bit DAC x 3.
Anyway like I said in my earlier reply … I also have connected an old Asus O’play HD2 via optical out to my htr3072 receiver and with that old device I’m able to play the 192 file, the receiver shows 192 on his display. So it can play those files except via my Kodi in coreelec on my X96MaxPlus. There are only 2 device trees, I tried them both, with the same problem.

It possible that your box could send only 96kHz.
I had one box with same problem. All other boxes works normal on 192kHz via SPDIF.

… and again the specifications for that receiver state that the digital input (optical/cpax) only support 96kHz.

EDIT - maybe post a debug log so that we can see what might be going on.

1 Like

Hi, with a bit of searching here is the debug log file. Let me know if you need more information. Thanks.log-2020-12-20-14.16.39.zip (91.4 KB)

The Kodi logi indicates that it’s playing the track (assuming it is the Enya track!) at 192kHz. If you can’t hear it on your AV amp unless you manually downsample it to 96kHz, then it suggests very strongly to me that your amp can only accept input on the S/PDIF up to 96kHz as per the printed specifications. I’m at a loss as to why the amp is apparently accepting and displaying 192kHz on the optical S/PDIF from another source :thinking: Do you have a log from the other source? Can you tell the difference when listening to a 192kHz vs a 96kHz source?

2020-12-20 15:11:04.536 T:4043735936   DEBUG: CActiveAE::ClearDiscardedBuffers - buffer pool deleted
2020-12-20 15:11:04.538 T:3930264448   DEBUG: Previous line repeats 1 times.
2020-12-20 15:11:04.538 T:3930264448   DEBUG: AudioDecoder::GetReplayGain - Final Replaygain applied: 1.000000, Track/Album Gain 89.000000, Peak 1.000000
2020-12-20 15:11:04.538 T:4035343232    INFO: CActiveAESink::OpenSink - initialize sink
2020-12-20 15:11:04.538 T:4035343232   DEBUG: CActiveAESink::OpenSink - trying to open device ALSA:iec958:CARD=AMLAUGESOUND,DEV=0
2020-12-20 15:11:04.538 T:4035343232    INFO: CAESinkALSA::Initialize - Attempting to open device "iec958:CARD=AMLAUGESOUND,DEV=0"
2020-12-20 15:11:04.546 T:4035343232    INFO: CAESinkALSA::Initialize - Opened device "iec958:CARD=AMLAUGESOUND,DEV=0,AES0=0x04,AES1=0x82,AES2=0x00,AES3=0x0e"
2020-12-20 15:11:04.547 T:4035343232    INFO: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2020-12-20 15:11:04.547 T:4035343232    INFO: CAESinkALSA::InitializeHW - Using data format AE_FMT_S16NE
2020-12-20 15:11:04.547 T:4035343232   DEBUG: CAESinkALSA::InitializeHW - Request: periodSize 9600, bufferSize 38400
2020-12-20 15:11:04.548 T:4035343232   DEBUG: CAESinkALSA::InitializeHW - Got: periodSize 9600, bufferSize 38400
2020-12-20 15:11:04.548 T:4035343232   DEBUG: CAESinkALSA::InitializeHW - Setting timeout to 200 ms
2020-12-20 15:11:04.548 T:4035343232   DEBUG: CAESinkALSA::GetChannelLayout - Input Channel Count: 2 Output Channel Count: 2
2020-12-20 15:11:04.548 T:4035343232   DEBUG: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR
2020-12-20 15:11:04.548 T:4035343232   DEBUG: CAESinkALSA::GetChannelLayout - Got Layout: FL, FR (ALSA: none)
2020-12-20 15:11:04.548 T:4035343232   DEBUG: CActiveAESink::OpenSink - ALSA Initialized:
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Output Device : AML-AUGESOUND
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Sample Rate   : 192000
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Sample Format : AE_FMT_S16NE
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Channel Count : 2
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Channel Layout: FL, FR
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Frames        : 9600
2020-12-20 15:11:04.548 T:4035343232   DEBUG:   Frame Size    : 4
2020-12-20 15:11:04.553 T:4043735936   DEBUG: CActiveAE::ClearDiscardedBuffers - buffer pool deleted
2020-12-20 15:11:04.592 T:3930264448   DEBUG: Previous line repeats 1 times.
2020-12-20 15:11:04.592 T:3930264448    INFO: PAPlayer::PrepareStream - Ready
2020-12-20 15:11:04.595 T:3921871744   DEBUG: OnAVStarted: CApplication::OnAVStarted

Try a 9.2 nightly build and see if that fixes the problem.

Dear All,
Thanks for all the effort and good information.
But I have found the problem. I have 3 device coupled with my AV Receiver via a optical switch.
When I connected the X96Max+ directly with a optical cable with my AV Receiver it worked. It shows now 192 khz. So it is the switch or the optical cable that is the problem.
Thanks.

It would have helped the analysis if you had indicated in the first instance that there was other equipment between your AV receiver and your X96 box. However, we got there in the end. I think that you will not be able to hear the difference between the same audio material whether output at 192kHz or downsampled to 96kHz. It’s the audio mastering/mixing that influences the sound mostly. Try Enya at 48kHz and see if you can hear the difference! I wouldn’t have thought that there would be a native 192kHz master available for her catalogue, but maybe some newer stuff, perhaps?

Make a mountain out of a molehill.
Nobody will hear he difference between the same audio material whether output at 192kHz or downsampled to 96kHz using this AVR(Yamaha RX-V385)
I don´t believe anybody will hear the difference with HiFi hardware

1 Like

About | FAQ | Terms of Service | Privacy Policy | Legal Notice