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

[TDS]

Originally Posted by ProWo

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.

[TDS]

Originally Posted by 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.

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]

Originally Posted by TDS

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.

[TDS]

Originally Posted by ProWo

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.

[TDS]

Originally Posted by ProWo

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.

[TDS]

Originally Posted by 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.

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]

Originally Posted by TDS

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?

[TDS]

Originally Posted by oniiz86

@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]

Originally Posted by TDS

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.

[ProWo]

Originally Posted by TDS

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.

[TDS]

Originally Posted by 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.

So, running it thru MKVToolNix first ???

[TDS]

Originally Posted by ProWo

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.

What about Keep or Retain....

[ProWo]

Originally Posted by TDS

What about Keep or Retain....

Alall settings you have made will remain.

[ProWo]

Originally Posted by TDS

So, running it thru MKVToolNix first ???

You can also remux it with clever FFmpeg-GUI.

[TDS]

Originally Posted by ProWo

Alall settings you have made will remain.

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

Keep or Retain.

[ProWo]

Originally Posted by TDS

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

Keep or Retain.

You are right, keep is better ...