•   
  • 1
  • 31
  • 32
  • 33(current)
  • 34
  • 35
  • 70
  •   
Android Passthrough Changes with v17
This is going to be my Automated response to all Krypton Audio Passthrough problems to try and stop frustrations boiling over.

The issue is Android device Firmware that needs updating because of Kodi Krypton's implementation of....

Welcome to Android MediaCodec standards - click here

(2016-09-05, 23:15)AFTVboy Wrote: Android Firmware that meets the IEC61937 Audio standard used in Kodi Krypton v17 currently includes the Xiaomi Mi Box and the nVIDIA Shield.

Any other Android Kodi boxes not implementing the IEC standard in Firmware will have DTS and HD Audio Passthrough issues with Kodi Krypton. These devices must use Kodi Jarvis or for DTS passthrough - Transcode the Audio to AC3, using the following Kodi Audio settings:

Number of Channels: 2.0
Passthrough: On
AC3: Yes
AC3 Transcoding: Yes
DTS: No

OR if you want full Audio passthrough with Kodi (inc. HD) with an AMLogic S905 device, flash LibreELEC Kodi to a Samsung EVO or Sandisk Class 10 microSDHC card.

W.

sorry for bugging.

how can I know if an android box is compliant with the IEC standard?
is there a raccomended list for kodi?
I loved my experience with a cheap android box and kodi.... it worked just flawless... and kodi 17 is way better in my opinion...
(2017-02-06, 10:43)thrxxx Wrote: how can I know if an android box is compliant with the IEC standard?
is there a raccomended list for kodi?

(2017-02-06, 10:43)AFTVboy Wrote: Android Firmware that meets the IEC61937 Audio standard used in Kodi Krypton v17 currently includes the Xiaomi Mi Box and the nVIDIA Shield.

Huh
http://kodi.wiki/view/Log_file/Easy

And look for:
21:39:25.951 T:18446744073429449008 DEBUG: AESinkAUDIOTrack: Using IEC PT mode: 13
21:39:25.952 T:18446744073429449008 DEBUG: 8 Channel PT via IEC61937 is supported

From a Kodi Krypton - Xiaomi Mi Box Log:

Code:
21:39:25.695 T:18446744073429449008 NOTICE: special://profile/ is mapped to: special://masterprofile/
21:39:25.695 T:18446744073429449008 NOTICE: -----------------------------------------------------------------------
21:39:25.695 T:18446744073429449008 NOTICE: Starting Kodi (17.0-RC3 Git:20170111-4d93228). Platform: Android ARM 32-bit
21:39:25.695 T:18446744073429449008 NOTICE: Using Release Kodi x32 build
21:39:25.695 T:18446744073429449008 NOTICE: Kodi compiled Jan 12 2017 by GCC 4.9.0 for Android ARM 32-bit API level 21 (API level 21)
21:39:25.696 T:18446744073429449008 NOTICE: Running on Xiaomi MIBOX3 with Android 6.0.1 API level 23, kernel: Linux ARM 32-bit version 3.14.29
21:39:25.696 T:18446744073429449008 NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
21:39:25.696 T:18446744073429449008 NOTICE: Host CPU: AArch64 Processor rev 4 (aarch64), 4 cores available
21:39:25.696 T:18446744073429449008 NOTICE: Product: once, Device: once, Board: once - Manufacturer: Xiaomi, Brand: Xiaomi, Model: MIBOX3, Hardware: amlogic
21:39:25.813 T:18446744073429449008 NOTICE: External storage path = /storage/emulated/0; status = ok
21:39:25.813 T:18446744073429449008 NOTICE: ARM Features: Neon enabled
21:39:25.816 T:18446744073429449008 NOTICE: Local hostname: localhost
21:39:25.817 T:18446744073429449008 NOTICE: Log File is located: /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/temp//kodi.log
21:39:25.925 T:18446744073429449008 DEBUG: Firmware implements AC3 RAW
21:39:25.925 T:18446744073429449008 DEBUG: Firmware implements EAC3 RAW
21:39:25.926 T:18446744073429449008 DEBUG: Firmware implements DTS RAW
21:39:25.947 T:18446744073429449008 DEBUG: AESinkAUDIOTRACK - 32000 supported
21:39:25.948 T:18446744073429449008 DEBUG: AESinkAUDIOTRACK - 44100 supported
21:39:25.949 T:18446744073429449008 DEBUG: AESinkAUDIOTRACK - 48000 supported
21:39:25.950 T:18446744073429449008 DEBUG: AESinkAUDIOTRACK - 96000 supported
21:39:25.951 T:18446744073429449008 DEBUG: AESinkAUDIOTRACK - 192000 supported
21:39:25.951 T:18446744073429449008 DEBUG: Firmware implements DTS-HD RAW
21:39:25.951 T:18446744073429449008 DEBUG: AESinkAUDIOTrack: Using IEC PT mode: 13
21:39:25.952 T:18446744073429449008 DEBUG: 8 Channel PT via IEC61937 is supported
21:39:25.953 T:18446744073429449008 NOTICE: Found 1 Lists of Devices
21:39:25.953 T:18446744073429449008 NOTICE: Enumerated AUDIOTRACK devices:
21:39:25.953 T:18446744073429449008 NOTICE: Device 1
21:39:25.953 T:18446744073429449008 NOTICE: m_deviceName : AudioTrack
21:39:25.953 T:18446744073429449008 NOTICE: m_displayName : android
21:39:25.953 T:18446744073429449008 NOTICE: m_displayNameExtra: audiotrack
21:39:25.953 T:18446744073429449008 NOTICE: m_deviceType : AE_DEVTYPE_HDMI
21:39:25.953 T:18446744073429449008 NOTICE: m_channels : FL,FR,FC,LFE,BL,BR,SL,SR
21:39:25.953 T:18446744073429449008 NOTICE: m_sampleRates : 32000,44100,48000,96000,192000
21:39:25.954 T:18446744073429449008 NOTICE: m_dataFormats : AE_FMT_S16LE,AE_FMT_RAW,AE_FMT_RAW
21:39:25.954 T:18446744073429449008 NOTICE: m_streamTypes : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048​,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_DTSHD,STREAM_TYPE_TRUEHD

