Hi Kai,
Before I make a bug report, am I missing something?
Yes. You have too many links to external stuff (tarballs, logs [why not
attached here?], various scenarios, various requests, and it's unclear
what the problem is.
Your only problem report:
CPU iPhone OS 8_3 like Mac OS X)
On Thu, Apr 30, 2015 at 10:05 AM, Kai Hendry hen...@webconverger.com wrote:
On 30 April 2015 at 15:38, Moritz Barsnick barsn...@gmx.net wrote:
Yes. You have too many links to external stuff (tarballs, logs [why not
attached here?], various scenarios, various requests, and it's unclear
what the
On 30 April 2015 at 17:21, Tom Evans tevans...@googlemail.com wrote:
What is missing (and the only thing that is really required) is the
full command line that you used to invoke ffmpeg, and the console
output that invocation of ffmpeg produced, presented as inline in the
email. No
On Thu, Apr 30, 2015 at 11:06 AM, Kai Hendry hen...@webconverger.com wrote:
On 30 April 2015 at 17:21, Tom Evans tevans...@googlemail.com wrote:
What is missing (and the only thing that is really required) is the
full command line that you used to invoke ffmpeg, and the console
output that
On Thu, Apr 30, 2015 at 17:05:27 +0800, Kai Hendry wrote:
Whoa, I try to be as detailed as possible and then I get criticized
for including too much stuff?! :) Email attachments suck, that's why I
didn't include the tarball.
Well, within three lines of email, you posted three links:
Here is
On Thu, 30 Apr 2015 18:06:03 +0800
Kai Hendry hen...@webconverger.com wrote:
Wow, so you've not seen a -report like this?
http://s.natalian.org/2015-04-30/ffmpeg-20150430-102645.log
The -report option creates an output using the verbose loglevel
resulting in such a large output. It is often
