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

[ProWo]

Newest beta (v3.0.9.01), online now.
Fixed: minor bugs.
Improved: cutting code.
Added: LoudNorm filter 2 pass.

[guest]

Hi ProWo,

This is a great little app, I mostly use it for converting audio, however, I have just recently needed to change the colour space on some videos, and I find this is the easiest way to do it.

But having to go thru all the settings for each new job, is a bit of a pain,
is there some way that you can save the settings you use regularly, as a template or preset ??

Regards

[ProWo]

Hi ProWo,

This is a great little app, I mostly use it for converting audio, however, I have just recently needed to change the colour space on some videos, and I find this is the easiest way to do it.

But having to go thru all the settings for each new job, is a bit of a pain,
is there some way that you can save the settings you use regularly, as a template or preset ??

Regards

Hi TDS
Thank you for liking my program.
As for your wish, I think that in most cases the tasks are different and that such templates are simply underused.
Besides, it would be a considerable coding effort.

[guest]

Hi TDS
Thank you for liking my program.
As for your wish, I think that in most cases the tasks are different and that such templates are simply underused.
Besides, it would be a considerable coding effort.

Thanks for the prompt reply.

OK, that's fair enough, but it would be nice if there was something like an .ini file that you could edit to suit some settings that you would use EVERYTIME.

Cheers

[guest]

Hi TDS
Thank you for liking my program.
As for your wish, I think that in most cases the tasks are different and that such templates are simply underused.
Besides, it would be a considerable coding effort.

Hi ProWo,

I have to "sing the praise's" on this little app you've created, yet again.

Today I learned something about it, that is awesome, the "cut" function.

I have a TV series that has the annoying "previously" review that goes for more than a minute, and I tried another idea I had, but it only cut the video.

So after a bit of trial and error to see what the settings did, I was able to get all 8 episodes cut to my liking :)

And another good thing, because it doesn't take very long to process, if you've miscalculated the start point, you just go back and run it again.

This is going to be SO, SO handy for the "Game Of Throne's", for example, cutting off that "boring" intro, and so many other series & TV episode's.

AWESOME :thanks::thanks::thanks:

[ProWo]

Hi ProWo,

I have to "sing the praise's" on this little app you've created, yet again.

Today I learned something about it, that is awesome, the "cut" function.

I have a TV series that has the annoying "previously" review that goes for more than a minute, and I tried another idea I had, but it only cut the video.

So after a bit of trial and error to see what the settings did, I was able to get all 8 episodes cut to my liking :)

And another good thing, because it doesn't take very long to process, if you've miscalculated the start point, you just go back and run it again.

This is going to be SO, SO handy for the "Game Of Throne's", for example, cutting off that "boring" intro, and so many other series & TV episode's.

AWESOME :thanks::thanks::thanks:
Thank you for your praise.:)
Try the latest beta (v3.0.9.02, online now).
Fixed some small bugs in the cutting section.

[guest]

Thank you for your praise.:)
Try the latest beta (v3.0.9.02, online now).
Fixed some small bugs in the cutting section.

Hi ProWo,

My observations of the latest beta..

Using the "Cut" feature, once a clip is loaded, and you've entered the required "Start Time", you have to just quickly click on the "End Time" (which hasn't been changed) button to get the "Check Time" button to re-appear, to proceed.

Also, is seems that you have to "Quit" the app, if you want to edit another clip, not a big problem, tho.

Other than that, it's been working well :)

EDIT:-

A bit more info, regarding HDR10 & HDR10+..

