Re: [libdv-dev] defined but unused variables

[Dan D. <da...@de...>]

I dropped Fabrice from the recipients and added the FFMPEG DV developer
Roman...

On Tue, 2004-03-23 at 17:23, Drew Perttula wrote:
> Dan Dennedy:
> > Likewise, raw dv stream handling is encapsulated in ffmpeg/libavformat,
> > and I encourage all applications using libdv to move to ffmpeg where
> > there is more active maintainership (yes, kino is as well; stay tuned).
> >=20
>=20
> Do you encourage moving to ffmpeg for all operations, or just the stream
> handling?=20

I suggest for DV decoding and decoding at least. Optionally, you can
choose to use libavformat. ffmpeg does not have a DV audio "decoder."
Rather, libavformat extracts the uncompressed PCM, while libavcodec is
required for video decoding.

>  I would miss the datetime/timestamp accessors if I went to
> ffmpeg right now, but if ffmpeg is the future, maybe I should use ffmpeg
> plus accessor-code-ripped-from-libdv?=20

I have asked Roman to look over the libdv API for features that might be
missing in ffmpeg. IMO, this metadata should eventually be supported by
libavformat and libavcodec contexts. Besides, the above we would need
scene change and speed as well, that I can immediately think of off the
top of my head.

Also, libavformat needs seeking support for raw DV files. I tested a
Quicktime 'dvc' plus 'twos' audio track; ffplay did not pickup the audio
and hung after a few seconds of successfully playing video. ffmpeg
reported:
Input #0, mov,mp4,m4a,3gp, from '/home/ddennedy/dvgrab-001.mov':
  Duration: 00:00:15.0, bitrate: 30315 kb/s
  Stream #0.0: Video: dvvideo, 720x480, 29.97 fps
  Stream #0.1: Audio: pcm_s16be, 48000 Hz, stereo, 1536 kb/s
which is correct, but it was unable to process even the first frame.