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!