Re: [FFmpeg-user] Audio delayed with DeckLink

[Marton Balint]

On Thu, 13 Oct 2016, PSPunch wrote:


Hi,

On Win7 x64, Capturing SDI from DeckLink Duo 2.

When encoding with FFmpeg, audio seems to be about 100ms later than 
video. Is there a known solution to this, or is there a way to delay 
video by roughly 100ms?


I tested the DeckLink drivers on Linux, and they very often fail to 
provide proper timestamps for the audio and video they produce, there is 
also a noticable clock skew after a few hours if you use their video 
clock, and they also skip frames (different number of audio and video 
frames) in the event of a signal loss.


To work around this problem, there are the audio_pts and video_pts 
options, so you can customize where you want your timestamps to come 
from. In my experience, wallclock is the only thing that works 
reliably, so I typically use these options:


-vsync 1
-video_pts wallclock
-audio_pts wallclock
-af aresample=async=1

Regards,
Marton
___
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".

[FFmpeg-user] Creating image stream from h264 and piping

[Adriano Todaro]

Hi all,

I'll try to describe clearly what I'm trying to achieve.

If I use this command:

ffmpeg -i 'rtsp://
user:password@192.168.1.90:554/axis-media/media.amp?videocodec=h264' -vf
"select='eq(pict_type,I)'" -vsync vfr  thumb%04d.jpg

FFmpeg creates a series of JPEG images from the I frames of the original
video stream.

Now I need to pipe this output, but if I do:

ffmpeg -i 'rtsp://
user:password@192.168.1.90:554/axis-media/media.amp?videocodec=h264' -vf
"select='eq(pict_type,I)'" -vsync vfr  pipe:1

I get the error:



ffmpeg version 3.1.4 Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 6.2.1 (GCC) 20160830
  configuration: --prefix=/usr --disable-debug --disable-static
--disable-stripping --enable-avisynth --enable-avresample
--enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl
--enable-ladspa --enable-libass --enable-libbluray --enable-libfreetype
--enable-libfribidi --enable-libgsm --enable-libiec61883
--enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb
--enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus
--enable-libpulse --enable-libschroedinger --enable-libsoxr
--enable-libspeex --enable-libssh --enable-libtheora --enable-libv4l2
--enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp
--enable-libx264 --enable-libx265 --enable-libxvid --enable-netcdf
--enable-shared --enable-version3 --enable-x11grab
  libavutil  55. 28.100 / 55. 28.100
  libavcodec 57. 48.101 / 57. 48.101
  libavformat57. 41.100 / 57. 41.100
  libavdevice57.  0.101 / 57.  0.101
  libavfilter 6. 47.100 /  6. 47.100
  libavresample   3.  0.  0 /  3.  0.  0
  libswscale  4.  1.100 /  4.  1.100
  libswresample   2.  1.100 /  2.  1.100
  libpostproc54.  0.100 / 54.  0.100
Input #0, rtsp, from 'rtsp://
root:avansig@192.168.1.90:554/axis-media/media.amp?videocodec=h264':
  Metadata:
title   : Media Presentation
  Duration: N/A, start: 0.040089, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuv420p(tv, bt709), 1280x800 [SAR 1:1
DAR 8:5], 25 tbr, 90k tbn, 180k tbc
[NULL @ 0x5590e4565b00] Unable to find a suitable output format for 'pipe:1'
pipe:1: Invalid argument



Seemingly because ffmpeg can't guess the output format anymore.

So the question is: how can crete a stream of jpeg images that I can send
through pipe:1?

I've tried to add something like "-f jpeg" but of course it didn't work.


Thanks in advance,

Adriano Todaro.
___
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".

[FFmpeg-user] ffv1 level

[Jim Shupert]

if one does not declare a level or a gop  what is the default

meaning


ffmpeg -i  \
-acodec  copy   \
-vcodec  ffv1   \
-level   3  \
-coder   1  \
-context 1  \
-g   1  \



-level   3
declares   , ffv1 vers 3
 -g   1
declares a gop of 1

what is the default if not declared

ffmpeg -i  \
-acodec  copy   \
-vcodec  ffv1   \
-coder   1  \



thanks

jS

___
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".

[FFmpeg-user] hls hevc_qsv ffmpeg generates one big chunk

[dariusz wapiński]

