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

[ProWo]

four more points.
1. Is there any way I don't notice to copy prepared ffmpeg command line?
2. Is it possible to add custom arguments if I want?

You can use the batch function.
Instead of clicking encode you click on "To batch".
Close the app. A new file BT_open.txt is created in your target folder.
Edit it as you like (the commandline only) and save it.
Restart the app and click main page, batch tasks, excute.
The modified batches are processed.

3. Is hardware accelerated decoding supported? I mean laptop with nvidia dgpu and Intel cpu. This case use nvdeс to decode and cpu to svt av1 encode

You can use one of the _qsv (Intel) or _nvenc encoders. With both you can check/uncheck the HW decoding checkbox.

4. I have ffmpeg build with libfdk_acc. Is the any way to add it into the audio codec list?

Will add it.

P. S. is it possible to transfer 10+ to just 10 keeping at least static HDR?

Will have a look on this.

EDIT: Done. Update, test and report.

[videoAI]

@ProWo
3.4.5.03

Feature Request [Aka improvement]

Instead of this lengthy process, why not implement a simple dialog box with Execute [run as is],
Modify [Edit first] buttons that loads and allows editing of the BT_open.txt file from within Clever,
without having to close and open the App.

Better yet, why not store every FFmpeg command to be executed in this or similar text file
and allow the user to edit it as well from within the App without restarting.

To add custom arguments, you can use the batch function.
Instead of clicking encode you click on "To batch".
Close the app. A new file BT_open.txt is created in your target folder.
Edit it as you would the command line and save it.
Restart the app and click main page, batch tasks, execute.
The modified batch is processed.

[ProWo]

Feature Request [Aka improvement]

Instead of this lengthy process, why not implement a simple dialog box with Execute [run as is],
Modify [Edit first] buttons that loads and allows editing of the BT_open.txt file from within Clever,
without having to close and open the App.

Better yet, why not store every FFmpeg command to be executed in a this or similar text file
and allow the user to edit it as well from within the App without restarting.

I don't want users messing around with the command line.

[hakupla]

Plays with checkbox in batch tasks in recent update

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at clever_FFmpeg_GUI.Form38.DataGridView1_CellMouseEnter(Object sender, DataGridViewCellEventArgs e)
   at System.Windows.Forms.DataGridView.OnCellMouseEnter(DataGridViewCellEventArgs e)
   at System.Windows.Forms.DataGridView.UpdateMouseEnteredCell(HitTestInfo hti, MouseEventArgs e)
   at System.Windows.Forms.DataGridView.OnMouseMove(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseMove(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

P.S.
Using the sample I tested saving static HDR 10 metadata and found that.

... -hide_banner -loglevel error -stats -y -fflags +genpts -i "C:\Users\nk\Downloads\Birds of Prey (2020) clip.4K.HDR10Plus.ATMOS.mkv" -vf fps=24000/1001  -map 0:0 -c:v:0 libsvtav1  -x265-params level=5.1:high-tier=1:hdr10=1:hdr10-opt=1:repeat-headers=1:master-display=G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(40000000,50):max-cll=683,136 -crf 18 -preset 3 -aspect 1.78 -an -sn -dn -metadata:g encoding_tool="clever FFmpeg-GUI"...

I assume the program thinks that h265 is HDR format only. However according to https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/Parameters.md
Mastringdisplay ColorPrimaries etc. are supported in AV1

[ProWo]

Plays with checkbox in batch tasks in recent update

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at clever_FFmpeg_GUI.Form38.DataGridView1_CellMouseEnter(Object sender, DataGridViewCellEventArgs e)
   at System.Windows.Forms.DataGridView.OnCellMouseEnter(DataGridViewCellEventArgs e)
   at System.Windows.Forms.DataGridView.UpdateMouseEnteredCell(HitTestInfo hti, MouseEventArgs e)
   at System.Windows.Forms.DataGridView.OnMouseMove(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseMove(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Could you please post the exact steps to this error message?
Can't reproduce it here.

I assume the program thinks that h265 is HDR format only. However according to https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/Parameters.md
Mastringdisplay ColorPrimaries etc. are supported in AV1.

Maybe other codecs too, but for the moment only hevc is supported for HDR encoding.

[videoAI]

This forum is full of outdated and abandoned software that is old, not updated anymore,
or mostly non-functioning.

One of the major reasons a software application survives the time factor is good design.
If it takes into account that dependencies do change overtime or get upgraded, then that
might extend it lifetime a bit longer.

Some of the old programs I still use hardcoded the FFmpeg version they use and won't
work with an updated version. others hardcode settings, configurations, or even profiles
in code. I can still use some of them only because my video collection still uses H264.

If I decided to move to H265, or even H266 in the near future, most of these old programs
wont work anymore.

So what can a modern, nicely designed App, do to extend its lifetime in the future?

1. De-couple the App code from the underlining dependencies [ex: FFmpeg] so one
can update the App/GUI without major code re-writes.

2. Keep all codec/format [dropdown values] handling; data-driven (ex: save to JSON/YAML
or lookup tables) rather than hard-code them in the App code.

3. Save settings, workflow / business rules, profiles, etc. in config & Lookup files so they can
be updated without code changes.