roma_inp -strict experimental
-filter_complex "[0:v]yadif=0:0:0,format=pix_fmts=yuv420p"
-c:v h264_v4l2m2m -pix_fmt yuv420p -rc VBR -b:v 400 -qmin 10 -qmax 51
-profile:v high -level 4.2 -shm separate_buffer -rsh 0
-g:v 25 -movflags +faststart+write_colr -an -y
"./output_file_
ix_fmt yuv420p -rc VBR -b:v 400 -qmin 10 -qmax 51
-profile:v high -level 4.2 -shm separate_buffer -rsh 0
-g:v 25 -movflags +faststart+write_colr -an -y
"./output_file_tiny_h264_VBR_g25.mp4"
Signed-off-by: hydra
---
libavcodec/v4l2_m2m.h | 12 +
libavcodec/v4l2_m2m_enc
accurate_rnd+full_chroma_int+full_chroma_inp -strict experimental
-filter_complex "[0:v]yadif=0:0:0,format=pix_fmts=yuv420p"
-c:v h264_v4l2m2m -pix_fmt yuv420p -rc VBR -b:v 400 -qmin 10 -qmax 51
-profile:v high -level 4.2 -shm separate_buffer -rsh 0
-g:v 25 -movflags +faststart+write_c
> On 2022-02-16 02:37, Stephen Hutchinson wrote:
> > There is another option, basically what Gyan suggested earlier: grab the
> > release build of 3.7.1, fetch the extra headers from the Github repo,
> > then copy either all the contents of the tarball's /usr directory into
> > the system /usr dir
On 31.01.2021 10:06, hydra wrote:
> > When cross-compiling ffmpeg and sdl2 under ubuntu/mingw64 -
> >
> > ffmpeg builds with sdl2 2.0.12 ok
> > however it fails to build with sdl2 2.0.14
> >
> > If someone has done it, any advice on how to build with s
On 2021-01-31T16:45:08+0100, Timo Rothenpieler wrote:
> > Not sure what to make of that attachment to your mail. Is that supposed to
> > be a log?
> hydra, please have a look at http://support.microsoft.com/kb/278061/en.
>
> --
> Re
On 31.01.2021 10:06, hydra wrote:
> > When cross-compiling ffmpeg and sdl2 under ubuntu/mingw64 -
> >
> > ffmpeg builds with sdl2 2.0.12 ok
> > however it fails to build with sdl2 2.0.14
> >
> > If someone has done it, any advice on how to build with s
When cross-compiling ffmpeg and sdl2 under ubuntu/mingw64 -
ffmpeg builds with sdl2 2.0.12 ok
however it fails to build with sdl2 2.0.14
If someone has done it, any advice on how to build with sdl2 2.0.14 would be
appreciated.
<>___
ffmpeg-devel mail
> > Hello,
> >
> > This patch adds Video Codec SDK 10 features support:
> >
> > * Presets and tuning info
> > * Multipass encode modes
> > * Low Delay Key Frame Scale
>
>
> Hello and thank you for this patch. Possibly this post belongs in
ffmepg-user.
>
> Per the above archive post ab
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft Works
> Sent: Wednesday, July 1, 2020 1:34 PM
> To: Roman Arzumanyan ; FFmpeg development discussions
> and patches
> Cc: Yogender Gupta
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Video Codec SDK 10
> features suppor
> Hello,
>
> This patch adds Video Codec SDK 10 features support:
>
> * Presets and tuning info
> * Multipass encode modes
> * Low Delay Key Frame Scale
Hello and thank you for this patch. Possibly this post belongs in
ffmepg-user.
Per the above archive post above (
http://ffmpeg.or
On 27.10.19 02:14, hydra at gmail.com wrote:
> > I see the attachment (attached by outlook) was scrubbed.
> > Sorry, I'd hoped it would work.
> > So, patch just pasted below to see if that works.
> >
> Please use git send-email. It's the easiest way to
htly modify relevant error messages
and change error messages in nvenc_check_capabilities to be issued
as warnings instead of verbose.
Thank you for considering the patch.
hydra (1):
Slightly update nvenc error messages and warnings
libavcodec/nvenc.c | 40 +--
---
libavcodec/nvenc.c | 40 +---
1 file changed, 21 insertions(+), 19 deletions(-)
diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
index bbb43ddad8..a18eb1df89 100644
--- a/libavcodec/nvenc.c
+++ b/libavcodec/nvenc.c
@@ -321,39 +321,39 @@ static int nvenc
> On 14.10.2019 18:56 Timo Rothenpieler wrote:
> > On 14.10.2019 17:43, Hendrik Leppkes wrote:
> > > Since some users seem to have blindly passed -refs to their
> > > commandline which now fails without really telling them why, any
> > > thoughts on moving the capability check error messages onto a
On 14.10.2019 18:56 Timo Rothenpieler wrote:
> On 14.10.2019 17:43, Hendrik Leppkes wrote:
> > Since some users seem to have blindly passed -refs to their
> > commandline which now fails without really telling them why, any
> > thoughts on moving the capability check error messages onto a high log
>>On Wed, Feb 6, 2019 at 9:51 PM Carl Eugen Hoyos
>>wrote:
>>>We already provide a build script and we believe that it works very
>>>well, in addition a kind supporter offers osx binaries.
>>
>>That's all true, but not all users want to build manually (or have the
>>technical skills to understa
> -Original Message-
> From: ffmpeg-devel On Behalf Of Tobias Rapp
> Sent: Friday, July 6, 2018 8:16 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] New build system
>
> On 04.07.2018 16:36, Mathieu Duponchelle wrote:
> > [...]
> >
> > If there are any other questions
never mind. found something that works, only posted here for closure.
eg
.\ffmpeg.exe -hide_banner -v verbose -init_hw_device
opencl=ocl:1.0 -filter_hw_device ocl -i
".\test_01.mpg" -an -map_metadata -1 -sws_flags
lanczos+accurate_rnd+full_chroma_int+full_chroma_inp -filter_complex
"[0:v]yad
OK and thank you, these do work fine and produce handy results and the
documentation you linked works.
".\ffmpeg_3.latest_master.exe" -v verbose -init_hw_device list
".\ffmpeg_3.latest_master.exe" -v verbose -init_hw_device opencl
I'll head over to ffmpeg-user (and do some reading) to find out
Most systems have a "clinfo" program which will list all the queryable
properties of the available devices.
From docs:
-init_hw_device type[=name][:device[,key=value...]]
Initialise a new hardware device of type type called name, using the
given device parameters. If no name is specified
-Original Message-
From: hydra3...@gmail.com
Sent: Sunday, November 26, 2017 11:37 PM
To: ffmpeg-devel@ffmpeg.org
Cc: hydra
Subject: Re: [FFmpeg-devel] [PATCH 00/15] OpenCL infrastructure, filters
OK, the experimental -opencl_bench option has been removed by recent
commits.
Thank
OK, the experimental -opencl_bench option has been removed by recent
commits.
Thank you for the updates to OpenCL.
It cross-compiles OK, however I'm not sure about the replacement
functionality. So, 2 things.
1. may I enquire how one ascertains the numbers to use like this ?
-opencl_option
Hello. Per ticket https://trac.ffmpeg.org/ticket/6731 I too am having
trouble cross-compiling ffmpeg.
This is the configure being used
./configure --arch=x86 --target-os=mingw32 --cross-prefix=/home/u/Desktop/ffmpeg-windows-build-helpers-withOpenCL-master/sandbox/cross_compilers/mingw-w64-i68
ffmpeg no longer builds with the openjpeg dependency as built
from its git.
The patch seems to fix ffmpeg so that it builds with openjpeg v2.3 as a
dependency built from its git.
From 80412c4b26d197e9627b097443e7032c106de4ff Mon Sep 17 00:00:00 2001
From: hydra
Date: Fri, 6 Oct 2017 02:19:34
25 matches
Mail list logo
