Re: [libdv-dev] Possible bug encoding interlaced material?

[Roman S. <rv...@su...>]

<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 :-)

> While
> having encodedv work correctly would be good, a general libdv solution is
> the most important consideration from my point of view since it would mean
> that the output from programs which use libdv (such as cinelerra) would be

  Last I've heard cinelerra had a way of using ffmpeg's DV codec instead
  of libdv. 

Thanks,
Roman.