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

[ProWo]

Are these “Mux whole grid” rules are correct?
- Everything that is visible in the grid will be muxed.

Yes

- All selected streams get muxed into one file.

Yes, but your selection is wrong. E01+E03 are muxed together.
It should be selected the first file streams only.

The unselected streams get muxed according to name.

Correct.

[Findu]

>> All selected streams get muxed into one file.
> Yes, but your selection is wrong. E01+E03 are muxed together.
It should be selected the first file streams only.

To avoid errors here, you could only show the “Mux whole grid” option if only the first stream (or streams with the first file mane) is selected and more than one file name is present in the grid.

EDIT: If someone makes a wrong selection afterwards, the option will also disappear or inactive.

EDIT 3: I just noticed that this is already implemented. But when muxing is finished and the hidden streams are displayed again, "Main Page" remains hidden. It appears when you activate "Simple remux".

[Attachment 88095 - Click to enlarge]

EDIT 2: “Mux whole grid” for singel audio streams?
If you only want audio from a video, lets say aac to mp3, should you also mux that stream after encoding?

[doctorjellybean]

Wow! I only discovered it this morning, and have already used it for a number of files.

Is it possible to not append _1.eng\_2.eng and _V0 to the filenames?

Perhaps, for a future update, the Source Page can be on the Main Page. It would save a lot of clicking backwards and forwards.

Thank you for this great tool!

[videoAI]

I am facing the same issue as well ..

EDIT: v3.4.4.12 now always center the app window position on the desktop when you perform an app update.
Does the app not not read/process the <my_pos>835?233</my_pos> information at first launch after an update of the app?

[ProWo]

But when muxing is finished and the hidden streams are displayed again, "Main Page" remains hidden. It appears when you activate "Simple remux".

Should be fixed now.

EDIT 2: “Mux whole grid” for singel audio streams?
If you only want audio from a video, lets say aac to mp3, should you also mux that stream after encoding?

If the converted audio stream comes from a video, it is also added to the muxgrid list.

[ProWo]

Is it possible to not append _1.eng\_2.eng and _V0 to the filenames?

This behavior is intended and used in the mux grid to identify single streams and read in the audio/subtitle language tags.

Perhaps, for a future update, the Source Page can be on the Main Page. It would save a lot of clicking backwards and forwards.

The source page contains a lot of info and can not be integrated in the main page.

[ProWo]

I am facing the same issue as well ..

EDIT: v3.4.4.12 now always center the app window position on the desktop when you perform an app update.
Does the app not not read/process the <my_pos>835?233</my_pos> information at first launch after an update of the app?

Found the bug. Will be fixed soon.

EDIT:
Done

[Findu]

If you place v3.4.4 on the desktop and then update to nightly, the original position remains, just as before. The problem only occurs starting with approximately v3.4.4.07.

---

The missing "Main Page" button on the mux page has been fixed.

---

>> EDIT 2: “Mux whole grid” for singel audio streams?
If you only want audio from a video, lets say aac to mp3, should you also mux that stream after encoding?
> If the converted audio stream comes from a video, it is also added to the muxgrid list.

The question is whether it makes sense to multiplex MP3 files after encoding them.
Because the files can be played without muxing as well.

[ProWo]

If you place v3.4.4 on the desktop and then update to nightly, the original position remains, just as before. The problem only occurs starting with approximately v3.4.4.07.

Thx for this precise hint.
Found the bug. It was with v3.4.4.08.
Will upload the last nightly tomorrow.

EDIT:
Done

[Findu]

Unfortunately the "Main Page" button now disappears after normal multiplexing.

Could you start the text with "All visible streams ..."?

[Attachment 88113 - Click to enlarge]

[doctorjellybean]

I admit that the Multiplex page confuses me, as I don't know how it works. So for now I use MKVToolNix for multiplexing.

[videoAI]

@ProWo

1- I noticed that the Movie Name [Title] isn't being read by Clever anymore.

2- Also the Video/Audio stream titles are not read, saved , or displayed anywhere.

3- Another thing .. the target file name is [Test.mp4] when the source file name is [Test_edited.mp4].
Does that seem right? you might be using the term '_edited' in your code !!

4- Any plans to read/write the Metadata field 'Comment' in the future?
It can go under Various [no encode needed]

Media Info

Complete name : C:\T\Test\Test_edited.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 2.50 MiB
Duration : 1 min 0 s
Overall bit rate : 349 kb/s
Frame rate : 30.000 FPS
Movie name : My Title
Writing application : videoAI
Comment : My Remark

[Attachment 88114 - Click to enlarge]

[davidt1]

I admit that the Multiplex page confuses me, as I don't know how it works. So for now I use MKVToolNix for multiplexing.

