A good discussion of this is here look at the “Bitrates and How They Matter” section. That’s the concept, but it isn’t actually quite as simple as that since recordings almost always have a variable bitrate, while we looked at the total average bitrate in the example above. This could also happen if you have set an overall remote connection speed limit and have enough remote connections that you are hitting that limit. You can’t stuff 3.5 Mbps through a 3.0 Mbps limit, so Plex is going to see that and transcode to a lower bitrate on the fly when that file is played to obey the 3.0 Mbps limit you set. Let’s say you have a file that is recorded at 3.5 Mbps (the average amount of data stored per second) and you have limited your remote connections to 3.0 Mbps each. Yes, you are correct that limiting bandwidth for remote clients can force transcoding. Or… the connection isn’t fast enough somewhere to stream a higher bitrate, so it has to transcode… If you have access to the Plex server you can check these under Settings -> Remote Access. This could also be because the server you are streaming from has been intentionally set to limit the bitrate of each remote stream, or has been set to limit the total bitrate for remote streams and the server is maxing out. Maximum H.264 level - 4.1 has always been good for what I play - but could vary depending on how this file is encoded.Direct Play - Force if you want direct play forced, or auto if you want it.Remote Quality - If it is set under the bitrate of the original this could cause it to transcode.Possibly video settings in the Plex app on the Roku… I don’t have a setup of a Roku streaming remote, but take a look at: If so, the question is why it is playing at 3 Mbps. It is playing at 3 Mbps, which at 3 Mbps can be 720p, but could be at a lower bitrate than the original file so it has to transcode. I see this is a remote connection, so off the top of my head it could be a couple things.
0 kommentar(er)
