[x264-devel] Re: [PATCH] Forcing frame coding as IDR

[Jingyi Hu]

It all depend on the clips and output frame location:
1)If all clips contents are not all related, the separate encoding will make 
more efficient in coding mv search, reference frame search etc.

2)If you do not have a IDR interval parameter setting and clips scene 
changes a little, you will not have a IDR for a while. In this case, it will 
big offset between IDR and require frame #.

3)Usually end user do not have accurate idea about exact frame #. If you 
force set the frame # become IDR, it will increase stream data overhead.

4)The best approach to give the time duration or output bitstream size. Let 
program determine which frame numbers are and carry the extract output.

Thanks.

Jingyi Hu


>From: Alex Izvorski <aizvorski at gmail.com>
>Reply-To: x264-devel at videolan.org
>To: x264-devel at videolan.org
>Subject: [x264-devel] Re: [PATCH] Forcing frame coding as IDR
>Date: Mon, 04 Jun 2007 19:19:19 -0700
>
>On Sun, 2007-06-03 at 16:53 -0400, Jingyi Hu wrote:
> > If you want to split them by particular frames, you real need encoding 
>as
> > independent output bit stream data. So it can keep consist bitrate and
> > quality.
> >
> > JIngyi Hu
>
>Why would you say they have to be encoded separately?  If you cut a
>stream produced with x264 just before the PPS/SPS NALs which come before
>an IDR frame, each part will be a perfectly valid stream on its own.  It
>may not exactly meet vbv constraints, but it will be close.  There are a
>number of applications where this is valuable.
>
>Regards,
>--Alex
>
>
>--
>This is the x264-devel mailing-list
>To unsubscribe, go to: http://developers.videolan.org/lists.html
>

_________________________________________________________________
Get a preview of Live Earth, the hottest event this summer - only on MSN 
http://liveearth.msn.com?source=msntaglineliveearthhm

-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html