Hello all,
I have encoded a bunch of videos for my iPad into MPEG-4-AVC using
ffmpeg + libx264.
I'm using Debian Linux 9/testing and it's version of ffmpeg on x64 for encoding.
ffmpeg version 3.1.2-1 Copyright (c) 2000-2016 the FFmpeg developers
Two of my videos have very strange behavior:
They
//pastebin.com/NgkJVARD
--
-Alexey Eromenko "Technologov"
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
lue
collect2: error: ld returned 1 exit status
library.mak:102: recipe for target 'libavcodec/libavcodec.so.57' failed
make: *** [libavcodec/libavcodec.so.57] Error 1
If compiler doesn't like "libavcodec", then why configure step succeeded ?
Any ideas ?
--
-Alexey Erom
+faststart didn't solve the problem, sadly.
http://pastebin.com/r2yg1w1V
Here is what I'we got: -- using Atomic Parsley tool
F:\Test-video-coding\Apple-decoder-issues>C:\Dropbox\Install-experimental\Atomic
Parsley-win32-0.9.0\AtomicParsley.exe Pocahontas2-Anti-Apple-360p-2pass-faststar
t.mp4 -T
More info on this issue:
Encoding only the first 2 minutes work fine (using -to 00:02:00), but
encoding the first 4 minutes already results in an error.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
T
Here is an example broken video file: -- (video data was blurred on purpose.)
https://drive.google.com/open?id=0BycgkMZbeQOzaXpFRVJ5T09VeTQ
This broken video cannot be played on iTunes/Quicktime, beyond about 50 seconds.
___
ffmpeg-user mailing list
ffmp
>I haven’t looked at your file, but the first thing I would do is compare your
>encoding settings (which, as far as I can see, you still haven’t posted) to
>the video specifications of the playback device. For your iPad Pro, they are:
I posted everything. All default settings still cause the pr
Okay, for now I was forced to open a bug report #5882
https://trac.ffmpeg.org/ticket/5882
So far I found this problem on 3 out of 700+ videos, making it fairly
rare, but still significant. That means about 0.5% of my videos DO NOT
PLAY on iPad/Apple products no matter which encoding settings I use
I have provided a new test case and a new evidence for this bug:
https://trac.ffmpeg.org/ticket/5882
--
-Alexey Eromenko "Technologov"
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To u
Sadly ffmpeg developers don't care about bugs, and close bugs without
any explanation.
https://trac.ffmpeg.org/ticket/5882#comment:10
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visi
Hello all,
Bug #5882; Certain x264 videos do not play on Apple decoders
(Quicktime/iTunes/iPad)
Today was closed by developer "cehoyos" without any explanation, and
without any resolution.
He treats all bugs like that ? Worse yet; he treats all people like bugs ?
--
-Alexe
e (iOS + Mac OS). Perhaps not for every minor release,
but for major releases QA is a must-have.
I can do some of the testing myself, being a QA guy, I'm capable of
this task, but when there is a severe and critical issue, alarms must
be sounde
I have a strong belief, that produced MP4 files should be played on
all popular players, and any potential issues must be documented.
Additionally ffmpeg should provide a BIG WARNING that a resulting file
will not be playable on Apple decoders, and offer to fix it
automatically.
-Alexey
_
/ffmpeg
How do you fight this problem ?
--
-Alexey Eromenko "Technologov"
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpe
I have downloaded ffmpeg-git to $HOME
alexey@deb9ws:~/ffmpeg$ pwd
/home/alexey/ffmpeg
alexey@deb9ws:~/ffmpeg$ ./ffmpeg -version
ffmpeg version N-81947-gc45ba26-3 Copyright (c) 2000-2016 the FFmpeg developers
Plus I have Debian's version of ffmpeg installed, for reference (it
cannot be removed, si
I have done as suggested, but problem was NOT FIXED.
alexey@deb9ws:~/ffmpeg$ ./configure --enable-gpl --extra-version=4
--enable-libx264 --enable-libx265 --enable-static --disable-shared
$ make
$ ./ffmpeg
... returns me the WARNING from system avformat library, rather than custom.
Any other opti
I did:
$ make clean
Yeah, finally it works, Big Thanks !
> I *think* he just copied Debian's switches. ;-)
Indeed, initially I just copied Debian's switches. But now I removed
all the extras.
So, back to my patch. Will test it now. I want to auto-fix timebase on
both MP4 and MOV containers.
___
, so you prefer to update them more frequently
?
Just wanna know a bit of background about political and/or technical
design decision of times past.
--
-Alexey Eromenko "Technologov"
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://
nd is therefore twelve bytes larger than a
> version 0 mdhd atom.
>
> Thank you for finally solving the question why QT fails!
>
> Carl Eugen
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listi
And please DONT push me to MOV.
The same way that I don't encode audio only-for-Apple and I don't
encode images only-for-Apple, I want to encode video to work
everywhere.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listi
Let's call my wish " -compatible 1.0" (targeting current-gen hardware)
and once all the popular hardware platforms advances to HEVC to AV1
codec, we will create a new profile " -compatible 2.0" for UltraHD
resolution 4K and 60 fps and 10-bit and updated codecs and more...
So once every 5 to 10 yea
Carl Eugen Hoyos wrote:
>How can I reproduce this?
Encode any file into *.mov and try to play it. Either from Samsung
File Manager or Samsung Video Player or from Android Gallery. (tested
on Samsung Galaxy S7, but I'm pretty sure same will happen on every
other Galaxy; If you need I can also test
On Wed, Oct 12, 2016 at 11:46 PM, Carl Eugen Hoyos wrote:
> 2016-10-12 23:38 GMT+02:00 Alexey Eromenko :
>> Carl Eugen Hoyos wrote:
>>>How can I reproduce this?
>>
>> Encode any file into *.mov and try to play it.
>
> Sorry that my question was so unclear:
&
On Thu, Oct 13, 2016 at 12:10 AM, Carl Eugen Hoyos wrote:
> 2016-10-12 23:58 GMT+02:00 Alexey Eromenko :
>
>> The problem is not encoded file per se, but the *.mov file
>> extension, that Android dislikes. As I said after a simple
>> rename to MP4 extension, it works.
>
On Oct 13, 2016 2:12 AM, "Reindl Harald" wrote:
>
>
>
> Am 12.10.2016 um 22:31 schrieb Alexey Eromenko:
>>
>> And please DONT push me to MOV.
>>
>> The same way that I don't encode audio only-for-Apple and I don't
>> encode image
25 matches
Mail list logo
