Hi! Just wondering if the testers have continued to have good results with the fix and what the timeline might be for getting it to production. I’m in the same boat where I require transcoding for TrueHD and crash predictably. Thanks.
I am expecting it to be released as a hotfix beta release to 1.13.5
At the moment we are going through regression testing. We know the fix resolves the issue.
I’m suffering from similar crashing issues, yesterday was the first time I was monitoring the server at the same time as the crash happened, and saw the memory use of the transcoder. I was going to upload the logs and ask for the dev build, but if it’s about to go out on the Beta I will switch to that channel and wait for a little while. I don’t know if it’s restricted to TrueHD for me, but it was a TrueHD movie that crashed yesterday. I can upload logs if they will help anyone.
Thanks to everyone who’s working on this.
Tested using about 8 4k movies I have. The crash happens consistently on the TrueHD audios. I have one movie that is not using truehd and it will, instead of crashing just buffer at about the same time the others would crash. not sure if that helps at all. Was on public release Version 1.13.5.5332, installed the Beta Version 1.13.6.5339, testing again.
This seems like a pretty obvious bug. Is it safe to assume a temporary workaround is to, if available, manually select another audio stream?
Plex may also want to consider a more sophisticated logging mechanism. For example, any Sonos controller app can gather diagnostic logs from the device, all speakers, submit the logs, and generate a unique code. Given the complexity of host oses, media formats ETC plex should have a mechanism to push a button, set log levels, grab logs, package them up, then send it somewhere.
I myself don’t mind getting way into the debugging weeds, but given that is my day job and money was paid for this product, it is a little insulting being given a homework assignment to get help. Plex may build a better customer base not alienating paying customers.
So I was having this issue while optimizing 4k videos with TrueHD. I’m glad to say that so far I’ve made it further than I was able to before (it was failing at around 20%, now it’s at 30%+ and the memory is stable on the process at around 1.2GB (which is a lot better than it was).
Thanks Plex crew for the fix and for all those that tried the test builds to ensure it fixed it!