(2017-02-06, 10:43)thrxxx Wrote:
(2016-09-05, 23:15)AFTVboy Wrote: Android Firmware that meets the IEC61937 Audio standard used in Kodi Krypton v17 currently includes the Xiaomi Mi Box and the nVIDIA Shield.

Any other Android Kodi boxes not implementing the IEC standard in Firmware will have DTS and HD Audio Passthrough issues with Kodi Krypton. These devices must use Kodi Jarvis or for DTS passthrough - Transcode the Audio to AC3, using the following Kodi Audio settings:

Number of Channels: 2.0
Passthrough: On
AC3: Yes
AC3 Transcoding: Yes
DTS: No

OR if you want full Audio passthrough with Kodi (inc. HD) with an AMLogic S905 device, flash LibreELEC Kodi to a Samsung EVO or Sandisk Class 10 microSDHC card.

W.

sorry for bugging.

how can I know if an android box is compliant with the IEC standard?
is there a raccomended list for kodi?
I loved my experience with a cheap android box and kodi.... it worked just flawless... and kodi 17 is way better in my opinion...

IEC61937 - Currently the Xiaomi Mi Box, NVIDIA Shield &
Devices with Rockchip processors like Ugoos(UT3, UT4, UT6) & Nagrace(NT-N8, NT-V8, NT-V6) also support it.
Just avoid any cheap, zero supported, no name devices with flashy advertisements that mean nothing from Amlogic & Rockchip otherwise you can forget about pass-through ever working.
(2017-02-06, 10:53)mo123 Wrote: IEC61937 - Currently the Xiaomi Mi Box, NVIDIA Shield &
Devices with Rockchip processors like Ugoos(UT3, UT4, UT6) & Nagrace(NT-N8, NT-V8, NT-V6) also support it.
Just avoid any cheap, zero supported, no name devices with flashy advertisements that mean nothing from Amlogic & Rockchip otherwise you can forget about pass-through ever working.

