Incorrect frame rate when using CSV Files

[sheppy99]

When I try and optimise comskip using the CSV file it always detects the framerate as 25 despite the original being 50 and showing 50 in the original scan log. The scan log post CSV shows 25 and the resultant XML file has cut points of double what they should be. I'm guessing that comskip has no way of knowing that the original framerate should be and that it isn't in the CSV file.
Is there a setting somewhere I can set manually to override this?

[erik]

Maybe the
fps=50
setting in the ini file still works

[sheppy99]

thanks will give it a try - does it matter where in the ini file I put it?

[sheppy99]

That works, thanks v much

[erik]

Will update the doc for this use cae