This is the original MediaInfo:-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 7 min
Bit rate : 3 070 kb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.021
Stream size : 1.44 GiB (94%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 197 cd/m2
Maximum Frame-Average Light Level : 137 cd/m2

and this is after a "Cut" :-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 5 min
Bit rate : 3 070 kb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Variable
Frame rate : 24.518 FPS
Original frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 0)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.020
Stream size : 1.44 GiB (96%)
Writing library : x265 3.5+86-6da609e41:[Windows][GCC 12.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039
Language : English
Default : No
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant

I could send you a sample if you'd like ??

EDIT #2:-

I changed the "P-level" to 6.2, and now it seems to be OK...so it's just a learning curve.

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.2@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 7 min
Bit rate : 3 070 kb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.021
Stream size : 1.44 GiB (94%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 197 cd/m2
Maximum Frame-Average Light Level : 137 cd/m2

Like I mentioned before, it would be nice to have a way of changing and saving particular "user" settings...;)

EDIT #3:-

No, there is still something with running it thru "Cut" that changes it, again.

Is there a way to have multiple settings at the same time, as it appears that every option, is a seperate process. eg:- can't do a cut, AND a P-level change at the same time.

If I do a P-level change to get the HDR10 & HDR10+ displayed in MediaInfo, doing a "Cut" on the converted clip, removes the HDR10+.

[ProWo]

Using the "Cut" feature, once a clip is loaded, and you've entered the required "Start Time", you have to just quickly click on the "End Time" (which hasn't been changed) button to get the "Check Time" button to re-appear, to proceed.
You can also use the TAB button

Also, is seems that you have to "Quit" the app, if you want to edit another clip, not a big problem, tho.
No, use the source button and drag & drop the new file.

As for HDR10 / HDR10+:
Did you use the Keyframe Cut variant?
If so, the original file is only cut and remuxed.
It may be that the FFmeg mkv muxer changes/forgets/not copies some tags.
But the video track should remain unchanged and keep all characteristics of the original video track.
I think the changed tags are just cosmetic.

[guest]

You can also use the TAB button


No, use the source button and drag & drop the new file.

As for HDR10 / HDR10+:
Did you use the Keyframe Cut variant?
If so, the original file is only cut and remuxed.
It may be that the FFmeg mkv muxer changes/forgets/not copies some tags.
But the video track should remain unchanged and keep all characteristics of the original video track.
I think the changed tags are just cosmetic.

Ok, thanks for the tip.

Like I said, I'm on a learning curve with this, but I'm sure Ill get there.

I'll "take note" of the settings I've been using, and report back.

EDIT:- new day, more testing (or familiarization), I wasn't using "Frame Cut", so I have just ran one thru using "Frame Cut", and indeed, it retains (display's) HDR10/HDR10+ in MediaInfo. :),
However, the problem with using "Frame Cut", it's not cutting it exactly where it needs to be, so I might have to do "Frame Accurate Cut", and then run it thru to change the "P-frame" :(

OK, just did the "P-frame" test, and that didn't bring back the HDR10+, but the HDR10 is there, so like you said, it might just be cosmetic.

And not that it should matter, but I running FFMPEG 6.0

EDIT #2:- OK, everything seems to be going OK, I am editing "The Game of Thrones", and Season 1 is 6.2 HDR, and after the "Cut", it still is,
however, Season 2 (and up to Season 7) are "only" 5.1 HDR, and after a "Cut", they are 5.0, but no HDR "flag" in MediaInfo, and I can't change that outcome.

I've just noticed that some are being changed from 5.1 to 5, and that might be why the HDR flag is missing, as the one that are still 5.1 are still showing as HDR.

I think that there might need to be some way to change the P-level from the "Cut" page, not a separate operation.

But even tho it's not "flagged" as HDR, when I play the edited clips in PotPlayer, they are indicated to be HDR....

And another strange thing, every so often, when you "Check Times", it throws up an error about the "search range being too small".

I've noticed you don't get much feedback, so I hope you don't mind me bothering you....

[guest]

Hi,

Noticed you posted this on page 1, so I have just tried that, not sure what the differences are, as you didn't post anything about it (like you usually do).

Still randomly changing the P-levels, I think I'm going to have to re-encode them first to 6.2 HDR10/HDR10+, and then run them thru "Cut".

Cheers

[ProWo]

Hi,

Noticed you posted this on page 1, so I have just tried that, not sure what the differences are, as you didn't post anything about it (like you usually do).

Still randomly changing the P-levels, I think I'm going to have to re-encode them first to 6.2 HDR10/HDR10+, and then run them thru "Cut".

