clever FFmpeg-GUI, a lightweight and portable GUI for FFmpeg

[ProWo]

Originally Posted by TDS

Well, it's nice to get the instructions from the creator, HOWEVER, this is NOT doing what I was expecting it to...

This actually increases the video playback speed, and reduces the length of the clip

Did you read what I wrote above?

Originally Posted by TDS

I need it to increase the frame rate from 23.9xx to 60 fps without ANY increase in "speed".

Did you read what I wrote above?
Uncheck the Change length box.

Originally Posted by TDS

This clip was about an hour long, but it's now less than half, and after doing all those settings & clicking "Encode", it was done in an instant, and produced a 0kb file

Works flawlessly here.
Which ffmpeg version are you using?

[ProWo]

Originally Posted by locotus

Do that solution work for telecined content?

Yes it does, but with telecined video that is not the way to go.
If your video is a 29.97 fps video coming from a 23.976 fps source, the IVTC filter is the right choice.
This will return the 29.97 fps video to its original 23.976 fps state and remove the frames added during the telecine process.
If you just change the frame rate (while keeping the duration the same), it will only add or remove more frames and pretty much ruin the video.

[TDS]

Did you read what I wrote above?
Uncheck the Change length box.

Interestingly enough, before I sent the previous post, I had tried with all the same settings but NOT the "Change Length", and basically got the same result, and instant "encode" and 0Kb's...

And if memory serves, I did a run with 50 in the "fps" box, and that did process, but it was still the original 23.9xx.

I am still using those Game of Thrones episodes that didn't like the Cut function, so maybe they are the problem....

Works flawlessly here.
Which ffmpeg version are you using?

Did you do your test on a 4K video, setting it at 60 ??

I get my builds from here:-

https://github.com/BtbN/FFmpeg-Build...ses/tag/latest

[ProWo]

Originally Posted by TDS

Interestingly enough, before I sent the previous post, I had tried with all the same settings but NOT the "Change Length", and basically got the same result, and instant "encode" and 0Kb's...

And if memory serves, I did a run with 50 in the "fps" box, and that did process, but it was still the original 23.9xx.

I am still using those Game of Thrones episodes that didn't like the Cut function, so maybe they are the problem....



Did you do your test on a 4K video, setting it at 60 ??

I get my builds from here:-

https://github.com/BtbN/FFmpeg-Build...ses/tag/latest

Retested with this build from your source

https://github.com/BtbN/FFmpeg-Build...gpl-shared.zip

and a 4k video, no problem, works fine.

[TDS]

Originally Posted by ProWo

Retested with this build from your source
and a 4k video, no problem, works fine.

Well, the mystery continues.....

It's not that I only use it on 1 PC, so it's not that.

It's always the way, isn't it, you try and explain a problem, and the creator has no issue's.

[ProWo]

Originally Posted by TDS

Well, the mystery continues.....

It's not that I only use it on 1 PC, so it's not that.

It's always the way, isn't it, you try and explain a problem, and the creator has no issue's.

It would be nice if you stayed fair.
You write about problems that I cannot reproduce here. There can be many reasons for this, different operating systems, different video sources, different software versions, etc.
You could try a different video for example.

[TDS]

Originally Posted by ProWo

Retested with this build from your source
and a 4k video, no problem, works fine.

Originally Posted by ProWo

It would be nice if you stayed fair.
You write about problems that I cannot reproduce here. There can be many reasons for this, different operating systems, different video sources, different software versions, etc.
You could try a different video for example.

Sorry, I think you've taken this the wrong way.

I was trying to say that its not just a particular pc that I'm having an issue on.

Its like taking your car to a mechanic, explaining the problem, they can't find the problem, so they can't do anything about it...they take it for test drive, no problems, but when you drive back home, the problem is still there.

I'm running Windows 11 22H2..

I will try another video.

[ProWo]

Newest beta (v3.1.0.03), online now.
Fixed: missing variable reset bug.
Changed: seeking approach in cut section, cosmetics on many forms.
Added: Virtualdub2 as viewer in cut section.

[TDS]

Originally Posted by ProWo

Newest beta (v3.1.0.03), online now.
Fixed: missing variable reset bug.
Changed: seeking approach in cut section, cosmetics on many forms.
Added: Virtualdub2 as viewer in cut section.

I think I may have found what the problem is...

Using this latest build, I imported a short 4K clip, and changed the FPS to 60 (from 23.97x), changed it to x265, CRF to 16, preset to medium, but when the profile is changed, was when the encode was done in an instant, with a 0kb file.

If left @ auto, it was fine with all the other settings.

Virtualdub2 is a nice addition.

[ProWo]

Originally Posted by TDS

I think I may have found what the problem is...

Using this latest build, I imported a short 4K clip, and changed the FPS to 60 (from 23.97x), changed it to x265, CRF to 16, preset to medium, but when the profile is changed, was when the encode was done in an instant, with a 0kb file.

If left @ auto, it was fine with all the other settings.

Thanks for the hint.
Indeed, when encoding with x265 encoder, the profiles of x264 encoder were used and that could not work.
This bug is now fixed in the latest beta (v3.0.1.04).

[ProWo]

Newest beta (v3.1.0.04), online now.
Fixed: bug with x265 profile settings.

[TDS]

Originally Posted by ProWo

Newest beta (v3.1.0.04), online now.
Fixed: bug with x265 profile settings.

I just tried this on my little laptop, loaded an x264 clip...

Went thru the settings, but there seems to be a different possible issue with "Profile", with both x264, or x265, it's "stuck" @ Auto..., no other options.

Tried it several times with different clips, and FFmpeg's.

All the other options worked OK...

[ProWo]

Originally Posted by TDS

I just tried this on my little laptop, loaded an x264 clip...

Went thru the settings, but there seems to be a different possible issue with "Profile", with both x264, or x265, it's "stuck" @ Auto..., no other options.

Tried it several times with different clips, and FFmpeg's.

All the other options worked OK...

This is not an issue, it happens because your video has no bit depth info and therefore the app can't do the correct profile selection.
Change Bit Depth to 8 or 10 bits and the possible profiles can be selected.
The best choice is auto anyway, because then the encoder chooses the best profile by itself.
Actually the profile selection is only built in for compatibility reasons, that is if you need a certain profile for some reason.

[TDS]

Originally Posted by ProWo

This is not an issue, it happens because your video has no bit depth info and therefore the app can't do the correct profile selection.
Change Bit Depth to 8 or 10 bits and the possible profiles can be selected.
The best choice is auto anyway, because then the encoder chooses the best profile by itself.
Actually the profile selection is only built in for compatibility reasons, that is if you need a certain profile for some reason.

OK, well that worked

But I have to say that I am still not having any success with changing the frame rate...I have tried 2 different clips, one with 23.97x & another with 119.88, and setting them @ 60, there are not changing.

Wait just a minute....it seems that the framerate HAS been changed, however, that change in not reflected when checking with MediaInfo !!!

But if I reload the clips I have just "converted" with clever, then clever displays the new framerate, as do other encoding apps.

So something is being "lost in translation" regarding the new fps, and MediaInfo...

And sadly, the 4K HDR10 clip still loses the HDR10 tag, and is also changed from level 6.1 to 5.1 , in MediaInfo.

Is there something wrong with MediaInfo ??

Is there another similar tool I can try to test ??

[ProWo]

Originally Posted by TDS

And sadly, the 4K HDR10 clip still loses the HDR10 tag, and is also changed from level 6.1 to 5.1

Use the HDR10 Button in the x256 settings.

[TDS]

Originally Posted by ProWo

Use the HDR10 Button in the x256 settings.

I guess it will take me a little while to figure out all the in's & out's...

I just did a conversion, and changed several settings, and it's all displayed in MediaInfo

Thanks for your patience & instruction

Would it be possible to add a kb/s setting in the Encoder section, and of course retain the CRF setting ? Just to have the 2 different options.

And maybe also have the P-level option for x264 & non HDR x265 in the Encoder section as well ?

I only mention that, due to that option being available when it IS HDR x265, so might as well have it for all.

[ProWo]

Newest beta (v3.1.0.05), online now.
Changed: Cut section again.

[TDS]

Originally Posted by ProWo

Newest beta (v3.1.0.05), online now.
Changed: Cut section again.

Hi ProWo,

Me again...So I have just given your latest beta a test run, and it seems to do the cuts where I want them (well, on the clips I tested), it does more "testing" on the file, then choose "Cut",
it does all it steps (10 in all), and ALL the temp files are shown in the folder I set for the output, then when it's all done the little "DONE" window pops up,
click on that, it proceeds to "clean up" all the temp files, and then the folder becomes empty

I did search for it, but was no where to be found, so I tried it on another PC, different file, same result...

So something nasty seems to happen after you click on "DONE".

So due to this, I can't check the "cutted" file, to check the edit, the P-level, and if it's retained the HDR10 tag

I was going to attach some screenshots, but I think I've described it well enough.

[ProWo]

The output file should have the same name as the input file, with _cutted added.

[TDS]

Originally Posted by ProWo

The output file should have the same name as the input file, with _cutted added.

Correct, and its always done that for me, until this latest build.

If I have the output folder open, before I click on "DONE", all the temp files are there....as soon as I click on "DONE" they ALL disappear before my eyes, and then the folder is empty...NO cutted file !!!!!