Open ojones-sage opened 6 years ago
have you posted a question on the forum. I recall an issue some time ago in the server part where sagetv calculates this #. I thought it was fixed. Either way, it's not calculated in the miniclient, it's calculated by the server.
Thanks Stuckless - I was wondering if that was the case. I'm an amateur at java and when I was looking at the server side code it looked like it was looking for a bandwidth report from the UI first (which I assumed was the client but likely a bad guess) before it started to send data to determine an estimate. I was assuming the client was able to "report" its speed to the server but looks like I have it backwards. I will post a comment on the server side github.
I'm also looking for hints about where in the code the server/client "sets" the streaming resolution (if forced to transcode) in order to get away from 352x240. Is that also a server side question (part of the old placeshifter code maybe)?
I am not sure if this is more of a server or client issue but on fast wan links (Cable) that have asymmetric upload and download bandwidth (or significant ping times) the bandwidth isn't calculating correctly resulting in a 150Mbps / 25Mbps client side link detecting at <10Mbps and being forced to transcode.
Is there anyway to provide an override in the settings to "fake" or force the reported bandwidth? I've tested the connection point to point and I can move raw MPEG files over the hardware VPN at wire speed (nearly 150Mbps).