I am a long time user of MKVToolnix. It's a great program for what it is: only mux to MKV. Clever does much more and it is not that hard to use.

For muxing:

1. Open the app. Click on "Multiplex". Start dragging and dropping files onto the mux page. You need a "stay on top" program to make it stay on top. This is where MKVToolnix has the advantage with its built-in stay on top function.

Once I became used to Clever, I find myself using it more and more. Being a beta user is a lot of fun. ProWo is so responsive to ours suggestions.

[ProWo]

Unfortunately the "Main Page" button now disappears after normal multiplexing.
Could you start the text with "All visible streams ..."?

Should be fixed now.

[Findu]

The disappearing "Multiplex" button and the remaining position of the app window after updating are fixed in v3.4.4.14.
Thank you ProWo.

With normal multiplexing, _mux is no longer appended to the filename. I suspect this is intentional.

However, in the output filenames, you truncate everything with the last _ of the original name. But only with muxing.
1_2_3.mp4 -> 1_2.mp4

[doctorjellybean]

I admit that the Multiplex page confuses me, as I don't know how it works. So for now I use MKVToolNix for multiplexing.

I am a long time user of MKVToolnix. It's a great program for what it is: only mux to MKV. Clever does much more and it is not that hard to use.

For muxing:

1. Open the app. Click on "Multiplex". Start dragging and dropping files onto the mux page. You need a "stay on top" program to make it stay on top. This is where MKVToolnix has the advantage with its built-in stay on top function.

Once I became used to Clever, I find myself using it more and more. Being a beta user is a lot of fun. ProWo is so responsive to ours suggestions.

Thanks.

What I do is extract the audio and subtitle files, and then Encode / Convert the Video stream using the Batch option. Once I'm done, the files are listed in the Multiplex window. What confuses me is how to use it so that I end up with individual multiplexed files, e.g. in my screenshot 3 files, and not one single file.

Why are Vobsub subtitles extracted as mkv files?

[ProWo]

The disappearing "Multiplex" button and the remaining position of the app window after updating are fixed in v3.4.4.14.
Thank you ProWo.

With normal multiplexing, _mux is no longer appended to the filename. I suspect this is intentional.

However, in the output filenames, you truncate everything with the last _ of the original name. But only with muxing.
1_2_3.mp4 -> 1_2.mp4

This is intentional.
For example, if you re-encode mp4 episodes in batches (audio and video) and select mkv as the container in the mux grid and then use “mux whole grid,” you will not need to rename the output files afterwards.

[ProWo]

What I do is extract the audio and subtitle files, and then Encode / Convert the Video stream using the Batch option.

If you want convert the videostream only, you don't have to extract the other streams first, they are avaiable from the source file.

Once I'm done, the files are listed in the Multiplex window. What confuses me is how to use it so that I end up with individual multiplexed files, e.g. in my screenshot 3 files, and not one single file.

In your screenshot you're muxing 3 single streams (2 extracted, 1 recoded). The result is one file with 3 streams.

Why are Vobsub subtitles extracted as mkv files?

File extraction is only an intermediate step, and the mkv container can store most streams.
For example, mp4 cannot store srt subtitles without conversion.

[Findu]

@ ProWo

Does the following make sense to you?

As the app can't know that you just want to encode audio from a video file, you could add a checkbox "Just convert audio" with tootip "Just encode audio without data transfer for further processing".
When you check it, the "Encode" button change to "Convert" as well.
None of these encoded files are available for multiplexing and therefore do not appear in the “Unused Files” list.


[Attachment 88117 - Click to enlarge]

[Attachment 88118 - Click to enlarge]

I know that convert isn't really the right term here when you extract and encode audio from a video.

[ProWo]

1- I noticed that the Movie Name [Title] isn't being read by Clever anymore.

The title tag (as format tag) is read, written and displayed correctly in mux grid (for mkv, mp4, mov).

2- Also the Video/Audio stream titles are not read, saved , or displayed anywhere.

The title tag (at stream level) is read, written and displayed correctly for mkv.
For mp4/mov ffprobe can't find the data, therefore they cannot be read / displayed, but they are written correctly.

3- Another thing .. the target file name is [Test.mp4] when the source file name is [Test_edited.mp4].
Does that seem right? you might be using the term '_edited' in your code !!

Read my answer to Findu in post #2387.

4- Any plans to read/write the Metadata field 'Comment' in the future?

No.

[ProWo]

Does the following make sense to you?
As the app can't know that you just want to encode audio from a video file, you could add a checkbox "Just convert audio" with tootip "Just encode audio without data transfer for further processing".

Not really; when recoding an audio file, nothing is written to the mux list.
If the source is a video file, so further use is to be expected.

[Findu]

@ ProWo

> If the source is a video file, so further use is to be expected.

That's correct!

---