Hello,

any ideas why it doesnt work?


/ffmpeg-3.1.4/ffmpeg -loglevel debug -progress - -re -i
udp://x.x.x.x?fifo_size=100_nonfatal=1_size=1048576
-threads 2 -acodec copy -vcodec hevc_qsv -load_plugins
6fadc791a0c2eb479ab6dcd5ea9da347 -preset veryfast -q 20  -g 250 -f tee -map
0:a -map 0:v -flags +global_header
[hls_time=10:hls_list_size=3:hls_wrap=0tart_number=1:hls_flags=delete_segments:hls_segment_filename=/run/hls/1/high/fragment%03d.ts]/run/hls/1/high/playlist.m3u8

it generates one big file but i want segments with duration 10second. Are
there any issues with hevc_qsv and hls segmenter???
best regards



--
View this message in context: 
http://ffmpeg-users.933282.n4.nabble.com/hls-hevc-qsv-ffmpeg-generates-one-big-chunk-tp4677880.html
Sent from the FFmpeg-users mailing list archive at Nabble.com.
___
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".

Re: [FFmpeg-user] nvenc h264 encoding

[Sven C. Dack]

On 13/10/16 16:05, Nicolas George wrote:

Le duodi 22 vendémiaire, an CCXXV, Sven C. Dack a écrit :

If I'm not mistaken then yuv444p is linked to 10-bit depth encoding

Not necessarily. ...


Sorry if I wasn't clear enough. I didn't say yuv444p was a 10-bit format. I said 
it is /linked/ to 10-bit depth encoding.


Of course can one use and convert basically any format into whatever the 
hardware needs as input. It's just not being done here.


___
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".

Re: [FFmpeg-user] nvenc h264 encoding

[Nicolas George]

Le duodi 22 vendémiaire, an CCXXV, Sven C. Dack a écrit :
> If I'm not mistaken then yuv444p is linked to 10-bit depth encoding

Not necessarily. yuv444 is opposed to yuv420: with 420, pixels are grouped
as 2×2 squares, where all four pixels have their brightness ("y" =
"luminance") encoded, while the color ("u"/"v" = "chrominance") is the same
for all four; with 444, pixels have all three components coded individually.
That means that in 444, each pixels use three components, while in 420 they
only use 1.5 on average, half as much. This makes sense because the eye is
more sensitive to brightness changes than color changes.

10-bits depth is opposed to 8-bits depth, it measures the accuracy for each
component.

All four combinations are possible: yuv420p8, yuv420p10, yuv444p8,
yuv444p10. The 8 is usually not printed because it was for a long time the
only possible choice and is still the default. Of course, because of
compatibility problems, once you decide to ditch yuv420p8, you might as well
go all the way to yuv444p10, therefore the two intermediate ones are more
rarely seen. But yuv444p8 makes sense for screencasts, to avoid color
bleeding.

The p means that libavcodec stores the three components in three separate
memory areas rather than interleaved all together like rgb24.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature
___
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".

Re: [FFmpeg-user] nvenc h264 encoding

[Sven C. Dack]

On 13/10/16 14:01, tyt xtreme wrote:

And what can i do on Windows to check these capabilities?
Btw the GPU is a Gainward 6 Gb nVidia GTX 980 Ti so i think this should
support the above formats.
If I'm not mistaken then yuv444p is linked to 10-bit depth encoding, which is 
only possible on the newer Pascal cards (the 10x0 series). The Video SDK page 
only mentions HEVC/H.265, but I believe it also applies to AVC/H.264. See here: 
https://developer.nvidia.com/nvidia-video-codec-sdk


Try using "high" instead of "high444p" for the profile and "nv12" or "yuv420p" 
for the pixel format.


If you want best quality for compression then add "-rc vbr_2pass -rc-lookahead 
32" to the command line. The encoder cannot actually do two full passes, but it 
can look ahead up to 32 frames, which acts as a substitute for 2-pass encoding 
and can improve the picture quality a lot especially around I-frames.




On Thu, Oct 13, 2016 at 1:52 PM, Sven C. Dack  wrote:


On 13/10/16 11:34, tyt xtreme wrote:


Dear All,

Any idea why this encoding doesn't work?

$ ffmpeg -i perspective.mp4 -c:v h264_nvenc -profile:v high444p
-pixel_format yuv444p -preset default perspective_out.mp4

