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

[Marcellos]

Also when you use cropping on any codec encoder :

[Attachment 82715 - Click to enlarge]

you do not have the page when you choose scale algorithm when you press encode :

[Attachment 82716 - Click to enlarge]

and the movie is encoded with the black border


[Attachment 82717 - Click to enlarge]

Hope there is just a glitch and will be corrected if it is possible !!

Thanks for this great tool !!!

[ProWo]

After version clever_f3.2.8.03 when you try svt-av1 encode you have this error

[Attachment 82713 - Click to enlarge]
Thanks

Your settings make no sense.
You first cropped with the result 1280x688, which gives a DAR of 1.85.
If you resize to frame width 1920 then the frame height must be 1036 with the same DAR, and not 1080 as in your picture.
Padding with the same values as frame with and frame height makes no sense and is pointless.

As for the error:
I confirm it. The FFmpeg code has been changed.
(av1 only supported in MP4 and AVIF, and not in mov, as before).
I will change this in the next beta.

In the meantime there is the following workaround:
Make your settings and then click on To batch, instead of encode.
Then quit clever FFmpeg-GUI.

You will now find a new text file BT_open.txt in your destination folder.

Open it in your text editor and change .mov to .mp4
Save the file, close the text editor and restart clever FFmpeg-GUI.

This will now start directly into the batch grid.
Click execute, and your AV1 video will now be encoded correctly.

[Marcellos]

After version clever_f3.2.8.03 when you try svt-av1 encode you have this error

[Attachment 82713 - Click to enlarge]
Thanks

Your settings make no sense.
You first cropped with the result 1280x688, which gives a DAR of 1.85.
If you resize to frame width 1920 then the frame height must be 1036 with the same DAR, and not 1080 as in your picture.
Padding with the same values as frame with and frame height makes no sense and is pointless.

What is the point of cropping if i want the same resolution to be 1920:1080 like i did before and not 1920:1036 as you say ?

Just like i do it with ffmpeg script for example : -vf "yadif=0:0:0,crop=1280:692:0:14,scale=1920:1080:fl ags=lanczos,setsar=1:1" -r 24 -aspect 1.7777
Thanks again !!!

[ProWo]

What is the point of cropping if i want the same resolution to be 1920:1080 like i did before and not 1920:1036 as you say ?
Just like i do it with ffmpeg script for example : -vf "yadif=0:0:0,crop=1280:692:0:14,scale=1920:1080:fl ags=lanczos,setsar=1:1" -r 24 -aspect 1.7777
Thanks again !!!

Every movie has its original aspect ratio, i.e. the ratio of frame width to frame height.
You should not change this aspect ratio, as this will change the visual result.

So if you resize from 1280x692 (1.85) to 1920x1036 (1.85) then the visual result is the same.
If you resize from 1280x692 (1.85) to 1920x1080 (1.78) then the visual result is changed.
If you absolutely want to change the output format to 1920x1080, then you must resize to 1920x1036 and pad to 1920x1080.
In this case black bars above and bottom are added.

You could also resize the whole 1280x720 to 1920x1080, without any cropping.

[videoAI]

Autoupdate on startup would be a good idea

[oniiz86]

@ProWo I've PM'ed you over at the Doom9 forums but thought I'd let you know here, I've discovered a video encoding bug in the latest Beta v3.3.0.02 that isn't present in the previous Beta v3.3.0.01 or the Official v3.3.0 release, a "Error creating an internal frame pool" dialog pops up, do you think you may know what this may be?

[Attachment 82797 - Click to enlarge]

[ProWo]

@ProWo I've PM'ed you over at the Doom9 forums but thought I'd let you know here, I've discovered a video encoding bug in the latest Beta v3.3.0.02 that isn't present in the previous Beta v3.3.0.01 or the Official v3.3.0 release, a "Error creating an internal frame pool" dialog pops up, do you think you may know what this may be?

[Attachment 82797 - Click to enlarge]

Hi oniiz86,
I can't reproduce that here.
Does this also happen with another movie or only with this one?
Which settings did you make exactly?
Post a mediainfo report from this movie here.

[oniiz86]

