By: NoSpammer (no.delete@this.spam.com), November 19, 2020 7:48 am
Room: Moderated Discussions
Chester (lamchester.delete@this.gmil.com) on November 18, 2020 2:06 pm wrote:
> 1000 kbps is way too low for any res today. Youtube isn't exactly the champion of quality. They recommend
> 5 mbps for 720p30, and 8 mbps for 1080p30. You can push a bit lower if you need to save every last
> bit, but I've never liked the results for say, 3.5 mbps w/720p30. 1000 kbps is ridiculous.
I'd say 1000 kbps is quite a good guess for the middle of the range as used in real life. On the lower side real time interactive video is more like a quarter of that figure, and you can get plenty of popular torrents at 2000 kbps. In real life I've seen 1300 kbps HD studio broadcast operating for a year and no one called back to complain about video quality.
Anyways, the bitpacker setting will have a minor influence on the total running time when most of the time will be spent in the unoptimized motion estimation code.
> 1000 kbps is way too low for any res today. Youtube isn't exactly the champion of quality. They recommend
> 5 mbps for 720p30, and 8 mbps for 1080p30. You can push a bit lower if you need to save every last
> bit, but I've never liked the results for say, 3.5 mbps w/720p30. 1000 kbps is ridiculous.
I'd say 1000 kbps is quite a good guess for the middle of the range as used in real life. On the lower side real time interactive video is more like a quarter of that figure, and you can get plenty of popular torrents at 2000 kbps. In real life I've seen 1300 kbps HD studio broadcast operating for a year and no one called back to complain about video quality.
Anyways, the bitpacker setting will have a minor influence on the total running time when most of the time will be spent in the unoptimized motion estimation code.
