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

[Lathe]

Originally Posted by ProWo

Hi Lathe,
please cut 30 seconds of this video, upload it to any hoster and post the link here. Then I will analyze it.

I will try to do that, thanks! But, I don't think the file is at issue here. This is a different file than the original one I was talking about here with the dual HEVC video files. I found one that APPEARS just to be a simple UHD/HDR single file and CleverFFmpeg seemed to load it just fine, but:

1) I got the prompt that the file did not have any 'Meta data' for HDR, so I don't know if that means it is not encoded with that or what.

2) Primarily, since your interface was truncating all the prompts where I am supposed to select the options that I show clearly in the pictures in my above post, I could not continue to use it. (Personally, as far as the functionality of your program, I think that is more important so that one can actually select those options and not be frozen at that point where you cannot continue with the program)

I'm thinking perhaps of loading the previous instance of your program because the interface thing changed right after downloading your new stable version.

But yes, as per (1) it would be good to know why the program said there was not any 'HDR Meta data' and what that means. I just processed it thankfully through Handbrake (although I prefer the results of your program quite a bit more) and it processed just fine and I THINK looks alright. I used the BT709 filter.

I took some snippets directly from this 61 Gig UHD/HDR file and I'm uploading it to my Google Pictures folder, it's going to take about 14 minutes and then I'll try to post a link to it here. I've not done that before with GP's, and my site is currently down due to having to do something with my hosting, so hopefully this will work. I tried to choose the smallest snippet (around 245 Megs as opposed to 350 Megs)

It WOULD be a very good thing to know though that if I do get that prompt as I have shown the picture above, do I then still try to do an HDR-SDR conversion, or do I just skip that part? WHAT do I do when I see this prompt...?

Okay, here you go... I hope it works.

https://photos.app.goo.gl/HYcAoYQP2hUTtuXeA

I think you can choose 'download' from the 3 dots on the upper right.

[Lathe]

Okay... Well one thing I did find out was that, yes, the problem with 'Scaling' or whatever you'd call it to be able to see the full option windows has to do with your new version. It DOES show with your older version, so just the new version does that. So, using the 2nd to last version I was at least able to see the full option windows and select the options. I still got the prompt that the HDR/HLG metadata was missing, so I tried to do the encode straight with no HDR conversion, but the resulting file reading it with MediaInfo still showed the colorspace to be 2020 and it showed Dolby Vision. So, I'm running it again with the HDR conversion to see what the difference is.

***EDIT

I think with this new UHD file (whether it is HDR or not) at least seems to be encoding through CleverFFmpeg okay. I'm trying one snippet with HDR conversion and one snippet without in order to compare them.

So, at least if this works, then with your older version I can at least run the program and choose the options. AND, if the new UHD file is indeed 'Okay', then that will pretty much solve what I need to do.

The ONLY thing again, and I'm sorry to keep mentioning it, but if I do get that prompt with the 'HDR/HLG metadata missing' do I just then assume I DON'T need to use the HDR conversion? The MediaInfo still says that it has Dolby Vision, so I don't know how that impacts it. But, at least in doing these two encodes, one with and one without the HDR conversion, perhaps I can get an idea as to which one looks 'right'...

***EDIT 2

Yep... in comparing the two encodes, the one where I did the HDR conversion looks a LOT brighter and probably the way it should be, so I'm trying to do the whole film that way now. I guess that MIGHT answer my pesky question then, that I DO indeed have to use the HDR conversion even though I get that prompt. HOPEFULLY, if nothing goes wrong now with the file, and the encode finishes, I should have a nice 1080 print which I bet will look a LOT better than the one I did with Handbrake...

[Lathe]

... and then I get this...

I SWEAR I am so damn F****d with this! Nothing F'n works! I F***'n give up man, GEEZ...!

Handbrake did it just fine, although I don't think it looks as good. Well, since for whatever the hell reason, I sure can't use your program anymore which SUX!



BE txt:

Video ---> x264 (avc) - Stream ID 0 from ?G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv?5619629?-y -fflags +genpts -i "G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv" -vf fps=24000/1001,scale=1920:1080,format=yuv420p,zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=709,tonemap=mobius:desat=2,zscale=t=709:m=709:r=tv,format=yuv420p -map 0:0 -c:v libx264 -profile:v high -preset medium -tune film -crf 20 -aspect 1.78 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -an -sn -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?E:\TSMUXER 2\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32_0_0_x264 (avc).mkv?1
Audio ---> DTS - Stream ID 1 from ?G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv?5619627?-y -fflags +genpts -i "G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv" -map 0:1 -c:a dca -strict -2 -b:a 1536k -ar 48000 -vn -sn -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?E:\TSMUXER 2\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32_1_0_.dts?1
Audio ---> DTS - Stream ID 2 from ?G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv?5619627?-y -fflags +genpts -i "G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv" -map 0:2 -c:a dca -strict -2 -b:a 1536k -ar 48000 -vn -sn -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?E:\TSMUXER 2\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32_2_0_.dts?1
Audio ---> DTS - Stream ID 3 from ?G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv?5619638?-y -fflags +genpts -i "G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv" -map 0:3 -c:a dca -strict -2 -b:a 1536k -ar 48000 -vn -sn -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?E:\TSMUXER 2\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32_3_0_.dts?1
Audio ---> ac3 - Stream ID 4 from ?G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv?5619627?-y -fflags +genpts -i "G:\___TL\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32.mkv" -map 0:4 -c:a ac3 -b:a 192k -ar 48000 -vn -sn -dn -metadata:g encoding_tool="clever FFmpeg-GUI" ?E:\TSMUXER 2\Torso.1973.2160p.Italian.Version.UHD.Blu-ray.REMUX.DV.HDR.HEVC.DTS-HD.MA.1.0-W32_4_0_.ac3?1

