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

[videoAI]

Adobe Premiere’s Essential Sound potential export formats: [.m4a] or [.mp4] with AAC audio

1. It is better to select .m4a format
2. Select the audio track you want to export
3. Open the Essential Sound panel (Window > Essential Sound)
4. Choose the appropriate audio type (Dialog, Music, SFX, etc.)
5. Click the Export button in the Essential Sound panel
6. In the export settings:
- Choose AAC as the audio codec
- Select desired bitrate (typically 256 kbps for good quality)
- Pick your output location
7. Click Export

[videoAI]

ffprobe false positive

ffprobe can sometimes falsely detect a "video stream" in a text file due to how it attempts to parse
and interpret file contents.

This happens because:

1. ffprobe tries to interpret raw binary data as a potential multimedia stream
2. Text files contain binary data that, when misinterpreted, might look like a video stream to the tool
3. The detection is often a false positive and doesn't mean the file actually contains a valid video track.

Potential Reasons for False Detection:
1- Random binary patterns in the text file that resemble video stream headers
2- Encoded or compressed text files with unusual binary representations
3- Specific text encodings or file formats that confuse ffprobe's stream detection


[Attachment 90013 - Click to enlarge]


[Attachment 90015 - Click to enlarge]

[ProWo]

Hi ProWo – to explain further…bear with me, hope this makes some sense…

Please post a pic from this clever FFmpeg-GUI's multiplex window here.

[Findu]

@ ProWo

Suggestion for the Scan for errors page.

How about showing all option frames, aktive and inaktive?

Before the scan:

[Attachment 90020 - Click to enlarge]

After the scan when errors have been found:

[Attachment 90021 - Click to enlarge]

After viewing the errors, when you answer Yes or No, you sould be directed to the Main page.

[Attachment 90022 - Click to enlarge]

Currently you see that empty Scan page.

[Attachment 90023 - Click to enlarge]

[Findu]

@ ProWo
v3.4.9.03

Spectogram does not open Photos.exe any longer.

[Findu]

@ ProWo

Would it be useful to offer a pan audio filter that allows the volume of each audio channel to be changed manually?
A simple example for muting the left channel of a stereo output: -af "pan=stereo:c0=0*c0|c1=1*c1"
The same ffmpeg filter also works with ffplay for previewing.

[ProWo]

@ ProWo
v3.4.9.03

Spectogram does not open Photos.exe any longer.

Thx, fixed now.

[ProWo]

@ ProWo
Would it be useful to offer a pan audio filter that allows the volume of each audio channel to be changed manually?
A simple example for muting the left channel of a stereo output: -af "pan=stereo:c0=0*c0|c1=1*c1"

Is already implemented in the remap filter.

[Angy86]

Interesting

[videoAI]

v3.4.9.04

Q: Did you know that 'Clever' is a screen recorder?
A: Don't believe me? check out the attached video.

Q: But, .. did you know that Clever can encode a plain
text file into a video [mp4, mkv, etc]?

How? read on ..

1- I dragged a plain text file into Clever.

2- Clever says 'No Video/Audio/Subtitle information detected'.
but we know better .. under the Encode/Convert section, a
video stream is already visible. hmm .. did ffprobe detect a
video stream in a plain text file !!!!

3- Clicking the video stream button, encode -> Clever produces
an mkv video file without any complaints. Interesting ..

4- Clicking multiplex, Clever complains 'file is not allowed for multiplexing.'
Clever is still complaining about the loaded text file, but we now better
because the mkv file produced from the text file in step #3 is already in
the Mux grid. Can we use it? off course we can.

Ok, so I used some loopholes .. but it was Cool .. huh ..

[ProWo]

v3.4.9.04

Q: Did you know that 'Clever' is a screen recorder?
A: Don't believe me? check out the attached video.

Q: But, .. did you know that Clever can encode a plain
text file into a video [mp4, mkv, etc]?

How? read on ..

1- I dragged a plain text file into Clever.

2- Clever says 'No Video/Audio/Subtitle information detected'.
but we know better .. under the Encode/Convert section, a
video stream is already visible. hmm .. did ffprobe detect a
video stream in a plain text file !!!!

3- Clicking the video stream button, encode -> Clever produces
an mkv video file without any complaints. Interesting ..

4- Clicking multiplex, Clever complains 'file is not allowed for multiplexing.'
Clever is still complaining about the loaded text file, but we now better
because the mkv file produced from the text file in step #3 is already in
the Mux grid. Can we use it? off course we can.

Ok, so I used some loopholes .. but it was Cool .. huh ..

As you see, I've implemented a few new features in this nightly ...

[jopavirando]

Hey Prowo, the new features are great, but I can't burn subtitles into videos anymore. I'm behind. What did I miss?

[ProWo]

Hey Prowo, the new features are great, but I can't burn subtitles into videos anymore. I'm behind. What did I miss?

Load your video, click encode video, check burn-in subitles, drag or add your subtitle, click encode.

[videoAI]

FYI .. Win 11 bug
https://forum.videohelp.com/threads/418685-Finally-found-an-amazing-video-crop-app#post2787688

[Findu]

@ ProWo
v3.4.9.04 Feedback

Thx for the last fix and for adding the new mux tooltips. Now you can see more clearly what will happen.

The "four" grid options after muxing do exactly as discribed in the tooltips. Also for Simple remux and Mux whole grid. Great!

The tooltip for Attachments could expand to "Add or remove image/font only for MKV containers."
And could the tooltip also be visible for the inactive button?
Because if you don't know about the mkv container, you wonder why the button is always inactive.

Pls expand the tooltip for New DAR values at the Lossless page as well.

