Server Version#: v1.26.0.5715-8cf78dab3
Player Version#: 4.76.1
A little stumped on this one… I keep getting playback errors and transcode errors on H264. No problem with H265, What’s even more strange is that it only seems to happen on certain clients. Apple TV 4th Gen, Samsung Tizen (which used to never have problems), and Chrome. My phone (Pixel 6) can play the file just fine. The file plays fine in VLC. I have hardware acceleration on. nvidia RTX4000 GPU. Logs below…
May 03, 2022 12:16:22.544 [20420] INFO - Plex Media Server v1.26.0.5715-8cf78dab3 - Microsoft PC x64 - build: windows-x86 windows - GMT -04:00
May 03, 2022 12:16:22.544 [20420] INFO - Windows version: 10.0 (Build 19044), language en-US
May 03, 2022 12:16:22.545 [20420] INFO - 32 3593 MHz processor(s): Architecture=0, Level=25, Revision=8448 Processor Identifier=AMD64 Family 25 Model 33 Stepping 0, AuthenticAMD
May 03, 2022 12:16:22.545 [20420] INFO - Compiler is - MSVC 1924
May 03, 2022 12:16:22.545 [20420] DEBUG - “C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe”
May 03, 2022 12:16:22.540 [3812] ERROR - [Transcoder] [dca @ 07313a40] Not a valid DCA frame
May 03, 2022 12:16:22.540 [3812] ERROR - [Transcoder] Error while decoding stream #0:1: Invalid data found when processing input
May 03, 2022 12:16:22.540 [3812] ERROR - [Transcoder] [h264 @ 071da580] Invalid NAL unit size (0 > 5635).
May 03, 2022 12:16:22.540 [3812] ERROR - [Transcoder] [h264 @ 071da580] Error splitting the input into NAL units.
That combination of symptoms and log messages probably means the file isn’t structured perfectly. VLC is particularly good at playing badly-formed files.
Here’s the strange thing. I ran a few of the H264 files that wouldn’t play back through TDARR and they are being recognized as H265/not required for transcode. I also tried to handbrake them, but they still show up as H264 in Plex/won’t play.
The files must be corrupt. I’ll try re ripping them to H265 again.
I disagree with the solution on this @Wombat8. I experienced this last night myself on a file that can play OK if I play from start but when I selected the ‘Play’ button, which turned out to be resume, last night Plex crashed.
Below I’ve copied a little bit of my log file from right before the error happened and attached the PlexServer log file for further investigation. @BigWheel , I’ve also included a .xml file (remove the .txt extension) saved from ‘Get Info’ for the file. It will play alright IF I restart from the beginning and so far today I have no had any issues with Aloha Fluffy playing, if I start the file from the beginning or refresh now that the cache is probably current for the file.
Based on what I’ve been able to figure out from Plex log files in the past, my guess would be that Plex saw that the file had been played, but it was played long enough ago that the cache info it had could no longer be resolved and was unable to get out of the state it was in (bad error handling) and crashed. Unfortunately, Plex didn’t then decide to flush that entry from the cache so that the ‘Resume’ button would become ‘Play’ once again.
Jun 17, 2022 21:20:17.203 [1268] DEBUG - Request: [127.0.0.1:60611 (Loopback)] PUT /video/:/transcode/session/4e7bfe204188c6b5-com-plexapp-android/6c7c77d9-05ee-453f-9bfb-493f2b2f6860/progress/stream?index=0&id=0&codec=hevc&type=video (15 live) Signed-in Token (Dzeff) (domu) (range: bytes=0-) (Memory Usage: 272.0 MB/7286.0 MB)
Jun 17, 2022 21:20:17.203 [15808] DEBUG - Completed: [127.0.0.1:60611] 200 PUT /video/:/transcode/session/4e7bfe204188c6b5-com-plexapp-android/6c7c77d9-05ee-453f-9bfb-493f2b2f6860/progress/stream?index=0&id=0&codec=hevc&type=video (15 live) 0ms 195 bytes (pipelined: 5) (range: bytes=0-) (Memory Usage: 272.0 MB/7286.0 MB)
Jun 17, 2022 21:20:17.206 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 611).
Jun 17, 2022 21:20:17.206 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Error splitting the input into NAL units.
Jun 17, 2022 21:20:17.206 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 120).
Jun 17, 2022 21:20:17.207 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Error splitting the input into NAL units.
Jun 17, 2022 21:20:17.207 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 108).
Jun 17, 2022 21:20:17.207 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Error splitting the input into NAL units.
Jun 17, 2022 21:20:17.207 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 110).
Jun 17, 2022 21:20:17.208 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Error splitting the input into NAL units.
Jun 17, 2022 21:20:17.208 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 110).
Jun 17, 2022 21:20:17.208 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Error splitting the input into NAL units.
Jun 17, 2022 21:20:17.208 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 109).
Jun 17, 2022 21:20:17.208 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Error splitting the input into NAL units.
Jun 17, 2022 21:20:17.209 [1268] ERROR - [Transcoder] [h264 @ 02d68640] Invalid NAL unit size (0 > 123).
My files wouldn’t play at all. I would get a transcode error whenever I tried to play them on certain clients (see original post). I couldn’t start/stop playback in Plex. They’d play fine on VLC.
I went through my library, identified the problem files and re-ripped the original media source or grabbed the original file if I had it (I backed up part of my library prior to TDARR H265 conversion) and converted them again to H265 using Handbrake on a newer PC.
I did try a few of the original files in H264 and they played fine.
I had two PC’s combing through my movie libraries when I did the TDARR conversions and the files associated with the older of the two PC’s (2014 i5) were the corrupted ones. I know this because I had this PC pointed to my kids movie library and 90% of them were corrupt.
My best guess is that TDARR on the older PC corrupted the files during conversion somehow.
