<div dir="ltr">2013/4/2 Carl Eugen Hoyos <span dir="ltr"><<a href="mailto:cehoyos@ag.or.at" target="_blank">cehoyos@ag.or.at</a>></span><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">Lars Hammarstrand <lars.hammarstrand@...> writes:<br>
<br>
> > Could you run the testsuite (make SAMPLES=path fate) on the<br>
> > iPhone? This would allow to verify if only H264 is affected<br>
> > or also other codecs.<br>
><br>
> 4. Sorry, you have to be a bit more specific on this one<br>
> since I'm not a ffmpeg core developer. FATE is a rather<br>
> complex automated testing environment<br>
<br>
</div>Yes, definitely:<br>
$ make SAMPLES=fate-suite fate-rsync<br>
$ make SAMPLES=fate-suite fate<br>
;-)<br>
(Needs rsync installed)<br></blockquote><div><br></div><div style>Are you sure this will work on IOS, I mean have anyone ever tested to run FATE directly from an IOS device like an iphone or ipad? Remember, there is no development environment natively on IOS thus everything needs to be cross compiled on OSX and then transferred over to the device for execution... </div>
<div style><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Most of your remaining questions are simply impossible<br>
to answer (I don't remember FFmpeg ever having a<br>
maintainer for x86, ppc or any other architecture and<br></blockquote><div><br></div><div style>Seriously, are you absolutely sure that FFmpeg is never ever tested on ANY platform before a public release??</div><div><br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
allow me to repeat that only trac is relevant on<br>
this mailing list), </blockquote><div><div><br></div><div>I think you missed my point for the second time :) But never mind, I'll file a bug report at libav myself...</div></div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
but please test if -cpuflags -neon<br>
or --disable-neon helps.<br></blockquote><div><br></div><div style>Will do! </div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
(I will open a ticket if all information is available,<br></blockquote><div><br></div><div style>Great, here are some additional configure flags. Please tell me if you need anything else to open a ticket!</div><div style>
<br></div><div style><div><font face="courier new, monospace">$ ./ffmpeg</font></div><div><font face="courier new, monospace">ffmpeg version 1.2 Copyright (c) 2000-2013 the FFmpeg developers</font></div><div><font face="courier new, monospace"> built on Apr 2 2013 17:54:06 with llvm-gcc 4.2.1 (LLVM build 2410.2.00)</font></div>
<div><font face="courier new, monospace"> configuration: --disable-ffplay --disable-ffserver --disable-ffprobe --disable-doc --disable-bzlib --target-os=darwin --enable-cross-compile --enable-gpl --enable-version3 --arch=arm --cpu=cortex-a8 --enable-pic --extra-cflags='-arch armv7' --extra-ldflags='-arch armv7' --extra-cflags='-mfpu=neon -mfloat-abi=softfp -mvectorize-with-neon-quad' --enable-neon --disable-armv5te --disable-armv6 --disable-armv6t2 --enable-optimizations --enable-debug=3 --disable-stripping --cc=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc --as='<a href="http://gas-preprocessor.pl">gas-preprocessor.pl</a> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc' --sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk --extra-ldflags=-L/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/usr/lib/system</font></div>
<div><font face="courier new, monospace"> libavutil 52. 18.100 / 52. 18.100</font></div><div><font face="courier new, monospace"> libavcodec 54. 92.100 / 54. 92.100</font></div><div><font face="courier new, monospace"> libavformat 54. 63.104 / 54. 63.104</font></div>
<div><font face="courier new, monospace"> libavdevice 54. 3.103 / 54. 3.103</font></div><div><font face="courier new, monospace"> libavfilter 3. 42.103 / 3. 42.103</font></div><div><font face="courier new, monospace"> libswscale 2. 2.100 / 2. 2.100</font></div>
<div><font face="courier new, monospace"> libswresample 0. 17.102 / 0. 17.102</font></div><div><font face="courier new, monospace"> libpostproc 52. 2.100 / 52. 2.100</font></div><div><font face="courier new, monospace">Hyper fast Audio and Video encoder</font></div>
<div><font face="courier new, monospace">usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...</font></div><div><br></div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
if you open it without bisecting this will unfortunately<br>
not really help.)</blockquote><div><br></div><div style>I'll need some more detailes how we shall proceed with bisecting. Is it possible to automate everything with a script, like "Start: git get next version, compile, copy to device, remote exec, check return code, break if error else goto start" ?? </div>
<div style><br></div><div style>I've no intention to compile hundreds of different versions by hand you know. :) :)</div><div style>--</div><div style><br></div><div style>Regards, Lars.</div><div style><br></div></div>
</div></div>