hi,
I noticed that my plex server, for certain clients, while transcoding has the following bandwidth usage/behavior.
if the client is one of the following, Plex Web (with Edge or IE 11, others are OK), Android App, the server (Version 0.9.16.6 ) seems to send the transcoded data as fast as possible to the client, in my case its using 12mbps of my internet bandwidth, then idle till it sends again the data to the client.
for other client like Plex Web App on Google Chrome or IOS it seems to be ok. there I have a continuous bandwidth usage of about 4mbps (clients are set to 3mbps)
is this behavior to be expected?
Hope my explanation makes sense
@make77 said:
hi,
I noticed that my plex server, for certain clients, while transcoding has the following bandwidth usage/behavior.
if the client is one of the following, Plex Web (with Edge or IE 11, others are OK), Android App, the server (Version 0.9.16.6 ) seems to send the transcoded data as fast as possible to the client, in my case its using 12mbps of my internet bandwidth, then idle till it sends again the data to the client.
for other client like Plex Web App on Google Chrome or IOS it seems to be ok. there I have a continuous bandwidth usage of about 4mbps (clients are set to 3mbps)
is this behavior to be expected?
Hope my explanation makes sense
It is the expected behaviour for transcoding.
For your other cases, it might directplay the media.
The behaviour depends on the streaming protocol used (HLS or DASH). Some browsers only support one type, other browsers support several. Which one is used depends (among other factors) upon whether you are transcoding or Direct Playing as you’ve found out.
In practice, there should be no big difference in the actual user experience - no matter which one is used.