Another Windows 64 bit seems to be working, it was in the middle of a queue, after the install it started back up and working on it’s own now with no input from me.
Tested on Ubuntu 24.04.2
6 episodes in a row and the queue is working great ![]()
After bare handed fighting with Write acces commands on proxmox and my lxc, NFS permission fixes, chmod commands, swimming trough random rwxr-xr-x gibberish and fightingg off permission imps. Your build fixed my issue.
Exactly the same pain and process as Edwin above me with Proxmox, but also ChatGPT telling me it’s a feature not a bug =))
This new build works, you’re awesome thank you <3
Edit: it seems that the Pause button does not work, I still have 2 processes running on GPU, one is Plex Media Server which continuously starts a Transcoder process on the GPU.
The server is idle, no clients connected and no other tasks are running except the Conversions (paused) ones.
This bug is better than the original one, let’s keep this one instead ![]()
Just upgraded to “Version 1.41.7.9717” BETA on my Linux box (Ubuntu 24.04.2 LTS)
Queued up 5 episodes of a TV series and only the first one optimized. Same as before. Previous optimizations still show 0 files, even though multiple files had been optimized.
MacOs version seems to be churning through the queue like it always used to! THANK YOU Chris for taking the time to look through this problem and deliver a fix. Much appreciated.
Latest BETA resolved my optimized queuing issue.
I’ll test the latest, but all builds up until 1.41.3.9314 seem to be broken. I had to roll back to this version to get my conversions working again.
Is there a beta fix for the broken optimizer for Nvidia Shield?
still broken on 1.41.4.9463, manually trying 1.41.7.9749
still broken in 1.41.7.9749 (not sure if this fix made in into this build or not.)
I would just manually go back to a previous build. You might have to manually reinstall an older APK
I was having this issue and found the thread through Google. I downloaded Chris’ build and it seems to be working now (Windows, Intel - 64-bit).
Still waiting for Plex and Google to push an update to fix the broken optimizer in Nvidia Shield. Shouldn’t need to learn how to sideload an older version. Plex knows this has been an issue for a bit now.
Fixed it for me on linux arm64 with version 1.41.7. I am using this docker image: 1.41.7
Hey Chris, I’m on server version 1.41.8.9834 on Linux + Docker and noticed optimization is stuck at ‘waiting’. Seems like it’s been stuck like that for a while across multiple PMS versions.
Anything I can try to get this working without having to redo all my optimizations?
I’ve tried the basic turn it off and on, but no luck.
Still having this issue on 1.42.1.10060
Transcode will process several files and then get stuck using “original quality”. Currently sitting at -1% progress (seems fishy) while transcoding a movie at “4.5x speed”.
@APitou there is a known issue (fixed in 1.42.2) when the ‘Maximum simultaneous background video transcode’ setting is set to unlimited. can you try changing that setting to anything else and see if that resolves your issue?
@gravee first off I would 100% immediately update to 1.42.1.10060 to avoid the security vulnerability. second while I don’t remember the nature of the issue off the top of my head its likely you need to clear your queue and start again. I would back up your database, clear the queue, and then try adding 1 to 2 more items to see if they resolve. with the backed up database you can always restore your queue if this does not resolve the matter
No worries on server version, I have it auto updating, so I’m on the latest stable. ![]()
As for the optimize queue, after I made my post, I did exactly what you said, but mostly because I wanted Plex to optimize everything to HEVC again.
I didn’t do a DB backup back then because I don’t care about losing the queue.
In the new queue, about 10% of the items got optimized, but most of them are stuck as ‘waiting’. I remember seeing one of them error out that it can’t write to the disk, but that’s not true because other optimizations worked.
I haven’t done this yet, because I just thought of it, I might need to run a permission fix on my movie share. Some folders might have wrong permissions.
The thing is the queue shouldn’t get stuck if one thing fails to encode.
Let me know if there’s anything specific you want me to test. I set up the new queue many weeks ago, so any logs related to that are lost to the ether.

