#40829: ffmpeg 2.0.2 - ffv1 codec is bogus --------------------------------+---------------------- Reporter: andre.dos.anjos@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: ffmpeg | --------------------------------+---------------------- Comment (by devans@…): My results seem to be consistent with yours. Both programs build without error with their respective ffmpeg version (I'm using ffmpeg@2.0.2 and ffmpeg@1.2.2). Running the ffmpeg@2.0.2 version fails with errors and produces a corrupted avi file with video and audio streams. {{{ $ ./ffmpeg_test test.avi [libmp3lame @ 0x7fa7d201f200] Channel layout not specified Output #0, avi, to 'test.avi': Stream #0:0: Video: ffv1, yuv420p, 352x288, q=2-31, 400 kb/s, 90k tbn, 25 tbc Stream #0:1: Audio: mp3 (libmp3lame), 44100 Hz, 2 channels, fltp, 64 kb/s Error encoding video frame: Invalid argument }}} The ffmpeg@1.2.2 version run successfully and produces a valid avi file (video only, no audio stream) {{{ $ ./ffmpeg_test-1x test-1x.avi Output #0, avi, to 'test-1x.avi': Stream #0:0: Video: ffv1, yuv420p, 352x288, q=2-31, 400 kb/s, 90k tbn, 25 tbc }}} Comparing the two programs with diff shows what I would call substantial differences in code. Obviously there are substantial (upstream) changes in the ffmpeg code as well between these two versions. MacPorts just packages the code supplied from upstream. So I would think that this is a problem that you should take up with the ffmpeg developers. I would suggest the ffmpeg-users list to start. I don't see any indication that the problem stems from MacPorts itself unless you have other evidence to that effect. -- Ticket URL: <https://trac.macports.org/ticket/40829#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X