Cheers
Am currently working on v3.0.9.04, with very many improvements and changes in the cut section.
If you want you can try it, online now.

[guest]

Am currently working on v3.0.9.04, with very many improvements and changes in the cut section.
If you want you can try it.
I attach it here

Hi ProWo,

OK, looking forward to what you've done, however, attaching the app like you have, is not a good way to do anything on this Forum, due to the "Attachments Pending Approval", can take a LONG time...might be best to either wait 'til you've made in available for everyone, or upload it to MediaFire or similar, then provide a link.

Regards.

[ProWo]

Newest beta (v3.0.9.04), online now.
Changed: cutting section (many improvements, bugs fixed).
Added: LoudNorm filter pass label.

[guest]

Newest beta (v3.0.9.04), online now.
Changed: cutting section (many improvements, bugs fixed).
Added: LoudNorm filter pass label.

Hi, I have just tested this build, and I can see a couple of problems.

I'm using it on the same PC, same files.

I can't see any differences :(

And the player doesn't display, you can hear it, but you can't see it, then it stops, and has a mini lockup, then you have to press ESC.

Ran one file thru "Cut", and it's still downgrading from Level 5.1 to 5, and no HDR10 info is displayed in MediaInfo.

But PotPlayer detects it as being HDR....

Strange...I will try it again after I have re-encoded to Level 6.2.

Cheers

[ProWo]

@TDS
What version is your ffmpeg?
Do you have tryed with v6.0?

[guest]

@TDS
What version is your ffmpeg?
Do you have tryed with v6.0?

I am using v6.0...

EDIT:-

I updated to a newer v6.0 build, the player is working for me, but the P-levels are still a problem.

[ProWo]

Newest beta (v3.0.9.05), online now.
Changed: cutting code again.
Added: ffmpeg version info on start screen.

[ProWo]

@TDS
Try the latest beta to see if the HDR tags are ok now.

[guest]

@TDS
Try the latest beta to see if the HDR tags are ok now.

Hi, I certainly will, but tomorrow (my time).

Will report back, of course, thanks :)

EDIT:-

Well, I really don't know what's going on with this, but I think I've stumbled on what's is making this change the P-level & HDR10 status...

IF I don't do any cutting, the P-level & HDR10 status don't change, HOWEVER, when I do do a cut, that when things get messed up.

So here is a link to a 5 minute sample of the video that I am working on (and some before & after MediaInfo)...

test sample (https://www.mediafire.com/file/v3z1xnm1jsat8r3/clever.7z/file)

[ProWo]

Hi, I certainly will, but tomorrow (my time).

Will report back, of course, thanks :)

EDIT:-

Well, I really don't know what's going on with this, but I think I've stumbled on what's is making this change the P-level & HDR10 status...

IF I don't do any cutting, the P-level & HDR10 status don't change, HOWEVER, when I do do a cut, that when things get messed up.

So here is a link to a 5 minute sample of the video that I am working on (and some before & after MediaInfo)...

