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.

[ingsoc]

v3.4.5 and last bet

[ProWo]

v3.4.5 and last bet
error

Error caused by the error check during encoding, too sensitive.
I've removed it. Update to v3.4.5.05.

[videoAI]

My collection of Media files is standardized on the MP4 container format.
oh .. @ProWo isn't gonna like this statement at all .. .. anyways,
I needed one MOV and one MKV file for testing the utilities that I am
building right now. More on that later ..

so I usually use Losslesscut and change file containers in mere seconds:
- select 1 from ~20 container types, click export. [2 seconds]. but this
time around, I already had Clever open, so I figured why not !! I am sure
Clever can do it .. suffice it to say I ended up spending 12 frustrating
minutes out of my very precious time and gone through 3 screens
before arriving at the multiplex screen and creating my two test files.

Now I really understand why every time I recommend Clever to someone
on this forum they push back .. it is confusing, it is awkward, it is buggy,
it is messy, I tried it but still looking for alternatives, I don't like it, there is
no help file, there are no tutorials. etc .. they say .. not me ..

I am going to end this post on a positive note.

@ProWo, please allow access to the first page [with multiplex] from all
other screens. currently other screens link to the open source screen !!

[ProWo]

so I usually use Losslesscut and change file containers in mere seconds:
- select 1 from ~20 container types, click export. [2 seconds].

With the source file alreday loaded, change the container and click multiplex.
Less than 2 seconds.

but this
time around, I already had Clever open, so I figured why not !! I am sure
Clever can do it .. suffice it to say I ended up spending 12 frustrating
minutes out of my very precious time and gone through 3 screens
before arriving at the multiplex screen and creating my two test files.

12 minutes for this.... I don't think so.
There are two ways to create this 2 test files.

1) Start clever, click multiplex, check stay open, drag your mp4, select mkv as container and click multiplex.
If finished, selelect mov as container and click multiplex.
Done.

2) if you are into program for other tasks, most likekly you see the main screen.
Click multiplex, check stay open, select all streams and hide them.
Then do the same as at 1).

Never ever 12 minutes....

btw
If you like Losslesscut, use it.

[davidt1]

There is no perfect app. I use Clever mostly for muxing. It is great for that. I can also use Losslesscut for muxing, but it's more complicated and time consuming. Losslesscut is not a finished product. It hasn't been updated in months.

[videoAI]

Since Container change is a copy, lossless operation [99% of the time],
how about adding it [Container change] to the various screen.
And how about linking to the 'various' screen from the first page .. good idea ha ..

Pls find my replies below ..

click export. [2 seconds].

With the source file already loaded, change the container and click multiplex.
Less than 2 seconds.

Where do you change the container? unless you are at the Mux screen?
That's why I kindly requested quick links from all other pages to the
first page with Mux.
Currently you only get to the Mux screen:
1- from page#1
2- or if clever decides to take you there [like after a stream extract]

Never ever 12 minutes....
If you like Losslesscut, use it

Thx for the tip , I already do

[videoAI]

- I think it is one of the best finished free products out there ..
- What's to update .. it links to FFmpeg [which is updated to 8.x now]
BTW, the dev does not want to add any lossy feature, to keep the
program true to its name.

Losslesscut is not a finished product.
It hasn't been updated in months.

[davidt1]

Default check does not work for Mp4. It works for MKV.

I checked the default for the srt sub stream.


[Attachment 88503 - Click to enlarge]

But does not show on the muxed file.


[Attachment 88504 - Click to enlarge]

[dave_van_damme]

@ProWo

re: Muxed DVD showing green screen in VLC

[ProWo]

Default check does not work for Mp4. It works for MKV.
I checked the default for the srt sub stream.
But does not show on the muxed file.

This is a videoplayer problem.
The default flag should be written (check this with mediainfo), but the flag isn't honored by the player.

[ProWo]

@ProWo
re: Muxed DVD showing green screen in VLC

