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

[Findu]

@ProWo

I don't know why the Locate button for the ffmpeg folder was disabled in the settings, because it was very useful.

How about adding at least a Reset button?
Clicking it would clear only the current ffmpeg path from the configuration file and restart the app, automatically prompting you to select the new ffmpeg path.

[Findu]

@ProWo
3.5.1.01 feedback

Thank you for the last changes.

I found the following:
- When you load a raw stream, the new fps detection show 90 fps for an original 25 fps file. 3.5.1 detected 180 fps.
An othe source with 23,976 fps is now detected with 29,97 fps and with 59,94 in 3.5.1.
24, 30 and 60 fps sources get detected correctly so far.

- You also see a debug/cmd window when you click Yes for a corrected copy of the raw file. portable.config is still set to <cmd_l>0</cmd_l>

[Attachment 90974 - Click to enlarge]

[ProWo]

I found the following:
- When you load a raw stream, the new fps detection show 90 fps for an original 25 fps file. 3.5.1 detected 180 fps.
An othe source with 23,976 fps is now detected with 29,97 fps and with 59,94 in 3.5.1.
24, 30 and 60 fps sources get detected correctly so far.

What's Mediainfo's framerate from this two streams?
Could you post this two raw streams here or elsewhere to test?

- You also see a debug/cmd window when you click Yes for a corrected copy of the raw file. portable.config is still set to <cmd_l>0</cmd_l>

Oh, I forgot this test-message. Will remove it.

[Findu]

@ProWo

You have PM

[Findu]

vvc encoding is working on my AMD & Intel system.
ffplay does the playback well.

[ProWo]

@ProWo
You have PM

Thx

Your sample test2 ori 25 fps detect 90 fps.h264
Detected with 90fps (wrong) but the mediainfo is:


[Attachment 90981 - Click to enlarge]
This sample is defective.

Your sample __38134___27827___38081___36947___29289___35821_-__34987___26102___38388___36951___24536___30340-ori 23_976 fps detect 29_97 fps.h264
Detected with 29.97 fps (correct). His mediainfo:


[Attachment 90982 - Click to enlarge]

[Findu]

Okay.
I checked other files and most of the raw streams does not have a fps entry.
3.5.1.01 always detect 90 fps in that case. But the source is 23,976, 24 or 25 fps.

[Attachment 90983 - Click to enlarge]

Sorry, I found the problem with the short sample (test2 ori 25 fps detect 90 fps.h264).
As the raw files have more than 500 MB, I cut one and used the cut to extract the short raw stream.
And that produce the high value for, Frame rate : 120 000.000 FPS