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

[Findu]

Yes, sure.

Just re-tested.
Let me explain:
When I enter start time 5 and end time 30, I get the info for the real cut at 08,640 and 30.000. Okay, that is what I want. A 21,36 second clip.

[Attachment 89088 - Click to enlarge]

But the ffmpeg command use the next start keyframe of 08,640 which is 13,000.
And the command cut exactly at that (to late) point and keep the duration of 21s. So the clip starts to late, keep the 21s duration and therefor also ends at a later point in the video.
When you simply change the ffmpeg command to the mentioned real start cut at 08,640, you get your correct clip.
Start at 08,640 end at 30,000 - duration 21.36s.

[davidt1]

@davidt1

Open the MKV file you muxed with MKVToolnix in Clever and navigate to Multiplex.
I guess the text for the language is written in the Title field.


[Attachment 89057 - Click to enlarge]

I don't see anything in the title field. Your picture shows the title field with a wide width. Is the field width adjustable with that version? If so, I would like to have that version. For me nothing is adjustable.


[Attachment 89089 - Click to enlarge]

[ProWo]

But the ffmpeg command use the next start keyframe of 08,640 which is 13,000.
And the command cut exactly at that (to late) point

No, it cut at 08.640.

[Findu]

Please take a look!

Other mp4 file, same problem:
Only mp4 files have that problem!

Picture of the video at Frame 2880 (0:00:48.000) [K] should be the first picture of cut 1

[Attachment 89090 - Click to enlarge]

Picture of the video at Frame 3240 (0:00:54.000) [K] should be the first picture of cut 2

[Attachment 89091 - Click to enlarge]

Picture of the video at Frame 3600 (0:01:00.000) [K]

[Attachment 89092 - Click to enlarge]

Picture of the video at Frame 3960 (0:01:06.000) [K] should be the last picture for all cuts

[Attachment 89093 - Click to enlarge]

cut 1:
start cut 44, real cut 48
end cut always 1:06 = real cut at keyframe
duration 18, 1080 frames

Stream cut: ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4?174850?-hide_banner -loglevel error -stats -y -ss:0:0 54 -i "C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4" -frames:v 1079 -map 0 -map_metadata 0 -movflags use_metadata_tags -c copy -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720_cut#1.mp4?0?44 - 66

First picture of the cut output, duration 12

[Attachment 89094 - Click to enlarge]

Last picture of the cut output

[Attachment 89095 - Click to enlarge]


cut 2:
start cut 50, real cut 54
end cut always 1:06 = real cut
duration 12, 720 frames

Stream cut: ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4?174850?-hide_banner -loglevel error -stats -y -ss:0:0 60 -i "C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4" -frames:v 719 -map 0 -map_metadata 0 -movflags use_metadata_tags -c copy -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720_cut#2.mp4?0?50 - 66

First picture of the cut output, duration 6

[Attachment 89096 - Click to enlarge]

Last picture of the cut output

[Attachment 89097 - Click to enlarge]

[ProWo]

Other mp4 file, same problem:
Only mp4 files have that problem!

OK, I think to know where the problem is.
With mp4, variable framerate, especially with 23.976 or 29.97 fps, Virtualdub2 isn't reliable to locate the keyframes.
Use Ffplay instead.

[Findu]

Frame rate mode : Constant
Frame rate : 60.000 FPS

A keyframe all 6s
ffplay show the I frame at 48.016, VD2 at 48.000
ffplay is allways .016 later at all keyframes.

But when I enter 48.000 or 48.016, the real cut is set at 48.000 by the app.

[ProWo]

Frame rate mode : Constant
Frame rate : 60.000 FPS

A keyframe all 6s
ffplay show the I frame at 48.016, VD2 at 48.000
ffplay is allways .016 later at all keyframes.

But when I enter 48.000 or 48.016, the real cut is set at 48.000 by the app.

Strange behavior; check the keyframes with avidemux to know, if VD2 or Ffplay is right.

[Findu]

AviDemux has all at .000 like VD2

That code:

Stream cut: ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4?174850?-hide_banner -loglevel error -stats -y -ss:0:0 48 -i "C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4" -frames:v 1440 -map 0 -map_metadata 0 -movflags use_metadata_tags -c copy -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720_cut#6.mp4?0?40 - 66

generate the correct 18s cut file.
-ss:0:0 48
-frames:v 1440 (but that are 24s, not 18s)

[ProWo]

AviDemux has all at .000 like VD2

Stream cut: ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4?174850?-hide_banner -loglevel error -stats -y -ss:0:0 48 -i "C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720.mp4" -frames:v 1440 -map 0 -map_metadata 0 -movflags use_metadata_tags -c copy -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?C:\Users\Findu\Downloads\Brute Concrete - a 64K intro by UFDD 720_cut#6.mp4?0?40 - 66

generate the correct 18s cut file.
-ss:0:0 48
-frames:v 1440 (but that are 24s, not 18s)

Just out of curiosity, could you remux the mp4 to mkv and repeat the cut?

[Findu]

Will be done...

Next strange behavior:
If the end cut isn't exactly an I-frame, the -frames:v value in the code is aways the correct end cut for the output.

EDIT: same file in a mkv container process correct cuts!!!

I'm going offline for today!

[ProWo]

Will be done...
EDIT: same file in a mkv container process correct cuts!!!

Ok, could you make another test with this mp4?
Use the Fix Timestamps function with it (Losless changes, fix time stamps) and repeat the cut with the new created mp4.

[Findu]

Please take a look!

avidemux show this message for the timefix file.
So I'll have the correction done.

