Thanks Carl, you are spot on! It is indeed down to the multi-threading.
On 23 July 2014 11:43, Carl Eugen Hoyos wrote:
> Simon Pickles thefoundry.co.uk> writes:
>
> > In 2.1.4 I don't get 1 returned by got_packet_ptr.
> > However, if I keep trying to decode the frame, it
> > eventually starts
Simon Pickles thefoundry.co.uk> writes:
> In 2.1.4 I don't get 1 returned by got_packet_ptr.
> However, if I keep trying to decode the frame, it
> eventually starts to decode after FIFTEEN attempts!
(Do you have an eight-core cpu?)
I suspect this is the multi-threading delay, set
threads to
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, Si
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 frame
Simon Pickles 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 reprodu
Hi
I've just upgraded from FFmpeg 1.0 to 2.1.4 and although it was pretty
painless, I am having a weird problem with a few codecs. So far I've found
this problem occurs with PNG, jpeg2000 and DNxHD.
Basically, in the old version a mov format with a png codec used to work
fine, with every call to
