>On 19/06/2025 22.46, Carl Zwanzig wrote:
>> On 6/19/2025 7:07 PM, Mark Filipak wrote:
>>> On 19/06/2025 18.27, Rob Hallam wrote:
It is published. You can compile and distribute it to your heart's
content- that's one of the great things about Free software.
>>>
>>> I'm on Windows. There'
On 19/06/2025 08.03, Reindl Harald wrote:
> There is a FOSS clone of TextPad. It's named NotePad++. It's somewhat
pathetic.
Cough.
Had been sympathetic with making things clearer, but definitely lost me with
that and the FOSS "reasoning".
Oh dear.
Good luck with continuing to improve clarity w
-Original Message-
From: ffmpeg-user On Behalf Of Paul B Mahol
Sent: Wednesday, June 18, 2025 4:25 PM
To: FFmpeg user questions
Subject: Re: [FFmpeg-user] Yes or No? About the processing pipeline.
On Tue, Jun 17, 2025 at 11:19 PM Mark Filipak <
markfilipak.imdb-at-gmail@ffmpeg.org> w
Hello. Video filter 'colorspace' aborts with "Unsupported input primaries 2
(unknown)" with -f concat as input.
Is there a way to set/force those things between the filters 'scale' and
colorspace (or between input and the first filter) so that
colorspace works ?
In the examples below, bt470bg i
Hello. I am hoping to produce a slideshow from a list of jpeg images.
I was anticipating bt709 output from scale, however the log appears to show
it's producing bt470bg with limited range, even though I
specify out_color_matrix=bt709 and out_range=full
Any suggestions would be very welcome.
Ed
> On 2023-02-27 04:59 pm, hydra3...@gmail.com wrote:
> > the "colorspace=bt709:iall=bt601-6-625:fast=0" seems to be ignored entirely
> > and the resulting clip is BT709.
>
> This tells colorspace that the input is 601 and the output should be 709.
>
> And mediainfo shows the output to have 709, as
Hello.
I am attempting to shrink a progressive 1080p PAL clip to PAL DVD 576p and
change colorspace from bt709 to bt601.
Unfortunately I must be doing something wrong but I do not know what, since in
this filter complex:
-filter_complex
"pad=0:1080:0:-1,scale=720:576:flags='lanczos+accurate_rn
> Now climb back into your HOLE and die.
>
> Dave
I don't think I've seen a worse comment on any thread.
As soon as you see that type of post, you know there's either an unstable teen
or a damaged individual posting it.
No one should ever wish someone to die because your feelies are hurt. Peri
>amindfv--- via ffmpeg-user wrote:
>> Ironically the single reason this thread has devolved into personal attacks
>> and irrelevance to the original question is your own
contributions.
>
>"The single reason"? So I'm control of the keyboard of all participants in
>this thread?
>
>There was in fa
I just saw this about Google Magritte
"Magritte is an image redaction library to disguise the identity of persons in
photos and video streams."
"Google announced its machine learning tool called Magritte was going open
source. According to information sent to Gizmodo, the
tool detects objects in
Hello. I am attempting to use 64bit ffmpeg (built from latest git) on a
Raspberry Pi 4 (aarch64) and am seeing unexpected results.
The input is avc interlaced 1080i25 (PAL country) constant frame rate.
The ffmpeg command below should deinterlace and transcode into progressive avc
using the Pi's
> Subject: [FFmpeg-user] UDP NVENC HEVC transcoding
>
> Hello!
>
> I'm transcoding/resizing some UDP live streams using CUVID and NVENC. It
> works but I got the feeling could be better, this is the my command line:
>
> ffmpeg -vsync 0 -hwaccel cuvid -c:v h264_cuvid -resize 1280x720
> -drop_secon
> On Behalf Of Carl Eugen Hoyos
> Sent: Friday, July 31, 2020 8:27 AM
>> I have a .mpg with interlaced mpeg2 and ac3 audio, which needs
>> converting to progressive .mp4 avc/aac.
>>
>> The interlaced video is a bit grainy etc so I hope to deinterlace and
>> clean it up using vapoursynth CUDA fi
Hello.
I have a .mpg with interlaced mpeg2 and ac3 audio, which needs converting to
progressive .mp4 avc/aac.
The interlaced video is a bit grainy etc so I hope to deinterlace and clean it
up using vapoursynth CUDA filters and at the same time convert the audio, using
a single commandline, pe
> Extract of "C:\SOFTWARE\ffmpeg\0-homebuilt-x64\ffmpeg.exe" -hide_banner -v
> debug -h encoder=h264_nvenc
> -rcE..V.. Override the preset rate-control
> (from -1 to INT_MAX) (default -1)
> constqp 0E..V.. Constant QP mode
> vbr
Hello,
I just cross-compiled ffmpeg about an hour ago to try out the new nvenc
options, and received an error (see below).
It says "-rc:v vbr_hq" is an older older 2 Pass RC Mode, but doesn't indicate
in the help (also see below) that is older nor which is newer and shoould be
used.
There is
Hello. Seeking clarification from some kind soul(s) on how to use ffmpeg's
new NVEnc encoder options arising from use of the Nvidia Video SDK 10.
I notice with delight four new patches to do with Nvidia NVEnc and Video SDK
10.
https://github.com/FFmpeg/nv-codec-headers/commit/5ee2ae591f74f53b
Well, I'm a dumb user and google gave me LOTS and LOTS of commandlines that
work - simply filter the google results by the "date in the last year" to be
sure you get the latest syntax. Lots.
You appear to continually avoid "what is it you wish to do with a specific
example video that you have"
Ah, had a look at the code and "-rc-lookahead" forces b-adapt and i-adapt to
become off.
[url]https://git.videolan.org/?p=ffmpeg.git;a=blob;f=libavcodec/nvenc.c;h=11
1048d043263fc852dfbe48912b378f1b2d7977;hb=ba6b20df3f74a6092dc01023b07760da58
188d82[/url]
Not sure what the real-world effect of rem
8000 -ab 384k -ar 48000 -y
"T:\HDTV\Converted\test.hevc.mp4"
ffmpeg version N-95812-gd73f062706-hydra/v02_courtesy_DeadSix27 Copyright
(c) 2000-2019 the FFmpeg developers
built with gcc 9.2.0 (GCC)
configuration: --arch=x86_64 --target-os=mingw64
--cross-prefix=x86_64-w64-m
Morton, in accordance with the rules, I see you have been requested not to top
post.
Here's a link explaining what it means :
https://en.wikipedia.org/wiki/Posting_style#Top-posting
Cheers
<>___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffm
t experimental -profile:v main -level
6 -movflags +faststart+write_colr -af
loudnorm=I=-16:TP=0.0:LRA=11:measured_I=-24.63:measured_LRA=14.00:measured_TP=-6.33:measured_thresh=-35.74:offset=0.10:linear=true:p
rint_format=summary -c:a libfdk_aac -cutoff 18000 -ab 384k -ar 48000 -y
"T:\HDTV\Conver
> On 22-11-2019 07:23 pm, Carl Eugen Hoyos wrote:
> ...
> The MOV muxer does
> default to CFR mode but ffmpeg switches to VSCFR mode when there's only
> one video stream being output with a non-zero first pts, In this mode,
> the gap at the head of the stream will be filled.
>
> Maybe the switch t
=dar=16/9"
-c:v
hevc_nvenc -pix_fmt nv12 -preset slow -rc:v vbr_hq -2pass 1 -rc-lookahead:v 32
-cq 22 -qmin 14 -qmax 32 -spatial_aq 1 -temporal_aq 1
-strict experimental -movflags +faststart+write_colr -profile:v main -level 6
-an -y "G:\HDTV\test\ABC ME.2019-11-20.ts.h265.mp4"
ff
OK, just for completeness then, these work, as mentioned here
https://forum.videohelp.com/threads/392398-FFMPEG-and-new-GPU-based-YADIF_CU
DA-deinterlacer#post2544357
Result = slower to use yadif_cuda with unsharp_opencl than vanilla yadif
with unsharp_opencl
-
> Hello, seeking help to use the newly updated FFMPEG filter YADIF_CUDA.
>
> I keep getting error "Impossible to convert between the formats supported
by the filter 'graph 0 input from stream 0:0' and the filter
'auto_scaler_0'"
>
> I'm obviously doing something wrong in (not?) converting betwe
Hello, seeking help to use the newly updated FFMPEG filter YADIF_CUDA.
I keep getting error "Impossible to convert between the formats supported
by the filter 'graph 0 input from stream 0:0' and the filter
'auto_scaler_0'"
I'm obviously doing something wrong in (not?) converting between format
Hello, 2 things.
1 Apparently ffmpeg can be built with --enable-gcrypt so I thought I'd give
it a try.
libgpg-error is a dependency of libgcrypt.
One or both of two recent commits in
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgpg-error.git;a=summary
seems to cause an error building libgcrypt
> From: ffmpeg-user On Behalf Of
> Moritz Barsnick
> Sent: Tuesday, November 27, 2018 1:03 AM
> To: FFmpeg user discussions
> Subject: Re: [FFmpeg-user] L-SMASH-WORKS and replacement for
> deprecated ffmpeg --enable-avresample
>
> On Tue, Nov 27, 2018 at 00:26:09 +1030, hydra3...@gmail.com wrote
Hello. I gather that when built from source, x264.exe can
- input various container formats if built with "lavf support" (from
ffmpeg).
- output various container formats if built with "L-SMASH support" (from
L-SMASH-WORKS) https://github.com/VFR-maniac/L-SMASH-Works
eg from it's help:
Infile ca
Hello. I have an issue with using yadif and OpenCL (opencl with the
latest
git updates) in combination.
Using the latest ffmpeg master built as at 2017.11.26, I'm having trouble
deciphering what the error messages means and, more importantly, what to
do
about them.
Changing from -vf to -filt
Hello. I have an issue with using yadif and OpenCL (opencl with the latest
git updates) in combination.
Using the latest ffmpeg master built as at 2017.11.26, I'm having trouble
deciphering what the error messages means and, more importantly, what to do
about them.
Changing from -vf to -filter_
Hello. I have an issue with using yadif and OpenCL (opencl with the latest
git updates) in combination.
Using the latest ffmpeg master built as at 2017.11.26, I'm having trouble
deciphering what the error messages means and, more importantly, what to do
about them.
Changing from -vf to -filter_
33 matches
Mail list logo
