I have been getting this massage Conversion failed. The transcoder exited due to an error.
on my windows 10 64x chrome and Samsung TV
but not on my android galaxy S8
PLEX Server ver. 1.13.3.5223
i couldn’t upload the log so i put it on mega
1 Like
I was seeing the same error after updating to 1.13.4.5251 today.
I had to download the latest installer, repair the installation, and restart to get streams working properly again.
Well perhaps not, still happening, though not as often…
I also use a W10 host
Analyzing the media files that are getting these transcoder errors seems to fix those files.
Same problem here Plex 1.13.4.5251
nope, i did and im still getting this error.
Please follow this thread instead so it is all in one place
It is unfortunately NOT A SOLUTION but hopefully we will get an answer there
Thanks
Had the same. Server 2016 Essentials. Downgraded PMS at first but did not resolve anything. Did spot that Windows had an update Tuesday. Removed KB4338814 https://support.microsoft.com/da-dk/help/4338814/windows-10-update-kb4338814 and it seems to run fine for an hour now.
It seems like KB4338819 would be the Windows 10 version.
Unfortunately this might not be the right answer, as discussed in several forums over the last few years, this has been happening a lot, so an update from just last Tuesday cannot be the only culprit. Plus my pc does not have that update yet it is showing the same problems. And if you look at other forums people are having the same issue on linux, server 2016 and even windows 7. So although it might work for you, and maybe someone else it is is not an definitive answer, but every little help.
Notice: KB4345421 update fixed the problem on my Windows 10 Pro 64Bit machine.
I am completely up to date as of 8/3/18 and still getting this error frequiently, I’ve attached logs if anyone is able to assist. I used to think its tautulli but even with it closed I still get the error, thanks for anyone’s help!
Having the same issue, if someone from Plex wants my logs I have about 4 days of constant transcode issues. Verbose logging just enabled and on 1.13.5.5291.
I am guessing you are not up to date. Have you checked your Windows Update to verify you have the two patches that Microsoft released to fix problems?
Please verify you have the following Windows Updates installed:
July 10, 2018 - KB4338819 (OS Build 17134.165) - which introduced the issue
July 16, 2018 - KB4345421 (OS Build 17134.167) - First fix
July 24, 2018 - KB4340917 (OS Build 17134.191) - Second update Microsoft released fixing other issues
If you do not have the KB4345421 update you could still be having these issues.
Please make sure these updates are installed and reboot after each installation to ensure the update completely finishes installing.
Seeing these lines in your logs posted makes me question whether the correct patches have been installed
Aug 03, 2018 21:30:23.822 [29052] ERROR - [Transcoder] [stream_segment,ssegment @ 0405c340] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/d8demd2fafldte29ipkw84we/a534f9e8-c3e0-4332-8eb5-c9289338b766/seglist'
Aug 03, 2018 21:30:23.825 [23108] ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
Aug 03, 2018 21:30:23.853 [29052] ERROR - [Transcoder] Error writing trailer of media-%05d.ts: Invalid argument
Also please turn off the Verbose logging. That option should only be turned on when requested by a Plex Employee during issue debugging. Verbose adds extra logging information that is not normally needed and can cause your logs to roll over way too quickly.
1 Like
The error is generic. Hundreds of different issues may give rise to this error. So same error reported over long time does not mean same issue.
Since 10th July hundreds of users were affected by a bad windows update which Microsoft fixed 6 days later however not all users got the fix automatically see post in the topic where most users reported the issue
In that thread there are a number of posts that show how one can establish if it was the issue caused by the windows update
The development build seems to work for me! 5 tests, 4 successfull played till the end. One stopped loading at 1h but i think that was a different issue. Tried with different 4k movies, all of those seem to work.
Just to clarify for anyone else - this was specifically for a memory leak issue in the transcoder with TrueHD audio
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
