On 24/03/2024 15:48, Mark Filipak wrote:
I cut at the end of an open GOP. When I did that, FFmpeg did not set the MPEG
'broken_link' flag to '1'.
The frame following the cut has to be flagged:
'closed_gop' = '0' because it's an open GOP, also, and
'broken_link' = '1'.
How do I do that? I
On 20/01/2021 03:06, owen s wrote:
with software libx264 using crop filter
crop=width:heigh:x:y, i could crop around a specific point. using
h264_vaapi and -vf crop=width:height
doesn't control the crop location.
also with libx264 -video_size=widthxheight worked, but with h264_vaapi, the
video
On 19/01/2021 16:07, owen s wrote:
I am running this command with
ffmpeg -y -loglevel debug \
-vaapi_device /dev/dri/renderD128 \
-loop 1 -r 1 -i ./image.jpg -pix_fmt vaapi_vld \
-b:v 18000k -minrate 18000k \
-vf 'format=nv12|vaapi,hwupload,scale_vaapi=w=1280:h=720' \
-rc_mode 3 \
-r 30 -g 60 \
On 19/01/2021 14:47, alfonso santimone wrote:
Hi all,
how can i convert a H.264 High L5.0 .mov video to a H.264 High L5.1 or L4.0
.mov video without loosing to much quality?
I've tried...
ffmpeg -i input.mov -c:v libx264 -profile:v high -level:v 4.0 -c:a copy
output.mov
but from a 02:46
On 06/02/2020 06:11, Kai Hendry wrote:
> Hi there,
>
> For sometime I've been happily using kmsgrab to make screencasts on my
> Archlinux Xorg desktop.
>
> https://github.com/kaihendry/recordmydesktop2.0/blob/9825a44d886318d78463c0a602681c0c7931cf83/x11capture#L71
>
> But then it broke after a
On 30/01/2020 11:00, test wrote:
> Hi All. Thanks in advance for any assistance provided.
>
> I've been trying to get kmsgrab to work on my second rx570.
> Aim is to record multiple framebuffers on both cards. Both cards are
> maxed in terms of CRTC's, so switching all to one card isn't an
>
On 17/09/2019 17:33, JackDesBwa wrote:
> Hi,
>
> I do stereoscopic (3d) photography for a few years and I just start to
> experiment on stereoscopic videos.
> The filter_complex argument of ffmpeg allows me to do the editing I have in
> mind more precisely and less painfully than I was able to do
On 27/10/18 17:24, Ronak wrote:
> Hi all,
>
> I'm trying to build the latest HEAD version of Ffmpeg on Linux on the
> following platform.
>
> Linux 4.9.124-0.1.ac.198.71.329.metal1.x86_64 #1 SMP Thu Aug 30 20:39:05 UTC
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> But, I'm getting compilation
On 25/06/18 10:42, Moritz Barsnick wrote:
> On Mon, Jun 25, 2018 at 09:10:29 +0800, Kai Hendry wrote:
>> However since kmsgrab requires CAP_SYS_ADMIN as it points out to its
>> friendly documentation
>> https://www.ffmpeg.org/ffmpeg-devices.html#kmsgrab I believe I need to
>> run it with `sudo`.
>
On 18/06/18 21:32, Victor Helmholtz wrote:
> Hi,
>
> I am trying to encode raw yuv file using VAAPI hardware acceleration on a
> machine with i7-6700 CPU running Debian 9 “Stretch” but I am getting error “A
> hardware frames reference is required to associate the encoding device.”. I
> have
On 17/06/18 21:30, Carl Eugen Hoyos wrote:
> 2018-06-17 22:00 GMT+02:00, Mark Thompson :
>
>> Intel devices do not support MPEG-4 part 2 at all. If you are using
>> the Mesa driver on an AMD device, some MPEG-4 part 2 streams
>> may be supported if you set
On 13/06/18 21:00, André Hänsel wrote:
>> Can you retest with git head?
>>
>> Build FFmpeg from source and retest.
>
> I don't think I can do that easily, but I found a static build on the FFmpeg
> website. It's supposed to support VAAPI:
>
> # ./ffmpeg -hwaccels
>
> ffmpeg version
On 13/06/18 19:22, André Hänsel wrote:
> When I scale with scale_vaapi, it results in a green line at the bottom of
> the image, see attachment.
>
> Command line:
> ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128
> -hwaccel_output_format vaapi -i bbb.mp4 -vf
>
On 13/06/18 11:29, André Hänsel wrote:
> I'm trying to transcode an MPEG4 avi to MP4 with VAAPI, but I'm getting an
> error:
>
> Impossible to convert between the formats supported by the filter
> 'Parsed_null_0' and the filter 'auto_scaler_0'
> Error reinitializing filters!
> Failed to inject
is probably a
reasonable strategy.
- Mark
> -Message d'origine-
> De : ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] De la part de Mark
> Thompson
> Envoyé : jeudi 24 mai 2018 12:22
> À : ffmpeg-user@ffmpeg.org
> Objet : Re: [FFmpeg-user] h264 pic_init_qp_minus26 out o
On 24/05/18 10:46, Phillipe Laterrade wrote:
> Hello,
>
>
>
> I'm experiencing a problem when transcoding to h264 :
>
> The pic_init_qp_minus26 parameter is out of range (-28,-30,-31..) on some
> files but not on the whole transcoded files.
The range of pic_init_qp_minus26 is [-26 - 6 *
On 27/04/18 02:28, JD wrote:
> On 04/26/2018 06:56 PM, Kieran O Leary wrote:
>> On Fri, 27 Apr 2018, 01:29 JD, wrote:
>>
>>> 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
On 23/03/18 21:37, Piergiorgio Sartor wrote:
> Hi all,
>
> I've recently got a Nvidia GT1030 graphic card,
> which should be Pascal generation, supporting
> HEVC encoding.
>
> The system is Fedora 27, up to date, with
> official Nvidia driver and CUDA libraries form
> rpmfusion repository.
>
On 23/03/18 13:15, Carl Eugen Hoyos wrote:
> 2018-03-23 14:12 GMT+01:00, Mark Thompson <s...@jkqxz.net>:
>> On 23/03/18 01:28, Kai Hendry wrote:
>>> Thank you Moritz! Damn, I feel like a fool. ;)
>>>
>>> Unfortunately Mark's suggestion doesn't seem to ha
On 23/03/18 01:28, Kai Hendry wrote:
> Thank you Moritz! Damn, I feel like a fool. ;)
>
> Unfortunately Mark's suggestion doesn't seem to have an impact.
>
> As you hopefully can see here:
> https://s.natalian.org/2018-03-23/1521768226.mp4
>
> The mouse still doesn't move smoothy across the
On 20/03/18 10:24, Kai Hendry wrote:
> Hi Mark,
>
> On 20 March 2018 at 17:58, Mark Thompson <s...@jkqxz.net> wrote:
>> Show your command line? The pts values in that file are quite uniform,
>> suggesting that you've forced the output to be treated as if it is 30/10
On 20/03/18 02:30, Kai Hendry wrote:
> Hi there,
>
> With my brand new Intel 8th gen laptop (Intel Corporation UHD Graphics
> 620 (rev 07) with 8 core Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz on
> Archlinux, I thought I'd experiment with hardware accelerated capture
> as opposed to my normal
On 01/03/18 11:57, oktay eşgül wrote:
> Hi,
>
> I am trying to encode webrtc vidyo call records.Currently,we have Nvidia
> 1080ti GPu and using cuda.
>
> Yet ,current gpu do not support webm encoding. Need to figure out
> applicable hardware to be able to use webm encoding.
>
> As far as I
On 16/02/18 15:03, Piotr Oniszczuk wrote:
>
>
>>
>> VDPAU is fully supported via the hwaccel API and is usable in the ffmpeg
>> program via the -hwaccel option. The (deprecated for years) standalone
>> VDPAU decoder which you are trying to use here was removed from master with
>> the
On 16/02/18 12:55, Piotr Oniszczuk wrote:
> Carl,
> Thx for prompt replay.
> Pls see in-line
>
>> Wiadomość napisana przez Carl Eugen Hoyos w dniu
>> 16.02.2018, o godz. 11:22:
>>
>> 2018-02-16 11:00 GMT+01:00 Piotr Oniszczuk :
>>
>>> -I have some
r:1/1 -> w:426 h:240
> fmt:yuv420p sar:640/639 flags:0x2
> [hwupload @ 0x54102c0] Surface format is yuv420p.
> [Parsed_overlay_opencl_5 @ 0x5415580] [framesync @ 0x54156d0] Selected
> 1/9 time base
> [Parsed_overlay_opencl_5 @ 0x5415580] [framesync @ 0x54156d0] Sync level 2
> [Parsed_overlay_opencl_5 @ 0x5415580] Using kernel overlay_no_alpha.
> [Parsed_overlay_opencl_5 @ 0x5415580] Fail
On 09/01/18 06:01, 郭浩 wrote:
> i want to use overlay_opencl, and i build the ffmpeg with opencl success! but
> i run the command , it alway report "[Parsed_overlay_opencl_5 @ 0x4f22e80]
> Failed to finish command queue:",i am not sure my command is correct , can
> someone tell me how this
On 29/11/17 12:58, Carl Eugen Hoyos wrote:
> 2017-11-29 11:19 GMT+01:00 Zhenan Lin :
>
>> CONFWIN_A_Sony_1/CONFWIN_A_Sony_1/CONFWIN_A_Sony_1.bit
>> HM 16.9: a3ce3f936ff69ff1ec2621a622dd37ac
>> FFmpeg: c0a13e81b3a68c4263f240eb99a281b0
>
> Needs "-vf crop=412:236:2:0" for
On 05/10/17 07:48, Carl Eugen Hoyos wrote:
> 2017-10-04 23:20 GMT+02:00 Mark Thompson <s...@jkqxz.net>:
>> On 03/10/17 21:22, Jonathan Viney wrote:
>>> On Tue, Oct 3, 2017 at 1:56 PM, Mark Thompson <s...@jkqxz.net> wrote:
>>>
>>>> On 03/10/17
On 03/10/17 21:22, Jonathan Viney wrote:
> On Tue, Oct 3, 2017 at 1:56 PM, Mark Thompson <s...@jkqxz.net> wrote:
>
>> On 03/10/17 00:56, Jonathan Viney wrote:
>>> Hi,
>>>
>>> I am pulling an RTSP stream from an Axis 4K IP camera. The stream from
On 03/10/17 00:56, Jonathan Viney wrote:
> Hi,
>
> I am pulling an RTSP stream from an Axis 4K IP camera. The stream from the
> camera is 30fps, but the resulting stream from ffmpeg is 29.97fps. Here is
> the command:
>
> ffmpeg -rtsp_transport tcp -i rtsp://10.9.9.1:554/axis-media/media.amp
>
On 28/05/17 12:22, Andy Furniss wrote:
> ==13089== HEAP SUMMARY:
> ==13089== in use at exit: 1,641,516,251 bytes in 201,131 blocks
> ==13089== total heap usage: 2,075,668 allocs, 1,874,537 frees,
> 68,823,339,225 bytes allocated
> ==13089==
> ==13089== 368 bytes in 1 blocks are possibly
On 28/02/17 18:52, w_boba wrote:
> Mark,
>
> As I have mentioned in my first post, I am working with ffmpeg version
> n3.2.4-4-g36fff6c, which is near-current, and commit you have mentioned is
> dated Dec 2016. I believe that commit is already included in my branch, last
> commit I see there is
On 28/02/17 17:25, w_boba wrote:
> I forgot to add: "CodecPrivateData" attribute is "required" for SmoothStream
> according to MS document:
>
> https://msdn.microsoft.com/en-us/library/ff728116%28v=vs.95%29.aspx
I'm not familiar with this format at all, but it looks like it will be
generating
On 20/12/16 18:21, Anton Sviridenko wrote:
> I want to use hardware acceleration for processing multiple realtime
> videostreams (coming over RTSP).
> I've read this thread -
> http://ffmpeg.org/pipermail/ffmpeg-user/2016-December/034530.html
>
> and have some questions related to scaling this
On 05/12/16 12:51, Archer Chang wrote:
> I use the VAAPI HW ACCEL to transcode file to the FLV format that the
> command as follows.
>
> ffmpeg -vaapi_device /dev/dri/renderD128 -hwaccel vaapi
> -hwaccel_output_format vaapi -hwaccel_lax_profile_check -i infile.mkv -vf
>
ode directly from the ffmpeg utility into your
application if you want (assuming you comply with the licence terms).
- Mark
> On Fri, 2 Dec 2016, at 09:03 PM, Mark Thompson wrote:
>> On 02/12/16 10:57, Victor dMdB wrote:
>>> I was wondering if there were any examples of impleme
On 02/12/16 10:57, Victor dMdB wrote:
> I was wondering if there were any examples of implementations with
> avformatcontext?
>
> I've looked at the source of ffmpeg vaapi implementation:
> https://www.ffmpeg.org/doxygen/trunk/ffmpeg__vaapi_8c_source.html
>
> and there is a reference to the cli
On 23/11/16 11:48, desktop ready wrote:
> On Wed, 23 Nov 2016 10:00:25 +0000, Mark Thompson <s...@jkqxz.net> wrote :
>
>> On 23/11/16 03:09, desktop ready wrote:
>>> Hello,
>>>
>>> I would like to confirm a bug/problem before submitting a bug
>>&
On 23/11/16 03:09, desktop ready wrote:
> Hello,
>
> I would like to confirm a bug/problem before submitting a bug report.
> I am working on Debian Jessie/Stable amd64 on an Intel Skylake i3-6320
> and would like to decode an HEVC 8-bit encoded UHD movie.
>
> With a fresh ffmpeg github checkout
On 08/11/16 21:59, Mark Thompson wrote:
> On 08/11/16 12:17, 肖文良 wrote:
>> Built from the latest git source seems not help.
>>
>> following command runs about 15+ seconds. nothing was captured. If I add
>> -loglevel debug, this log keep being printed:
>>
>&g
On 19/06/16 00:34, Andy Furniss wrote:
> Mark Thompson wrote:
>>
>> So, I also went and built mesa with the encode patches and had a go. With
>> the changes above, it does get to actually trying to encode, but that nuked
>> my GPU to the point of requiring reboot.
On 18/06/16 16:37, Mark Thompson wrote:
> On 17/06/16 23:33, Andy Furniss wrote:
>>
>> AMD are working on vaapi encode for mesa, only a few patches about so far
>> and they got rejected - though not for functionality.
>>
>> They do work with gstreamer, but trying
On 17/06/16 23:33, Andy Furniss wrote:
>
> AMD are working on vaapi encode for mesa, only a few patches about so far and
> they got rejected - though not for functionality.
>
> They do work with gstreamer, but trying above with ffmpeg fails as below
> (render node or X) seems the surface is
On 13/05/16 20:43, Armin K. wrote:
> I noticed that recently a VAAPI based H264 encoder was added to ffmpeg.
> I built ffmpeg from git and now I have h264_vaapi listed in ffmpeg -encoders
> output.
>
> However, when I try to use ffmpeg ... -vcodec h264_vaapi I get the following
> error:
>
>
45 matches
Mail list logo