Source is 23,976, with assumefps converted to 25 fps.

Setting in HCM was 25fps, but it then display's the running time of the original source, thus the running time @ 23,976 fps.

Sorry but after a quick test, I don' thave the behaviour you say.

First, I correct something : purebasic can't return then time lenght, but only the frame number. That is why I need the user to give the fps to compute the time.

This is my test :
Source (with virtualdub) : 61279 frames, 42min36sec, 23.976
HCMatic w/o assumeFps(25): 61258, 42min35 sec if I select fps=23.976, 40min50sec if I select fps=25
HCMatic with assumeFps(25): 61275, 42min36 sec if I select fps=23.976, 40min51sec if I select fps=25

You can see that purebasic has a bug in the way it retrieves the frame number because the part in red is false, but this error is always less than a sec - harmless.
Nevertheless, HCMatic indicates the correct time when you select fps=25, whatever you have an assumeFps or not in the script.

Can you check the frame number of your source and compare it with what HCMatic indicates ? Are you sure you are not using a "convertFps" or "changeFps" ?

I will check it ASAP!

Hi Phil,
thanx a lot for this nice tool, and for keeping it uptodate.
From Changelog I understand that the last change is not in the GUI, but internal, isn't it?.
I mean, I didn't test it, but I suppose that when interlaced is not selected, "*PROGRESSIVE" will be added to the .ini, am I true?.

Cheers

You are all right .

Note: there is a tiny change in the interface itself : in the log, the bitrate obtained for each source is indicated at the begining of the line now, and not in the end. This allow to read it even if the filenames are very long (I prefered that insteed of adding a scroll bar).