The target file names get cut at the last "_". But only with muxing.
Here a screenshot to clarify:

[Attachment 88120 - Click to enlarge]

---

It's good that error checking for videos is available again.
mpeg2_qsv has been removed for new Intel Meteor Lake CPUs.

[mpeg2_qsv @ 000001f5a0471240] Current profile is unsupported
[mpeg2_qsv @ 000001f5a0471240] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.

But I would expect to see -preset and -profile in the mpeg2_qsv settings. Currently you use the same one as for mpeg2 in the gui.

---

Can you please add HWA decoding (-vsync 0 -hwaccel:0 auto) for the vp9_qsv and av1_qsv encoders.
It is working on my Intel system.

[ProWo]

The target file names get cut at the last "_". But only with muxing.

That's aspected. The last _ is the necessary separator to identify the same file name.
But file names like the ones you showed are not common.

But I would expect to see -preset and -profile in the mpeg2_qsv settings. Currently you use the same one as for mpeg2 in the gui.

Can you please add HWA decoding (-vsync 0 -hwaccel:0 auto) for the vp9_qsv and av1_qsv encoders.
It is working on my Intel system.

Will work on this.

EDIT:
Done.

[videoAI]

@ProWo,
v 3.4.4.14

[Edit#2] Found the problem ..
1- Open or drag an mp4 file -> Main -> Multiplex .. meta data is read [ok]
2- From source page, click Multiplex, click Add file .. meta data is not read [issue].
If you add more files, their meta data isn't read as well ..

Kindly add to your issues list

Clever is not showing anything in the Mux grid title box for this file !!

[Edit #1] if I Mux the file with clever and add a title , the title shows, and is read back.
but it seems, clever is not always displaying Titles written by other Apps, to the same field,
while windows detail, in properties, can.

Does the 'Writing application' field get anything to do with this issue??

General
Complete name : C:\T\Test\Test_edited.mp4
Format : [1, here]
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 2.50 MiB
Duration : 1 min 0 s
Overall bit rate : 349 kb/s
Frame rate : 30.000 FPS
Movie name : My Title [2, or here]
Writing application : videoAI
Comment : My Remark


[Attachment 88121 - Click to enlarge]

1- I noticed that the Movie Name [Title] isn't being read by Clever anymore.

The title tag (as format tag) is read, written and displayed correctly in mux grid (for mkv, mp4, mov).

[videoAI]

@ProWo,
v 3.4.4.14

Another crash ...
Bug #11 Source Page Crash

It happens from time to time. It mostly happens going back to the [Select Source] page from the [Multiplex] page.
had 4 similar crashes in the last 2 days, by just using the app.

I recommend slowing down the "enhancement changes" and giving more priority to bugs which cause crashes.

Try:
Suspend Layout: Before making changes, suspend the layout of the DataGridView.
Perform Operations: Perform the necessary operations.
Resume Layout: Resume the layout.

Debugging tip
When encountering layout-related exceptions in DataGridView, consider temporarily setting

dgv.AutoSizeColumnsMode = DataGridViewAutoSizeColumnsMode.None

to see if it resolves the issue, allowing you to further diagnose and modify your code as needed.
This approach can help you isolate whether the problem is related to auto-sizing or not.

*********** Exception Text **************
System.InvalidOperationException: This operation cannot be performed while an auto-filled column is being resized.
at System.Windows.Forms.DataGridView.PerformLayoutPri vate(Boolean useRowShortcut, Boolean computeVisibleRows, Boolean invalidInAdjustFillingColumns, Boolean repositionEditingControl)
at System.Windows.Forms.DataGridView.SetColumnHeaders HeightInternal(Int32 columnHeadersHeight, Boolean invalidInAdjustFillingColumns)
at System.Windows.Forms.DataGridView.AutoResizeColumn HeadersHeight(Boolean fixedRowHeadersWidth, Boolean fixedColumnsWidth)
at System.Windows.Forms.DataGridView.OnColumnHeadersG lobalAutoSize()
at System.Windows.Forms.DataGridView.set_TopLeftHeade rCell(DataGridViewHeaderCell value)
at System.Windows.Forms.DataGridView.get_TopLeftHeade rCell()
at System.Windows.Forms.DataGridView.OnCellMouseEnter (DataGridViewCellEventArgs e)
at System.Windows.Forms.DataGridView.UpdateMouseEnter edCell(HitTestInfo hti, MouseEventArgs e)
at System.Windows.Forms.DataGridView.OnColumnWidthCha nged(DataGridViewColumnEventArgs e)
at System.Windows.Forms.DataGridView.AdjustFillingCol umns()
at System.Windows.Forms.DataGridView.ComputeLayout()
at System.Windows.Forms.DataGridView.PerformLayoutPri vate(Boolean useRowShortcut, Boolean computeVisibleRows, Boolean invalidInAdjustFillingColumns, Boolean repositionEditingControl)
at System.Windows.Forms.DataGridView.OnHandleCreated( EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************

[Attachment 88122 - Click to enlarge]

Clever v 3.4.3.28
BTW, issue is still there. had 3 crashes since the last time I reported the bug.
you can arrive at the exception error from multiple scenarios. I narrowed it
down a bit. it seems to occur when your code is preparing to display a grid.
seems to apply to all your grids.

These posts are not very helpful.
I use the program every day and have not experienced any crashes.

[davidt1]

In older version, the top of the screen used to say "Output to source folder" or "Output to target folder". Now it just says "Output to source folder."

What happened? It doesn't hurt to display "Output to target folder" if target folder was selected.

[videoAI]

Good idea

I would add .. how about ...
Re-claim the space and use it as a status bar for displaying temp massages.
And get rid of most of the annoying temp popups ..
[popups were the old ways of designing Apps, Modern Apps don't have them anymore]
Hint: Mobile Apps

In older version, ...
It doesn't hurt to display "Output to target folder" if target folder was selected.

[videoAI]

@ProWo,
v 3.4.4.14

FYI, .. just a little text adjustment.


[Attachment 88137 - Click to enlarge]

If I'm not mistaken, encode is required to change the Profile,
but is not required to change the Level.

Since they are paired, I hoped both could be in one place, to check or change.

[Findu]

@ ProWo

Joining does not work for me. Please be patient...
The cuts are correct and vidlist.txt also. But when you click Join, the second cut file grow ~10 times and nothing else happens.

---

Could "Stay Open" stay visible during video encoding so that it can be checked if it is forgotten, like in audio encoding?

[videoAI]

In FFmpeg, the H.264 codec supports various profiles and levels,
which define the features and constraints of the encoded video.
Here is a list of common profiles and levels, along with how they typically pair together:

Profiles

- baseline: Suitable for low-complexity applications like video conferencing.
- main: Suitable for broadcast and streaming applications.
- high: Suitable for high-definition applications like Blu-ray discs.
- high10: Similar to high but supports 10-bit depth.
- high422: Similar to high but supports 4:2:2 chroma sampling.
- high444: Similar to high but supports 4:4:4 chroma sampling.
- constrained_baseline: A subset of the baseline profile with additional constraints.
- progressive_high: A subset of the high profile with additional constraints.

Levels

- 1: Up to 64 kbps, 960x544 pixels, 15 fps.
- 1.1: Up to 192 kbps, 1280x720 pixels, 30 fps.
- 1.2: Up to 384 kbps, 1280x720 pixels, 30 fps.
- 1.3: Up to 768 kbps, 1280x720 pixels, 60 fps.
- 2: Up to 2 Mbps, 1920x1080 pixels, 30 fps.
- 2.1: Up to 4 Mbps, 1920x1080 pixels, 30 fps.
- 2.2: Up to 4 Mbps, 1920x1080 pixels, 60 fps.
- 3: Up to 10 Mbps, 1920x1080 pixels, 60 fps.
- 3.1: Up to 14 Mbps, 1920x1080 pixels, 60 fps.
- 3.2: Up to 20 Mbps, 1920x1080 pixels, 60 fps.
- 4: Up to 25 Mbps, 4096x2304 pixels, 30 fps.
- 4.1: Up to 50 Mbps, 4096x2304 pixels, 30 fps.
- 4.2: Up to 50 Mbps, 4096x2304 pixels, 60 fps.
- 5: Up to 135 Mbps, 4096x2304 pixels, 60 fps.
- 5.1: Up to 240 Mbps, 4096x2304 pixels, 60 fps.
- 5.2: Up to 240 Mbps, 4096x2304 pixels, 120 fps.
- 6: Up to 240 Mbps, 4096x2304 pixels, 120 fps.
- 6.1: Up to 240 Mbps, 4096x2304 pixels, 120 fps.
- 6.2: Up to 240 Mbps, 4096x2304 pixels, 120 fps.

Pairing Profiles and Levels

- baseline: Typically paired with levels 1, 1.1, 1.2, 1.3, 2, 2.1, 2.2, 3, 3.1, 3.2.
- main: Typically paired with levels 2, 2.1, 2.2, 3, 3.1, 3.2, 4, 4.1, 4.2, 5, 5.1, 5.2, 6, 6.1, 6.2.
- high: Typically paired with levels 3, 3.1, 3.2, 4, 4.1, 4.2, 5, 5.1, 5.2, 6, 6.1, 6.2.
- high10: Typically paired with levels 3, 3.1, 3.2, 4, 4.1, 4.2, 5, 5.1, 5.2, 6, 6.1, 6.2.