Too many errors. Giving up.

[gatsu 0]

Hello,

 

I'm not exactly sure which forum to put this problem in. I switched to using a Linux server but it also happened when I was using a Windows Emby server. When I start this show after playing for maybe less than a minute the show would restart a couple times and skip to the next episode and a pop up saying "Too many errors. Giving up." will show.

 

This doesn't happen with any other shows or movies that I have. It only happens to this series.

 

This happens when I use the Emby app on my TV but if I use my ShieldTV in another room I don't have this problem.

 

Thanks for the help.

 

embyserver.txt

ffmpeg-transcode-d92ab304-51de-4796-827c-07a16e39ca91_1.txt

[ebr 16169]

That message indicates that the app tried to play this movie every way possible and none of them worked.

 

If you turn off the subtitles, does it play?

[gatsu 0]

I turned off the subtitles through the Emby app.

 

I still get "Too many errors. Giving up."

 

Should I remove the embedded subtitles from the video?

embyserver.txt

ffmpeg-directstream-6e98e6ab-7684-447c-a1b5-82ec329f62f1_1.txt

ffmpeg-transcode-7f39fb56-3a00-40c5-b969-ac3cd8971b95_1.txt

ffmpeg-transcode-db55a163-7271-4f2a-8ccb-440c8b50787f_1.txt

[ebr 16169]

Can you please follow the instructions for sending a log from the app?  Play this item until it fails and then send the log immediately after.

 

Thanks.

[aja07 20]

I get this problem on my Mibox for recorded TV (SBS Australia) as the recording includes English (DVB-Teletext)

 

I have to to switch the subtitles to None in the ATV app for the episode before it will play.

Edited November 21, 2019 by aja07

[Luke 42077]

I get this problem on my Mibox for recorded TV (SBS Australia) as the recording includes English (DVB_TELETEXT) 

 

I have to to switch the subtitles to None in the ATV app for the episode before it will play.

 

 

@@aja07 can we please look at an example? Thanks !

[aja07 20]

@@aja07 can we please look at an example? Thanks !

Hi  @@Luke , can you get this ?

 

https://1drv.ms/u/s!At0OMBUBX5hliSLuDMfEcX7AZG8W?e=a9MfN9

Edited November 21, 2019 by aja07

[gatsu 0]

Can you please follow the instructions for sending a log from the app?  Play this item until it fails and then send the log immediately after.

 

Thanks.

 

I just sent the log.

 

Running Man Episode 440

Around 9:41 AM

Local User logged in a steve.

 

Thanks for the help.

[ebr 16169]

Looks like a problem with the audio track and, since it is already 2 channel AAC, we never try to convert it to anything else.

11-21 09:42:19.839 17785 18297 E ffmpeg_jni: Error in avcodec_receive_frame: Invalid data found when processing input
11-21 09:42:19.850 17785 18275 E ExoPlayerImplInternal: Playback error.
11-21 09:42:19.850 17785 18275 E ExoPlayerImplInternal: com.google.android.exoplayer2.ExoPlaybackException: com.google.android.exoplayer2.ext.ffmpeg.FfmpegDecoderException: Unexpected decode error

[Richard Branches 330]

By the way, could you please add that "too many errors, giving up" message to onesky? I've never seen it there. Thanks.

[gatsu 0]

 

Looks like a problem with the audio track and, since it is already 2 channel AAC, we never try to convert it to anything else.

11-21 09:42:19.839 17785 18297 E ffmpeg_jni: Error in avcodec_receive_frame: Invalid data found when processing input
11-21 09:42:19.850 17785 18275 E ExoPlayerImplInternal: Playback error.
11-21 09:42:19.850 17785 18275 E ExoPlayerImplInternal: com.google.android.exoplayer2.ExoPlaybackException: com.google.android.exoplayer2.ext.ffmpeg.FfmpegDecoderException: Unexpected decode error

 

Do you think it's because my TV can't handle audio track? It works on ShieldTV and other AAC 2.0 audio tracks works on my TV, but comparing two of the same episode with different audio tracks. The one with an audio track of 192kb/s and 48Hz gives errors while the one with an audio track of 253kb/s and 44.1Hz works. I'm not sure if that difference will cause the errors to occur.

 

But thanks for finding out where the error is occurring.

[ebr 16169]

It is actually ffmpeg having trouble with decoding it...

[Luke 42077]

Is this consistent at the same spot for the same file?

[aja07 20]

For the file I posted (see link above) it happens immediately on mibox ATV.  Emby Theatre however, can play it.

[Luke 42077]

Does it happen with any other files?

[gatsu 0]

Is this consistent at the same spot for the same file?

 

It happens to me on the same spot on the same file and on other files that have the same audio files with 192kb/s and 48Hz. I'm not sure if that is the reason it causes the "Too many errors. Giving up" prompt and to cause problems with ffmpeg to decoding it.

[Luke 42077]

We'll see what @@ebr thinks. Thanks.

[aja07 20]

It happens to me on any tv recording file that has English (DVB-TELETEXT) set. Have to switch it off for the recording to play.  Its not an issue for me as I would have switched it off anyway as I don't need the teletext, but for some reason most if not all shows recorded from SBS Australia channel has this teletext set.

[ebr 16169]

It happens to me on any tv recording file that has English (DVB-TELETEXT) set. Have to switch it off for the recording to play.  Its not an issue for me as I would have switched it off anyway as I don't need the teletext, but for some reason most if not all shows recorded from SBS Australia channel has this teletext set.

 

This is more than likely some other issue.  Can you please open a new thread with details?

 

Thanks.

[ebr 16169]

Not sure it will make a difference, but can you try the beta version of the app?

[gatsu 0]

Not sure it will make a difference, but can you try the beta version of the app?

I tried it, still the same.

 

Do you think the server update 4.3.0.26 might help? There is an ffmpeg 4.3 update in it, but I have to wait for arch update.

[ebr 16169]

Do you think the server update 4.3.0.26 might help? There is an ffmpeg 4.3 update in it, but I have to wait for arch update.

 

No, the server won't make a difference here.  It is on the app side that the audio is unable to be decoded.  We will probably have to add another fallback that forces audio to be converted by the server.

[markbrown3000 0]

I was having the same issue. I changed it to an external player, I used VLC, and it started working fine. Haven't had any issues since. 

[Luke 42077]

Hi there, can we please look at an example? Thanks.