Bitrates first, then pixels
Itunes 1080p will also look like crap unless Apple increases the bitrates significantly (and far beyond what most of the internet infrastructure can support).
Better that Apple first increase the bitrates of 720p material to at least DVD bitrates, then move to 1080p when the bitrate can be at least doubled again.
I've found that when compressing video for the web or weak devices, it's often better to reduce the picture size if you're trying for small file sizes.
For example, at low bitrates a 320x240 video double-sized to 640x480 often looks better than a 640x480 video encoded at the same bitrate. The 2X scaling can introduce fewer artifacts than compressing 4X as many pixels into the same stream. (It's not unusual for an embedded video on a website to do this - the HTML for the player window will force a 2X stretch from a smaller input stream.)
Pretty much this. A lot of people are speculating that Apple TV and other DD methods will kill blu ray, but i have to respectfully disagree. While Apple TV's 720p streaming is nice, blu ray still looks noticeably better. Until itunes is able to provide 1080p streaming, Blu ray will always have a place.
Itunes 1080p will also look like crap unless Apple increases the bitrates significantly (and far beyond what most of the internet infrastructure can support).
Better that Apple first increase the bitrates of 720p material to at least DVD bitrates, then move to 1080p when the bitrate can be at least doubled again.
I've found that when compressing video for the web or weak devices, it's often better to reduce the picture size if you're trying for small file sizes.
For example, at low bitrates a 320x240 video double-sized to 640x480 often looks better than a 640x480 video encoded at the same bitrate. The 2X scaling can introduce fewer artifacts than compressing 4X as many pixels into the same stream. (It's not unusual for an embedded video on a website to do this - the HTML for the player window will force a 2X stretch from a smaller input stream.)