April 2018 - ffmpeg-user - lists.ffmpeg.org

Build FFmpeg4.0 with opencl
by Dong QingDan 28 Apr '18

28 Apr '18

Hello. How are you? I am trying to compile ffmpeg4.0 with opencl. but it failed with "Opencl not found" I want to know the solution for this. I appreciate you help me. regards.

2 2

ProRes XQ 12-bit support
by Elliott Balsley 28 Apr '18

28 Apr '18

According to the white paper, ProRes files can contain 12-bit RGB video with an optional 16-bit alpha channel. Is there some way to tell whether this alpha channel exists? I believe this video clip is 12-bit RGB with a 16-bit alpha channel, but I am trying to verify that. Ffprobe calls it yuv444p10le. DaVinci Resolve identifies it as 16-bit, probably because it sees the alpha channel and only reports the highest bit depth of any channel. Also — does ffmpeg support 12-bit RGB? I do not see it listed in “ffmpeg -pix_fmts”. ffprobe -show_streams B002_C037_06288E_prores444XQ_full12.mov ffprobe version N-90742-g0b3c1854cb Copyright (c) 2007-2018 the FFmpeg developers built with gcc 7.3.0 (GCC) configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth libavutil 56. 15.100 / 56. 15.100 libavcodec 58. 19.100 / 58. 19.100 libavformat 58. 13.100 / 58. 13.100 libavdevice 58. 4.100 / 58. 4.100 libavfilter 7. 17.100 / 7. 17.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 libpostproc 55. 2.100 / 55. 2.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'B002_C037_06288E_prores444XQ_full12.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2018-04-17T19:58:27.000000Z Duration: 00:00:01.33, start: 0.000000, bitrate: 1551673 kb/s Stream #0:0(eng): Video: prores (ap4x / 0x78347061), yuv444p10le(bt709, progressive), 3840x2160, 1551663 kb/s, SAR 1:1 DAR 16:9, 24 fps, 24 tbr, 24 tbn, 24 tbc (default) Metadata: creation_time : 2018-04-17T19:58:27.000000Z handler_name : Apple Alias Data Handler encoder : Apple ProRes 4444 XQ timecode : 00:00:00:00 Stream #0:1(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2018-04-17T19:58:28.000000Z handler_name : Apple Alias Data Handler reel_name : B002_C037_06288E timecode : 00:00:00:00 Unsupported codec with id 0 for input stream 1 [STREAM] index=0 codec_name=prores codec_long_name=Apple ProRes (iCodec Pro) profile=unknown codec_type=video codec_time_base=1/24 codec_tag_string=ap4x codec_tag=0x78347061 width=3840 height=2160 coded_width=3840 coded_height=2160 has_b_frames=0 sample_aspect_ratio=1:1 display_aspect_ratio=16:9 pix_fmt=yuv444p10le level=-99 color_range=unknown color_space=bt709 color_transfer=bt709 color_primaries=bt709 chroma_location=unspecified field_order=progressive timecode=N/A refs=1 id=N/A r_frame_rate=24/1 avg_frame_rate=24/1 time_base=1/24 start_pts=0 start_time=0.000000 duration_ts=32 duration=1.333333 bit_rate=1551663072 max_bit_rate=N/A bits_per_raw_sample=10 nb_frames=32 nb_read_frames=N/A nb_read_packets=N/A DISPOSITION:default=1 DISPOSITION:dub=0 DISPOSITION:original=0 DISPOSITION:comment=0 DISPOSITION:lyrics=0 DISPOSITION:karaoke=0 DISPOSITION:forced=0 DISPOSITION:hearing_impaired=0 DISPOSITION:visual_impaired=0 DISPOSITION:clean_effects=0 DISPOSITION:attached_pic=0 DISPOSITION:timed_thumbnails=0 TAG:creation_time=2018-04-17T19:58:27.000000Z TAG:language=eng TAG:handler_name=Apple Alias Data Handler TAG:encoder=Apple ProRes 4444 XQ TAG:timecode=00:00:00:00 [/STREAM] [STREAM] index=1 codec_name=unknown codec_long_name=unknown profile=unknown codec_type=data codec_tag_string=tmcd codec_tag=0x64636d74 id=N/A r_frame_rate=0/0 avg_frame_rate=24/1 time_base=1/24 start_pts=0 start_time=0.000000 duration_ts=32 duration=1.333333 bit_rate=24 max_bit_rate=N/A bits_per_raw_sample=N/A nb_frames=1 nb_read_frames=N/A nb_read_packets=N/A DISPOSITION:default=1 DISPOSITION:dub=0 DISPOSITION:original=0 DISPOSITION:comment=0 DISPOSITION:lyrics=0 DISPOSITION:karaoke=0 DISPOSITION:forced=0 DISPOSITION:hearing_impaired=0 DISPOSITION:visual_impaired=0 DISPOSITION:clean_effects=0 DISPOSITION:attached_pic=0 DISPOSITION:timed_thumbnails=0 TAG:creation_time=2018-04-17T19:58:28.000000Z TAG:language=eng TAG:handler_name=Apple Alias Data Handler TAG:reel_name=B002_C037_06288E TAG:timecode=00:00:00:00 [/STREAM]