[ProWo]

Originally Posted by Lathe

Okay, here you go... I hope it works.
https://photos.app.goo.gl/HYcAoYQP2hUTtuXeA

This video was recoded from an HDR10 source, no longer has HDR metadata, but the HDR10 colorspace, transfer matrix info was incorrectly retained.
If the colors are correct, you can simply re-encode it as you wish. If the colors are pale and lack contrast, re-encode it with tone mapping (HDR to SDR).

As for the missing buttons, that's a high DPI scaling problem that I still need to fix.

[ProWo]

----------------------------------------------------------------------------------
September 08 2024 release version 3.3.0.
----------------------------------------------------------------------------------
Fixed:
Important bug with High DPI in many screens.
----------------------------------------------------------------------------------

[Lathe]

Originally Posted by ProWo

This video was recoded from an HDR10 source, no longer has HDR metadata, but the HDR10 colorspace, transfer matrix info was incorrectly retained.
If the colors are correct, you can simply re-encode it as you wish. If the colors are pale and lack contrast, re-encode it with tone mapping (HDR to SDR).

As for the missing buttons, that's a high DPI scaling problem that I still need to fix.

Thanks!

[ProWo]

Newest beta (v3.3.0.01), online now.

Added:
Change framerate without recoding for mpeg2 videos.
h264_qsv and hevc_qsv encoding with hardware acceleration (for Intel CPU's).

Fixed:
Bug in mpeg1/mpeg2 stream extraction raw or container(thx to Amiga for the hint).
Bug in mpeg2 encoding/extractiing.
Bug in filterchain with scaling.

Changed:
ffmpegsource2 instead of lwlibavvideosource because missing UTF8 support (with avisynth).

Improved:
Recognition of already processed streams and still open tasks.
Video stream indexing (completely rewritten).
HDR Info,.
Muxing grid handling.
Join grid handling.
Many code improvements.

[ProWo]

Newest beta (v3.3.0.02), online now.

Added:
mpeg2_qsv (for Intel GPU's), h264_nvenc and hevc_nvenc (for nVidia GPU's) hardware accelerated encoders.
(I cannot test the nVidia hardware acceleration because I do not have an nVidia GPU. So test it and report here if it works or if errors occur.)

Fixed:
Muxing hevc to mp4 gave wrong FPS values.
Encoding HDR to BT709 without tonemapping error (thx to javieracdc for the hint).
App vanishing when minimized.

Improved:
Application stability.

Changed:
FFmpeg commandline execution code is centralized now.

[ProWo]

Newest beta (v3.3.0.03), online now.

Added:
Output filename check for existing files or batch tasks.

Fixed:
Bug with av1 encoding (thx to Marcellos for the hint).

Improved:
Crop handling code.

Changed:
Output files destination handling.

Removed:
hwaccel auto (not working on Win7, thx to oniiz86 for the hint).

[Lathe]

Hey, Mr. ProWo! I wanted to ask you your opinion if I may please...

I notice on the last few encodes that when converting from UHD to HD using Mobius and a desaturation of '2' (default) the result seems like it comes out rather bright. Just for comparison, I also tried HandBrake which of course does not give you the choices that your program does, but the brightness seemed to look better, more natural.

Any thoughts...? Should I try different settings when using CleverFFMpeg? I thought maybe I'd try the 'Haber' I think it's called, and I chose a desaturation of '1' just to see how it looks.

I would really appreciate any input you might have about this.

Thank you!

***EDIT

Hmmm... Interesting. I checked the encode so far (DAMN your program is fast!) and I compared it to the original UHD file played by KM Player, and you know, I don't know if I just happened to guess it right, but with the 2 changed settings I mentioned above, the resulting picture looks pretty damn good! I see no difference. That's a good thing, right? Thanks!

[ProWo]

Newest beta (v3.3.0.04), online now.

Added:
Chapters creating: automatic insertion of start chapter at starttime 0 (video start), so that chapter 1 is now reached by the player commands.
Output file names check.
h264_amf and hevc_amf hardware accelerated encoding.
webvtt subs muxing in 3gp,mp4,mov.

Fixed:
Bug in chapters naming.
Bugs in output file naming.
Bug in forms positioning.
Bug in audio channels remap.
Bug in batch file handling.
Bug in crops handling.

Changed:
Output file naming.
Commandline for nvenc hardware encoding.

Resumed:
Hardware decoder, for supported hardware accelerated videoencoder only (The hw_accel decoder can be deactivated in the encoder settings).

[ProWo]

----------------------------------------------------------------------------------
October 25 2024 release version 3.3.1.
----------------------------------------------------------------------------------
Added:
Change framerate without recoding for mpeg2 videos.
h264_qsv and hevc_qsv encoding with hardware acceleration (for Intel GPU's).
h264_amf and hevc_amf encoding with hardware acceleration (for AMD GPU's).
mpeg2_qsv (for Intel GPU's), h264_nvenc and hevc_nvenc (for nVidia GPU's) hardware accelerated encoders.
(I cannot test the nVidia and AMD hardware acceleration because I do not have the related hardware. So test it and report here if it works or if errors occur.)
Output filename check for existing files or batch tasks.
Chapters creating: automatic insertion of start chapter at starttime 0 (video start), so that chapter 1 is now reached by the player commands.
Output file names check.
webvtt subs muxing in 3gp,mp4,mov.

Fixed:
Bug in mpeg1/mpeg2 stream extraction raw or container(thx to Amiga for the hint).
Bug in mpeg2 encoding/extractiing.
Bug in filterchain with scaling.
Muxing hevc to mp4 gave wrong FPS values.
Encoding HDR to BT709 without tonemapping error (thx to javieracdc for the hint).
App vanishing when minimized.
Bug with av1 encoding (thx to Marcellos for the hint).
Bug in chapters naming.
Bugs in output file naming.
Bug in forms positioning.
Bug in audio channels remap.
Bug in batch file handling.
Bug in crops handling.
bug in change framerate (various)

Improved:
Recognition of already processed streams and still open tasks.
Video stream indexing (completely rewritten).
HDR Info,.
Muxing grid handling.
Join grid handling.
Many code improvements.
Application stability.
Crop handling code.

Changed:
ffmpegsource2 instead of lwlibavvideosource because of missing UTF8 support (with avisynth).
FFmpeg commandline execution code is centralized now.
Output files destination handling.
Output file naming.
Commandline for nvenc hardware encoding.
----------------------------------------------------------------------------------

[ProWo]

Newest beta (v3.3.1.01), online now.

Added:
AMD and nVidia HW supported encoding: -rc hq vbr.
-tag:v hvc1 for hevc streams muxing (thx to neptune84 for the hint).

Fixed:
AMD and nVidia HW supported encoding: bugs in profile, preset and tune selections.
Bug in chapters handling.
Bug with faststart for mp4 and mov muxing.

Changed:
ac3 decoder DRC set to on (default), if not recoded to ac3.

[tebasuna51]

Originally Posted by ProWo

Changed:
ac3 decoder DRC set to on (default), if not recoded to ac3.

For what?

[ProWo]

Originally Posted by tebasuna51

For what?

In the previous versions, every ac3 stream was preset to DRC off due to a user request.
However, DRC off only makes sense if ac3 is encoded again to ac3.
For all other target codecs, the default setting (DRC on) should be better.

[SeeMoreDigital]

When somebody has taken the time to create/produce a professional recording why would anybody want to slap dynamic range compression on it afterwards...

[tebasuna51]

Originally Posted by ProWo

However, DRC off only makes sense if ac3 is encoded again to ac3.

But ffmpeg never encode AC3 with DRC, like other encoders.

For all other target codecs, the default setting (DRC on) should be better.

Not for me.
Please let at least at user choice.

[ProWo]

Originally Posted by tebasuna51

But ffmpeg never encode AC3 with DRC, like other encoders.

It's a decoder setting, not an encoder setting.
See here:
https://www.ffmpeg.org/ffmpeg-codecs...ecoder-Options

Originally Posted by tebasuna51

Not for me.
Please let at least at user choice.

The user choice remains, only the setting has been changed.

[ProWo]

Originally Posted by SeeMoreDigital

When somebody has taken the time to create/produce a professional recording why would anybody want to slap dynamic range compression on it afterwards...

see here:
https://hydrogenaud.io/index.php/topic,123091.0.html

[Lathe]

Hey ProWo, I wanted to get your advice (and any others of course) as to what to do with this UHD 4k Blu-ray that I would normally use your program to convert from UHD-HD and from HDR-SDR. I came across this before where I guess the full 4k rip has 2 video files. It was explained to me that the smaller 2nd video file is the DV information.

So, when I choose this file to load into Clever FFMpeg, do I just choose the entire MKV file with all the information like I normally do, and will Clever FFMpeg 'Know' what to do with those 2 video files? Or, will I have to select ONE of them, the primary, larger one, and then Clever FFMpeg will be able to process that okay?

It seems like I tried this before and Clever FFMpeg threw an error either in loading or even like 2/3 the way through encoding.

What do I do...? Thank you kindly for the help!

Here is the MediaInfo file for the 2 video files:

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 27 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
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 : 350 cd/m2
Maximum Frame-Average Light Level : 190 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 27 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
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