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

[ProWo]

@FTG
I have now tested different variants, but everything is as expected.
Can you describe the problem using an example?

[FTG]

@FTG
I have now tested different variants, but everything is as expected.
Can you describe the problem using an example?

I tested it more deeply, and it turns out it isn't a problem with your tool, but the player I'm using.
I will report the issue to the player's developers.

By the way, while testing, I needed to encode the same file a few times, to which the "Keep open"
option came handy, but there is still something which got in the way: same filenames output. Converting
the same source file but with at least one different parameter, won't change the output filename automatically,
nor will allow to change it manually neither through the tool itself; so, I had to change each previously converted
filename manually through Windows between conversions.

[ProWo]

By the way, while testing, I needed to encode the same file a few times, to which the "Keep open"
option came handy, but there is still something which got in the way: same filenames output. Converting
the same source file but with at least one different parameter, won't change the output filename automatically,
nor will allow to change it manually neither through the tool itself; so, I had to change each previously converted
filename manually through Windows between conversions.

Will be fixed in the next beta.

[ProWo]

Newest beta (v3.1.8.02), online now.

New:
Batch processed tasks preserved on application exit or shutdown.

Fixed:
Bug in video indexing.
Bug in batch processing avs tasks.
Bug in get source codec with DTS audio.
Bug in progressbar on batch processing.

Changed:
Output files naming (audio and video encoding).

Improved:
Preprocessed and batch streams handling.
Stream duration analysis.

[FTG]

OK, thanks.

By the way, about the problematic file I talked before, the PotPlayer's devs told me
something like it was due to the file itself, because:

...the exact length of the RAW file is unknown. Therefore, it is shown as an approximation,
and each player measures it differently. In other words, "01:52:51" shown by other players
is also an incorrect value, and the correct value is approximately "01:52:40". You can find out
by playing from beginning to end without seeking.

I doubt it, but the thing is, after playing the same file with different players (MPC, PowerDVD, DVDFab Player,
etc.) all of them always show me "01:52:51"; and loading the file into "Audacity", also shows a "01:52:51" length.
And as I commented before, by simply changing only the audio file's frequency from the original "44.1 kHz" to "48 kHz",
will make PotPlayer shows the expected length ("01:52:51"). Although it plays fine, maybe the file is corrupted somehow,
I'm not sure about it.

[ProWo]

OK, thanks.

By the way, about the problematic file I talked before, the PotPlayer's devs told me
something like it was due to the file itself, because:

...the exact length of the RAW file is unknown. Therefore, it is shown as an approximation,
and each player measures it differently. In other words, "01:52:51" shown by other players
is also an incorrect value, and the correct value is approximately "01:52:40". You can find out
by playing from beginning to end without seeking.

I doubt it, but the thing is, after playing the same file with different players (MPC, PowerDVD, DVDFab Player,
etc.) all of them always show me "01:52:51"; and loading the file into "Audacity", also shows a "01:52:51" length.
And as I commented before, by simply changing only the audio file's frequency from the original "44.1 kHz" to "48 kHz",
will make PotPlayer shows the expected length ("01:52:51"). Although it plays fine, maybe the file is corrupted somehow,
I'm not sure about it.

I don't quite understand.
Potplayer shows 01:52:51 for the 41.1kHz file and for the newly encoded 48kHz file also?
What is the problem then?

[FTG]

I forgot to tell what the "unexpected/wrong" length shown by "PotPlayer" is: "01:53:07".

Listening to the "AC-3" file using "PotPlayer" shows the above incorrect length, while
using other players as well as loading it into "Audacity", the "01:52:51" "expected" duration
is shown.

I made this video for them, which shows the issue:

https://gofile.io/d/mKBZmp

And by just converting (using your tool or others) that file's original frequency (44.1 kHz) to 48 kHz,
will make the expected "01:52:51" length shows up in PotPlayer, instead the wrong "01:53:07" one.

I can share such file with you, in case you are curious about it.

[ProWo]

----------------------------------------------------------------------------------
December 01, 2023 release version 3.1.9.
----------------------------------------------------------------------------------
New:
Open tasks resumed after application close.

Fixed:
Bug with webvtt subtitles.
Bug with hardcoding pgs subtitle.
Some other small bugs.

Improved:
Batch processing chain.
Output file naming.
----------------------------------------------------------------------------------

[ProWo]

Newest beta (v3.1.9.01), online now.

New:
Possibility to cancel single batch tasks instead all.

Fixed:
Bug in open tasks file create.
Bug in HDR/HLG recognition.
Bug in stream extraction with ts files.
Bug in video DAR calculation.

[FTG]

----------------------------------------------------------------------------------

I'm getting this while trying to cut a video (I tried with mkv and m2ts):



By the way, I'm trying to cut a video sourced from a BD, and your program
tells me it has no "keyframes". Is that possible?

[ProWo]

Try the newest beta. (3.1.9.01)

[FTG]

Try the newest beta. (3.1.9.01)

I already tried it, with the same results.

By the way, I also tried to split such video with MKVToolNix, and the output was quite inaccurate,
but then I tried with a commercial tool and I got it cut precisely.

[ProWo]

Could you cut a 60 second piece and post it here for further investigation?

[FTG]

Could you cut a 60 second piece and post it here for further investigation?

You can test it with this one:

https://www.demolandia.net/downloads.html?id=83491561

It seems the bug is affecting all the videos I tried.

[ProWo]

Could you cut a 60 second piece and post it here for further investigation?

You can test it with this one:

https://www.demolandia.net/downloads.html?id=83491561

It seems the bug is affecting all the videos I tried.

Tested this one with v3.1.9.
No problems, found 2 keyframes (with this 19.605 seconds example, read the index.txt):
F0-0.00000
F249-10.38500

