clever FFmpeg-GUI, small FFmpeg UI, fully portable, no installation.

[Findu]

Thanks for fixing!
The unsharp filter matrix check also works well.

---

Retesting with ffmpeg 8.0
The combination of qsv encoding and qsv filter slows down the encoding speed for me compared to the normal filter.
For example the scale down from 4k h264 to 800x450 h264.

11,7x with 50 % GPU decoding
ffmpeg -i Input.mp4 -vf scale=800:450 -map 0:0 -c:v h264_qsv -global_quality 25 Output.mp4

9,29x with 80 % GPU decoding and 100 % GPU video processing
ffmpeg -hwaccel qsv -hwaccel_output_format qsv -i Input.mp4 -vf vpp_qsv=w=800,vpp_qsv=h=450 -map 0:0 -c:v h264_qsv -global_quality 25 Output.mp4

BTW: On the Intel system I can't use qsv HWA decoding with normal filters like resize or rotation etc. As it is expected to use the qsv filter vpp_qsv.
But that's fine for my system because the vpp_qsv filter works slower than the normal filter.

[videoAI]

Thanks for fixing ..

Other filters values bled into Time Lapse

Thx for testing and the hint, is fixed now.

[Findu]

@ ProWo

How about this text change?

[Attachment 88778 - Click to enlarge]

[Attachment 88779 - Click to enlarge]

[davidt1]

v3.4.5.19 still does not select all streams.


[Attachment 88780 - Click to enlarge]


v3.4.4 selects all streams.


[Attachment 88781 - Click to enlarge]

[Findu]

@ ProWo

You set the "Start at second" value in the Preview of "Crop detection" to the "Actual crop at" time, but I can not change that value in the Preview.
Is that intentional?

[ProWo]

You set the "Start at second" value in the Preview of "Crop detection" to the "Actual crop at" time, but I can not change that value in the Preview.
Is that intentional?

The preview is done at the value in "Actual crop".
You can change this value.

[ProWo]

v3.4.5.19 still does not select all streams.

Found the bug. With the next nightly it's fixed.

[ProWo]

How about this text change?

Will be done.

[davidt1]

v3.4.5.20 selects all streams. Thank you, ProWo.

[tb52]

Hi, I'm enjoying using Clever FFMpeg... I have a question I haven't found an answer to.

Can you describe how each of the 5.1 > 2 downmix options affect the resulting stereo mix in plain English?

Thanks very much, tb

[Findu]

@ ProWo

>> You set the "Start at second" value in the Preview of "Crop detection" to the "Actual crop at" time, but I can not change that value in the Preview.
> The preview is done at the value in "Actual crop". You can change this value.

Yes, I know.
When the file contain only one video and one audio stream, the "Preview settings" window does not show up. So this is the only way to change the start time of the crop preview.
When the file contain more audio streams, the "Preview settings" window show up to be able to select the audio stream of the crop preview.
But in what scenario is a specific audio stream important for crop?
It would make more sense to be able to change the start time of the preview again, for example to be able to jump to bright film passages to see whether there are still black edges that need to be cut away. Even for files with only one audio stream.

[ProWo]

I have a question I haven't found an answer to.
Can you describe how each of the 5.1 > 2 downmix options affect the resulting stereo mix in plain English?

See here:
https://jellyfin.org/docs/general/post-install/transcoding/downmix/
and here:
https://superuser.com/questions/852400/properly-downmix-5-1-to-stereo-using-ffmpeg

[ProWo]

When the file contain more audio streams, the "Preview settings" window show up to be able to select the audio stream of the crop preview.
But in what scenario is a specific audio stream important for crop?

This was a user request.
But I agree; audio has nothing to do with video cropping. Maybe I should remove audio altogether here.

BTW: You can change the position of the video in the preview window by right-clicking on an imaginary horizontal line in the image.

[Findu]

It is okay to use a singel "Preview settings" window for all previews.
Audio is sometimes the main reason to cut recordings. So it should remain.
Just make the "Start at second" value changeable in crop. It is a good idea to start the preview directly from the "Actual crop".

