And let me raise an eyebrow at TheEndless: you did not equate a bug of player crash&burn to the behavior of "won't play a stream", did you?
No I did not. I was commenting on the fact that the attribute is being used incorrectly,
and if it were working correctly, it should fail to play the stream.Nope. You are doing "mind-reading" here. There is nothing that says what will happen if there is no stream satisfying MaxBandwidth. It seems logical to you it should not play. To me - today (and considering the moon phase) - it seems logical it should play something, even if it does not match. Currently that is undocumented behavior. What it shouldn't do though, is crash and burn.
Two completely different bugs.1 bug and 1 unspecified behavior. They cannot be placed on the same plane - is my objection. By "equate" i meant bringing one to the level of the other. One cannot excuse the other... it's not a balance, not a wash.
In my testing on the local network, setting either / both values made absolutely no difference. The only change was the "dots" on the screen.
it seems logical it should play something
By "equate" i meant bringing one to the level of the other.