Using the photos feature of Plex is virtually unusable because the server attempts to transcode every picture, resulting in e.g. a 10 second wait for the next picture. I’ve PMS on a Synology DS214 NAS, and client is Apple TV 4k. There’s no need for PMS to transcode the picture (at least if it’s a JPG) - just send it in it’s original size/format and let the client display it natively.
If you could add a feature to PMS so an admin can choose to disable any attempted transcoding of photos when browsing via photo library, that would be a very simple and effective fix. Please, please!
Hi ChuckPa (and others reading this). It’s plain ol’ regular JPG’s as taken on iPhones and other cameras. It’s a problem on the server side, as PMS tries to transcode/resize/process every photo before sending it to the client, resulting in 8+ seconds wait per picture on the client side to view it. Same delays whether attempting to view on latest Apple TV via latest Plex client, or viewing on Windows laptop using web client. And PMS makes my Synology NAS jump to near 100% CPU when viewing on any of those clients.
Just need a simple toggle added to PMS to disable photo transcoding and leave it to the client to resize (and I bet that resize logic is already built into most clients already).
Let’s say I write a web page. I take the time to put in really nice images. I even take the time to tell the browser which size to display the image at. If your browser can’t understand and handle <img src="filename.jpg" alt="Image Title" style="width:500px;height:600px;"> is that a server problem or a browser (app) problem? IMO, that’s an app problem.
If you turn off photo transcoding, any photos in formats other than JPG, which the app can’t display natively (e.g HEIF, IMG, etc) will be blank squares. That’s not correct behavior either.
The solution here is to find out why the clients are not leveraging their native resize ability. true?
