Interpret fps (AssumeFPS) & Conditional

[silverline]

Hi there,
first of all thank you for this cool software! (Although I only scratched the surface of it until now)
Because I have to convert a lot of BluRay m2ts files to a editable format, I am happy to have found Ffastrans. Now my PC can do this overnights and I can edit the next day. perfect.

There are some things I would like to mention here.
1. Because we produce in 25fps I used the simple possibility to interpret the source to 25fps with "m_clip = AssumeFPS(m_clip, 25)". This works fine for the m2ts files, for they are mostly 24 or 23,976 fps and speedup doesn't matter much. But I noticed, that Ffastrans sometimes only delivered a *.avs file. This was especially strange, because I noticed that it produced large intermediates (mkv), that were totally playable. First I thought it was an codec input issue, but then I had the idea, that it could be the input frame rate - and it was. The few files that were already 25fps produced *.avs files.
Could it not just proceed with producing a movie file although fps are already 25?

2. So I inserted two conditionals: "%f_frame_rate% (=) 25.00" & "%f_frame_rate% (<>) 25.00" so that the 25fps files could be processed without fps interpretation. And it worked. But the massages in the Ffastrans monitor regarding to the conditions are a bit irritating.
When fps is not equal to 25 the message is: '1st evaluation of "%f_frame_rate%=25.00" is "24=25" (couldn't it be "false" or "24<>25"?)
When fps is equal to 25 the message is: '1st evaluation of "%f_frame_rate%<>25.00" is "25<>25" (also strange, for 25 ist not <> 25)
You know what I mean?

All the best

[admin]

Hi silverline, thank you for using FFAStrans and welcome to the forum!

I know it seem a bit confusing, and even irritating but there is a logic behind it:

1. It shows that the evaluation of the node came out false, or failed.

2. It shows the variables you used and more important, the data those variables was populated with. But it's not suppose to show what the evaluation is not, if you know what I mean. F.ex.: You want "24=25" to show "24<>25" instead but "24<>25" is not what you evaluated. You evaluated "24=25", which is false. I can sort of see that showing "24<>25" sort of makes sence in this case but so does "24<25". Both are equally true. So.... what evaluation you did not use should FFAStrans be showing instead? It can't make that decision. Of course, there are probably better ways of showing what went wrong and I'm up for suggestions here.

-steipal

[silverline]

Hi steipal,

thanks for the quick reply. I kind of understand... I think it's just about getting used to it. But as it works finde, I could get used to every kind of log message. Maybe "1st evaluation of "%f_frame_rate%=25.00" is "horseshoe" would be nice

Just a quick question:
is it somehow possible to have an automatic audio loudness normalization done. You know, like "ebu R128" or other LUFS targets?

silverline

[admin]

Something in that area is on my to-do list.

-steinar