Jump to content

'direct play error' for this file, audio stream info wrong


justinrh
 Share

Recommended Posts

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

image.png.bc01b3a0e6fc5527cc9a6a94ebd6c937.png

Link to comment
Share on other sites

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?

 

Link to comment
Share on other sites

pwhodges
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

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

Happy2Play

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 by Happy2Play
Link to comment
Share on other sites

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.

IMG_2023-01-20_18-11-52.jpeg

Edited by justinrh
Link to comment
Share on other sites

Happy2Play
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.

IMG_2023-01-20_18-11-52.jpeg

No idea as that would contradict the logs provided.

Link to comment
Share on other sites

GrimReaper
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

Happy2Play

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

I sent a log from the app @ 6:49pm ET, user home.

Edited by justinrh
oops, someone asked LOL
Link to comment
Share on other sites

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

rbjtech

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 ?

image.thumb.png.90472f119f8241b84eebfe97ab27c694.png

Link to comment
Share on other sites

justinrh

@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

justinrh
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

Happy2Play
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.

 

image.thumb.png.76ef81226cb3cbde9844abc39fc89f59.png

Note all three remux logs convert truehd track.  No other track is ever selected.

Edited by Happy2Play
new image
Link to comment
Share on other sites

justinrh

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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...