...
[h264_nvenc @ 01d84640] No free surfaces
Video encoding failed
Conversion failed!


Surfaces are a reference to the memory buffers used by the encoder. You
can find out about which surfaces your graphics card supports by opening
the Nvidia settings panel, -> "VDPAU Information", -> "Surface Limits".

If your card doesn't support the pixel format or the picture exceeds the
surface limit might this already explain why you get this error message.
Although I would expect to see a different error message...

You can also check with "nvidia-smi" which applications are currently
using your graphics card. Suspended processes, zombie processes or just
multiple processes can also exhaust the amount of available surfaces.

___
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".

___
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".



___
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".

Re: [FFmpeg-user] framerate conversion with sync audio

[Carles Vila]

>
> > How can I apply the same filter to all audio streams?
>
> You use -filter_complex instead of -vf and -af
>
> -filter_complex
> [0:0]setpts=PTS*0.8[v];[0:1]asetrate,aresample[a0];[0:2]
> asetrate,aresample[a1]
> and then -map [v] -map [a0] -map [a1]
> (untested)
>

After a couple of attempts, it works! But I keep using the -r 25 option
before -i. It works just fine for me.
___
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".

Re: [FFmpeg-user] dpx to prores & h.264 - color shift

[Andy Furniss]

Kevin Wheatley wrote:

Andreas,

instead of using the -colormatrix option try instead using

-vf 
scale=in_range=full:in_color_matrix=bt709:out_range=tv:out_color_matrix=bt709

assuming your DPX files are utilising full range encoding


also scale has flags which may or may not affect quality in this case.

IIRC getting them to work can be a bit variable, historically

-sws-flags flag1+flag2 ... used to work, but not last time I tested so

-vf scale=:flags=flag1+flag2. was what I last used - best

to double check with -loglevel verbose + check output to be sure.

https://www.ffmpeg.org/ffmpeg-scaler.html#scaler_005foptions

I am thinking of trying accurate_rnd full_chroma_int full_chroma_inp 
bitexact


not that I know what's best or relevant, so trial and error really.
___
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".

Re: [FFmpeg-user] nvenc h264 encoding

[tyt xtreme]

And what can i do on Windows to check these capabilities?
Btw the GPU is a Gainward 6 Gb nVidia GTX 980 Ti so i think this should
support the above formats.

On Thu, Oct 13, 2016 at 1:52 PM, Sven C. Dack  wrote:

> On 13/10/16 11:34, tyt xtreme wrote:
>
>> Dear All,
>>
>> Any idea why this encoding doesn't work?
>>
>> $ ffmpeg -i perspective.mp4 -c:v h264_nvenc -profile:v high444p
>> -pixel_format yuv444p -preset default perspective_out.mp4
>>
>> ...
>> [h264_nvenc @ 01d84640] No free surfaces
>> Video encoding failed
>> Conversion failed!
>>
> Surfaces are a reference to the memory buffers used by the encoder. You
> can find out about which surfaces your graphics card supports by opening
> the Nvidia settings panel, -> "VDPAU Information", -> "Surface Limits".
>
> If your card doesn't support the pixel format or the picture exceeds the
> surface limit might this already explain why you get this error message.
> Although I would expect to see a different error message...
>
> You can also check with "nvidia-smi" which applications are currently
> using your graphics card. Suspended processes, zombie processes or just
> multiple processes can also exhaust the amount of available surfaces.
>
> ___
> 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".
___
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".

[FFmpeg-user] Audio delayed with DeckLink

[PSPunch]

Hi,

On Win7 x64, Capturing SDI from DeckLink Duo 2.

When encoding with FFmpeg, audio seems to be about 100ms later than  
video. Is there a known solution to this, or is there a way to delay  
video by roughly 100ms?


Below is the command & output when using NVENC and streaming UDP, but  
delayed audio is present also when using libx264 or outputting to FLV file.


Also there is no such sync issues when capturing the same SDI input  
using Blackmagic Media Express.



---
ffmpeg -f decklink -i "DeckLink Duo (3)@9" -vcodec nvenc -b:v 2M  
-pix_fmt yuv420p -acodec aac -b:a 128k -bsf:v h264_mp4toannexb -f mpegts  
udp://127.0.0.1:30003?pkt_size=1316



