[MPlayer-dev-eng] Lots of stuff for NUT

[Michael Niedermayer]

Hi

On Thu, Jan 12, 2006 at 09:27:52PM +0200, Oded Shimon wrote:
> On Thu, Jan 12, 2006 at 08:06:47PM +0100, Michael Niedermayer wrote:
> > Hi
> > 
> > On Wed, Jan 11, 2006 at 08:59:25PM +0200, Oded Shimon wrote:
> > [...]
> > > > write_sp(){
> > > > 1. find the most recent keyframes in each stream which have pts<=current dts
> > > > 2. find the corresponding syncpoints for these keyframes and set the back_ptrs
> > > > 3. find the first keyframe after each of these syncpoints and set sp_pts to
> > > > their maximum pts
> > > > }
> > > > 
> > > > and when to write it:
> > > > "if writing the next frame would cause the syncpoint distance to be >t then
> > > > write a syncpoint before the next frame"
> > > > together with:
> > > > "if any back_ptr would change by >T then write a syncpoint"
> > > > work?
> > > > or does this fail in some silly case
> > > 
> > > I think you convinced me with "if any back_ptr would change by >T then 
> > > write a syncpoint".
> > > 
> > > I revisited the old situation where this idea broke, and this rule solves 
> > > it.
> > > 
> > > The idea is still complicated in the sense that it's not fully 
> > > straightforward to write a seeker, and also that you need to remember 
> > > several keyframes per stream (i.e., manage a buffer), not just store some 
> > > single variables. I think you'll also need to store all/some syncpoints... 
> > > But you needed that anyway for the index.
> > > 
> > > There's one part I still have problem with - what is "current_dts"?... 
> > > unfortunately, dts is not monotone across streams... you can't just grab 
> > > the dts of the last frame put in the file, because you could end up with 
> > > non monotone syncpoint ts.
> > 
> > well choosing dts is easy, do strict dts ordering
> 
> I thought we discussed this... :)
> Didn't we finally decide on loose MN rule, not strict dts?

iam fine with either but in that case here dts ordering is easier ...


[...]

-- 
Michael