@ProWo I've PM'ed you over at the Doom9 forums but thought I'd let you know here, I've discovered a video encoding bug in the latest Beta v3.3.0.02 that isn't present in the previous Beta v3.3.0.01 or the Official v3.3.0 release, a "Error creating an internal frame pool" dialog pops up, do you think you may know what this may be?

[Attachment 82797 - Click to enlarge]

Hi oniiz86,
I can't reproduce that here.
Does this also happen with another movie or only with this one?
Which settings did you make exactly?
Post a mediainfo report from this movie here.

Here is the Neighbors MediaInfo report,

Complete name : Q:\Neighbors 1981.mkv
Format : Matroska
Format version : Version 4
File size : 6.85 GiB
Duration : 1 h 35 min
Overall bit rate mode : Variable
Overall bit rate : 10.3 Mb/s
Frame rate : 23.976 FPS
Movie name : Neighbors (1981) / Neighbors (1981)
Encoded by : Sartre
ContentType : Movie
Description : Lock the doors... here come the Neighbors
Released date : 1981-12-18
Recorded date : 1981-12-18
Writing application : mkvmerge v86.0 ('Winter') 64-bit
Writing library : libebml v1.4.5 + libmatroska v1.7.1
Cover : Yes
Attachments : cover.jpg / kodi-metadata
ACTOR : John Belushi, Kathryn Walker, Cathy Moriarty, Dan Aykroyd
ARTIST : John Belushi, Kathryn Walker, Cathy Moriarty, Dan Aykroyd
DIRECTOR : John G. Avildsen
GENRE : Comedy
PRODUCER : David Brown, Richard D. Zanuck
PRODUCTION_STUDIO : Zanuck/Brown Productions
SCREENPLAY_BY : Larry Gelbart
SUMMARY : Lock the doors... here come the Neighbors
SYNOPSIS : One man's quiet suburban life takes a sickening lurch for the worse when a young couple move into the deserted house next door. From the word go it is obvious these are not the quiet professional types who *should* be living in such a nice street. As more and more unbelievable events unfold, our hero starts to question his own sanity... and those of his family.
WRITTEN_BY : Larry Gelbart

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 35 min
Width : 1 920 pixels
Height : 1 040 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Title : Neighbors.1981.Sony.1080p.BluRay.x265.HEVC.FLAC-SARTRE
Writing library : x265 3.6+65+67-7ee6bf075:[Windows][MSVC 1928][64 bit] 10bit

Audio
ID : 2
Format : FLAC
Format/Info : Free Lossless Audio Codec
Codec ID : A_FLAC
Duration : 1 h 35 min
Bit rate mode : Variable
Channel(s) : 1 channel
Channel layout : M
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Compression mode : Lossless
Title : FLAC 1.0
Writing library : libFLAC 1.3.3 (2019-08-04)
Language : English
Default : Yes
Forced : No
MD5 of the unencoded conten : 53C6DC5824B75B55EBAD0C10B0A10169

I've tried another film with a HEVC stream & I received the same error, perhaps it's HEVC related as there are no such issues with AVC streams?

[Attachment 82798 - Click to enlarge]

Also for some strange reason the frame rate is reported as 23.81 fps in the top right hand corner not the proper 23.976 fps, the MediaInfo reports 23.976 (24000/1001) but for some strange reason when I actually play the file with MPC-HC & click on File then Properties the dialog box reports the frame rate as 23.81fps.

[Attachment 82799 - Click to enlarge]

Complete name : Q:\Beetlejuice 1988.mkv
Format : Matroska
Format version : Version 4
File size : 3.62 GiB
Duration : 1 h 32 min
Overall bit rate : 5 620 kb/s
Frame rate : 23.976 FPS
Encoded date : 2023-09-07 19:16:47 UTC
Writing application : mkvmerge v67.0.0 ('Under Stars') 64-bit
Writing library : libebml v1.4.2 + libmatroska v1.6.4

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 32 min
Bit rate : 4 484 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.090
Stream size : 2.88 GiB (80%)

Here is a short sample https://www.sendspace.com/file/l9cd2p

[ProWo]

Here is a short sample https://www.sendspace.com/file/l9cd2p

This example is 23.81 fps.

from ffprobe:
"r_frame_rate": "500/21",
"avg_frame_rate": "500/21",

