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

[SeeMoreDigital]

Originally Posted by Hellboy.

I use .w64 because it works with tsMuxeR and .wav don't.

Yes it does!

What size/type of .wav contained files are you using?

[Hellboy.]

Using the new beta i convert the dts-hd to pcm using the same settings i show in this picture
https://forum.doom9.org/showpost.php...&postcount=394
and tsMuxer don't accept the file.

wav = 5.35 GB

[ProWo]

Originally Posted by Hellboy.

Using the new beta i convert the dts-hd to pcm using the same settings i show in this picture
https://forum.doom9.org/showpost.php...&postcount=394
and tsMuxer don't accept the file.

wav = 5.35 GB

I have made some tests for pcm encodings >4 Gb:
pcm as wav: is cut off at 4Gb, content not complete.
pcm with -rf64 auto as wav: complete content is preserved, is played by most players, but not recognized by tsmuxer.
pcm as w64: recognized by tsmuxer, but not played by most players.
pcm in mka container: complete content is preserved, is played by all players, is recognized by tsmuxer.

I will therefore return to the previous command line for pcm encoding. For pcm encodings >4Gb the mka container should therefore be used.

[ProWo]

Newest beta (v3.2.5.03), online now.
Added: Sample muxing (request by kssxs).
Fixed: Bug in audiofilter with flac encoding.
Removed: -rf64 auto filter with pcm encoding, not working as aspected.

[Hellboy.]

Under "Audio Encoding>Change length & pitch", which do you recommend: Length only or Length & pitch.
Thanks.

Edit:

If i understand correctly
Length only = Preserving Pitch
Length & pitch = Correcting Pitch

[Emulgator]

Depends on what you want to achieve.

In terms of damage there is one operation less damaging:
Having length multiplied by the same factor as pitch is divided (length *1,2 AND pitch/1,2).

Resampling for a length change only OR for pitch change only will generate more damage.

[ProWo]

Newest beta (v3.2.5.04), online now.
Fixed: Bug with using raw vc1 streams, bug with framerate recognition of vc1 in m2ts (thx to Amiga for the hint).
Improved: Video indexing for cut, keyframe cut precision.

[ProWo]

----------------------------------------------------------------------------------
April 30 2024 release version 3.2.6.
----------------------------------------------------------------------------------
Fixed: major bug (missing variable reset after sample video encoding/muxing).

Changed: Audio spectrogram picture type (png to jpg).
New logo and new icon.
Cut code.

Improved: Video without duration info handling.
Sample handling (video encoding, muxing).
----------------------------------------------------------------------------------

[Lathe]

Originally Posted by ProWo

----------------------------------------------------------------------------------
April 30 2024 release version 3.2.6.
----------------------------------------------------------------------------------
Fixed: major bug (missing variable reset after sample video encoding/muxing).

Changed: Audio spectrogram picture type (png to jpg).
New logo and new icon.
Cut code.

Improved: Video without duration info handling.
Sample handling (video encoding, muxing).
----------------------------------------------------------------------------------