Looks the Xiaomi Mi Box is quite a guess: not every box works the same, some users can't use netflix properly or the passthrough doesn't work [reddit source]... [and I can't find a shop for europe... is the gearbest model the right one? or is the 3s o 3p version that is crap?]

Well... Not interested in a NVIDIA Shield [I have a PS4] I'm guessing which android set top box is worth to buy... maybe the WeTek Hub?
Seriously! You are NOT looking hard enough, go to Post #1 of the Mi Box Hardware thread

AND look in the START HERE thread in the Hardware Sub-Forum, there are links literally everywhere to click and compare.

Notice to everyone...

I am now deleting off topics posts in this thread from this point forward !

(2017-02-04, 10:12)stefh Wrote: Using Shield TV 2015 + Turtle Beach Audio Advantage Micro 2 USB for toslink out.

Kodi 16: USB optical passthrough DTS and DD 5.1 just fine.
Updated to Kodi 17 yesterday: USB optical passthrough of DTS and DD 5.1 not working anymore. Only 2 channel PCM will work.

SPMC 16.5.5 works fine after selecting RAW, but I stopped using SPMC a while ago because of built-in subtitles not working from library.

I am wondering whether the Kodi team took ShieldTV + USB audio for toslink into account (however pcm 2.0 works, probably has to do with the fact that I cannot choose RAW over IEC and I think Kodi 16 was not using IEC yet?).

Hope this can be fixed, otherwise "stuck" with kodi 16.
You & I are in the same boat. I don't really feel like going back to 16.1 so until/if this gets fixed, I'll probably have to hook my Roku 4 back up & use Plex to watch my Blu ray rips.
(2017-02-07, 03:29)maddog510 Wrote:
(2017-02-04, 10:12)stefh Wrote: Using Shield TV 2015 + Turtle Beach Audio Advantage Micro 2 USB for toslink out.

Kodi 16: USB optical passthrough DTS and DD 5.1 just fine.
Updated to Kodi 17 yesterday: USB optical passthrough of DTS and DD 5.1 not working anymore. Only 2 channel PCM will work.

SPMC 16.5.5 works fine after selecting RAW, but I stopped using SPMC a while ago because of built-in subtitles not working from library.

I am wondering whether the Kodi team took ShieldTV + USB audio for toslink into account (however pcm 2.0 works, probably has to do with the fact that I cannot choose RAW over IEC and I think Kodi 16 was not using IEC yet?).

Hope this can be fixed, otherwise "stuck" with kodi 16.
You & I are in the same boat. I don't really feel like going back to 16.1 so until/if this gets fixed, I'll probably have to hook my Roku 4 back up & use Plex to watch my Blu ray rips.

Exact same for me, Shield TV -> Turtle beach USB -> toslink. Lost DD & DTS.
I will confirm tonight, but I do believe passthrough was working on RC3/RC4. An easy solution might be to downgrade 17 final to 17 RC4. Atl least we would still be on v17.
Hi folks,

I've just noticed something interesting, regarding the capability to passthrough DTS, but at fist the debug log: The provided log was recorded on the latest 17.1 RC, during this playback no DTS-PT worked, only DD-transcoding. As the Nvidia Shield suports DTS and IEC8..., I found this a bit surprising.

I remembered working DTS-PT on RC4 from 30th January, so I tested this one again ... and no working PT.
While reseting the Audio and display settings I noticed the "Sync Playback to Display" option had been enabled. After disabling this option alone, DTS-PT was working again. So I updated again to 17.1RC, DTS-PT still working fine here.

To cross check this I wanted to reenable the "Sync Playback to Display" option in 17.1 RC, but had not been able to do so, as I couldn't find in anymore ...

I'm going to set up a device this weekend and will check that once again ...


Any hints why this option is missing and able to cause this problem?
(2017-02-06, 10:53)mo123 Wrote:
(2017-02-06, 10:43)thrxxx Wrote:
(2016-09-05, 23:15)AFTVboy Wrote: Android Firmware that meets the IEC61937 Audio standard used in Kodi Krypton v17 currently includes the Xiaomi Mi Box and the nVIDIA Shield.

Any other Android Kodi boxes not implementing the IEC standard in Firmware will have DTS and HD Audio Passthrough issues with Kodi Krypton. These devices must use Kodi Jarvis or for DTS passthrough - Transcode the Audio to AC3, using the following Kodi Audio settings:

Number of Channels: 2.0
Passthrough: On
AC3: Yes
AC3 Transcoding: Yes
DTS: No

OR if you want full Audio passthrough with Kodi (inc. HD) with an AMLogic S905 device, flash LibreELEC Kodi to a Samsung EVO or Sandisk Class 10 microSDHC card.

W.

sorry for bugging.

how can I know if an android box is compliant with the IEC standard?
is there a raccomended list for kodi?
I loved my experience with a cheap android box and kodi.... it worked just flawless... and kodi 17 is way better in my opinion...

IEC61937 - Currently the Xiaomi Mi Box, NVIDIA Shield &
Devices with Rockchip processors like Ugoos(UT3, UT4, UT6) & Nagrace(NT-N8, NT-V8, NT-V6) also support it.
Just avoid any cheap, zero supported, no name devices with flashy advertisements that mean nothing from Amlogic & Rockchip otherwise you can forget about pass-through ever working.

...the no-name boxes are in, or slowly but surely they all will be, in the mix. Passthrough works fine with latest upcoming (02/17) firmware releases and kodi 17. At least that's what it looks like, I just look at the logs.

Word to the wise: as RK is actively developing its own private decoder - it can and will break from public standards - unexpectedly, with any given update. If you want standards compliant hardware, whether it be for audio or video related functions, Rockchip is a poor choice.

Code:
22:41:05.551 T:18446744072286140512  NOTICE: Starting Kodi (17.0 Git:20170201-a10c504). Platform: Android ARM 32-bit
22:41:05.551 T:18446744072286140512  NOTICE: Using Release Kodi x32 build
22:41:05.551 T:18446744072286140512  NOTICE: Kodi compiled Feb  1 2017 by GCC 4.9.0 for Android ARM 32-bit API level 21 (API level 21)
22:41:05.551 T:18446744072286140512  NOTICE: Running on rockchip T051 with Android 5.1.1 API level 22, kernel: Linux ARM 64-bit version 3.10.0
22:41:05.551 T:18446744072286140512  NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
22:41:05.551 T:18446744072286140512  NOTICE: 8 CPU cores available
22:41:05.552 T:18446744072286140512  NOTICE: Product: rk3368_box, Device: rk3368_box, Board: rk30sdk - Manufacturer: rockchip, Brand: Android, Model: T051, Hardware: rk30board

22:41:05.621 T:18446744072286140512   DEBUG: Firmware implements AC3 RAW
22:41:05.621 T:18446744072286140512   DEBUG: Firmware implements EAC3 RAW
22:41:05.622 T:18446744072286140512   DEBUG: AESinkAUDIOTRACK - 32000 supported
22:41:05.623 T:18446744072286140512   DEBUG: AESinkAUDIOTRACK - 44100 supported
22:41:05.624 T:18446744072286140512   DEBUG: AESinkAUDIOTRACK - 48000 supported
22:41:05.625 T:18446744072286140512   DEBUG: AESinkAUDIOTRACK - 96000 supported
22:41:05.625 T:18446744072286140512   DEBUG: AESinkAUDIOTRACK - 192000 supported
22:41:05.626 T:18446744072286140512   DEBUG: AESinkAUDIOTrack: Using IEC PT mode: 10
22:41:05.626 T:18446744072286140512   DEBUG: 8 Channel PT via IEC61937 is supported
22:41:05.626 T:18446744072286140512  NOTICE: Found 1 Lists of Devices
22:41:05.626 T:18446744072286140512  NOTICE: Enumerated AUDIOTRACK devices:
22:41:05.626 T:18446744072286140512  NOTICE:     Device 1
22:41:05.627 T:18446744072286140512  NOTICE:         m_deviceName      : AudioTrack
22:41:05.627 T:18446744072286140512  NOTICE:         m_displayName     : android
22:41:05.627 T:18446744072286140512  NOTICE:         m_displayNameExtra: audiotrack
22:41:05.627 T:18446744072286140512  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
22:41:05.627 T:18446744072286140512  NOTICE:         m_channels        : FL,FR,FC,LFE,BL,BR,SL,SR
22:41:05.627 T:18446744072286140512  NOTICE:         m_sampleRates     : 32000,44100,48000,96000,192000
22:41:05.627 T:18446744072286140512  NOTICE:         m_dataFormats     : AE_FMT_S16LE,AE_FMT_RAW,AE_FMT_RAW
22:41:05.627 T:18446744072286140512  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_DTSHD,STREAM_TYPE_TRUEHD

22:41:31.997 T:18446744072304477320    INFO: CAEStreamParser::SyncTrueHD - TrueHD stream detected (8 channels, 48000Hz)
22:41:31.999 T:18446744072304477320  NOTICE: Creating audio stream (codec id: 86061, channels: 8, sample rate: 48000, pass-through)
22:41:31.999 T:18446744072304477320   DEBUG: CVideoPlayerAudio:: synctype set to 0: clock feedback
22:41:32.000 T:18446744072287574968    INFO: CActiveAESink::OpenSink - initialize sink
22:41:32.000 T:18446744072287574968   DEBUG: CActiveAESink::OpenSink - trying to open device AUDIOTRACK:AudioTrack
22:41:32.000 T:18446744072287574968   DEBUG: CAESinkAUDIOTRACK::Initialize requested: sampleRate 192000; format: AE_FMT_RAW; channels: 8
22:41:32.001 T:18446744072287574968   DEBUG: Updated SampleRate: 32000 Distance: 160000
22:41:32.001 T:18446744072287574968   DEBUG: Updated SampleRate: 48000 Distance: 144000
22:41:32.001 T:18446744072287574968   DEBUG: Updated SampleRate: 96000 Distance: 96000
22:41:32.001 T:18446744072287574968   DEBUG: Updated SampleRate: 192000 Distance: 0
22:41:32.001 T:18446744072287574968  NOTICE: Trying to open: 192000 samplerate 6396 channelMask 10 encoding
22:41:32.003 T:18446744072287574968   DEBUG: Minimum size we need for stream: 35665
22:41:32.003 T:18446744072287574968   DEBUG: Created Audiotrackbuffer with playing time of 23.218750 ms min buffer size: 71330 bytes
22:41:32.004 T:18446744072300234680   DEBUG: CVideoPlayerVideo::CalcDropRequirement - hurry: 0
22:41:32.015 T:18446744072287574968  NOTICE: CAESinkAUDIOTRACK::Initializing with: m_sampleRate: 192000 format: AE_FMT_S16LE (AE) method: IEC (PT) stream-type: STREAM_TYPE_TRUEHD min_buffer_size: 71330 m_frames: 2229 m_frameSize: 16 channels: 8
22:41:32.016 T:18446744072300234680   DEBUG: CVideoPlayerVideo::CalcDropRequirement - hurry: 0
22:41:32.021 T:18446744072287574968   DEBUG: CActiveAESink::OpenSink - AUDIOTRACK Initialized:
22:41:32.021 T:18446744072287574968   DEBUG:   Output Device : android
22:41:32.021 T:18446744072287574968   DEBUG:   Sample Rate   : 192000
22:41:32.022 T:18446744072287574968   DEBUG:   Sample Format : AE_FMT_S16NE
22:41:32.022 T:18446744072287574968   DEBUG:   Channel Count : 8
22:41:32.022 T:18446744072287574968   DEBUG:   Channel Layout: FL,FR,FC,LFE,BL,BR,SL,SR
22:41:32.022 T:18446744072287574968   DEBUG:   Frames        : 2229
22:41:32.022 T:18446744072287574968   DEBUG:   Frame Size    : 16

OTBig Grinisplay.Mode is where RK won't budge, they are intentionally forking old versions of kodi to build against in favor of their dead end RKdecoder which implements their private, non-standards compliant refresh switching, etc.

Sorry for the users that got trapped, but I'm done with RK because of this. Dropping my last release over at freaktab and game over after that.
(2017-02-08, 00:39)Holger Kühn Wrote: Hi folks,

I've just noticed something interesting, regarding the capability to passthrough DTS, but at fist the debug log: The provided log was recorded on the latest 17.1 RC, during this playback no DTS-PT worked, only DD-transcoding. As the Nvidia Shield suports DTS and IEC8..., I found this a bit surprising.

I remembered working DTS-PT on RC4 from 30th January, so I tested this one again ... and no working PT.
While reseting the Audio and display settings I noticed the "Sync Playback to Display" option had been enabled. After disabling this option alone, DTS-PT was working again. So I updated again to 17.1RC, DTS-PT still working fine here.

To cross check this I wanted to reenable the "Sync Playback to Display" option in 17.1 RC, but had not been able to do so, as I couldn't find in anymore ...

I'm going to set up a device this weekend and will check that once again ...


Any hints why this option is missing and able to cause this problem?
Just read its description. It clearly states that it will disable pt. How would you sync to a display without altering audio?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2017-02-08, 07:20)fritsch Wrote:
(2017-02-08, 00:39)Holger Kühn Wrote: Any hints why this option is missing and able to cause this problem?
Just read its description. It clearly states that it will disable pt. How would you sync to a display without altering audio?

Hi fritsch, I see, thanks for pointing out.
Will amlogic s912 supports DTS PT? It comes with new firmware


Sent from my iPhone
The version we had - with the FW directly from AMLogic in latest iteration did it nicely. I cannot tell anything about cheap vendors shipping something ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
  •   
  • 1
  • 31
  • 32
  • 33(current)
  • 34
  • 35
  • 70
  •   



Logout Mark Read Team Forum Stats Members Help
Passthrough Changes with v178
This forum uses Lukasz Tkacz MyBB addons.