You can fix this with main, various, fix framerate, enter 23.976 and click fix.


as for the error:
no problem here with encoding this hevc example to avc with x264 and clever FFmpeg-GUI v3.3.0.02


[Attachment 82800 - Click to enlarge]

[oniiz86]

Here is a short sample https://www.sendspace.com/file/l9cd2p

This example is 23.81 fps.

from ffprobe:
"r_frame_rate": "500/21",
"avg_frame_rate": "500/21",

You can fix this with main, various, fix framerate, enter 23.976 and click fix.


as for the error:
no problem here with encoding this hevc example to avc with x264 and clever FFmpeg-GUI v3.3.0.02


[Attachment 82800 - Click to enlarge]

Thanks for that, I tried it again with the short sample I gave you but no such luck, it's strange that the Official v3.3.0 & Beta v3.3.0.01 have no such issues, did you happen to change the code between Beta v3.3.0.01 & v3.3.0.02? I wonder what "Error creating an internal frame pool" & "could not create the surfaces" means?

[Attachment 82801 - Click to enlarge]

I was wondering if you could add a reference to the Pixel Format options mentioning 8 Bit & 10 Bit as I accidentally encoded a 10 Bit HEVC file to 10 Bit AVC as I left this option set to "Auto", I didn't realise I had to select yuv420p for 8 Bit & yuv420p10le for 10 Bit, I believe previously the Pixel Format options were simply 8 Bit or 10 Bit, would yuv420p (8 bit) & yuv420p10le (10 bit) be possible?

[ProWo]

What's your ffmpeg version?
Try to update to the latest beta
https://www.gyan.dev/ffmpeg/builds/ffmpeg-git-full.7z

edit:

Try the following:
Make your settings in the video encode section.
Then click on to batch instead of encode.
Quit the program.

In the destination folder you will find a new text file called BT_open.txt.
Open it with your text editor and search for -hwaccel auto.
Select and delete it. Save the file.

Then restart clever FFmpeg-GUI, you will be automatically redirected to the batch tasks grid. Click on execute.
Is the batch task now executed without errors?

[oniiz86]

@ProWo Unfortunately I'm still on Windows 7, I believe I can only use FFmpeg 7.0.1 Essentials Build, will a previous FFmpeg 6.6.1 build still work reliably with your latest version of Clever FFmpeg-GUI?

[oniiz86]

What's your ffmpeg version?
Try to update to the latest beta
https://www.gyan.dev/ffmpeg/builds/ffmpeg-git-full.7z

edit:

Try the following:
Make your settings in the video encode section.
Then click on to batch instead of encode.
Quiet the program.

In the destination folder you will find a new text file called BT_open.txt.
Open it with your text editor and search for -hwaccel auto.
Select and delete it. Save the file.

Then restart clever FFmpeg-GUI, you will be automatically redirected to the batch tasks grid. Click on execute.
Is the batch task now executed without errors?

I don't believe it but I removed "-hwaccel auto" from the text file & went to execute the task & it is now all fine , was there a change implemented in the latest Beta v3.3.0.02?

[ProWo]

I don't believe it but I removed "-hwaccel auto" from the text file & went to execute the task & it is now all fine , was there a change implemented in the latest Beta v3.3.0.02?

Yes, this was added in the last beta and it works fine with Windows 10+11, but as you can see, not with Windows 7.
I will remove it again in the next beta, as it does not bring any great advantage.

[ProWo]

Newest beta (v3.3.0.03), online now.

Added:
Output filename check for existing files or batch tasks.

Fixed:
Bug with av1 encoding (thx to Marcellos for the hint).

Improved:
Crop handling code.

Changed:
Output files destination handling.

Removed:
hwaccel auto (not working on Win7, thx to oniiz86 for the hint).

[oniiz86]

@ProWo I downloaded the latest Beta v3.3.0.03 but the actual GUI version is 3.3.0.02 & the error is still present for me, this "Error creating an internal frame pool" pop up is still happening, has the Beta link been correctly updated?

Not sure if you saw in my above post regarding 8 Bit & 10 Bit references to yuv420p & yuv420p10le, could this be added to the Pixel Format options like the following, yuv420p (8 bit) & yuv420p10le (10 bit) would that be possible?

