justinrh 174 Posted January 24, 2023 Share Posted January 24, 2023 Two issues with a video: 1) transcodes because of a 'direct play error' - What is the error? 2) if you select one of the AC3 5.1 audio tracks, Android TV stats says 5.1 is selected but streaming TrueHD 7.1. (Upmixing to more channels than I have!?) - How/why is it not playing 5.1? a04_5.1_ffmpeg-remux-d3209973-2ce8-423a-a8ea-d1d0a216efd1_1.txta04_embyserver-63810091986.txta04_7.1_ffmpeg-remux-fad7e810-95c5-4835-bd87-fb5796d58781_1.txt Link to comment Share on other sites More sharing options...
Luke 36887 Posted January 24, 2023 Share Posted January 24, 2023 Quote 1) transcodes because of a 'direct play error' - What is the error? Hi, that's hard to say. You'll need to follow the process to submit an in-app log because currently the app does not send this information up to the server. Can you try our standard app and let us know if there's a playback error with that? https://emby.media/emby-for-android.html Thanks. Link to comment Share on other sites More sharing options...
pwhodges 1509 Posted January 24, 2023 Share Posted January 24, 2023 9 hours ago, justinrh said: 2) if you select one of the AC3 5.1 audio tracks, Android TV stats says 5.1 is selected but streaming TrueHD 7.1. Have you got confused by the fact that one of the AC3 tracks is actually also 7.1? Paul Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 24, 2023 Author Share Posted January 24, 2023 12 hours ago, pwhodges said: Have you got confused by the fact that one of the AC3 tracks is actually also 7.1? Nope. I select a 5.1 track. Link to comment Share on other sites More sharing options...
Happy2Play 8145 Posted January 24, 2023 Share Posted January 24, 2023 (edited) Not sure here as I don't know about track selection, but this shows alternate track was never selected or used. 17:29:53.906 Stream #0:0[0x1011]: Video: hevc (Main 10) (HDMV / 0x564D4448), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], Level 153, 23.98 fps, 23.98 tbr, 90k tbn, Start-Time 11.651s 17:29:53.906 Stream #0:1[0x1015]: Video: hevc (Main 10) (HDMV / 0x564D4448), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 1920x1080 [SAR 1:1 DAR 16:9], Level 153, 23.98 fps, 23.98 tbr, 90k tbn, Start-Time 11.651s 17:29:53.906 Stream #0:2[0x1100]: Audio: truehd (AC-3 / 0x332D4341), 48000 Hz, 7.1, s32 (24 bit), Start-Time 11.651s 17:29:53.906 Stream #0:3[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s, Start-Time 11.651s 17:29:53.906 Stream #0:4[0x1101]: Audio: eac3 (AC-3 / 0x332D4341), 48000 Hz, 7.1, fltp, 1664 kb/s, Start-Time 11.651s 17:29:53.906 Stream #0:5[0x1102]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s, Start-Time 11.651s 17:29:53.906 Stream mapping: 17:29:53.906 Stream #0:0 -> #0:0 (copy) 17:29:53.906 Stream #0:2 -> #0:1 (truehd (native) -> ac3 (native)) 7.1 converted to 5.1 -c:v:0 copy -bsf:v:0 hevc_mp4toannexb -c:a:0 ac3 -ab:a:0 384000 -ar:a:0 48000 -ac:a:0 6 Might be container but missing all per track metadata also. Edited January 24, 2023 by Happy2Play Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 24, 2023 Author Share Posted January 24, 2023 (edited) If I understand the stats correctly, Emby is saying the source is 5.1but it is outputting 7.1. Is this a correct interpretation? This pic is from a diff video, but same scenario. Edited January 24, 2023 by justinrh Link to comment Share on other sites More sharing options...
Happy2Play 8145 Posted January 24, 2023 Share Posted January 24, 2023 35 minutes ago, justinrh said: If I understand the stats correctly, Emby is saying the source is 5.1but it is outputting 7.1. Is this a correct interpretation? This pic is from a diff video, but same scenario. No idea as that would contradict the logs provided. Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 24, 2023 Author Share Posted January 24, 2023 Any idea what the error is about? (Maybe audio is a side-effect of the error?) Link to comment Share on other sites More sharing options...
GrimReaper 3226 Posted January 24, 2023 Share Posted January 24, 2023 3 minutes ago, justinrh said: Any idea what the error is about? (Maybe audio is a side-effect of the error?) 22 hours ago, Luke said: Hi, that's hard to say. You'll need to follow the process to submit an in-app log because currently the app does not send this information up to the server. Quote Emby for Android TV/Fire TV and Emby for Roku Logs These apps have the option to send an app log to us electronically. You enter the settings page and turn on the "Debug Options". Now there will be a new option on the user menu at the top of your app home page labelled "Send Log". Quote If you are using Android TV/Fire TV and your problem is with playback, please send the log directly from the playback OSD. There will be an option on the "cog" menu. Reproduce your problem and then use this button to send the log. Then add the following information to your report in the forum: Exactly what you were doing and what happened. Include the name of whatever you played if it is a playback problem The time you sent the log (in Eastern Time please - UTC -5) The name of the Emby user on the local server that was logged in at the time Link to comment Share on other sites More sharing options...
Happy2Play 8145 Posted January 24, 2023 Share Posted January 24, 2023 Devs may see something in client logs as server logs really don't cover any Client "DirectPlayError" as the client does not like something specific to the file. Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 24, 2023 Author Share Posted January 24, 2023 (edited) I sent a log from the app @ 6:49pm ET, user home. Edited January 24, 2023 by justinrh oops, someone asked LOL Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 25, 2023 Author Share Posted January 25, 2023 As for the audio, is it possible that the 5.1 tracks are simply the Atmos metadata? (Don't pound me if that is a totally crazy idea!) Link to comment Share on other sites More sharing options...
ebr 14862 Posted January 25, 2023 Share Posted January 25, 2023 Hi. I think that is just a display error in the stats. The log is telling the truth. How long after switching tracks did you take that screenshot? It could take up to 10 seconds for it to be accurate. There could also be a bug in the display under certain circumstances. Can you try sideloading our standard android app on the same device and see how that compares? https://emby.media/emby-for-android.html Thanks. Link to comment Share on other sites More sharing options...
rbjtech 4170 Posted January 26, 2023 Share Posted January 26, 2023 Graphical view on what the playback is doing direct from the ffmpeg log files. But your screen grab shows source as DTS-HD !? Do you have the right log files ? Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 26, 2023 Author Share Posted January 26, 2023 @rbjtech The pic is exemplary, as stated. You need to grab the 5.1 log (your screenshot looks like you are analyzing the 7.1 log). Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 26, 2023 Author Share Posted January 26, 2023 On 1/25/2023 at 8:49 AM, ebr said: I think that is just a display error in the stats. The log is telling the truth. How long after switching tracks did you take that screenshot? I just tried it again after opening Emby - straight to the second 5.1 track. Here's the log. NOTE: stats say 7.1 in and 7.1 out. (I have a 5.1 system.) It still shows the error; I invoked stats about 10 seconds after starting to play. I know this is a diff answer than before - I think the pieces of my system sometimes gets out of sync, but I don't know for sure. (Maybe it is me with all of my experimentation!) I'm wondering if it is even valid to select a 5.1 track. Any reason it would not be valid? a04_5.1ac3_ffmpeg-remux-c6bb5de6-e102-46d5-b9f7-900442ffdbb5_1.txt Link to comment Share on other sites More sharing options...
Happy2Play 8145 Posted January 26, 2023 Share Posted January 26, 2023 (edited) 22 minutes ago, justinrh said: @rbjtech The pic is exemplary, as stated. You need to grab the 5.1 log (your screenshot looks like you are analyzing the 7.1 log). As already mentioned, no logs show you ever using secondary audio track. It is always the first audio track. Your 5.1 and 7.1 logs are the same. Note all three remux logs convert truehd track. No other track is ever selected. Edited January 26, 2023 by Happy2Play new image Link to comment Share on other sites More sharing options...
justinrh 174 Posted January 26, 2023 Author Share Posted January 26, 2023 Strange. How is it that selecting a certain track is not being played? Is it the Atmos layer? Seems like Emby should understand this and not show it, since it is not useful. (Or maybe it is like the multiple video track DV scenario I had in another post where only hardware can know what to do with the tracks.) So, the mysteries are: it is sending 7.1 audio to a 5.1 system, and a 'direct play error'. Link to comment Share on other sites More sharing options...
Happy2Play 8145 Posted January 26, 2023 Share Posted January 26, 2023 5 minutes ago, justinrh said: Strange. How is it that selecting a certain track is not being played? Is it the Atmos layer? Seems like Emby should understand this and not show it, since it is not useful. (Or maybe it is like the multiple video track DV scenario I had in another post where only hardware can know what to do with the tracks.) So, the mysteries are: it is sending 7.1 audio to a 5.1 system, and a 'direct play error'. Transcoding track 0:2 shouldn't have anything to do with the direct play error. That is just what the server is delivering to the client. For some reason if you are selecting 0:3, 0:4 or 0:5 tracks it is not happening. Your playback logs always use TRUEHD track. 1 Link to comment Share on other sites More sharing options...
Solution rbjtech 4170 Posted January 27, 2023 Solution Share Posted January 27, 2023 (edited) The file above is a raw .m2ts file ripped RAW from a UHD disk. It contains a dual layer dolby vision and as it's from a UHD disk, it also highly like to have a TrueHD track with an AC3 'Core' ( in a similar fashion to DTS-HD having a DTS Core.) MKV/MP4 RIP's of UHD disks usually extract this out - so it's discreetly selectable - but in this case, I *think* it's possible being done dynamically. Quote 16:07:36.461 Stream #0:2 -> #0:1 (truehd (native) -> ac3 (native)) If you look in the log - it says 'native' on both ends of the stream - thus it is not 'converting' the format - it is only extracting it. In summary - everything looks ok. Emby is doing everything expected of it - I think.. If you were to run this m2ts through makemkv - then I suspect it would direct play without any issues - and then you would be able to select and direct play the AC3 5.1 track if you so wished. For info - I extract or create a DD 5.1 track and make it Audio Track #1 and make it Default for ALL my UHD Media. This way, it has the highest possible chance of direct playing on any client without user involvement (incl an ms edge browser) - as the majority of clients simply cannot playback HD Audio due to not supporting those codecs or not having the HDMI bandwidth to do so (ARC issues). Edited January 27, 2023 by rbjtech 1 Link to comment Share on other sites More sharing options...
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