Strange problem (seems only with VLC player);

I've extracted the streams (videostream as raw stream).
The extracted videostream plays fine with VLC, no green screen.
Once muxed (with clever or mkvtoolnix), it shows a green screen.
If hardware decoding is disabled in VLC player, the muxed video plays fine. With other players too.
I haven't found the reason for this yet.

[davidt1]

Default check does not work for Mp4. It works for MKV.
I checked the default for the srt sub stream.
But does not show on the muxed file.

This is a videoplayer problem.
The default flag should be written (check this with mediainfo), but the flag isn't honored by the player.

It's not a videoplayer problem because it plays MKV files with the default and MP4 file with no default. If the videoplayer is the problem, it would work the same way for both mp4 and mkv.

I verified this by using ffmpeg directly. It seems that FFMPEG does not apply a default to a sub stream in a MP4 file, but does with MKV files. I guess the only option left is to check the "forced" option to force it to become the default.

[ProWo]

It's not a videoplayer problem because it plays MKV files with the default and MP4 file with no default. If the videoplayer is the problem, it would work the same way for both mp4 and mkv.

Not true.
I just tested this with an mp4 file.
The default flag on the third subtitle is written correctly, but the player (VLC in my case) does not recognize it.

I verified this by using ffmpeg directly. It seems that FFMPEG does not apply a default to a sub stream in a MP4 file, but does with MKV files. I guess the only option left is to check the "forced" option to force it to become the default.

Also wrong.
The default flag on the subtitle is written correctly. As I said, check this with mediainfo.

[Findu]

@ ProWo

v3.4.5.05 Feedback

Would it make sense to use "Settings page 1" and "Settings page 2" as window title?

The restore of clever_3.4.5.02.bck does not work. And should the bck file remain after a restore?

It looks like that you removed the error check during video encoding. So not supported encoders create 0 kb files. And you see the "Success" notification. It should state "No success" in red or yellow in such a case.
And such files can not be analyzed for multiplexing.
How about a checkbox to reactivate the error check?

How about selecting all unused processed files by default? If you want to keep them, still click Quit.

[davidt1]

It's not a videoplayer problem because it plays MKV files with the default and MP4 file with no default. If the videoplayer is the problem, it would work the same way for both mp4 and mkv.

Not true.
I just tested this with an mp4 file.
The default flag on the third subtitle is written correctly, but the player (VLC in my case) does not recognize it.

I verified this by using ffmpeg directly. It seems that FFMPEG does not apply a default to a sub stream in a MP4 file, but does with MKV files. I guess the only option left is to check the "forced" option to force it to become the default.

Also wrong.
The default flag on the subtitle is written correctly. As I said, check this with mediainfo.

OK, I used mediainfo like you said. It shows exactly what I have been saying. It is not the videoplayer. It's ffmpeg. This is not your fault.

mp4 shows no default

[Attachment 88516 - Click to enlarge]

[Attachment 88517 - Click to enlarge]

mkv shows default.

[Attachment 88518 - Click to enlarge]

[Attachment 88519 - Click to enlarge]

[ProWo]

You must use mediainfo in text mode to see the default flag.

[dave_van_damme]

@ProWo
re: Muxed DVD showing green screen in VLC

Strange problem (seems only with VLC player);

I've extracted the streams (videostream as raw stream).
The extracted videostream plays fine with VLC, no green screen.
Once muxed (with clever or mkvtoolnix), it shows a green screen.
If hardware decoding is disabled in VLC player, the muxed video plays fine. With other players too.
I haven't found the reason for this yet.

Thanks for taking a look! I've had it happen with both NTSC and PAL dvds (not all of them). For this particular file it also happens if I mux in AVIdemux, too but that app is fine with some other files which Clever doesn't seem to like. Weird.

[ProWo]

Would it make sense to use "Settings page 1" and "Settings page 2" as window title?

