[Ffmpeg-devel] Re: [PATCH] DVCPRO50 support
Fri Mar 3 01:57:23 CET 2006
The only issue with DV in MOV files is that currently the dvvideo
avcodec does not fill in the DV metadata (DIF block headers, etc) or
audio. It leaves that job to the dvvideo avformat wrapper - which
applies to raw DV streams, but not MOV or AVI.
The resulting MOV files play in Quicktime Player, but they will not
work when output via FireWire to external video hardware, since FCP
just sends the raw DV data. It does not insert the headers or the
audio; it just assumes they are already valid. (a work-around is to
load the clip into FCP or Quicktime Player and then export it, which
will re-generate all the necessary metadata).
It seems like a proper fix will require a major re-architecture of the
DV avcodec and avformat, and possibly some modifications of the MOV
and AVI wrappers as well. This is a low priority for me because I
don't need full MOV support.
With regards to Baptiste's question of "why not a different codec?"-
DV25 and DV50 share so much code (probably 95%) that I don't see a
reason to split them up. In the future I may add DV100 (DVCPRO HD) to
the mix as well. You can determine the flavor of DV unambiguously just
by looking at the resolution and pixel format.
* Baptiste COUDURIER (baptiste.coudurier at smartjog.com) wrote:
> Steven M. Schultz wrote:
> > On Fri, 3 Mar 2006, Baptiste COUDURIER wrote:
> >>I tested the patch and it perfectly plays in Quicktime Player and Final
> >>Cut, in DV file format. Talking about MOV, setting fourcc to 'dv5p'
> >>makes it working.
> > I think for NTSC the DVCPRO50 fourcc is 'dv5n' - I'll check later
> > tonight when I have access to the system with DV50 capability.
> > CHeers,
> > Steven Schultz
> Exactly. I confirm.
> Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA
> SMARTJOG S.A. http://www.smartjog.com
> Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
> Phone: +33 1 49966312
> ffmpeg-devel mailing list
> ffmpeg-devel at mplayerhq.hu
More information about the ffmpeg-devel