Reply to thread

Message

<blockquote data-quote="Lehmden" data-source="post: 1075453" data-attributes="member: 109222">Hi.&nbsp;Normally HDTV is coded in h264 so there should'nt be a difference at all. And this has nothing to do with mpeg2 vs h264. it's the &quot;i&quot; vs the &quot;p&quot; that makes the difference. &quot;i&quot; means &quot;Interlaced&quot; and &quot;p&quot; means progressive. This interlaced video only is half a video. The stations broadcast only every second line per frame and the player (-hardware) needs to add the missing lines. When interlaced the first frame (picture) only has line 1, 3, 5, 7, 9,... and the second one has only lines 2,4,6,8,... the third one contains line 1,3,5,7,... again, the fourth one has line 2,4,6,8,... and so on. From every two half pictures the player has to render two full pictures. This eats lots and lots of hardware especially GPU power. The stations are broadcasting in 1080i to save 50% bandwidth and money. So the load is moved to the customer...</blockquote>

[QUOTE="Lehmden, post: 1075453, member: 109222"] Hi. Normally HDTV is coded in h264 so there should'nt be a difference at all. And this has nothing to do with mpeg2 vs h264. it's the "i" vs the "p" that makes the difference. "i" means "Interlaced" and "p" means progressive. This interlaced video only is half a video. The stations broadcast only every second line per frame and the player (-hardware) needs to add the missing lines. When interlaced the first frame (picture) only has line 1, 3, 5, 7, 9,... and the second one has only lines 2,4,6,8,... the third one contains line 1,3,5,7,... again, the fourth one has line 2,4,6,8,... and so on. From every two half pictures the player has to render two full pictures. This eats lots and lots of hardware especially GPU power. The stations are broadcasting in 1080i to save 50% bandwidth and money. So the load is moved to the customer... [/QUOTE]

Verification