MP4 Videos Hit "Bumps" and Crash on Mi Box S / Web Interface

[TheDetective 0]

I'm running into this issue where some of my MP4 files play to a specific point and then crash, moving the player to the next episode if it is a TV show."Too many errors, giving up appears on screen." I see this behavior on Android TV and in Chrome in the Web Player, but it works fine on my Android phone, Roku, and iPad. It also plays fine if I have Emby use VLC media player, of if I play it in Plex on the Mi Box. The files are all direct playing.

[ebr 16178]

Hi.  Can we please look at a specific example?

 

How to Report a Problem

[TheDetective 0]

Do you want me to turn on debug mode and submit the log for an affected file.

[TheDetective 0]

Hi.  Can we please look at a specific example?

 

How to Report a Problem

 

Here is the debug log file for one of the videos. It always tops playing exactly at 2:44 in the Emby player, but plays through fine in almost everything else. It doesn't look like the video skips in that spot, so I don't know that the problem is.

ffmpeg-directstream-a435f41a-2e9b-443e-93b3-1db3e0a42e37_1.txt

Edited December 15, 2019 by TheDetective

[Luke 42078]

HI, you said this only affects some of your mp4's...are there any common factors among those that are affected?

[TheDetective 0]

HI, you said this only affects some of your mp4's...are there any common factors among those that are affected?

Well, at least the ones that I have been trying to play lately with this issue were all recorded using PlayOn Desktop. However, I've played plenty through Emby that I recorded using this program with no issue.

[TheDetective 0]

I might add that if I play the files through DLNA in VLC they play fine.

[TheDetective 0]

This is very strange. So far I've ran into this issue on at least 5 files. There's alwys one specific spot that makes the Android TV player crash. It's in a different place in each video, but each time I play the video it always chokes in that place. I wonder if it's an exoplayer issue, but Plex is also using exoplayer, and it seems to play them fine. Could the videos be damaged in some way in those specific spots?

Edited December 15, 2019 by TheDetective

[Luke 42078]

Can you follow the instructions at the bottom of here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

to submit an in-app log? Then @@ebr will review. Thanks.

[TheDetective 0]

Can you follow the instructions at the bottom of here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

to submit an in-app log? Then @@ebr will review. Thanks.

Ok. I just sent the log from my Mi Box S after letting one of the files play till it hit the problem spot. I sent it at 5:50 PM Eastern . The file was s01e17 Not for Nothing of Wiseguy. Jonathan was logged into the server and watching.

[TheDetective 0]

I just tried the same file I sent the log from my Mi Box S on my Fire Stick 4K and it plays fine. 

[Luke 42078]

Hi, when you use the web app, what device is that on?

[TheDetective 0]

Hi, when you use the web app, what device is that on?

In Google Chrome on the computer the server is installed on.

[Luke 42078]

Can you attach the server log from the chrome playback attempt? Thanks.

[ebr 16178]

Ok. I just sent the log from my Mi Box S after letting one of the files play till it hit the problem spot. I sent it at 5:50 PM Eastern . The file was s01e17 Not for Nothing of Wiseguy. Jonathan was logged into the server and watching.

 

There is something wrong in the encode that our internal ffmpeg cannot deal with:

12-15 16:49:43.008 12955 19785 E ffmpeg_jni: Error in avcodec_send_packet: Invalid data found when processing input

I think we're going to need to add another fallback that will transcode audio in these situations.

 

Thanks.

 

Also, just for clarification - nothing is "crashing" here.  The player just stops and moves on to the next item.

[TheDetective 0]

There is something wrong in the encode that our internal ffmpeg cannot deal with:

12-15 16:49:43.008 12955 19785 E ffmpeg_jni: Error in avcodec_send_packet: Invalid data found when processing input

I think we're going to need to add another fallback that will transcode audio in these situations.

 

Thanks.

 

Also, just for clarification - nothing is "crashing" here. The player just stops and moves on to the next item.

Thanks for looking into this. I just retried these videos and out of the blue they are now working fine. I can't get any of them to freeze at any of those trouble spots again. Any idea how that could possibly be? As far as I can tell I haven't changed aby settings.

[Luke 42078]

Was there a system update?

[TheDetective 0]

Was there a system update?

I don't think so. It's on 4.3.0.30, which was the version when I set up this server a couple of weeks ago. And there was no update to the Mi Box that I'm aware of.

Edited December 16, 2019 by TheDetective

[ebr 16178]

What about OS, network, anti-virus, etc?

[TheDetective 0]

What about OS, network, anti-virus, etc?

As far as I can tell nothing changed between when I was having the issues and when it just suddenly started working. Something must have changed, but I can't figure out what.

[Luke 42078]

Thanks for the feedback.