test sample (https://www.mediafire.com/file/v3z1xnm1jsat8r3/clever.7z/file)

Tested, with your sample.
No problems here. Same P-Level as source.

https://files.videohelp.com/u/292773/1_2.jpg

[guest]

Tested, with your sample.
No problems here. Same P-Level as source.


Well, I'm glad I sent you that sample then, so I wonder what the problem is, my end...

I will try it on another PC, that has a very recent fresh W11 install.

So I'm sorry that I have put you thru this, when it's turned out to be a problem of mine, but it's all progress for this app of yours.

I will get back to you, when I test it again.

Regards.

EDIT:-

OK, have just tested it on another W11 PC, and I'm getting the same results, unfortunately.

Obviously, your PC(s) are set up differently to mine, what OS are you running ??

And what is your workflow to do a Cut ?? Keyframe or Frame Accurate cut, with what CRF setting.

Also, and I doubt that this has anything to do with it, but my cut start is 1m 56.500 sec.

So I will try again after I have encoded the videos to P-level 6.2, and a couple of filters, and hopefully it will work for me then, otherwise I will have to try something else :(

EDIT #2:-

Well, this really odd, I have re-encoded one of these videos to level 6.2 Main 10@L6.2@High, and after doing a cut, (using the above settings) its now Main 10@L5@Main.

Regards

[ProWo]

@TDS
Did some tests.
Result: With Keyframe cut all HDR tags are preserved, including the profile level.
With Frame accurate Cut this does not work, because a part is re-encoded, without the complete HDR command line with all parameters, which would have to be parsed first.
This is clearly too much work for me.
Therefore the conclusion: For HDR10 and HDR10Plus videos only Keyframe Cut works.

[guest]

@TDS
Did some tests.
Result: With Keyframe cut all HDR tags are preserved, including the profile level.
With Frame accurate Cut this does not work, because a part is re-encoded, without the complete HDR command line with all parameters, which would have to be parsed first.
This is clearly too much work for me.
Therefore the conclusion: For HDR10 and HDR10Plus videos only Keyframe Cut works.

Thanks for continuing to test things, and now "we" know what's going on :)

However, that's a shame that the Frame cut is what is killing the levels & HDR10, so what I guess I'll need to experiment with, is to get the keyframe as close as I can, to the frame I want to cut to, so thankfully you've got a player to check that :)

Just a side note, one of the re-encoded videos I ran thru cut, with framecut, even tho MediaInfo did not show any HDR10, on my 4K TV, it is still HDR :)

Regards.

[ProWo]

Just a side note, one of the re-encoded videos I ran thru cut, with framecut, even tho MediaInfo did not show any HDR10, on my 4K TV, it is still HDR :)
This happens because the first frames (from start cutpoint to the next I-Frame) are re-encoded, but without the HDR Info.
The rest of the movie (maybe >99%) is cutted only (therefore not changed), but the ffmpeg muxer in the final remux get the wrong info for the whole file from the first re-encoded frames.

[guest]

This happens because the first frames (from start cutpoint to the next I-Frame) are re-encoded, but without the HDR Info.
The rest of the movie (maybe >99%) is cutted only (therefore not changed), but the ffmpeg muxer in the final remux get the wrong info for the whole file from the first re-encoded frames.

Have done some more tests, using Keyframe cut, and it indeed retains the P-level & HDR10 :).

But as the Keyframes are set in the video, you can't get it exactly where you would like it, by less than a second.

There probably isn't an app that you can edit keyframe positions, but I'll have a look, anyway.

I want to sincerely thankyou for your patience with me during all this "fiddle", it's greatly appreciated, and I think I will use "clever" a LOT, for both video & audio editing :)

Cheers.

[ProWo]

Newest beta (v3.0.9.07), online now.
Changed: ffmpeg to FFmpeg, typos corrected, offset approach in cut section.
Fixed: Bugs in cut section.
Improved: Keyframe search in cut section.
Added: Keyframe info in cut section.

Recommended: Delete the following folder before the first start:
C:\Users\xxx\AppData\Local\clever_FFmpeg_GUI (where xxx=your user name on windows).

[ProWo]

Newest beta (v3.0.9.08), online now.
Fixed: a bug with process termination.

[guest]

Newest beta (v3.0.9.08), online now.
Fixed: a bug with process termination.

I had another "play" with this today, and actually had more success with retaining the HDR10 info, but only about 6 cuts out of 10.

[ProWo]

March 27, 2023 release version 3.1.0.
Added: Tooltips on many controls, keyframe info in cut section (with no video delay), LoudNorm Filter pass label, actual FFmpeg version info on start screen.
Changed: cutting section, cosmetics in many forms, HDR profile to level, video offset approach in cut section.
Fixed: typos, incorrect process termination, bug in DVD Rip, bugs in cut section.
Improved: command sequence for a faster start, keyframe search in cut section, First Start screen with detailed info now.

[guest]

March 27, 2023 release version 3.1.0.
Added: Tooltips on many controls, keyframe info in cut section (with no video delay), LoudNorm Filter pass label, actual FFmpeg version info on start screen.
Changed: cutting section, cosmetics in many forms, HDR profile to level, video offset approach in cut section.
Fixed: typos, incorrect process termination, bug in DVD Rip, bugs in cut section.
Improved: command sequence for a faster start, keyframe search in cut section, First Start screen with detailed info now.

