On Oct 13, 2016 2:12 AM, "Reindl Harald" <h.rei...@thelounge.net> 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 images only-for-Apple, I want to encode video to work
>> everywhere
> than just encode them H264 *baseline* which wroks on all apple devices,
android and everything else for many years - that's it

baseline won't solve the problems. It doesn't force low timebase and it
doesn't force yuv420p colorspace, it doesn't force FPS 30 limit, so things
won't work.

And high profile actually works fine on all of the devices I tested.

Back to the problem :

I propose two new solutions for ffmpeg : a patch that will auto-set a low
timebase, up to 100k and "-compatible 1.0" parameter to force many
parameters, including timebase, according to what decoders can actually
play back.

Is there a downside to force a timebase between 10k and 100k?

If we agree, we can try to write a solution.

ffmpeg-user mailing list

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to