frk1337 4 Posted February 3, 2020 Posted February 3, 2020 (edited) I started using Emby some days ago and so far love it! But I encountered problems when playing DTS-HD streams. Audio-passthrough to my receiver works for some time (~10-20s), then suddenly the picture freezes and my receiver shows the input signal switched from DTS:X to "ANALOG". After 10s this will go away and DTS:X starts to appear again though with a noticeable av-desync. No problems occur when playing Dolby Atmos/EAC3/AC3/Opus files. The problem does not occur (same file!) with Plex or Emby for Kodi. With those passthrough works without any problem. Disabling DTS passthrough leads to Emby transcoding the DTS-HD Master or DTS:X to ac3 but those start to glitch aswell. I then tested a backup audio stream (DTS audio encoded in Opus) as fallback. Even when I used this audio line (file had two audio lines; 0: DTS-HD, 1: Opus) it bugged and glitched. My suspicion: when DTS is available in the container something about the android tv app can't handle it. Device: Nvidia Shield 2019 Receiver: Onyko TX-NR686 App-Version: Latest beta from Google Play Store Logfile attached (ip adresses replaced with 0.0.0.0). embyserver.txt Edited February 3, 2020 by frk1337
frk1337 4 Posted February 3, 2020 Author Posted February 3, 2020 To rule out a corrupt file I tried a second file from a totally different source (one was DTS-HD 5.1 the other was DTS:X 7.1). Both showed exactly the same buggy behaviour.
ebr 16184 Posted February 3, 2020 Posted February 3, 2020 App-Version: Latest beta from Google Play Store Hi. As we note in our How to Report a Problem instructions - that doesn't tell us for sure what version you are using (maybe your device missed an update). Please provide the version number shown on the settings page for the app. Also, please cause this issue by playing just long enough for it to happen and then send a log from the app. Thanks.
frk1337 4 Posted February 3, 2020 Author Posted February 3, 2020 (edited) I just used the debug feature on the app to send you logs. Time: 1580740456 (15:34 local german time; UTC -5 = 09:34) Local user: max App version: Version 1.7.78g Registered Server version: 4.3.1.0 Edited February 3, 2020 by frk1337
ebr 16184 Posted February 3, 2020 Posted February 3, 2020 The DTS part may be a red herring. I don't see any problems here except what looks like some buffering happening - which could cause your receiver to go in and out of bitstreaming mode during the pause. What is the bitrate of the item in question? What are all the connections involved?
frk1337 4 Posted February 3, 2020 Author Posted February 3, 2020 General Unique ID : 187105313867094030857354210258869389809 (0x8CC32C344D3D5802A1645DAF1A3989F1) Complete name : XXX Format : Matroska Format version : Version 4 File size : 47.1 GiB Duration : 2 h 10 min Overall bit rate mode : Variable Overall bit rate : 51.7 Mb/s Encoded date : UTC 2020-02-03 04:45:30 Writing application : mkvmerge v43.0.0 ('The Quartermaster') 64-bit Writing library : libebml v1.3.10 + libmatroska v1.5.2 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5.1@High HDR format : SMPTE ST 2086, HDR10 compatible Codec ID : V_MPEGH/ISO/HEVC Duration : 2 h 10 min Bit rate : 46.7 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 (Type 2) Bit depth : 10 bits Bits/(Pixel*Frame) : 0.235 Stream size : 42.5 GiB (90%) Default : Yes Forced : No Color range : Limited Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : BT.2020 non-constant Mastering display color primaries : Display P3 Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2 Maximum Content Light Level : 500 cd/m2 Maximum Frame-Average Light Level : 200 cd/m2 Audio #1 ID : 2 Format : DTS XLL X Format/Info : Digital Theater Systems Commercial name : DTS-HD Master Audio Codec ID : A_DTS Duration : 2 h 10 min Bit rate mode : Variable Bit rate : 3 787 kb/s Channel(s) : 8 channels Channel(s)_Original : Object Based ChannelLayout_Original : Object Based Sampling rate : 48.0 kHz Frame rate : 93.750 FPS (512 SPF) Bit depth : 24 bits Stream size : 3.45 GiB (7%) Language : English Default : Yes Forced : No Connnection is 5GHz WLAN with net bandwith ~600-800mbit/s. First I thought about a buffering issue too. Doesn't explain why the sound get's asynced when it resumes. Why can Plex and Emby @ Kodi play it without any issues? Movies with 70mb/s and Atmos play fine through the app too. So I think the connection is stable enough.
ebr 16184 Posted February 3, 2020 Posted February 3, 2020 It could be the extremely high audio bitrate coupled with the high video bitrate. This is showing 3.7Mb/s for the audio where most HD audio is only 1.5.
frk1337 4 Posted February 3, 2020 Author Posted February 3, 2020 (edited) Most Atmos streams have higher bitrate, e.g. (video has 45mb/s aswell): Audio #1 ID : 3 Format : MLP FBA 16-ch Format/Info : Meridian Lossless Packing FBA with 16-channel presentation Commercial name : Dolby TrueHD with Dolby Atmos Codec ID : A_TRUEHD Duration : 2 h 1 min Bit rate mode : Variable Bit rate : 5 013 kb/s Channel(s) : 8 channels Channel layout : L R C LFE Ls Rs Lb Rb Sampling rate : 48.0 kHz Frame rate : 1 200.000 FPS (40 SPF) Compression mode : Lossless Stream size : 4.30 GiB (8%) Title : xxxx Language : English Default : Yes Forced : No Number of dynamic objects : 13 Bed channel count : 1 channel Bed channel configuration : LFE Then again, if it was bandwith related: why can plex and Emby for Kodi handle it without any problems? Edited February 3, 2020 by frk1337
ebr 16184 Posted February 3, 2020 Posted February 3, 2020 Most Atmos streams have higher bitrate, e.g. (video has 45mb/s aswell): Audio #1 ID : 3 Format : MLP FBA 16-ch Format/Info : Meridian Lossless Packing FBA with 16-channel presentation Commercial name : Dolby TrueHD with Dolby Atmos Codec ID : A_TRUEHD Duration : 2 h 1 min Bit rate mode : Variable Bit rate : 5 013 kb/s Channel(s) : 8 channels Channel layout : L R C LFE Ls Rs Lb Rb Sampling rate : 48.0 kHz Frame rate : 1 200.000 FPS (40 SPF) Compression mode : Lossless Stream size : 4.30 GiB (8%) Title : xxxx Language : English Default : Yes Forced : No Number of dynamic objects : 13 Bed channel count : 1 channel Bed channel configuration : LFE Then again, if it was bandwith related: why can plex and Emby for Kodi handle it without any problems? Because everyone is probably using a different method of passing the audio stream - that is definitely the case with Kodi.
frk1337 4 Posted February 3, 2020 Author Posted February 3, 2020 (edited) Okay forget everything I said, it just happend the first time with an Atmos file. So you seem to be correct about the buffering problem. I tried upping the Buffer to large in the options, that increased the time until the first occurance but it still happens. Hmm. Buffer too small? As said, never had problems with Kodi or Plex so the bandwith itself seems to be sufficient. Edited February 3, 2020 by frk1337
Solution frk1337 4 Posted February 3, 2020 Author Solution Posted February 3, 2020 Clearing data/cache of the app fixed all issues. I guess the app was "clogged" somehow... 1 1
ebr 16184 Posted February 3, 2020 Posted February 3, 2020 Well, that's very interesting. Thanks for reporting!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now