[Findu]

> BTW: You can change the position of the video in the preview window by right-clicking on an imaginary horizontal line in the image.

Cool!
You can make this great feature more understandable for everyone by attaching it to the "FFplay player controls" window.

[Attachment 88792 - Click to enlarge]

[tb52]

Thanks very much for the fast response. That's exactly what I needed. ~ tb52

[videoAI]

Interesting ..
BBcodec-Browser-Based-FFmpeg

[videoAI]

VAAPI Support for AMD GPUs on Windows

VAAPI can now be used for FFmpeg hardware acceleration on Windows for AMD GPUs, but with some important notes:

Key Developments
- Microsoft has recently added VAAPI support on Windows through:
1. A new libva-win32 node (since libva 2.17)
2. A VA-API driver called VAOn12, implemented on top of Direct3D 12 Video APIs
- This enables cross-platform VA-API acceleration that works across different hardware vendors

Implementation Details
- The new implementation uses Direct3D 12 as a backend
- Supports VA-API entry points similar to those on Linux
- Allows GPU adapter selection via `vaGetDisplayWin32` function

Practical Considerations
- Support is still relatively new & may have limitations
- Performance can vary depending on your specific AMD GPU & driver version
- Full hardware acceleration might not be guaranteed for all video processing tasks

Recommended FFmpeg Command:

ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i input.mp4 -c:v h264_vaapi output.mp4

To provide more context about VAAPI & FFmpeg hardware acceleration for AMD GPUs on Windows:

Current Status
- VAAPI is now supported on Windows for AMD GPUs
- Implemented through a new libva-win32 node (since libva 2.17)
- Uses Direct3D 12 Video APIs as a backend (VAOn12 driver)

Limitations & Considerations
- Support is still relatively new
- Performance may vary depending on:
1. Specific AMD GPU model
2. Driver version
3. FFmpeg version
- Full hardware acceleration is not guaranteed for all video processing tasks

Recommended Approach:
When using VAAPI on Windows with AMD GPUs, try:

# Basic hardware acceleration
ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i input.mp4 -c:v h264_vaapi output.mp4

# With additional filtering
ffmpeg -vaapi_device /dev/dri/renderD128 -i input.mkv -c:v h264_vaapi -vf 'format=nv12,hwupload' -f null -

[videoAI]

@ProWo
v3.4.5.20

Feedback #2:

Video Encoding -> various -> Properties

Testing HWA with color correction using
default sample [duration = 60], Encoder = x264
---------------------------------------------------
HWA none works, GPU utilization avg ~ 1 %

HWA vulkan works, GPU utilization avg ~ 1 %
it looks like this setting defaults to 'none'

HWA auto works, GPU utilization avg ~ 8 %