Hi,

I have a suggestion; would it be possible to change what happens after you click on OK on the DONE pop up, when the edit is completed ??

I think it would be nice if it did not clear what you had just edited, but stayed on that page, keeping the settings you've made, just in case you need to tweak it, and run that same job again.

If it's ok, THEN go back to the "Start"...by selecting Source file, or something.

[oniiz86]

I had another "play" with this today, and actually had more success with retaining the HDR10 info, but only about 6 cuts out of 10.
@TDS So has the latest 3.1.0 version fixed this issue with retaining the HDR10 info when cutting or has the behaviour remained unchanged, why do you think it is proving difficult to fix?

[guest]

@TDS So has the latest 3.1.0 version fixed this issue with retaining the HDR10 info when cutting or has the behaviour remained unchanged, why do you think it is proving difficult to fix?

Hi,

Well, as ProWo explained, it depends on how & where the cut is, to whether it retains the HDR10 info (or whatever they call it), however, even tho MediaInfo doesn't show the HDR10 flag after the cut, if I play the video in Pot Player, it DOES still show & play with HDR.

But it is a little odd that it will retain on some, but not all.

But I love the way that it cuts the audio & subtitle tracks :)

I'll have to leave that question up to ProWo...

[ProWo]

Hi,

I have a suggestion; would it be possible to change what happens after you click on OK on the DONE pop up, when the edit is completed ??

I think it would be nice if it did not clear what you had just edited, but stayed on that page, keeping the settings you've made, just in case you need to tweak it, and run that same job again.

If it's ok, THEN go back to the "Start"...by selecting Source file, or something.

Interesting idea.
I will add a checkbox in the next beta.
If this is checked, the current screen will stay open after encoding/abort, if not, everything will stay as before.
Initially only for audio or video encoding.

https://files.videohelp.com/u/292773/1_3.jpg

[ProWo]

Hi,

Well, as ProWo explained, it depends on how & where the cut is, to whether it retains the HDR10 info (or whatever they call it), however, even tho MediaInfo doesn't show the HDR10 flag after the cut, if I play the video in Pot Player, it DOES still show & play with HDR.

But it is a little odd that it will retain on some, but not all.

But I love the way that it cuts the audio & subtitle tracks :)

I'll have to leave that question up to ProWo...

I did further experiments with the HDR tags, and found out that the preservation of these tags does not depend on the way the cut is made, but on the way the source file is muxed.
So just remux first (best as mkv) and only then cut.

[guest]

I did further experiments with the HDR tags, and found out that the preservation of these tags does not depend on the way the cut is made, but on the way the source file is muxed.
So just remux first (best as mkv) and only then cut.

So, running it thru MKVToolNix first ???

[guest]

Interesting idea.
I will add a checkbox in the next beta.
If this is checked, the current screen will stay open after encoding/abort, if not, everything will stay as before.
Initially only for audio or video encoding.

https://files.videohelp.com/u/292773/1_3.jpg

What about Keep or Retain....

[ProWo]

What about Keep or Retain....
Alall settings you have made will remain.

[ProWo]

So, running it thru MKVToolNix first ???
You can also remux it with clever FFmpeg-GUI.

[guest]

Alall settings you have made will remain.

Sorry, what I meant was instead of labelling it as "Stay"..

Keep or Retain.

[ProWo]

Sorry, what I meant was instead of labelling it as "Stay"..

Keep or Retain.
You are right, keep is better ...

[guest]

You can also remux it with clever FFmpeg-GUI.

I haven't gotten around to using that, yet.

I think you call it Multiplex ?

Anyway, I tried your suggestion, and after the remux, it retained it's HDR10 flag, and it's P-level of 5.1.

However, after a cut, the HDR10 flag was gone, and it was down to P-level 5. I think this happens due to the default setting being level 5.