Thanks so much mate for all the hard work AND the great program! I am still somewhat new at this, I just wanted to ask you if you have a moment, when converting from HDR-SDR, what is the tone mapping being done exactly? I mean, what do the 'Mobius' and the desaturation settings do (I do know what saturation is, but I don't understand why it is set to desaturate at -2?)

I know you are likely very busy, but if you don't mind the bother if you could please kindly help me to understand what exactly the program is doing this way that would be great, thanks!

[ProWo]

Originally Posted by Lathe

when converting from HDR-SDR, what is the tone mapping being done exactly? I mean, what do the 'Mobius' and the desaturation settings do (I do know what saturation is, but I don't understand why it is set to desaturate at -2?)

Read the full info about ffmpeg tonemap filter:
https://ffmpeg.org/ffmpeg-filters.html#tonemap-1

[Lathe]

Originally Posted by ProWo

Read the full info about ffmpeg tonemap filter:
https://ffmpeg.org/ffmpeg-filters.html#tonemap-1

Thanks, will do!

[ProWo]

Newest beta (v3.2.6.01), online now.

Added: Keyframe check on cutting.
More info of subtitle type on subtitle burn in.
Automatic pixel format settings with HDR10/HLG sources.
wmv3 muxing.

Fixed: Bug in subtitle burn in with picture based subtitles.

Changed: Filter removed on file search (request by Ennio).
Removed first keyframe delay field (cut section).
Default settings for dynaudnorm filter.
Extraction of DVD and DVB subtitles to mkv.

[ProWo]

Newest beta (v3.2.6.02), online now.

Fixed: Disappearing bug.
Video encoding filterchain bug.
Bug in multiplex grid with preprocessed and batch streams.
Bug in ffmpeg path (thx Ndidi for the hint).

Changed: HDR info in file analysis and app.

Improved: automatic settings on HDR conversions.

[ProWo]

Newest beta (v3.2.6.03), online now.

Added:
UTF-8 support for filenames.

Fixed:
Bug in video stream extraction, with videostream index >0.

Changed:
Removed webvtt muxing to 3gp,flv,mov,mp4, not working.
Removed filename check and replace for non ascii characters, problematic with many foreign language filenames.

[ProWo]

----------------------------------------------------------------------------------
July 02 2024 release version 3.2.7.
----------------------------------------------------------------------------------
Added:
Keyframe check on cutting.
More info of subtitle type on subtitle burn in.
Automatic pixel format settings with HDR10/HLG sources.
wmv3 muxing.
UTF-8 support for filenames.
Extract mpeg1, mpeg2 video as mpg
wmv1 muxing to asf, avi, mkv, mp4, webm, wmv.

Fixed:
Bug in subtitle burn in with picture based subtitles.
Disappearing bug.
Video encoding filterchain bug.
Bug in multiplex grid with preprocessed and batch streams.
Bug in ffmpeg path (thx Ndidi for the hint).
Bug in video stream extraction, with videostream index >0.

Improved:
Automatic settings on HDR conversions.
Subtitles burn in.

Changed:
Filter removed on file search (request by Ennio).
Removed first keyframe delay field (cut section).
Default settings for dynaudnorm filter.
Extraction of DVD and DVB subtitles to mkv.
HDR info in file analysis and app.
Removed webvtt muxing to 3gp,flv,mov,mp4, not working.
Removed filename check and replace for non ascii characters, problematic with many foreign language filenames.
Removed wma2 muxing to webm (not working).
----------------------------------------------------------------------------------

[Lathe]

I've used your excellent program before to convert from HDR to SDR and from UHD to HD. But, this time when the conversion was finished with the exact same settings (level 4.1, etc) the resulting Blu-ray that I burned from it would NOT play on my OPPO player, it just froze. It does that when something in the Blu-ray is not right.

Why did encodes I did before work just fine when I burned the resulting Blu-rays, but this time it did not...? If this doesn't work for me anymore, than I can't use your program to create playable Blu-rays anymore and that would be a drag...

Thanks for any help!

***EDIT

I actually had to run your encode through BDRB in order to get the resulting burned Blu-ray to play properly, which it played just fine. Bummer I had to reencode it twice

[gonca]

Next time run it through tsMuxer and see if that plays back.

[Lathe]

Originally Posted by gonca

Next time run it through tsMuxer and see if that plays back.

For a Canadian guy you sure get around...

Thanks man. Yeah, it was such a bummer, doing the whole encode from HDR-SDR with the exact same settings and then the Blu-ray mysteriously choking on my OPPO (older BDP-83, but serviced recently)

And yeah, I had to add the audio tracks afterward, so I did use TSMuxer to do that, but the resulting Blu-ray did not play. I checked the encoding specs closely and I didn't see anything wrong with them. Don't remember if the Blu-ray compatible buffers were set though, but I never needed to worry about that before. Would be nice if there were a way to add x264 commands to CleverFFMpeg, but I don't think you can. Maybe I should try Hybrid...

Sure will be a shame if CleverFFMpeg doesn't actually work for me anymore to do these HDR-SDR conversions because the resulting picture looks really great! Even having to reencode it through BDRB with just barely enough compression so that it is forced to reencode, still the picture looks really good!

[gonca]

Try "simple x264 launcher"
also try using
--bluray-compat in your command line

[Lathe]

Originally Posted by gonca

Try "simple x264 launcher"
also try using
--bluray-compat in your command line

Yeah, I WOULD, but I can't see where you can add x264 commands to CleverFFMpeg. And... I wonder why I didn't have to do that before...?