HWA dxva2 works, GPU utilization avg ~ 8 %
[That's why I sometimes use dxva2, its synonymous with 'auto']

HWA d3d11va works, GPU utilization avg ~ 10 % [for sample]
* note:
On a larger file, HWA d3d11va took a long .. long time ..
[progress bar worked for ~ 2 mins, then stuck at 100% for ever, but finally finished]

HWA amf, nvdec, & qsv all didn't work & generated an error [with no error details]
I was surprised to see nvdec [a decoder ??!!], and was also surprised that choosing
'vulkan' didn't generate an error!!

Finally, VAAPI is missing from the list ..
[but I am not asking for it to be added]

Q1: Does the HWA dropdown supposed to show only values compatible with the
selected encoder? because it is not.

Q2: Does the HWA dropdown supposed to show only HWA Encode values? or
does it also show HWA Decode values? currently it is showing both. [ex: nvdec]


[Attachment 88842 - Click to enlarge]


[Attachment 88843 - Click to enlarge]

FFmpeg cmds attached:

[videoAI]

I am amazed at how inconsiderate some programmers are, and
how wasteful, of your disk space, and mine, they are.

With SSD's use on the rise, we all had to strike a balance between
disk speed & disk capacity. Most of us have chosen, or upgraded
to, SSD's for speed but ended up with smaller disk capacity because
of cost.

I searched my SSD for copies of ffmpeg, ffplay, & ffprobe.

I found 10 copies of each on my disk, used by different programs.

That's 30 duplicate files .. even with the ffmpeg bin folder location
already added to my path, and with file sizes approaching 200 mb
each, depending on your ffmpeg version, that's a potential:
30 x 200 mb = 6 Gb of wasted space on your precious SSD, and
mine.

What a waste ..

Ending on a positive note, our thanks go to the developers, who
have elected to not distribute copies of ffmpeg with their software
packages, or to allow linking to a single copy of it.

Noteworthy .. Clever, Losslesscut, ytdlp interface .. just to name
a few.

[videoAI]

@ProWo
v3.4.5.20
Bug #15 [I think .. ]

Bug #15 .. Crash reading BT_Open.txt file

How to duplicate:
Just finished posting HWA testing with color properties, under video encode where I generated
ffmpeg commands for each HWA value on my AMD system by sending the jobs to batch [to
have access to ffmpeg cmds generated by Clever for each]. then I quit the app and modified
the text file to make it more readable and attached it to my testing post.

forgot to delete the altered BT_Open.txt file [got distracted by a phone call]

The next time I attempted to open Clever .. !! boom !! .. another nasty crash
and I was stunned by Clever telling me: this is your 1st launch .. WHAT #%$^?

Now, I know what you are thinking .. the text file has been altered, so Clever
has every right to crash ..

I disagree !!

I think well written code should use 'try catch' every time it attempts, to write,
execute, invoke, change, or read contents from external files. This is why this
crash qualifies as a bug.

@ProWo, please add validation where needed.

PS. I noticed that ~ 90% of crashes in Clever are due to only 2 types of
programming issues:

1- Index was outside the bounds of the array [Array index]
2- Auto-filled column is being resized [DataGrid layout]

and the fixes are very simple ..

1- Check the index number to make sure it falls within the bounds of the array 0 <= $i < array.length
2- Disable auto layout till grid loading finishes, or contents change is complete, re-enable auto layout [sorting/resizing, ..]

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at clever_FFmpeg_GUI.Form0.Go_further()
at clever_FFmpeg_GUI.Form0.Target_check()
at clever_FFmpeg_GUI.Form0.FFmpeg_setting()
at clever_FFmpeg_GUI.Form0.Form0_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************

[Attachment 88845 - Click to enlarge]

[davidd]

FEATURE REQUEST
This is a brilliant program that I just found.
This may seem an unusual request, but could we please have an option to encode audio to WAV?
Thanks.

[ProWo]

FEATURE REQUEST
This is a brilliant program that I just found.
This may seem an unusual request, but could we please have an option to encode audio to WAV?
Thanks.

Already implemented. Use PCM encoder, the output is wav.

[ProWo]

Bug #15 .. Crash reading altered BT_Open.txt file

Interesting hint.
I've added a format consitency check on BT-open.txt read in.
Test it.

[ProWo]

Q1: Does the HWA dropdown supposed to show only values compatible with the
selected encoder? because it is not.

No, of course.
Hardware-assisted decoding should work with your hardware and is independent of the codec.

Q2: Does the HWA dropdown supposed to show only HWA Encode values? or
does it also show HWA Decode values? currently it is showing both. [ex: nvdec]

Only HWA Decode values.
Hardware-supported encoding is controlled by encoders.

[ProWo]

----------------------------------------------------------------------------------
September 21, 2025 release version 3.4.6.
----------------------------------------------------------------------------------
Added:
Backup handling (keep/restore/delete).
aac fdk encoder (only works if ffmpeg is compiled with it).
HDR10+ to HDR10 encoding (static HDR data only).
SDR to HDR10/HLG encoding (experimental).
Extracted raw streams added to processed streams list.
Output check for zero file/missing encoded file output.
Info for estimated colorspace (video encoding).
Check to avoid adding not admitted files in mux grid.
Dynamic range control for eac3 codec.
HWA options (hardware assisted decoding) for all video encoders.
Gamma RGB settings (video encoding).
Caret handling in audio-/video encoding.
Luma matrix & chroma matrix check for denoise filter (video encoding).
Check for correct format with bt-open.txt read in on start.

Fixed:
Bug with audio encoding and error scan in batch tasks.
Bug with sample settings (video encoding).
Bug with add file button not hiding (with mux_whole_grid).
Bug with Master display parsing (for HDR video).
Bug with DAR (display aspect ratio) rounding (video encoding).
Bug with adding not admitted streams to processed streams list.
Bug with missing starttime reset, if starttime>0 (video encoding).
Bug with lut's folder select loop.
Bug with mislined stream selection box (chapters window).
Bug with 8to6 channels selection and clever_norm filter (audio encoding).
Bug with missing CRF reset (changing encoder, video encoding).
Bug with mpeg2_qsv settings (video encoding).
Bug with filter_complex filter (video encoding).
Bug with non admitted container check (audio encoding).
Bug with missing HDR settings reset for SDR videos (if no HDR option is set).
Bug with Datagridview exceptions (caused by the DGV constructor).
Bug with first file check (multiplex window).
Bug with missing join button color change (if cut junks are present).

Changed:
Description and settings (rotate metadata only).
Extra button renamed to Various, and moved (audio encoding).
Video encoder names.
Update/backup/restore code.
App settings from pc_related to roaming (global).
Disposition code in multiplex.
Unused files rows are checked now.
Backup is mantained after restore.
Whole colorspace management.
HDR handling.
HWA options.
Moved all video properties filter to one page.
Selection for available HDR enoders.
Default value for luma amount from 1 to 0.
Buttons behavior (audio encoding, crop window).

Removed:
Error check while encoding (too sensitive).
Security check with delete tasks.

Improved:
How streams are added to processed files list.
Handling of missing ffmpeg folder/target folder.
Chapters info in multiplex window.
Update and restore scripts.

----------------------------------------------------------------------------------

[davidt1]

Thank you for the update, ProWo. Muxing works great, but the annoying messagebox for whole grid muxing is still there. LOL

It's all good. We appreciate your hard work.

[videoAI]

Thanks for the clarification ..

The location of the HWA Dropdown threw me off ..
within the encoder settings on the Video encoding screen.

But the list values accelerate decoding .. similar to the scan for errors batch screen HWA dropdown.
and off course only values compatible with your HW would work for you.

Q1

Hardware-assisted decoding should work with your hardware and is independent of the codec.

Q2

Only HWA Decode values.
Hardware-supported encoding is controlled by encoders.

[videoAI]

Another milestone .. Thank you

----------------------------------------------------------------------------------
September 21, 2025 release version 3.4.6.
----------------------------------------------------------------------------------

[videoAI]

WAV Audio Format Overview:

| Attribute | Details |
|-----------|---------|
| Full Name | Waveform Audio File Format |
| File Extension | .wav |
| Type | Uncompressed audio file format |
| Developed By | Microsoft and IBM |
| First Released | 1991 |
| Audio Encoding | Linear Pulse Code Modulation (LPCM) |

WAV (Waveform Audio File Format) is a standard audio file format primarily used for:
- Storing uncompressed, high-quality audio
- Preserving original audio quality without loss
- Professional audio recording and editing

Technical Details
- Typically uses PCM (Pulse Code Modulation) encoding
- Supports various bit depths (8, 16, 24, 32 bits)
- Common sample rates: 44.1 kHz (CD quality), 48 kHz, 96 kHz
- Large file sizes due to lack of compression
- Widely supported across audio software and operating systems

Common Use Cases
- Music production
- Sound design
- Audio recording
- Archival of high-quality audio

Extract audio from video as WAV

ffmpeg -i video.mp4 -vn -acodec pcm_s16le audio.wav

FEATURE REQUEST
could we please have an option to encode audio to WAV?