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

[videoAI]

@ProWo

Tested Ok.
Thank you, and keep up the great work.

I think it would make sense to get rid of the [DNxHR] popup:
and please replace the other [DNxHD] popup as well.

Done.

[videoAI]

v 3.4.3.37
Bug#9 [Hevc Crash] fixed.
Tested Ok.

The point of exposing this bug is to show that 'Clever' still has short comings when handling indexes in arrays.
More validation to make sure the passed index value does not exceed the bounds of the array is highly recommended.

Thank you for fixing the bug, and keep up the great work.

A sample hevc test file causes a crash when dropped into clever.

Exception fixed.
Your sample is a raw hevc stream, not muxed into mp4, but renamed only to mp4.
Other editors like Avidemux can't load this file.

[videoAI]

@ProWo
Please find my replies in brackets below ..

Your sample is a raw hevc stream [Agreed], not muxed into mp4, but renamed only to mp4
[needed to rename the extension to mp4 to play it in my MPC player]
Other editors like Avidemux can't load this file. [but, I bet Avidemux didn't crash in the process]
I would recommend to use real video files instead.
[Well, according to the website that has hundreds of test files for all video formats,
it is a real video file used specifically for testing and my MCP player agrees as it plays it fine]

[oniiz86]

@ProWo I just noticed a minor misspelling with the misspelling of the "Multiplex" button, it has 2 ii's on the "Select Source File" screen.


Also when I add a PGS subtitle stream that I want to "Scan for errors", it mentions Errors found! & when I hover over the "View Errors" button it has a wrong description for the dialog pop up "Edit the Chapters File"


When I click on "View Errors" it tells me that the "Text Editor" is missing, I don't believe this is correct as it's a PGS image-based subtitle stream, not an SRT text-based subtitle.


I was wondering if your program can determine if subtitle streams are corrupt with the "Scan for errors" button, it says "Errors found!" but it doesn't mention what kind of errors it discovered?

[ProWo]

@ProWo I just noticed a minor misspelling with the misspelling of the "Multiplex" button, it has 2 ii's on the "Select Source File" screen.

Thx for the hint. Will be fixed.

Also when I add a PGS subtitle stream that I want to "Scan for errors", it mentions Errors found! & when I hover over the "View Errors" button it has a wrong description for the dialog pop up "Edit the Chapters File"

Will be fixed too.

When I click on "View Errors" it tells me that the "Text Editor" is missing, I don't believe this is correct as it's a PGS image-based subtitle stream, not an SRT text-based subtitle.

If errors are found, they are written to a text file. To view this file, you need a text editor (e.g., Notepad or Notepad++).

I was wondering if your program can determine if subtitle streams are corrupt with the "Scan for errors" button, it says "Errors found!" but it doesn't mention what kind of errors it discovered?

The subtitle stream is a stream like others; if errors are found, you need the texteditor to see them.

[Findu]

@ ProWo

Thanks for changing the Multiplex tooltips text like "Clear grid after muxing" so that it does not delete files any longer, but it still delete related processed files.

---

vp9_qsv speed test:

-map 0:0 -c:v libvpx-vp9 -b:v 0 -deadline realtime -crf 31 1x
-map 0:0 -c:v vp9_qsv -b:v 0 -preset veryslow 10x
-map 0:0 -c:v vp9_qsv -b:v 0 -preset veryfast 19x


av1_qsv speed test:

-map 0:0 -c:v libaom-av1 -crf 35 -cpu-used 8 1x
-map 0:0 -c:v libsvtav1 -crf 35 -preset 10 14x
-map 0:0 -c:v librav1e -qp 35 -speed 8 1x
-map 0:0 -c:v av1_qsv -preset veryslow 10x
-map 0:0 -c:v av1_qsv -preset veryfast 24x

Adding these addtional av1_qsv parameters also work for me:
-extbrc 1 -look_ahead_depth 40 -b:v 1M -bufsize 2M -rc_init_occupancy 512K -low_power 0 -adaptive_i 1 -adaptive_b 1 -b_strategy 1 -bf 4

But it may not be so interesting to add them to the gui?

---

Two questions:
Did you try the vpp_qsv filter in combination with _qsv encoding?
ffmpeg -h filter=vpp_qsv

Does hevc_mf encoding work for you?

---

ADD: Could you please increase the window size in Scan for errors!

[Attachment 87984 - Click to enlarge]

[ProWo]

Thanks for changing the Multiplex tooltips text like "Clear grid after muxing" so that it does not delete files any longer, but it still delete related processed files.

Should not be. Will change this.

EDIT: Done.

Two questions:
Did you try the vpp_qsv filter in combination with _qsv encoding?
ffmpeg -h filter=vpp_qsv

Not tested.

Does hevc_mf encoding work for you?

Do you mean hevc_amf?
No not working, but this is aspected, I'm on Intel platform.

ADD: Could you please increase the window size in Scan for errors!

The messages window size is the same for the whole app.
This is the unique message with longer text and appears only with a missing text editor.
I'll leave it as is is.

[Findu]

I dont mean AMD hevc_amf,
it is hevc via Media Foundation hevc_mf,
ffmpeg -h encoder=hevc_mf

[ProWo]

I dont mean AMD hevc_amf,
it is hevc via Media Foundation hevc_mf,
ffmpeg -h encoder=hevc_mf

Interesting. Never seen it. I will test it.

EDIT: Tested, doesn't work for me.