Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#1934 closed defect (invalid)

DVCPRO50 .dv -> H.264 .avi = broken file

Reported by: noodles Owned by:
Priority: normal Component: ffmpeg
Version: git-master Keywords: h264
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no


FFmpeg 1.0 on Darwin/x86_64 via MacPorts?.

Converting a DVCPRO50 .dv file into an H.264 encoded AVI file produces a broken file that, despite being playable with ffplay, isn't watchable with VLC. YouTube? confirms that the file is broken by showing the same greyish field that VLC shows. This USED TO WORK, before 1.0.

P.S.: Will you kindly explain to me WHY THE FUCK every time I update ffmpeg, options change names, breaking my carefully honed ffpreset files? Are you guys complete IDIOTS or do you just enjoy pissing people off?

Change History (4)

comment:1 Changed 4 years ago by noodles

  • Summary changed from jDVCPRO50 .dv -> H.264 .avi = broken file to DVCPRO50 .dv -> H.264 .avi = broken file

comment:2 Changed 4 years ago by cehoyos

  • Keywords h264 added; H.264 DVCPRO50 avi dv transcoding removed
  • Priority changed from critical to normal
  • Resolution set to invalid
  • Status changed from new to closed
  • Version changed from 1.0 to git-master

Add "-pix_fmt yup420p" to your command line to get the same behaviour as with older versions (when only yuv420p was supported when encoding to h264).

For future tickets: Please always add your command line together with complete, uncut console output when reporting a problem.

Version 0, edited 4 years ago by cehoyos (next)

comment:3 follow-up: Changed 4 years ago by compn

which option changed names? we try to keep backwards compatability using aliases when options change.

comment:4 in reply to: ↑ 3 Changed 4 years ago by cehoyos

Replying to compn:

which option changed names?

The syntax of the -map option changed in an incompatible way. This was (or still is) a major issue imo, a minor issue would be that -t used to be an input option, it is now an output option (the new behaviour makes more sense imo, it was still an - undocumented? - change).

Note: See TracTickets for help on using tickets.