[Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?

Lars Hammarstrand lars.hammarstrand at gmail.com
Wed Apr 3 11:12:55 CEST 2013

2013/4/3 Carl Eugen Hoyos <cehoyos at ag.or.at>

> Lars Hammarstrand <lars.hammarstrand at ...> writes:
> > > Exactly 14 iterations, please trust me, I am doing
> > > this quite often.
> >
> > Ok, I'll trust you completely
> (I was actually wrong: 14 iterations == 15 compiles)

That will take roughly 7,5 hours (give or take) in a worst case scenario.
That's why I want to automate with git bisec run. I played around with "git
log" a found a commit that (what I think) seems close to 0.10 that will
produce 13 iterations:

$ git bisect good 33c21378a846d880110324f3e139a693a9bb30ca
Bisecting: 6686 revisions left to test after this (roughly 13 steps)
[15a0fb58a3294876c23989915a4a6202411be1b0] Merge remote-tracking branch

But it seems you are using an earlier commit. Which commit did you use for
"git bisect good"?

> > Before starting, please test -cpuflags -neon and
> > --disable-neon to make 100% sure that we know what
> > we are searching for.
> >
> > Success, --disable-neon and -cpuflags -neon did the trick!
> I hoped you would first test -cpuflags -neon on
> a build with "--enable-neon" and then "--disable-neon"
> without any cpuflags - sorry for being unclear!

Ok, I'll test that too!

> 100% unrelated to this bisect that we should really
> do in any case (you may already have realized that
> nobody else but you is able to do it):

Ok, lets do it! :)

> I only start to realize now what you are actually
> doing, please allow me state very, very clearly that
> it is imo *not* a good idea to update xbmc now to a
> version of FFmpeg that is already outdated. There
> will be no future release series containing new
> features but the old API!

Well, yes - we're aware about the new api and that 1.2 will the be the last
version with the old api. But since a change to the new api will take some
time to implement, we want to use the version 1.2 that solves a bunch of
other more or less serious problems that we currently struggle with in
version 0.10.2. We are talking show stoppers that is for instance
preventing users to watch certain content types, hangs or causes stuttering
video playback. And we can't be sure this problem won't occur with the new
api, can we?

Xbmc does currently work with ffmpeg n1.2 on all platforms except IOS thus
it's worth the effort to fix this particular problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20130403/c3618dd6/attachment.html>

More information about the Libav-user mailing list