5 24

Synchronizing RTSP signals with FFMPEG
by Miguel Titos 27 Apr '18

27 Apr '18

Hi, I have achieved to merge two RTSP signals in one with FFMPEG but in the resulting stream, the first input has a delay of between 2 and 5 seconds with respect to the second. And it is always the first input that is delayed compared to the second. The two RTSP signals come from the same camera model, same configuration, same room ... However, if I put the same RTSP signal (either of the two) as input 1 and input 2, the same thing happens. Despite being the same signal, the first input is delayed compared to the second one. How could I get them synchronized? This is the command that I execute: ffmpeg -rtsp_transport tcp -thread_queue_size 512 -rtbufsize 50M -r 15 -i rtsp://XXXX -rtsp_transport tcp -thread_queue_size 512 -rtbufsize 50M -r 15 -c:a aac -i rtsp://XXXX -filter_complex "[0:v]pad=iw*2:ih,setpts=PTS-STARTPTS[bg]; [1:v]setpts=PTS-STARTPTS[fg]; [bg][fg]overlay=w[out]" -map "[out]" -f hls -hls_time 2 -hls_list_size 5 -use_localtime 1 -use_localtime_mkdir 1 -hls_segment_filename 'LIVE/file-%s.ts' -map a -ar 16000 -ac 1 -ab 64000 -c:a aac -y output.m3u8 Here you have the process information: ffmpeg version 3.4.2 Copyright (c) 2000-2018 the FFmpeg developers built with Apple LLVM version 9.0.0 (clang-900.0.39.2) configuration: --prefix=/usr/local/Cellar/ffmpeg/3.4.2 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --disable-jack --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma libavutil 55. 78.100 / 55. 78.100 libavcodec 57.107.100 / 57.107.100 libavformat 57. 83.100 / 57. 83.100 libavdevice 57. 10.100 / 57. 10.100 libavfilter 6.107.100 / 6.107.100 libavresample 3. 7. 0 / 3. 7. 0 libswscale 4. 8.100 / 4. 8.100 libswresample 2. 9.100 / 2. 9.100 libpostproc 54. 7.100 / 54. 7.100 [rtsp @ 0x7fe284000e00] Missing PPS in sprop-parameter-sets, ignoring Input #0, rtsp, from 'rtsp://XXXX': Metadata: title : Media Presentation Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1280x720, 15 fps, 15 tbr, 90k tbn, 30 tbc Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp [rtsp @ 0x7fe28484de00] Missing PPS in sprop-parameter-sets, ignoring Input #1, rtsp, from 'rtsp://XXXX': Metadata: title : Media Presentation Duration: N/A, start: 0.000000, bitrate: N/A Stream #1:0: Video: h264 (Main), yuv420p(progressive), 1280x720, 15 fps, 15 tbr, 90k tbn, 30 tbc Stream #1:1: Audio: aac (LC), 16000 Hz, mono, fltp Stream mapping: Stream #0:0 (h264) -> pad (graph 0) Stream #1:0 (h264) -> setpts (graph 0) overlay (graph 0) -> Stream #0:0 (libx264) Stream #0:1 -> #0:1 (aac (native) -> aac (native)) Press [q] to stop, [?] for help [libx264 @ 0x7fe286802000] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 [libx264 @ 0x7fe286802000] profile High, level 4.0 [libx264 @ 0x7fe286802000] 264 - core 152 r2854 e9a5903 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=1 weightp=2 keyint=250 keyint_min=15 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 [hls @ 0x7fe286800000] Opening 'LIVE/file-1524728763.ts' for writing Output #0, hls, to 'output.m3u8' Thanks in advance, Miguel

