BUG? No zones specified -> large filesize

[crOOk]

When I don't specify a zone starting at frame 0 the file turns out very large. This works in first and second pass. I haven't figured out which options have to be turned on etc. but maybe someone else experienced the same problems.
I'm also having trouble reaching the right filesize in second pass. The first long encode went fine, but the two encodes I did today had (about!) first pass size... I'm gonna check all the settings now and do some testing and will report the results.

[sysKin]

Well yes, this GUI assumes that you know what you're doing. First zone must start at frame 0, and all zones must be in correct order.
If you don't do that, you're in trouble of some sort.

Radek

[crOOk]

The large filesize resulted of the fact that each and every frame was a keyframe... I thought what the "force kf" - option should do was forcing the first frame of the zone to be a kf, not all of them. I'll check this again.
Regarding the 2ndpass filesize being the same as the first pass filesize: I did not find a "video.stats" on my harddisk... i have to do some further research on this one because I didn't get any error messages when the secondpass started.


originally posted by sysKin
...know what you're doing.
Maybe I shouldn't even try to post bugs anymore...

[Prettz]

Originally posted by sysKin
Well yes, this GUI assumes that you know what you're doing. First zone must start at frame 0, and all zones must be in correct order.
If you don't do that, you're in trouble of some sort.

Radek
When he says "this GUI", I think that means that the GUI for future releases will be made newbie-proof.


edit: speaking of making things newbie-proof, on my first test of the new version I accidentally wasted 7 hours of encoding by entering 60 as the b-frame offset rather than .60 :rolleyes: