clever FFmpeg-GUI, a new small GUI for FFmpeg

[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.

[TDS]

Latest beta version v3.0.9.06 ???