2 3

Unable to build ffmpeg-4.0 on fedora 20 release
by JD 27 Apr '18

27 Apr '18

I would like to send the make output file to someone who might want to look at all the warnings (deprecated calls), and errors. Would someone please tell me where to upload the file or who to send it to. Thanx!! jd

4 5

Video overlay of several network inputs using ffmpeg
by Hristo Ivanov Ivanov 26 Apr '18

26 Apr '18

Hi, I am trying to overlay several network inputs(udp streams). The command I have so far looks like this: .\ffmpeg.exe -threads auto -y -i input0 -i input1 \ -filter_complex "[0:v]scale=1920x1080[v0];[1:v]scale=480x270[v1];[v0][v1]overlay=1440:810[v2]" \ -map [v2] -map 0:a -c:v libx264 -preset ultrafast -c:a copy output.mp4 When input0 and input1 are files the resulting output is correct, on the other hand, when the inputs are udp streams the resulting output is not correct, the video freezes most of the time. The file inputs are generated from the udp streams, using the following command: .\ffmpeg.exe -threads auto -y -i "udp://@ip:port" -c copy -f mpegts input1.mpg Why is the above command not producing good ouput for upd streams? What are the differences between the original stream and the dump of that stream for `ffmpeg.exe`. How can it be fixed? Thanks.

2 1

Help with subtitles
by Andrea Chen Guerra 26 Apr '18

26 Apr '18

I have dealt with varios codes, but i would like to know to make softsubtitles of a mkv become forced, that is when they are reproduced they sctive innedistely without having to one without to extract them.

1 0

Adding Chapters to MP4 (Timebase and Formatting)
by Karen Norton 26 Apr '18

26 Apr '18

