When looking at the server log, What can we look for to try to pin point issues with buffering for example ? like the CPU or reason for transcode etc … ? can someone clarify what were looking for ?
thanks
When looking at the server log, What can we look for to try to pin point issues with buffering for example ? like the CPU or reason for transcode etc … ? can someone clarify what were looking for ?
thanks
here is a quick example
My server is set on limit remote stream to 12mbps the Roku is set to 12 also
STREAM and SOURCE
if the server was set to 12mbit and so was her roku it should have direct played
Source was 9468 kbps
it transcoded to 11428kbps
it was a mp4 container but it’s transcoding to MPEGTS Witch i have no idea what that is ( this is on Tautulli ) if i check on plex web it would say Transcoding H264 to H264
it also did the audio AAC to AAC no idea why it is transcoding
so if i wanted to check the server log what am i looking for ?
thanks !
@TwistedEndz said:
When looking at the server log, What can we look for to try to pin point issues with buffering for example ? like the CPU or reason for transcode etc … ? can someone clarify what were looking for ?thanks
speed= and check for the trend. Speed is an instantaneous report but if you observe hovering too close to 1.0 it means you’re marginal as 1.0 = 1x realtime.@ChuckPA is this same for windows / Android ?
im not seeing speed= and MDE when doing a search with notepad+ on plexmedia server logs or any of the logs
All Plex Media Server.*.log files