[FFmpeg-cvslog] r18533 - trunk/libavcodec/h264.c
Wed Nov 18 09:10:53 CET 2009
On Tue, Nov 17, 2009 at 10:47:05PM +0000, Carl Eugen Hoyos wrote:
> Hi Michael!
> Michael Niedermayer <michaelni <at> gmx.at> writes:
> > > > New Revision: 18533
> > > >
> > > > Log:
> > > > Support broken avc nal encapsulation.
> > > > Fixes issue987.
> > >
> > > This commit broke the sample from issue 1550 (incoming/issue1550)
> > I wont touch roundup until its ML works again
> > I dont think its a good idea to change things on roundup while its in such
> > odd state. Besides it is majorly inconvenient.
> I have absolutely no problem not to look at roundup for some time.
What iam really concerned about is that if the ML is fixed, a large chunk of
changes might be missing of it while i work 99% with the ML, missing changes
would do no good for this ...
things like "hey ive alraedy sent a patch why did you reimplement it" or
"hey ive already awnsered that why do you close due to lack of an awnser!?"
> But how should I know that the ML is broken: I am not subscribed to the list...
> btw: Does the maintainer know that the ML is broken?
i dont know, i assumed someone told luca by now, that probably wasnt wise
from me. Ill CC this mail to him.
> > The extra time it costs me now to fight with its webinterface i can spend
> > reviewing patches that i shoul review and once roundupo has been fixed
> > you can remind me to look at this one ...
> Or I can repeat the (simple) facts:
> incoming/issue1550/ffmpeg.broken.clip.mkv decodes correctly with r18532, does
> not decode at all (=mostly grey, heavy corruption) since r18533.
If i fix it should i update roundup and live with another missing change on
the ML or should i not?
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
He who knows, does not speak. He who speaks, does not know. -- Lao Tsu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-cvslog