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

Alex Izvorski aizvorski at gmail.com
Tue Jun 5 04:10:00 CEST 2007


On Sat, 2007-06-02 at 22:08 -0600, Loren Merritt wrote:
> On Sat, 2 Jun 2007, Kurosu wrote:
> 
> > In order to encode several sequences together and then split them on 
> > particular frames, forcing those frames to be coded as IDR seemed to me to be 
> > a solution.
> >
> > That's what the patch does: implement a --intras switch for cli binary, and 
> > necessary interface in the structures for programmatical configuration. This 
> > follows how --zones is implemented.
> 
> IMO it would be simpler to add a parameter to --zones. It doesn't have to 
> be limited to setting qp or bitrate.
> 
> --Loren Merritt

Indeed.  I would suggest actually keeping this out of the codec core
(and x264_t).  The front-end (x264.c) can maintain an array of complete
settings for certain frame ranges and change settings with an
appropriate call to x264_encoder_reconfig() when appropriate.  This way,
we could for example define frame ranges with almost arbitrary settings
(limited only by what reconfig can handle).  It may be easier to
configure this by means of a config file than commandline, but even with
a commandline you could have a --range=<start>,<end> followed by any
valid x264 commandline switches (until the next --range option) which
would apply to those frames only.   There could still be an --intras
switch, but --intras=100,110 would be a special case of --range=100,100
--frametype=I --range=110,110 --frametype=I  etc.  Or call --range
--zone if you prefer.

I really do like the functionality in the patch, it is only a question
of how to best implement it.  Ideally, in a very general way ;)

Thoughts?
--Alex


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



More information about the x264-devel mailing list