Hello all, After much testing I was finally able to get chapters added to an MP4 file but I have a couple questions. Firstly here's my environment: Windows 10 FFMPEG version: N-85588-g6108805 built with gcc 6.3.0 The metadata file and command line is based on what I found here: https://www.ffmpeg.org/ffmpeg-all.html#Metadata-1 The example from that page: ;FFMETADATA1 title=bike\\shed ;this is a comment artist=FFmpeg troll team [CHAPTER] TIMEBASE=1/1000 START=0 #chapter ends at 0:01:00 END=60000 title=chapter \#1 [STREAM] title=multi\ line Command line: ffmpeg -i INPUT -i FFMETADATAFILE -map_metadata 1 -codec copy OUTPUT I found some posts where people used TIMEBASE=1/1 instead of 1/1000 which seemed to be easier because it appears that the timecode (00:00:00) can be used instead of having to convert to milliseconds. Ex: TIMEBASE=1/1 START=00:02:05.500 END=00:06:35.500 The posts weren't related to the Timebase so I don't know whether it actually worked for the people who posted but when I tried this it added the chapters but they didn't work when I clicked on them. Ex: In VLC under playback>chapters I can see the chapters but each chapter goes back to the beginning of the video instead of going to their respective time markers. When I convert to milliseconds and use 1/1000 it works. Question 1: Does Timebase=1/1 work? Is this the correct syntax? I've been converting DVDs to MP4s and I have a program that extracts the chapter information from the DVDs so it's far easier to use that Timebase because I already have the Start/End info from the extracted DVD chapters. It took me awhile to convert that info to milliseconds so would prefer to use 1/1. My next question is regarding formatting the global metadata info (the info before the first [CHAPTER]). The "title" and "artist" info appears differently in different players. For example in Windows Media Player this data cycles between the two lines before disappearing. I use VLC and this info appears as the video starts but it looks awful. In my code I have: ;FFMETADATA1 title=Homecoming - Live In Ireland artist=Celtic Woman It looks like it's one line (although it separates into two lines after a certain number of characters) but it has these weird square boxes where the line should break and it adds a hyphen. Here's a screenshot: I thought maybe I would just try a multiline format in title= like it shows under [STREAM] but this didn't work. I'm not sure if multiline doesn't work in title= or whether I need something other than the backslash. I tried: title=Homecoming - Live From Ireland\ Celtic Woman It cutoff after the backslash. Question 2: Is there anyway to alter the formatting for VLC? It's not such a big deal given it disappears after about 30 seconds. It's just not pretty to the eye. :-D Thanks. Karen

1 0

FFmpeg issue subtitle text right-to-left
by Anurag Roy 25 Apr '18

25 Apr '18

Hello there, I am using ffmpeg from long time now and I am very happy to encode videos using ffmpeg. I encode videos in many different language subtitles. But now I am having issue with hebrew language as it reads from right-to-left but after hardcoding, the text appears left-to-right as usual. So Is it possible to get a coding for parameters to set the text layout as right-to-left. Kindly please help. sincerely anurag

2 1

Threads for H264 Encode.
by Vittalprasad 25 Apr '18

25 Apr '18

Hi I tried FFMPEG x264 to encode YUV contents, here encoding shared across all available threads, but i would like specify only one thread for that encoding job. please let me know the correct command. i tried below command which has no effect on thread control. time ./ffmpeg -f rawvideo -pix_fmt yuv420p -s:v 1920x1080 -r 30 -i test.yuv -c:v h264 -profile:v baseline -r 30 test.mp4 -threads 1 -- Thanks & Regards Vittal Prasad B R

2 1

Re: [FFmpeg-user] ProRes XQ 12-bit support
by Phil Rhodes 25 Apr '18

25 Apr '18

> On 4/25/18, Gonzalo Garramuno <ggarra13(a)gmail.com> wrote: >> >> >> El 24/04/18 a las 18:32, Elliott Balsley escribio: >>> Here are a few sources stating there is a 12-bit codec. Are you >>> suggesting they are all wrong? >> No, he is informing you that there's no 12-bit codec in ffmpeg. > > Please, do not spread lies. In an effort to control the clearly rising temperature of this discussion, I think it's worth being clear that this situation is fairly normal. People associated with the ffmpeg project have said some extremely ill-informed things about factors relevant to film and television postproduction before. For instance, a while ago we had someone here arguing against the behaviour of Arri's cameras in the recording of RGB ProRes. Back in 2007, there was an argument by some very senior project people that drop-frame timecode should be omitted because it was seen as untidy. For ages, ffmpeg had very dubious handling of colourspace and luminance range conversion because it simply wasn't seen as important. It's my observation that the people who work on ffmpeg are not postproduction engineers. That's fine, but they often will not accept advice from their better-informed and more experienced peers, and may be very impolite when well-meaning advice is offered. I think that's less fine, but hey, I'm not in charge. Phil | | Virus-free. www.avg.com |

2 1