ffmpeg version N-79037-g370cecc Copyright (c) 2000-2016 the FFmpeg  
developers

  built with gcc 5.3.0 (GCC)
  configuration: --arch=x86_64 --target-os=mingw32  
--cross-prefix=/home/david/opt/ffmpeg-cross-compile/sandbox/cross_compilers/mingw-w64-x86_64/bin/x86_64-w64-mingw32-  
--pkg-config=pkg-config --disable-w32threads --enable-gpl  
--enable-libsoxr --enable-fontconfig --enable-libass --enable-libutvideo  
--enable-libbluray --enable-iconv --enable-libtwolame  
--extra-cflags=-DLIBTWOLAME_STATIC --enable-libzvbi --enable-libcaca  
--enable-libmodplug --extra-libs=-lstdc++ --extra-libs=-lpng  
--enable-libvidstab --enable-libx265 --enable-decklink  
--extra-libs=-loleaut32 --enable-libx264 --enable-libxvid  
--enable-libmp3lame --enable-version3 --enable-zlib --enable-librtmp  
--enable-libvorbis --enable-libtheora --enable-libspeex  
--enable-libopenjpeg --enable-gnutls --enable-libgsm  
--enable-libfreetype --enable-libopus --enable-frei0r  
--enable-filter=frei0r --enable-bzlib --enable-libxavs  
--enable-libopencore-amrnb --enable-libopencore-amrwb  
--enable-libvo-amrwbenc --enable-libschroedinger --enable-libvpx  
--enable-libilbc --enable-libwavpack --enable-libwebp --enable-libgme  
--enable-dxva2 --enable-libdcadec --enable-avisynth --enable-gray  
--enable-libopenh264 --extra-libs=-lpsapi --extra-cflags=  
--enable-static --disable-shared  
--prefix=/home/david/opt/ffmpeg-cross-compile/sandbox/cross_compilers/mingw-w64-x86_64/x86_64-w64-mingw32  
--enable-nonfree --enable-libfdk-aac --disable-libfaac --enable-nvenc  
--enable-runtime-cpudetect

  libavutil  55. 19.100 / 55. 19.100
  libavcodec 57. 28.103 / 57. 28.103
  libavformat57. 28.101 / 57. 28.101
  libavdevice57.  0.101 / 57.  0.101
  libavfilter 6. 39.102 /  6. 39.102
  libswscale  4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc54.  0.100 / 54.  0.100
[decklink @ 00603420] Found Decklink mode 1920 x 1080 with rate  
29.97(i)
[decklink @ 00603420] Frame received (#1) - No input signal  
detected - Frames dropped 1

Guessed Channel Layout for  Input Stream #0.0 : stereo
Input #0, decklink, from 'DeckLink Duo (3)@9':
  Duration: N/A, start: 0.00, bitrate: 1536 kb/s
Stream #0:0: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
Stream #0:1: Video: rawvideo (UYVY / 0x59565955), uyvy422,  
1920x1080, -5 kb/s, 29.97 tbr, 1000k tbn, 29.97 tbc

Output #0, mpegts, to 'udp://127.0.0.1:30003?pkt_size=1316':
  Metadata:
encoder : Lavf57.28.101
Stream #0:0: Video: h264 (nvenc) (Main), yuv420p, 1920x1080,  
q=-1--1, 2000 kb/s, 29.97 fps, 90k tbn, 29.97 tbc

Metadata:
  encoder : Lavc57.28.103 nvenc
Side data:
  cpb: bitrate max/min/avg: 0/0/200 buffer size: 400  
vbv_delay: -1

Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp, 128 kb/s
Metadata:
  encoder : Lavc57.28.103 aac
Stream mapping:
  Stream #0:1 -> #0:0 (rawvideo (native) -> h264 (nvenc))
  Stream #0:0 -> #0:1 (pcm_s16le (native) -> aac (native))

--
David Shimamoto
___
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".

Re: [FFmpeg-user] dpx to prores & h.264 - color shift

[Kevin Wheatley]

Andreas,

instead of using the -colormatrix option try instead using

-vf 
scale=in_range=full:in_color_matrix=bt709:out_range=tv:out_color_matrix=bt709

assuming your DPX files are utilising full range encoding


Kevin
___
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".

Re: [FFmpeg-user] nvenc h264 encoding

[Sven C. Dack]

On 13/10/16 11:34, tyt xtreme wrote:

Dear All,

Any idea why this encoding doesn't work?

$ ffmpeg -i perspective.mp4 -c:v h264_nvenc -profile:v high444p
-pixel_format yuv444p -preset default perspective_out.mp4

...
[h264_nvenc @ 01d84640] No free surfaces
Video encoding failed
Conversion failed!
Surfaces are a reference to the memory buffers used by the encoder. You can find 
out about which surfaces your graphics card supports by opening the Nvidia 
settings panel, -> "VDPAU Information", -> "Surface Limits".


If your card doesn't support the pixel format or the picture exceeds the surface 
limit might this already explain why you get this error message. Although I 
would expect to see a different error message...


You can also check with "nvidia-smi" which applications are currently using your 
graphics card. Suspended processes, zombie processes or just multiple processes 
can also exhaust the amount of available surfaces.


___
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".

Re: [FFmpeg-user] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Carl Eugen Hoyos]