---

I muxed a buggy file with show the "AC3 5.1 patch" for audio stream 1. Nothing was patched, and when you click OK at the dialog, the Audio encoding page is closing. Is that intentional?


[Attachment 90046 - Click to enlarge]


[Attachment 90047 - Click to enlarge]

I attach the buggy cut file for you to check.

[jopavirando]

Hey Prowo, the new features are great, but I can't burn subtitles into videos anymore. I'm behind. What did I miss?

Load your video, click encode video, check burn-in subitles, drag or add your subtitle, click encode.

What container should I burn it to? Maybe MP4 because it doesn't do that in MKV.

[ProWo]

What container should I burn it to? Maybe MP4 because it doesn't do that in MKV.

I think you are in wrong section. In video encoding section you can't set the container.
Go to the video encoding section (Encode/convert Video stream) to burn-it your subtitle.

[Findu]

@ ProWo

You have PM

[jopavirando]

What container should I burn it to? Maybe MP4 because it doesn't do that in MKV.

I think you are in wrong section. In video encoding section you can't set the container.
Go to the video encoding section (Encode/convert Video stream) to burn-it your subtitle.

sorry, you're right.

[Findu]

@ ProWo

I forgot to mention that if you enter an audio remap value that is too high, this popup window appear, with a space missing.

[Attachment 90062 - Click to enlarge]

[Findu]

@ ProWo

Cuting audio files - audio playback

FFplay offers a live spectrogram during audio playback, but no timecode.

How about adding a playback button that simply launches any standard Windows audio player?
Like a cmd with the full path to the audio file. Most of them display the timecode you need for your audio cut points. And you don't have to quit the player to search for the next timecodes. Nothing needs to be configured in the app, and it's easier than having the user start playback separately.

[ProWo]

Cuting audio files - audio playback
FFplay offers a live spectrogram during audio playback, but no timecode.
How about adding a playback button that simply launches any standard Windows audio player?

Good idea, thx. Will be implemented.

[Findu]

@ ProWo

You have PM

[Findu]

@ ProWo
3.4.9.05 feedback

Thank you for the last changes and fixes.

The audio remapping value check works well.
Good idea to insert the corresponding composing channel as formula instead of c1.

How about that formatting?
Now

[Attachment 90100 - Click to enlarge]

New

[Attachment 90101 - Click to enlarge]

---

The Cut page button for audio playback is working. Thanks.
Could you change the tooltip text like "Find your cut points for audio & video (in case at I-Frames)."

---

How about that grid options order?

Remove selected rows
Clear selected rows
Keep selected rows
Clear all rows
---

Could you also change the tooltip for New DAR values at the Lossless page.

1,33 = 4:3
1,78 = 16:9
1,85 = Cinema
2,39 = Cinemascope

[ProWo]

How about that formatting?

Nice, will be changed.

Could you change the tooltip text like "Find your cut points for audio & video (in case at I-Frames)."

I'll add a new tooltip for audio only.

How about that grid options order?
Remove selected rows
Clear selected rows
Keep selected rows
Clear all rows

No. I prefer the current order.

Could you also change the tooltip for New DAR values at the Lossless page.
2,39 = Cinemascope

You're right, the actual value for scope film is 2.39:1. Will change it from 2.35 to 2.39.

[Findu]

@ ProWo

You have PM

[OldCodger]

Hi videoAI , thanks for your reply and expert information. Although I could see no Export button in my Essential Sound Panel, I did manage to change the Export format to AAC AUDIO with no Video and it produced the requisite *.AAC file, which then worked perfectly with clever FFmpeg GUI.
(I tried the 3 dot menu but it was too convoluted for me to find what I was looking for).
Naively, I had assumed Premiere would make the required adjustments to the export format with no video and just AAC audio selected…as it appeared on the Output summary.

So videoAI ,thanks again for your most valuable guidance, much appreciated.

I’ll look at making a suitable preset for future use.
Regards…

P.S. I also experimented saving the same audio from within Davinci Resolve – which exported it as *.MP4 but it was in ‘QuickTime TC’ format and worked without a problem in clever FFmpeg GUI.

[oniiz86]

Could you also change the tooltip for New DAR values at the Lossless page.
2,39 = Cinemascope

You're right, the actual value for scope film is 2.39:1. Will change it from 2.35 to 2.39.

@ProWo Well is there any chance you could allow both values as 2.35:1 is still a common CinemaScope aspect ratio, why not mention both 2.35:1 & 2.39:1?

[videoAI]

| Aspect Ratio | Details | Usage |
|--------------|---------|-------|
| 2.35:1 | Predecessor to 2.39:1 | Classic widescreen format |
| 2.39:1 | Modern standard | Current cinema format |

Historical Context
- 2.35:1 was the original CinemaScope aspect ratio from the 1950s
- 2.39:1 gradually replaced 2.35:1 in professional cinematography
- Very similar ratios, often used interchangeably in practice

Technical Considerations
- Minimal difference between 2.35:1 and 2.39:1
- Both require letterboxing on 16:9 displays
- Most modern video tools treat these ratios similarly

Could you also change the tooltip for New DAR values at the Lossless page.
2,39 = Cinemascope

You're right, the actual value for scope film is 2.39:1. Will change it from 2.35 to 2.39.

@ProWo Well is there any chance you could allow both values as 2.35:1 is still a common CinemaScope aspect ratio, why not mention both 2.35:1 & 2.39:1?

[Findu]

@ ProWo

How about moving the buttons to the left? That looks neater.


[Attachment 90118 - Click to enlarge]


[Attachment 90119 - Click to enlarge]