Tested again with avidemux, which finds the same two keyframes.
Would recommend doing the following:
Delete this folder (it will be created again automatically):
C:\Users\xxx\AppData\Local\clever_FFmpeg_GUI (where xxx=your user name on windows).
Then restart clever FFmpeg-GUI.
It should work now.

[FTG]

[QUOTE=ProWo;2715345]

Could you cut a 60 second piece and post it here for further investigation?

You can test it with this one:
...

I tried that, but to no avail. Could it be related to the version of ffmpeg I'm using?

N-112539-g105657540b-20231029

I will try again later with other ffmpeg version.

[ProWo]

Check if your OS is up to date.

[FTG]

Check if your OS is up to date.

It seems it's not my system's fault but something with the tool itself. When I run your program
and use a "ffmpeg" path which has a blank space like:

"C:\Program Files\clever_ffmpeg_gui\ffmpeg\bin"

the problem will show up. But when I change the "ffmpeg" location to a path without
blank spaces, like:

"C:\whatever\Program Files\clever_ffmpeg_gui\ffmpeg\bin"

it will work fine.

[ProWo]

Will investigate on this.

[ProWo]

@FTG
Found the bug.
The video indexing is done by a batch script, and escaping paths with spaces in a complex commandline with arguments is very tricky.
Anyway, this will be fixed in the next beta.
Thanks for the hint.

[ProWo]

Newest beta (v3.1.9.02), online now.

Fixed:
Bug in video indexing, if ffmpeg path contains spaces.
Bug in open batch tasks handling.

Changed:
Video keyframes indexing.

[elendil]

Hi, is it possible to have an option to extract streams to source folder instead of fixed folder?
Also, it would be great on stream (audio) extraction to append, if present, the language of the audio stream to the file name (.en.ac3, .fr.ac3 for example), for 2 reasons:
- It's easier to know which language it is than _1, _2... when reading the file name
- It allows Mkvtoolnix to automatically put the language when adding the audio file instead of "unknown".

Also, am I the only one with weird window behaviours (not showing in taskbar, multiple windows when alt-tab...) ?
Finally, when audio streams are not in right order in the file (for example there are subtitles before) the audio stream selection menu in broken and we cannot change audio stream, but maybe this is a known issue?

[ProWo]

Hi, is it possible to have an option to extract streams to source folder instead of fixed folder?

You can change the target forder on the start screen.

Also, it would be great on stream (audio) extraction to append, if present, the language of the audio stream to the file name (.en.ac3, .fr.ac3 for example), for 2 reasons:
- It's easier to know which language it is than _1, _2... when reading the file name
- It allows Mkvtoolnix to automatically put the language when adding the audio file instead of "unknown".

This can be done, but with 3 characters (g.e. eng,fra) not 2. Will add it into the next beta.

Also, am I the only one with weird window behaviours (not showing in taskbar, multiple windows when alt-tab...) ?

This is a kown issue with the windows taskbar. You can minimize all windows to see clever and then the taskbar icon appears.

Finally, when audio streams are not in right order in the file (for example there are subtitles before) the audio stream selection menu in broken and we cannot change audio stream, but maybe this is a known issue?

I have never seen a video like this.
Can you post an example here (you can cut a 60 second piece with avidemux), then I can look into it.

[elendil]

You can change the target forder on the start screen.

Yeah it's not what i meant, i meant, having an option so that we don't have to change this folder each time, whatever the source folder, the extracted streams would always be in the source folder.

For the language on 3 characters it's ok, Mkvtoolnix recognizes it.

Here is an example of file where we can't choose 2nd audio stream

[ProWo]

Yeah it's not what i meant, i meant, having an option so that we don't have to change this folder each time, whatever the source folder, the extracted streams would always be in the source folder.

Will add a choice to extract to the source folder.

Here is an example of file where we can't choose 2nd audio stream

I have analyzed this video and i must say that i have never seen such a stream structure.
I have no idea what was used to mux it.
I will rewrite the code for the stream analysis and the problem will be fixed in the next beta.

[ProWo]

Newest beta (v3.1.9.03), online now.

New:
Option to select destination folder for extracted streams (target folder or source folder).
Output filename handling with audio encode.
Extracted audio and subtitle streams filenames with language tag (if any).

Fixed:
Stream handling with uncommon muxed videos.
Aac encoding not supported channel layout issue.

[ProWo]

----------------------------------------------------------------------------------
December 16, 2023 release version 3.2.0.
----------------------------------------------------------------------------------
New:
Possibility to cancel single batch tasks instead of all tasks.
Option to select destination folder for extracted streams (target folder or source folder).
Output filename handling with audio encode.
Extracted audio and subtitle streams filenames with language tag (if any).

Fixed:
Bug in open tasks file create.
Bug in HDR/HLG recognition.
Bug in stream extraction with ts files.
Bug in video DAR calculation.
Bug in video indexing, if ffmpeg path contains spaces.
Bug in open batch tasks handling.
Stream handling with uncommon muxed videos.
Aac encoding not supported channel layout issue.

Changed:
Video keyframes indexing.

Improved:
Streams handling.
----------------------------------------------------------------------------------

[mannequin80]

----------------------------------------------------------------------------------
December 16, 2023 release version 3.2.0.
----------------------------------------------------------------------------------

small request: b=1(0) - alternative boundary mode for DynAudNorm.

happy holidays!

[pchan]

Hi, I am new to clever_ffmpeg. I would like to try the deinterlace but I couldn't locate the deinterlace menu. Any tips on how to get to that menu is much appreciated.

[ProWo]

small request: b=1(0) - alternative boundary mode for DynAudNorm.

Will be implemented in the next beta.