Here's another suggestion, could you make the P-level adjustment available when doing ANY video editing/cutting, instead of having it as a separate option ?

Or, as I have suggested before, if there was a simple .ini type file that the user could edit, to suit their regular usage settings.

Baby steps..

[ProWo]

Newest beta (v3.1.0.01), online now.
Added: Keep section open checkbox (for audio and video encoding section).

[guest]

Newest beta (v3.1.0.01), online now.
Added: Keep section open checkbox (for audio and video encoding section).

OK, I've just had a play with this, and I'm a little disappointed :(

But like you said, that "Keep" option is only for main video & audio encoding but not for the "Cut" function.

And I have to say, I don't think the frame accurate option is that accurate, it seems to use the keyframe position's :(

[ProWo]

But like you said, that "Keep" option is only for main video & audio encoding but not for the "Cut" function.
In the next beta it's avaiable for the cut section too.

And I have to say, I don't think the frame accurate option is that accurate, it seems to use the keyframe position's :(
This is not a contradiction.
It uses the keyframe AFTER the start cut point. Up to this point the video is re-encoded from the start point.

[guest]

In the next beta it's available for the cut section too.

That will be nice :)

This is not a contradiction.
It uses the keyframe AFTER the start cut point. Up to this point the video is re-encoded from the start point.

So, it's not truly "frame" accurate !!!

Correct me if I'm wrong, but were the earlier builds more "accurate." ?

Can this be changed to be cut on the frame you want ?, generally keyframes can be a long way apart, and not that suitable for certain cuts.

[ProWo]

That will be nice :)

So, it's not truly "frame" accurate !!!

Correct me if I'm wrong, but were the earlier builds more "accurate." ?

Can this be changed to be cut on the frame you want ?, generally keyframes can be a long way apart, and not that suitable for certain cuts.

It is frame accurate.
In order not to re-encode the complete video and thus enable smart rendering, several steps are performed here. First it is determined which part can be cut with keyframe cut, then the missing part (in the start area) is completely newly coded, (it is coded exactly from the start frame), then all audio tracks and subtitle tracks are cut frame accurate, then the two video parts are combined and finally everything is muxed together.
This is a really complicated process.

[ProWo]

Newest beta (v3.1.0.02), online now.
Added: Keep section open checkbox (for cut section), switch background color (with color button on start screen).

[guest]

It is frame accurate.
In order not to re-encode the complete video and thus enable smart rendering, several steps are performed here. First it is determined which part can be cut with keyframe cut, then the missing part (in the start area) is completely newly coded, (it is coded exactly from the start frame), then all audio tracks and subtitle tracks are cut frame accurate, then the two video parts are combined and finally everything is muxed together.
This is a really complicated process.

Fair enough, but I can't get it to cut where I want it to, it just seems to choose the closest Keyframe, which is rarely at the correct time, it's either before or after the desired cut point :(, when using frame accurate.

[guest]

Newest beta (v3.1.0.02), online now.
Added: Keep section open checkbox (for cut section), switch background color (with color button on start screen).

Just tried the latest beta, and it's just not doing what I need it to, like I said above, even in Frame Accurate, it's using the Keyframes, and they are not in the right place for the cuts I want to do :(

If there was some way of removing, or moving the Keyframes, that would be nice...

Like the colour button :)

[ProWo]

Just tried the latest beta, and it's just not doing what I need it to, like I said above, even in Frame Accurate, it's using the Keyframes, and they are not in the right place for the cuts I want to do :(

If there was some way of removing, or moving the Keyframes, that would be nice...

The keyframes cannot be moved, they are set by the encoder during encoding.

I just did a test with a h264 video.
I loaded the video in Virtualdub2 and chose a B-Frame as startpoint.
As endpoint I looked for an I-frame.
I noted start time and end time and entered them into clever FFmpeg GUI,
selected Frame accurate cut above, pressed check times and then pressed cut.
Then checked the cut video in Virtualdub2.
The start frame fits exactly, the last frame is as desired the last P-frame before the entered I-frame (this guarantees a closed GOP).
So everything as desired, frame accurate and smart rendered.