@drinehart That was just coincidental. It does the same thing on lan
<Session id="tukjgu31s1l6fz0mf5pgivj7" bandwidth="10500000" location="lan" />
@drinehart That was just coincidental. It does the same thing on lan
<Session id="tukjgu31s1l6fz0mf5pgivj7" bandwidth="10500000" location="lan" />
I think Iām seeing the problem. Iām asking for help identifying further.
It appears to be: If streaming brain is in use, Itās reporting in Kbits/sec.
If true, thatās inconsistent and needs fixed.
Iām still seeing this on Plex Docker version 1.13.5.5332 via Tautulli. I have been having some remote streaming issues latelyā¦could this be messing with the streaming brain?
Iām seeing streaming brain say reqād bandwidth for a 8662 kbps HEVC file, being reported as 39 megabits.
This is a different issue.
Or more precisely, not an issue at all.
The 39 mbps it is reporting is probably a real bitrate āspikeā in your video stream.
It will only have an influence for clients with a very small network input buffer of only 5 mbps.
I want to ensure that this discussion does not die as it is still a problem.
<User id="1" thumb="https://plex.tv/users/<REDACTED>/avatar?c=<REDACTED>" title="<REDACTED>"/>
<Player address="<REDACTED>.3" device="OSX" machineIdentifier="u5s<REDACTED>5qr" model="" platform="Chrome" platformVersion="71.0" product="Plex Web" profile="Web" remotePublicAddress="" state="playing" title="Chrome" vendor="" version="3.77.4" local="1" userID="1"/>
<Session id="nkxi<REDACTED>n9uq" bandwidth="10000000" location="lan"/>
<TranscodeSession key="/transcode/sessions/9txf<REDACTED>5aeif5" throttled="0" complete="0" progress="-1" speed="1" duration="7200000" context="streaming" sourceVideoCodec="mpeg2video" sourceAudioCodec="ac3" videoDecision="transcode" audioDecision="transcode" protocol="dash" container="mp4" videoCodec="h264" audioCodec="aac" audioChannels="2" transcodeHwRequested="1" transcodeHwEncoding="nvenc" transcodeHwEncodingTitle="NVIDIA" timeStamp="1546895011.2153666" maxOffsetAvailable="25.045333333333328" minOffsetAvailable="1"/>
this is as of the current beta build. Its now reporting an even bandwidth="10000000" when it has not done a deepAnalysis or cannot determine the streaming bitrate. To display 0 would be significantly less intrusive to bandwidth metrics than to display 10Gbps. This is further driven by the fact that Plex now has a dashboard which if added would display inaccurately
Hopefully the new dashboard will drive a reconsideration on addressing this bug 
I can confirm this behavior. It happens consistently with all live streams.