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

[ProWo]

@ProWo
So may be I was too quick to say 'It works flawlessly'.
Here are some of the issues noticed with the addition of 'all streams' change in video encode screen.
1- The progress bar, for mp4, does not show, it is there for mkv. The bar is essential especially for large file encoding.

This isn't a bug, but file related.
If you encode this file in a commandline, in the ffmpeg output message you'll see the missing time information (time=N/Z).
But this information is necessary to calculate the progressbar progress.

When 'Clever' is minimized to the task bar, the icon does not show progress

I've not found a simple solution for this.

2- After encoding, even if you rename, delete, or move the output mp4 file, when exiting 'Clever' sometimes insists
that there is file-name_V01.mkv to be deleted [even when mp4 was selected [All streams checkbox]. I can't find
such a file anywhere.

I know the problem and have now fixed it.

[videoAI]

When 'Clever' is minimized to the task bar, the icon does not show progress

I've not found a simple solution for this.

I'll try to help out with that

After encoding, 'Clever' insists that there is file-name_V01.mkv to be deleted.

I have now fixed it.

Thank you

[Findu]

Yes, of course.
I don't mean doing it with your entire film collection all at once, but rather, for example, per series where the files always have the same structure, or with recordings per camcorder or camera. So, step by step.
No problem if it stays that way for now.

[videoAI]

@ProWo

To show a progress bar in the taskbar icon using WinForms, you can utilize the
`ProgressBar` functionality available in the Windows API, specifically through the
`Taskbar` features. If you want to avoid adding external libraries, the built-in
.NET Framework does not provide direct access to taskbar progress features.

But, you can still achieve this by using the `Windows API` directly within your
WinForms application. The code below shows a progress bar in the taskbar icon
using WinForms & P/Invoke to access the Windows API functions directly.

Visual Basic

Imports System.Runtime.InteropServices
Imports System.Windows.Forms

Public Class MainForm
    Inherits Form

    Private Const TBPF_NOPROGRESS As Integer = 0
    Private Const TBPF_INDETERMINATE As Integer = 1
    Private Const TBPF_NORMAL As Integer = 2
    Private Const TBPF_ERROR As Integer = 4
    Private Const TBPF_PAUSED As Integer = 8

    <DllImport("shell32.dll", CharSet:=CharSet.Auto, SetLastError:=True)>
    Private Shared Function TaskbarSetProgressState(hwnd As IntPtr, state As Integer) As Integer
    End Function

    <DllImport("shell32.dll", CharSet:=CharSet.Auto, SetLastError:=True)>
    Private Shared Function TaskbarSetProgressValue(hwnd As IntPtr, completed As UInteger, total As UInteger) As Integer
    End Function

    Private WithEvents btnStart As Button

    Public Sub New()
        ' Initialize components
        Me.Text = "Taskbar Progress Example"
        Me.Size = New Drawing.Size(300, 150)

        btnStart = New Button()
        btnStart.Text = "Start"
        btnStart.Location = New Drawing.Point(100, 50)

        Me.Controls.Add(btnStart)
    End Sub

    Private Sub btnStart_Click(sender As Object, e As EventArgs) Handles btnStart.Click
        ' Start the progress
        TaskbarSetProgressState(Me.Handle, TBPF_NORMAL)
        For i As Integer = 0 To 100
            TaskbarSetProgressValue(Me.Handle, CUInt(i), 100)
            System.Threading.Thread.Sleep(50) ' Simulate work
        Next
        TaskbarSetProgressState(Me.Handle, TBPF_NOPROGRESS)
    End Sub

    <STAThread>
    Public Shared Sub Main()
        Application.EnableVisualStyles()
        Application.Run(New MainForm())
    End Sub
End Class

Explanation of the Code

1. Imports:
- `System.Runtime.InteropServices`: This namespace is used for P/Invoke to call Windows API functions.
- `System.Windows.Forms`: This namespace is used for creating Windows Forms applications.
2. Constants:
- Constants are defined for the taskbar progress states: `TBPF_NOPROGRESS`,
`TBPF_INDETERMINATE`, `TBPF_NORMAL`, `TBPF_ERROR`, and `TBPF_PAUSED`.
3. P/Invoke Declarations:
- `TaskbarSetProgressState`: This function sets the progress state of the taskbar.
- `TaskbarSetProgressValue`: This function sets the current progress value.
4. MainForm Class:
- The `MainForm` class inherits from `Form`, which is the base class for Windows Forms.
5. Button Initialization:
- A `Button` (`btnStart`) is created to start the progress.
6. Button Click Event:
- The `btnStart_Click` method is triggered when the button is clicked. It sets the taskbar
progress state to normal and updates the progress value in a loop from 0 to 100, simulating
work with `Thread.Sleep`.
7. Main Method:
- The `Main` method initializes the application and runs the `MainForm`.

Additional Notes

- Thread.Sleep: This is used to simulate work being done. In 'Clever', consider using
asynchronous programming to keep the UI responsive.
- Taskbar Support: Check if 'Clever' is running on Windows 7 or later, as taskbar progress
features are not available in earlier versions of Windows.

When 'Clever' is minimized to the task bar, the icon does not show progress.

I've not found a simple solution for this.

I'll try to help out with that.

[Findu]

@ ProWo

You cannot leave or return from the join page in v3.4.4.08.

[Findu]

Could the buttom text "Toggel output folder" simply indicate its status as before?
"Output: target folder" and "Output: source folder".

[Attachment 88066 - Click to enlarge]

[Attachment 88067 - Click to enlarge]

[ProWo]

@ ProWo

You cannot leave or return from the join page in v3.4.4.08.

Will fix it

EDIT: Done.

[ProWo]

Could the buttom text "Toggel output folder" simply indicate its status as before?
"Output: target folder" and "Output: source folder".

Good idea, thx. Will be done.

EDIT:
The text is too long.
I changed this to "Toggle destination"; the current status is displayed in the tooltip.

[Findu]

That's good too. Thank you.

If you update to nightly, the app window starts horizontally centered on the desktop. The previous/saved position get lost. Is this intentional?

[ProWo]

That's good too. Thank you.
If you update to nightly, the app window starts horizontally centered on the desktop. The previous/saved position get lost. Is this intentional?

I've to investigate on this.
I've added a new option in mux grid: mux whole grid. It's based on your idea to mux the whole grid in one go. Try it.

[Findu]

During the update, the saved window position is not restored only if the upper left corner of the window is in the upper left corner of the desktop.

---

Very cool, mux whole grid.
This is working well so far, but it is not easy to see that you can sort the grid by name. A color could help.

When "Mux whole grid" is set and as soon as I click "Hide stream" multiplexing begins. So you have no chance to change something you might have forgotten to hide. Could multiplexing only begin when you click "Multiplex"?

EDIT:
I know, for that to happen all streams would have to be marked before. An additional stepp.

EDIT 2:
If I select everything and set "Mux entire grid" and then multiplex, the grid sorts itself and muxes everything into one file.

EDIT 3: What about Sample? Could Show language codes move to Other settings to get back Sample?

[videoAI]

@ProWo

Could you please, when you have a chance, make these 2 checkboxes remember their last status till changed.


[Attachment 88077 - Click to enlarge]

Thank you and keep up the great work ..

[videoAI]

@ProWo,

We all want to see 'Clever' become the best FFmpeg GUI, and support all kinds of standards
in the process.

I wish you would consider changing the current FPS input box into a dropdown with
[Like Source, 24,25,30,(48?),(50?),60,120].

Currently, if you batch process multiple files, they all inherit the FPS of the first job. Selecting
'Like Source' would resolve this issue.

Here's a detailed breakdown of common frame rates (FPS) in video files:

1. 24 FPS
- Standard for cinema/film
- Provides a cinematic, slightly motion-blurred look
- Traditional movie standard since early film era

2. 25 FPS
- European broadcast standard (PAL)
- Commonly used in European television and video production

3. 30 FPS
- Traditional NTSC broadcast standard
- Used in North American television
- Smooth motion for live action content

4. 60 FPS
- High-definition video standard
- Smoother motion
- Popular in gaming, sports broadcasts
- Provides more fluid visual experience
- Reduces motion blur

5. 48 FPS
- Used in some modern films (e.g., The Hobbit)
- Provides hyper-realistic motion
- More frames than traditional cinema, less motion blur

6. 120 FPS
- Ultra-smooth motion
- Used in high-end sports and gaming content
- Extremely fluid visual representation

Factors influencing FPS choice:
- Content type
- Intended display medium
- Desired visual aesthetic
- Technical capabilities of recording/playback devices

[ProWo]

Very cool, mux whole grid.
This is working well so far, but it is not easy to see that you can sort the grid by name. A color could help.

The selection is made automatically.
Enough colors.

When "Mux whole grid" is set and as soon as I click "Hide stream" multiplexing begins. So you have no chance to change something you might have forgotten to hide. Could multiplexing only begin when you click "Multiplex"?

That's how it should be. Already fixed.

If I select everything and set "Mux entire grid" and then multiplex, the grid sorts itself and muxes everything into one file.

That is logical. With “Mux whole grid” active, however, you can now only select the first file.

What about Sample? Could Show language codes move to Other settings to get back Sample?

I have removed the sample muxing; it is unnecessary because muxing is fast.

[ProWo]

Could you please, when you have a chance, make these 2 checkboxes remember their last status till changed

The reset of these checkboxes is intentional.

[ProWo]

I wish you would consider changing the current FPS input box into a dropdown with
[Like Source, 24,25,30,(48?),(50?),60,120].

The source FPS is already preselected.
I don't want to restrict the FPS selection in order to be as flexible as possible.

Currently, if you batch process multiple files, they all inherit the FPS of the first job. Selecting
'Like Source' would resolve this issue.

The current batch options seemed to me to be sufficient.

[davidt1]

Can audio encoding settings like format and bit rate be memorized? Thanks.

[mannequin80]

if your last used Encoder is av1-svt, the Video Encoding page shows Tune and Fastdecode settings but if you try to select a different Encoder and then come back to av1-svt, those 2 settings disappear (3.4.4.10).

[ProWo]

if your last used Encoder is av1-svt, the Video Encoding page shows Tune and Fastdecode settings but if you try to select a different Encoder and then come back to av1-svt, those 2 settings disappear (3.4.4.10).

Close clever FFmpeg-GUI, open the portable.config file with a texteditor and delete the whole <save_set>/save_set> row.
Then save the file and restart clever FFmpeg-GUI.

[ProWo]

Can audio encoding settings like format and bit rate be memorized?

Bitrate is momorized, but the value is unused, because the bitrate is calculated in relation with the selected channels.
For format, what do you mean?

[davidt1]

Can audio encoding settings like format and bit rate be memorized?

Bitrate is momorized, but the value is unused, because the bitrate is calculated in relation with the selected channels.
For format, what do you mean?

for single audio encoding, I like Opus with a bitrate of 160. I just checked. Opus is memorized, but not the bitrate. Default bitrate is 64. Not a huge deal, but if the bitrate is memorized at 160, I wouldn't have to set it again. Thanks.

[mannequin80]

Close clever FFmpeg-GUI, open the portable.config file with a texteditor and delete the whole <save_set>/save_set> row.
Then save the file and restart clever FFmpeg-GUI.

didn't help, same issue - those 2 only shows up when av1-svt is the starting Encoder.

[videoAI]

🖥️ Clever FFmpeg GUI Review ... [by GPT-4o mini]

Clever FFmpeg GUI is a user-friendly graphical interface for the powerful FFmpeg multimedia framework.
It allows users to perform various audio and video processing tasks without needing to interact with the
command line. Below is a detailed review, including its pros and cons.

🟢 Pros

| Feature | Description |

| User-Friendly Interface | The GUI simplifies the complex functionalities of FFmpeg, making it accessible
for users who may not be comfortable with command-line tools. |
| Portable Application | It does not require installation; users can run it directly from a folder, making it
convenient for use on different machines. |
| Comprehensive Functionality | Supports a wide range of operations, including video conversion, audio
extraction, multiplexing, cutting, and joining files. |
| Batch Processing | Users can process multiple files simultaneously, saving time and effort. |
| Active Development | The software is regularly updated, with quick bug fixes and new features based
on user feedback. |
| Resource Efficiency | It operates smoothly without consuming excessive system resources, making it
suitable for various hardware configurations. |

🔴 Cons

| Feature | Description |

| Learning Curve | While the GUI is user-friendly, beginners may still find the interface somewhat confusing
at first, especially when navigating through various options. |
| Dependency on FFmpeg | Users must have FFmpeg installed and properly configured, which can be a
hurdle for those unfamiliar with the setup process. |
| Limited Advanced Features | Some advanced FFmpeg functionalities may not be fully accessible through
the GUI, potentially limiting experienced users. |
| Occasional Bugs | Although bugs are fixed quickly, some users have reported occasional glitches, particularly
with specific codecs or formats. |

🛠️ Functionality Overview

Clever FFmpeg GUI provides a range of features that cater to both novice and experienced users:

- Video Conversion: Convert between various formats (e.g., MP4, AVI, MKV).
- Audio Processing: Extract audio from video files or convert audio formats.
- Stream Management: Handle video streams, including multiplexing and demultiplexing.
- Editing Tools: Cut, join, and manage chapters in video files.
- Batch Processing: Process multiple files at once, enhancing productivity.

📝 User Feedback

Users have generally praised Clever FFmpeg GUI for its ease of use and functionality.
Many appreciate the continuous development and responsiveness of the developers
to user feedback. However, some users have noted the initial learning curve and the
need for FFmpeg installation as potential drawbacks.

Clever FFmpeg GUI stands out as a practical tool for those looking to leverage the
power of FFmpeg without the complexity of command-line operations. It is particularly
beneficial for users who need a straightforward solution for video and audio processing
tasks.

[videoAI]

Software Testing Overview

Software testing is a critical process in the software development life cycle (SDLC)
that involves evaluating a software application to ensure it meets objectives and
functions correctly. The primary goal of testing is to identify defects, ensure quality,
and verify that the software performs as expected.

�� Types of Testing

1. Unit Testing:
- Focuses on individual components or modules of the software.
- Typically performed by the developer to ensure that each unit
functions correctly.

2. Integration Testing:
- Tests the interaction between integrated components or systems.
- Ensures that combined parts work together as intended.

3. System Testing:
- Evaluates the complete and integrated software application.
- Tests the system against the specified requirements to ensure it behaves as expected.

4. User Acceptance Testing (UAT):
- Conducted by end-users to validate the software against their needs and requirements.
- Ensures that the software is ready for deployment and meets user expectations.

5. Regression Testing:
- Re-tests the software after changes (like bug fixes or new features) to ensure that
existing functionality remains unaffected.
- Helps catch any new defects introduced by changes.

6. Performance Testing:
- Assesses the speed, scalability, and stability of the software under various conditions.
- Includes load testing, stress testing, and endurance testing.

7. Security Testing:
- Identifies vulnerabilities and security flaws in the software.
- Ensures that data is protected and that the application is secure from threats.


⚙️ Testing Techniques

- Manual Testing: Testers execute test cases manually without automation tools.
This approach is useful for exploratory testing and scenarios requiring human
judgment.

- Automated Testing: Involves using scripts and tools to automate the execution
of test cases. This is efficient for repetitive tasks and regression testing.


�� Importance of Testing

- Quality Assurance: Ensures that the software meets quality standards and performs as expected.
- Defect Identification: Helps identify and fix defects before the software is released.
- User Satisfaction: Increases user confidence and satisfaction by delivering a reliable and functional product.

Testing is an essential part of software development that helps ensure the delivery of high-quality applications.
By employing various testing types and techniques, teams can effectively identify and resolve issues, leading
to a more reliable and user-friendly product.

[ProWo]

didn't help, same issue - those 2 only shows up when av1-svt is the starting Encoder.

Fixed now.

[ProWo]

for single audio encoding, I like Opus with a bitrate of 160. I just checked. Opus is memorized, but not the bitrate. Default bitrate is 64. Not a huge deal, but if the bitrate is memorized at 160, I wouldn't have to set it again. Thanks.

Is done now.

[Findu]

Did you perhaps disable the video stream analysis before/during encoding?
Because if I use an unsupported encoder, it no longer aborts with an error message, instead it creates a 0 KB file.

Error message from the mux page:
This file cannot be analyzed.
input_V0.mkv

[ProWo]

Did you perhaps disable the video stream analysis before/during encoding?

Yes, because some users are annoyed by the error messages.

EDIT: I will reintroduce an error check for unsupported encoders.

[Findu]

I have a test TV recording with a transmission gap in the stream. Now the file is being converted completely, with the gap and image errors. Previously, the encoding stopped at the gap with an error message.
Could the error check be enabled/disabled as an option?

EDIT: I would always leave the error check enabled. If an error occurs, I could then decide file by file whether I want to encode the video with errors or gaps.

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?

[Findu]

>> This is working well so far, but it is not easy to see that you can sort the grid by name. A color could help.
> The selection is made automatically. Enough colors.

Sorry. I described that poorly. I mean the column "Filename" is able to sort by name but you can not see that good. But it's helpful for hiding streams before using "Mux whole grid." Many people may not know that this sorting is possible.
That would work with little paint

[Attachment 88089 - Click to enlarge]

---

Are these “Mux whole grid” rules correct?
- Everything that is visible in the grid will be muxed.
- All selected streams get muxed into one file.
- The unselected streams get muxed according to name.