Hi Findu,
as always, you come up with reasonable suggestions.
Is done.

The restore of clever_3.4.5.02.bck does not work. And should the bck file remain after a restore?

Restore works here as aspected. The backup file is now retained after a restore.

It looks like that you removed the error check during video encoding. So not supported encoders create 0 kb files. And you see the "Success" notification. It should state "No success" in red or yellow in such a case.
And such files can not be analyzed for multiplexing.
How about a checkbox to reactivate the error check?

The previous error check during encoding was too sensitive; I experienced several false alarms myself.
That's why I removed it; now there is an output file check. If there are zero files or missing files, an error message now appears.

How about selecting all unused processed files by default? If you want to keep them, still click Quit.

Good idea, is done now.

[davidt1]

Just updated to .06

1. Clever does not recognize sub codec anymore and thus does not allow changes to be made.

2. The app was deleted after closing.

Since Clever was deleted, how do I go back to .05? Thanks.

[oniiz86]

@ProWo Sorry to trouble you for a minor typo but discovered it on the Video Encoding screen when hovering over Frame Height, the popup has Height spelt incorrectly as Heigth.


[Attachment 88530 - Click to enlarge]

Also on the Audio Encoding screen, it mentions the AC3 Decoder DRC setting defaults to On but Off is always selected which is preferred anyway, can the popup be corrected to Off? Is this the DialNorm setting that removes the gain attenuation, so Off will have zero attenuation & have a value of -31dB?


[Attachment 88531 - Click to enlarge]

[ProWo]

[QUOTE=oniiz86;2782074]@ProWo Sorry to trouble you for a minor typo but discovered it on the Video Encoding screen when hovering over Frame Height, the popup has Height spelt incorrectly as Heigth.
Thx for the hint, will be fixed.

Also on the Audio Encoding screen, it mentions the AC3 Decoder DRC setting defaults to On but Off is always selected which is preferred anyway, can the popup be corrected to Off?

This must remain so because ffmpeg's default is on.
See here:
https://ffmpeg.org/ffmpeg-codecs.html#AC_002d3-Decoder-Options

[ProWo]

Just updated to .06

1. Clever does not recognize sub codec anymore and thus does not allow changes to be made.

Just tested. name.eng.srt is recognized correctly.

2. The app was deleted after closing.

Never seen this behavior.

Since Clever was deleted, how do I go back to .05? Thanks.

Did you make a backup of v3.4.5.05?
If so, extract the exe from the v3.4.5.06 zip archive and start it.
Click on settings, you'll see the info like in the pic.


[Attachment 88532 - Click to enlarge]

Click on Use it, set restore, click OK.

The app will restart with version 3.4.5.05.

btw.
I'm adding this backup for you.

[oniiz86]

Also on the Audio Encoding screen, it mentions the AC3 Decoder DRC setting defaults to On but Off is always selected which is preferred anyway, can the popup be corrected to Off?

This must remain so because ffmpeg's default is on.
See here:
https://ffmpeg.org/ffmpeg-codecs.html#AC_002d3-Decoder-Options

Oh okay I understand but why the discrepancy then as every source file I've loaded with a Dolby Digital audio stream in the Audio Encoding screen section has the AC3 Decoder DRC setting always set to Off, it never defaults to On?

[ProWo]

Also on the Audio Encoding screen, it mentions the AC3 Decoder DRC setting defaults to On but Off is always selected which is preferred anyway, can the popup be corrected to Off?

This must remain so because ffmpeg's default is on.
See here:
https://ffmpeg.org/ffmpeg-codecs.html#AC_002d3-Decoder-Options

Oh okay I understand but why the discrepancy then as every source file I've loaded with a Dolby Digital audio stream in the Audio Encoding screen section has the AC3 Decoder DRC setting always set to Off, it never defaults to On?

This was a request by many users.
If off, you have the full ac3 range. You can set it to on, if you prefer.