[FFmpeg-user] ff* command lines that work

hydra3333 at gmail.com hydra3333 at gmail.com
Mon Mar 9 21:39:53 EET 2020

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" type questions and just pose generalities, looking like a complete troll, which is why people are unhappy with your questioning approach.

I occasionally have a problem working out a commandline to use a specific video filter here and there, but googling and playing with it usually resolves the issue.

Here's an example of commandline I sometimes use (the numbers are calculated in a script and substituted into the commandline on the fly), so go for your life.

"C:\SOFTWARE\ffmpeg\0-homebuilt-x64\ffmpeg.exe" -v verbose -nostats -init_hw_device opencl=ocl:0.0 -filter_hw_device ocl -i "D:\TEMP\SCRATCH\example.mp4" -map_metadata -1 -vsync 0 -sws_flags lanczos+accurate_rnd+full_chroma_int+full_chroma_inp -filter_complex "[0:v]yadif=0:0:0,hwupload,unsharp_opencl=lx=3:ly=3:la=0.5:cx=3:cy=3:ca=0.5,hwdownload,format=pix_fmts=yuv420p" -strict experimental -c:v h264_nvenc -pix_fmt nv12 -preset slow -bf 2 -g 50 -refs 3 -rc:v vbr_hq -rc-lookahead:v 32 -cq 22 -qmin 16 -qmax 25 -coder 1 -movflags +faststart+write_colr -profile:v high -level 5.1 -af loudnorm=I=-16:TP=0.0:LRA=11:measured_I=-22.79:measured_LRA=15.70:measured_TP=-0.34:measured_thresh=-34.06:offset=0.40:linear=true:print_format=summary -c:a libfdk_aac -cutoff 18000 -ab 384k -ar 48000 -strict experimental -movflags +faststart+write_colr -y "T:\TEMP\example2.mp4"

-----Original Message-----
From: ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> On Behalf Of Mark Filipak
Sent: Tuesday, March 10, 2020 3:56 AM
To: ffmpeg-user at ffmpeg.org
Subject: Re: [FFmpeg-user] ff* command lines that work

On 03/09/2020 12:55 PM, Carl Eugen Hoyos wrote:
> Am Mo., 9. März 2020 um 17:45 Uhr schrieb Mark Filipak
> <markfilipak.windows+ffmpeg at gmail.com>:
>> I can't discern between command lines that work and command lines 
>> that don't work and command lines that used to work but no longer and 
>> command lines that should work but haven't been tested or that have bugs.
>> I don't understand what's the problem?
>> I simply want ff* command lines -- any type -- that are known/proven 
>> to work.
> I (slowly) start to understand:
> This is not possible as command lines typically only work for specific 
> input...

Of course, I understand that.

> - depending on input, a command line that is "proven to work"
> only produces an error.
> (Yes, FFmpeg is not that easily scriptable.)

That's not correct. A command line that has worked, worked. I don't need general templates. I just want command lines that have worked. I will figure out why they are specific to specific cases.
ffmpeg-user mailing list
ffmpeg-user at ffmpeg.org

To unsubscribe, visit link above, or email ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".

More information about the ffmpeg-user mailing list