I should also point out that I can use the built ffmpeg executable to perform conversions on the PNG encoded file. I've used:
./ffmpeg -loglevel debug -i /tmp/pngMov.mov /tmp/1.mov and it works. Whether its doing multiple decode attempts under the hood, I can't tell. On 23 July 2014 10:18, Simon Pickles <[email protected]> wrote: > Hi Carl, > > Thanks for the response. > > I've cloned the git repo, built it and repro'd the problem with the > example code I first posted. Here's the output: > > kludge:MacOS pickles$ ./TestApp > 1 streams > Codec > PTS=0, DTS=0, Duration=1, KeyFrame=1, Corrupt=0, StreamIdx=0, > PktSize=77686 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 0 > Decode 77686 frameDecoded 1 > Decode 77686 frameDecoded 1 > Decode 77686 frameDecoded 1 > Decode 77686 frameDecoded 1 > Decode 77686 frameDecoded 1 > > > Here's the build info: > > kludge:bin pickles$ ./ffmpeg > ffmpeg version 2.2.git Copyright (c) 2000-2014 the FFmpeg developers > built on Jul 23 2014 10:15:55 with gcc 4.0.1 (GCC) (Apple Inc. build > 5494) > configuration: > --prefix=/workspace/pickles/ffmpeg/git_20140723/bin/mac-64-x86-release-10.6 > --arch=x86_64 --cc=gcc-4.0 --extra-cflags=' -arch x86_64 -O3 -fPIC > -I/workspace/pickles/ffmpeg/git_20140723/bin/mac-64-x86-release-10.6/include' > --extra-ldflags='-L/workspace/pickles/ffmpeg/git_20140723/bin/mac-64-x86-release-10.6/lib > -arch x86_64' --enable-shared --disable-static --disable-ffplay > --disable-ffserver --disable-bzlib --disable-devices > --yasmexe=/workspace/pickles/ffmpeg/git_20140723/bin/mac-64-x86-release-10.6/bin/yasm > libavutil 52. 92.101 / 52. 92.101 > libavcodec 55. 69.100 / 55. 69.100 > libavformat 55. 48.101 / 55. 48.101 > libavdevice 55. 13.102 / 55. 13.102 > libavfilter 4. 11.102 / 4. 11.102 > libswscale 2. 6.100 / 2. 6.100 > libswresample 0. 19.100 / 0. 19.100 > > > On 22 July 2014 17:43, Carl Eugen Hoyos <[email protected]> wrote: > >> Simon Pickles <pickles <at> thefoundry.co.uk> writes: >> >> > I've just upgraded from FFmpeg 1.0 to 2.1.4 >> >> Given that 2.1 is very close to eol and 2.3 >> is binary compatible, this is really not a >> good idea. >> >> Additionally, if you found a bug (I don't know >> the issue you describe), you will have to test >> if is reproducible with current FFmpeg. >> >> Carl Eugen >> >> _______________________________________________ >> ffmpeg-user mailing list >> [email protected] >> http://ffmpeg.org/mailman/listinfo/ffmpeg-user >> > > _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
