[MPlayer-dev-eng] Updated nailfps filter patches

[Carl Eugen Hoyos]

 <xiphmont <at> xiph.org> writes:


> > My ts test file start with audio and video at 37974. With nailsync, mplayer
> > only shows the first frame repeatedly (perhaps until 37974?), so I don't
> > know if the patch can help with PAFF samples.
> 
> ...or if the demuxer is one of the many that can't report A/V
> presentation timestamps properly.  If the demuxer fudfes the values
> out of laziness ("nothing uses them anyway") the code won't work.
> I'll ad some more debug output so we can see if that's the case.  Is
> there any output to the console?

Yes, it tells that it shows the first frame repeatedly.
(I already removed the hard-to-apply-patch, but I'm sure you can test the
behaviour with any ts sample from samples.mplayerhq.hu)

[...]

> > > [before anyone complains, there is an exit() to kick out on an error
> > > in the audio filter.  There's no way for an audio filter to return a
> > > fatal error like a video filter can].
> >
> > That's clearly a showstopper, because mplayer file -af nailsync -vf nailfps
> > -fps 25 kills the console.
> 
> as in 'is unkillable'?

No, as in "echo off".

>  That's the mplayer sighandler biting you (I
> completely disable it in my builds, it causes me nothing but trouble).
>  The exit() is only called if nailsync is used without nailfps.

I don't think so: Did you try above command line?

Carl Eugen