[ProWo]

@ProWo I downloaded the latest Beta v3.3.0.03 but the actual GUI version is 3.3.0.02 & the error is still present for me, this "Error creating an internal frame pool" pop up is still happening, has the Beta link been correctly updated?

Not sure if you saw in my above post regarding 8 Bit & 10 Bit references to yuv420p & yuv420p10le, could this be added to the Pixel Format options like the following, yuv420p (8 bit) & yuv420p10le (10 bit) would that be possible?

The correct download link is the one form page #1 of thís thread, and the beta is updated to v3.3.0.03
The pixel formats yuv420p and yuv420p10le are already avaiable for the x264 encoder.
The #10 stays for 10 bits. (yuv420p10le)

[oniiz86]

@ProWo I downloaded the latest Beta v3.3.0.03 but the actual GUI version is 3.3.0.02 & the error is still present for me, this "Error creating an internal frame pool" pop up is still happening, has the Beta link been correctly updated?

Not sure if you saw in my above post regarding 8 Bit & 10 Bit references to yuv420p & yuv420p10le, could this be added to the Pixel Format options like the following, yuv420p (8 bit) & yuv420p10le (10 bit) would that be possible?

The correct download link is the one form page #1 of thís thread, and the beta is updated to v3.3.0.03
The pixel formats yuv420p and yuv420p10le are already avaiable for the x264 encoder.
The #10 stays for 10 bits. (yuv420p10le)

The latest Beta v3.3.0.03 application is dated 3/10/2024 which suggests it hasn't been updated that was the previous Beta v3.3.0.02 application date, should it not be 13/10/2024, strange the GUI still indicates v3.3.0.02 as you can see below,

[Attachment 82803 - Click to enlarge]

[ProWo]

@ProWo I downloaded the latest Beta v3.3.0.03 but the actual GUI version is 3.3.0.02 & the error is still present for me, this "Error creating an internal frame pool" pop up is still happening, has the Beta link been correctly updated?

Not sure if you saw in my above post regarding 8 Bit & 10 Bit references to yuv420p & yuv420p10le, could this be added to the Pixel Format options like the following, yuv420p (8 bit) & yuv420p10le (10 bit) would that be possible?

The correct download link is the one form page #1 of thís thread, and the beta is updated to v3.3.0.03
The pixel formats yuv420p and yuv420p10le are already avaiable for the x264 encoder.
The #10 stays for 10 bits. (yuv420p10le)

The latest Beta v3.3.0.03 application is dated 3/10/2024 which suggests it hasn't been updated that was the previous Beta v3.3.0.02 application date, should it not be 13/10/2024, strange the GUI still indicates v3.3.0.02 as you can see below,

[Attachment 82803 - Click to enlarge]

This isn't version 3.3.0.03...

[oniiz86]

@ProWo That's what I'm saying, the Beta v3.3.0.03 link on the first page of this thread, when I clicked on it, it's still the previous Beta v3.3.0.02, it's a strange one, I don't think it's a browser cache issue on my end.

[ProWo]

I checked the zip file for download again and it definitely contains version 3.3.0.03.

You are doing something wrong.
I think you are using the wrong zip file. Check your download folder.

In which folder was the previous version 3.3.0.02?
In this folder, overwrite only the file clever FFmpeg-GUI.exe with the new one from the zip archive you downloaded.
Leave the other files as they are.
Then double-click the new clever FFmpeg-GUI.exe.

[oniiz86]

I checked the zip file for download again and it definitely contains version 3.3.0.03.

You are doing something wrong.
I think you are using the wrong zip file. Check your download folder.

In which folder was the previous version 3.3.0.02?
In this folder, overwrite only the file clever FFmpeg-GUI.exe with the new one from the zip archive you downloaded.
Leave the other files as they are.
Then double-click the new clever FFmpeg-GUI.exe.

I normally allow it d/l to the desktop, I'm really silly, so sorry about this but it was a Chrome browser cache issue, I cleared the cache, then d/l the Beta again & it was the correct link this time around with Beta v3.3.0.03, never happened to me before when d/l your utility but there is always a first time, oh & that error is no longer present now, thanks so much again