[Attachment 89109 - Click to enlarge]

Values for the original file, after time stamps fix, after avidemux fix.

I frame all 6 seconds
The offset in clever is 0.016, 0, 0.2
ffplay show all I frames at x.016, x.017, first I frame at 0.200 6.100 12.200 18.100 24.200 alternating.
VD2 at x.000, x.000, first at .200 followed by all other at x.100
avidemux x.000, x.000, 5.900 11.900 and so on.

The cut clip should start at 48 with a length of 18s

Original file 00048.000 -> 00066.000, 18s
-ss:0:0 54 -frames:v 1079, clip start at 54 for 12s

timefix file 00048.000 -> 00066.000, 18s
-ss:0:0 54 -frames:v 1079, clip start at 54 for 18s

avidemux fix file 00047.900 -> 00066.000, 18,1s
-ss:0:0 53.9 -frames:v 1085, clip start at 48 for 18s (how it should be)

[videoAI]

@ProWo
v3.4.6.06

FYI ..
This could be just a glitch, but I captured it anyways.
I did not enter any value, the duration value was filled
automatically by Clever.


[Attachment 89108 - Click to enlarge]

[ProWo]

avidemux show this message for the timefix file.

No, I meant the fix time stamps function of clever, not avidemux.
Please repeat with it.

[Findu]

"timefix file" is the one with fix time stamps function of clever.
"avidemux fix" is the "timefix file" fixed with avidemux.

[ProWo]

"timefix file" is the one with fix time stamps function of clever.
"avidemux fix" is the "timefix file" fixed with avidemux.

Please cut the first 120 sec from the original mp4 with avidemux (without any fix) and post it here, so I can take a look.

[ProWo]

This could be just a glitch, but I captured it anyways.
I did not enter any value, the duration value was filled
automatically by Clever.

Thx for the hint, bug, will be fixed.

[Findu]

I cut off the end with avidemx.
Brute Concrete - a 64K intro by UFDD 720 cut.mkv

Only mkv was available as container.

[Findu]

Try the original
Brute Concrete - a 64K intro by UFDD 720.mp4

[Findu]

Like for the empty Join page, you should add the text line "Use the add files button or drag & drop the files here." also at the empty Multiplex page.
---

When the source file has been deleted and you return to the Main page, the Cut button should be removed. The rest is fine.
---

The "Chapter start time error" text is somehow double:

Start time smaller or equal than previous chapter start time.
Please enter a start time that is greater/later than the previous one.

The second sentence says it all, so the first is superfluous.

[ProWo]

Try the original

[Attachment 89111 - Click to enlarge]

This is a hard one, with weird ffmpeg behavior.
Will report tomorrow.

[Findu]

Thank you very much.
All MP4 files have this problem: the start cut is done one keyframe later. This often results in the end cut being incorrect.
---

Could you please move the button labels on the main page down one pixel? Except for Toggle Destination and Quit.
It doesn't sound much, but if you compare the images, you can see the difference.

[Attachment 89113 - Click to enlarge]

One pixel down

[Attachment 89114 - Click to enlarge]

[videoAI]

@ProWo
v3.4.6.06

Tip: try changing the order of MUX, CUT, JOIN to MUX, JOIN, CUT.
It looks better on no-file screen.


[Attachment 89115 - Click to enlarge]

[Attachment 89116 - Click to enlarge]

[videoAI]

@ProWo
v3.4.6.06

Tip: try switching the location of the edit & various menus
to better utilize screen real-estate, and still allow for future
feature addition to all menus.


[Attachment 89117 - Click to enlarge]

[videoAI]

@ProWo
v3.4.6.06

Q: How are you calculating/estimating progress values for the
encode screen progress bar? Pls educate us.

I am editing a large number of video files on a daily basis
and ~90% of the files don't display the progress bar properly.

To replicate issue:
- MP4 file
- Larger than 50mb

Issue:
- Progress bar goes to 100% in 2 sec, then stays there for
the duration of encoding.
- Task bar tab icon is not updated when clever is minimized,
or in normal state.
- FFmpeg statistics update as usual, but I have no idea how
long encoding will take, an issue, especially for larger files.

Note: This issue was raised before ..
#post2782593

As always .. thx .. & keep up the great work


[Attachment 89118 - Click to enlarge]

[videoAI]

@ProWo
v3.4.6.06

Even when the progress bar works, in batch mode, the taskbar icon
does not seem to update at all ..


[Attachment 89120 - Click to enlarge]

[ProWo]

Q: How are you calculating/estimating progress values for the
encode screen progress bar? Pls educate us.

Video time/duration*100


[Attachment 89122 - Click to enlarge]

I am editing a large number of video files on a daily basis
and ~90% of the files don't display the progress bar properly.

I can't replicate that.

- Task bar tab icon is not updated when clever is minimized,
or in normal state.

You need this 2 files in the clever folder:
Microsoft.WindowsAPICodePack.dll
Microsoft.WindowsAPICodePack.Shell.dll

They are included in full release zip.

[ProWo]

Tip: try changing the order of MUX, CUT, JOIN to MUX, JOIN, CUT.
It looks better on no-file screen.

Will be done.

[ProWo]

Tip: try switching the location of the edit & various menus

That's not a good idea.
Imagine if no file is loaded...

[ProWo]

Try the original

[Attachment 89111 - Click to enlarge]

I am working with this file and have gained some new insights of the ffmpeg behavior.
The problems arise when the video file does not start with a keyframe.
VD2 always shows a keyframe at start 0:00, even if there isn't one.
The container is not the problem.

It will take a few days, and I will have to completely rewrite the cut part.