Long Compressing time in Compressor

[Craig Seeman]

I rarely go that low for web. I bottom out at about 800kbps or so. My own provider starts base consumer download at 15,000kbps and others are around 5000kbps down (again this is where they start at bottom tier service). I guess it depends which market one serves. I don’t doubt that many of the typical reviewers may be in somewhat similar situations.

Note this article by Jan Ozer
https://www.streaminglearningcenter.com/articles/youtubes-new-hd-formats.html
YouTube 360p 736kbps
YouTube 480p 1202kbps
YouTube 720p 2023kbps

And the new 1080p is closer to 3000kbps
Vimeo is more or less in the same ballpark too.

So bottom line data rates tend to be much higher than they were a year or two ago.

[Nathan Veer]

It definitely depends on your market. I’m dealing with a daily 28:30min show. While I would hate to think of YouTube being any kinds of standard for online video quality, again, most encoders will get by if you keep your bandwidths that high. Then I have to ask myself, what is compression? It’s the art of maximizing quality at the smallest acceptable file size.

back to the original discussion, multpass makes all the difference in encoding by the very nature of what it is. Checking the video and it’s content before it actually encodes. How can a computer know what data to throw out unless it has seen the footage at least once. Matrox doesn’t do this neither does Elgato and that is why you wont see it used in serious web encoding applications.