2016-10-13 11:43 GMT+02:00 Sven C. Dack :
> On 13/10/16 07:56, Alexey Eromenko wrote:
>>
>> If we agree, we can try to write a solution.
>>
> You don't need people to agree with you. You really just need to
> provide patches, make sure you don't limit or destroy anybody
> else's work and be fair to all.
>
> When you get a No as an answer then demand an explanation
> and follow it. If you want ffmpeg to have a new option, a new
> decoder/encoder, filter, format, whatever, then just go ahead and do it.

This is all true but I would like to add that Michael has already suggested
which way to go.

Carl Eugen
___
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".

Re: [FFmpeg-user] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Sven C. Dack]

On 13/10/16 07:56, Alexey Eromenko wrote:

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

You don't need people to agree with you. You really just need to provide 
patches, make sure you don't limit or destroy anybody else's work and be fair to 
all.


When you get a No as an answer then demand an explanation and follow it. If you 
want ffmpeg to have a new option, a new decoder/encoder, filter, format, 
whatever, then just go ahead and do it.



___
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".

Re: [FFmpeg-user] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Reindl Harald]

Am 13.10.2016 um 08:56 schrieb Alexey Eromenko:

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 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


*you* are the one operating ffmpeg and so it's under your control, 
practically everyone which is using ffmpeg writes some wrapper script 
around and never bother about details in the future


  private $mp4_x264_options = array
  (
   array('param' => 'f',   'value' => 'ipod'),
   array('param' => 'preset',  'value' => 'slow'),
   array('param' => 'codec:v', 'value' => 'libx264'),
   array('param' => 'codec:a', 'value' => 'aac'),
   array('param' => 'strict',  'value' => 'experimental'),
   array('param' => 'cutoff',  'value' => '15000'),
   array('param' => 'flags',   'value' => '+loop+mv4'),
   array('param' => 'cmp', 'value' => '256'),
   array('param' => 'partitions',  'value' => 
'+parti4x4+parti8x8+partp4x4+partp8x8+partb8x8'),

   array('param' => 'me_method',   'value' => 'hex'),
   array('param' => 'me_range','value' => '16'),
   array('param' => 'subq','value' => '9'),
   array('param' => 'trellis', 'value' => '1'),
   array('param' => 'refs','value' => '5'),
   array('param' => 'g',   'value' => '250'),
   array('param' => 'keyint_min',  'value' => '25'),
   array('param' => 'sc_threshold','value' => '40'),
   array('param' => 'i_qfactor',   'value' => '0.71'),
   array('param' => 'qcomp',   'value' => '0.6'),
   array('param' => 'qmin','value' => '0'),
   array('param' => 'qmax','value' => '69'),
   array('param' => 'qdiff',   'value' => '4'),
   array('param' => 'bufsize', 'value' => '2M'),
   array('param' => 'pix_fmt', 'value' => 'yuv420p'),
   array('param' => 'multithreading',  'value' => true),
   array('param' => 'qt_faststart','value' => true),
   array('param' => 'movflags','value' => '+faststart'),
   array('param' => 'flvtool2','value' => false),
   array('param' => 'twopass', 'value' => true),
  );
___
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".

Re: [FFmpeg-user] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Alexey Eromenko]

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 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.

-Alexey.
___
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".