On Mon, 26 Jul 2004 13:39:36 +0200, Michael Roitzsch
> > Hmmm... What about Miguel? I see his name in the source. Is there any
> > chance he will pay attention to the issues?
> I am quite sure he will read this thread. Miguel, are you with us?
but i don't know much about direct show api either, i just converted
the c++ classes to plain c for use in xine.
On Sun, 25 Jul 2004 14:18:22 +0700, Peter Gubanov
> 1. A filter may output variable number of samples for one input sample.
> Variable means from 0 to N, N > 1. My fix solvs the problem with 0
> samples, but doesn't solve the problem with 2 or more samples. And
> h264dec may deliver several samples due to frame reordering or handling IDR.
I'm unsure if h264 has anything special here, but usually, at demuxer
level it is possible to say to what frame does a chunk belongs to.
ffmpeg and w32 decoders used to work like that, we gather compressed
data until BUF_FLAG_FRAME_END arrives.
the most notably exception is mpeg2 (demuxer knows nothing about
frames). Thibaut recently added a MPEG-ES parser to our ffmpeg wrapper
so we can find where the frames start/end. can't we do something
similar for h264?
another objection i have for modifying DS_VideoDecoder.c is that these
files were not created by us, but by avifile project. so it would be
nice if they agreed with the changes.