Edit: Since the utility has become portable, if there is an issue, is there a file to delete like there was previously under the Users/Master/AppData/Local path, is this the file "clever FFmpeg GUI.exe.config" to delete?

[ProWo]

Yes, correct.

[oniiz86]

@ProWo You had helped me with 2 25fps sources, one had a 5.1 track with a duration of 01:31:40.992 & it's video has a duration of 01:31:42.200, I wanted this 5.1 track to sync up with a different video that has a duration of 01:31:42.760 & its 2.0 track has a duration of 01:31:34.784, I made a mistake telling you that the 5.1 track had a duration of 01:31:34.784 when it was really 01:31:40.992, I used this calculation that you told me 01:31:34.784 = 5494.784 seconds
01:31:40.992 = 5500.992 seconds & 5494.784 : 5500.992 = 0.99887148, the Factor 0.99887148 made the 5.1 audio track's new duration come to 01:31:47.207 so for some strange reason it's greater than the video track duration of 01:31:42.760, perhaps it's not possible to re-encode the 5.1 audio stream with the factor adjustment, must I have to add an "ms" delay, I've observed that the audio is slightly ahead of the video?

[ProWo]

Hi oniiz86,

both videos are 25 fps?

Your data above is strange.
The target video has a duration of 01:31:42.760 and its stereo audio track has a length of 01:31:34.784?
That's almost 6 seconds difference!
Is there an audio delay of almost 6 seconds?
Load this video into clever FFmpeg GUI and post a picture of the source file info screen, the video encoding screen and the audio encoding screen so I can check all the timings.

We will deal with the 5.1 audio stream later.

[oniiz86]

Hi oniiz86,

both videos are 25 fps?

Your data above is strange.
The target video has a duration of 01:31:42.760 and its stereo audio track has a length of 01:31:34.784?
That's almost 6 seconds difference!
Is there an audio delay of almost 6 seconds?
Load this video into clever FFmpeg GUI and post a picture of the source file info screen, the video encoding screen and the audio encoding screen so I can check all the timings.

We will deal with the 5.1 audio stream later.

Yes that's correct both sources are 25fps, yes I know it is bizarre that there is an audio delay of almost 6 seconds but there is no apparent sync issue oddly enough, I'm not complaining as it is perfectly in sync.

[Attachment 82808 - Click to enlarge]

[Attachment 82809 - Click to enlarge]

[Attachment 82810 - Click to enlarge]

[ProWo]

OK, that's good, no audio delay, the audio is shorter then the video, but the difference stays at the end, with almost 6 seconds missing, but this is no problem in this case.

The 5.1 track does not need to be re-encoded, it is just a matter of finding the correct start.
Simply mux it with the new video and play it.
If you are lucky, it will already be synchronized.

If not, you will need to find the correct audio delay.
Play it with the VLC player and change the value of synch audio track (menu tools, synch tracks) until the audio is synchronized.
Note the value and remux the 5.1 track with the new video and enter the noted value in Audio delay.
The audio should now be synchronized.

[oniiz86]

@ProWo Thanks, I've already tried to simply mux the 5.1 track with the other video source but it was fairly out of sync but I'll report back with what I find using VLC player, hopefully only -10ms of delay will be needed.

I just thought for reference these are from the 25fps source with the 5.1 track,

[Attachment 82811 - Click to enlarge]

[Attachment 82812 - Click to enlarge]

[Attachment 82813 - Click to enlarge]

I don't understand why the 5.1 track will not simply sync up correctly as they are both 25fps sources with a slightly different video duration, the 5.1 track has a video duration of 01:31:42.760 & the other source with the 2.0 track has a video duration of 01:31:42.200, so a difference of 560 milliseconds.

[oniiz86]

@ProWo I think I've nailed the 5.1 audio track synchronization, it only required .500 s of delay (is this merely half a second of delay, is it the equivalent of 50ms) according to VLC player using "Track Synchronization", now is there an option to re-mux this track with the delay using Clever FFmpeg-GUI or must I use MKVToolNix?

[Attachment 82822 - Click to enlarge]

[ProWo]

In the mux grid, in the audio stream row.


[Attachment 82823 - Click to enlarge]