I don’t know if this will help anyone or what the possible reason for this is but we have been watching Outlander for the past few weeks and the issue above was evident in season 1 and 2 however we have just finished watching season 3 and the issue did not occur once during season 3. All files in the 5 seasons are mkv files at 720p (H.264) and around 500Mb in size. We will start season 4 this evening and will see how it goes.
Having the same issue with Play Next as well as playing the autoplay for the next episode.
Videos are MKV H.246 audio 5.1 DTS, all files above 500MB.
I have other videos MKV H.264 but audio 5.1 ACC and AC3 and those work fine.
I’ve also been having the same issue with my system for months. Would really like to see this finally resolved as it is rather irritating to deal with.
@anon18523487 I’ve reproduced the issue and attached the logs here in case this is helpful. I believe below is the relevant error copied from the Android Client log.
09-13 11:52:06.590 e: [ExoPlayer][EventLogger] playerFailed [eventTime=14.67, mediaPos=0.00, window=0, period=0
com.google.android.exoplayer2.c1: MediaCodecAudioRenderer error, index=3, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [6, 48000]), format_supported=YES
at com.google.android.exoplayer2.g1.handleMessage(SourceFile:43)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: com.google.android.exoplayer2.u2.x$b: AudioTrack init failed 0 Config(48000, 252, 144000)
at com.google.android.exoplayer2.u2.f0$c.b(SourceFile:5)
at com.google.android.exoplayer2.u2.f0.F(SourceFile:2)
at com.google.android.exoplayer2.u2.f0.T(SourceFile:2)
at com.google.android.exoplayer2.u2.f0.f(SourceFile:16)
at com.google.android.exoplayer2.u2.j0.c0(SourceFile:7)
at com.google.android.exoplayer2.z2.t.drainOutputBuffer(SourceFile:32)
at com.google.android.exoplayer2.z2.t.render(SourceFile:16)
at com.google.android.exoplayer2.g1.o(SourceFile:14)
at com.google.android.exoplayer2.g1.handleMessage(SourceFile:25)
... 3 more
Suppressed: com.google.android.exoplayer2.u2.x$b: AudioTrack init failed 0 Config(48000, 252, 144000)
... 12 more
]
09-13 11:52:06.591 e: [Player][ExoPlayer] Playback error detected
09-13 11:52:06.592 i: [Player][Timeline] Handling player error
09-13 11:52:06.593 i: [Player][Timeline] Playback stopped (error: true)
09-13 11:52:06.593 w: [Player][Timeline] player position was negative. Position time will be reported as 0.
09-13 11:52:06.594 e: An exception occurred: com.google.android.exoplayer2.c1: MediaCodecAudioRenderer error, index=3, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [6, 48000]), format_supported=YES
AndroidLog.zip (509.6 KB)
Plex Media Server Logs_2021-09-13_11-54-51.zip (3.8 MB)
2 Likes
I think they’ve just given up.
I’ve stopped paying Plex pass because I can barely use Plex with error and with 4K content not playing smoothly with a memory link.
I almost feel like they’ve gone backwards and now updating the UI while they have simple bugs that cause playback errors. Back to VLC I go.
I am pretty certain that this thread has been abandoned by the Plex team and is no longer reviewed. It may be time to simply start a new thread and hope someone from Plex sees it.
As A test, I challenge anyone from Plex to at least acknowledge they still continue to monitor this thread and still have this as an open issue. It’s simple… Plex please tell us you are continuing to monitor this thread.
2 Likes
I hope not. I have the server on a windows PC and then my two android TV’s (sony) both have this problem
1 Like
Anyone found a solution for this? any related threads that plex support is active in and hasn’t abandoned like this one?
Nope 🤷🏻 Plex just gave up from what I can tell.
Generally ignored problems that Plex no longer pretends to pay attention to will just wither away or accidentally be corrected when they decide to introduce new problems. You can always re introduce discussion about the problem, by posting a new thread about the issue. However, what usually happens is someone (of course well meaning) will point out there is already a thread on the issue and then close the new discussion about the problem before anyone does anything about it. Thus the cycle of report, glance at, ignore, forget continues
1 Like
The issue should be resolved in the next major beta release, v8.28. Will share a build tomorrow with a number of changes that should resolve the problem.
2 Likes
Much appreciated. Look forward to testing 
1 Like
Here’s a build you can try that might shed some light on the up next issue not appear.
This version includes the latest ExoPlayer version, a new and more robust demuxer implementation, improvements to the way track selection is implemented, and new handling for rendering to a surface. During video playback when the UI is visible numerous debug statistics will be displayed on the top. Our network cache still has some issues in this build, as such badly muxed videos may constantly buffer or play with artefacts / robotic sound - iOS video recordings from older iOS builds and AVI files might struggle to play smoothly.
If your still facing issues after trying this build, please can you fetch the client logs from this version, a screenshot of the player with the UI (and debug stats) visible and describe the problems you are experiencing.
4 Likes
New Player seems to be working well, I don’t get the error anymore when skipping to next ep/up next.
It is a bit more resource demanding as I’m sure it’s a beta build. I’ll hang tight for the public release.
Thanks for giving us the build
Longer edit
The best build yet on my smart TV. The interface both inside and outside of video playback has been much quicker. Must be using less memory as I had to make sure I forced closed YouTube to play a remux 4K 60-80GB bluray - no issue now with that beta build.
Any other later beta builds I can test for you?
1 Like
As of Plex MediaServer Version 1.25.2.5319 there is no longer an issue with the Play Next error I was originally receiving.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
