This is libdv devel list. (WAS: Re: [libdv-dev] Possible bug encoding interlaced material?)

[Stefan L. <st...@lu...>]

On Montag, 4. April 2005 03:02, Roman Shaposhnick wrote:
> <F2On Mon, Apr 04, 2005 at 10:14:44AM +0930, Jonathan Woithe wrote:
> > These tests seem to suggest that the root cause of the problem actually lies
> > in libdv's encoder.  It appears that when presented interlaced input, libdv
> > doesn't do the right thing, and perhaps even assumes the input is
> > non-interlaced: each field of the encoded frame contains blocky shadows of
> > the contents of the frame's other field.
> 
>   To make things a little bit clearer could you, please, run your
>   experiments using ffmpeg instead of libdv. Both for encoding and
>   decoding.
> 
> > Anyway, what do others think?  Is this an issue?  Is there a way to get
> > around it so interlaced material is encoded correctly to DV by libdv?
>   
>   Oh, yeah! Use ffmpeg :-)

Roman, this list should cover libdv development related things.
To me it is rather annoying as your default answer to questions like:
Q: I've a problem using libdv with ..
A: Use ffmpeg ..

If you know the source of some problems related to libdv it would
be more polite to post a fix .

-- 
Stefan Lucke