Koepi 03-01-2003 build and I-Frames.

[alx]

Well, just finished "Queen of the damned" with Koepi 03-01-2003 build and his new 15-01-2003 build and a very very very stupid idea came to my mind........as usual......he he he
With build 15/01, 1 pass = near 750mb. and second pass oversized (target was 625) because of a bug that this build has, but this is not the important thing........the REALLY IMPORTANT thing is that with build 03/01 with the known bug of lack of I-Frames, 1 pass = 602 mb....so i did not had to run the 2nd. pass....
Theres no quality diference (TO MY EYES!!!) between this two 1st pass as happened with other movies that i tried this with, Star Wars Episode I and II, Lilo & Stitch, Enough, Impostor, The Sweetest thing, etc etc.
As i said before, with Star Wars Episode II, the 1st. pass = 980mb., near 250 mb. less that when i made with other build with the same options, and again there were no quality difference TO ME.

Well, the stupid idea as you can see (and please feel free to say "alx, go and kill yourself"....hehe) is...."Was demostrated the high impact I-Frames has in compresability (if this word exist in english), so, why not have an option where you can select a percent of I-Frames to use?...let´s say, 100% by default, but you may want to "PLAY" with other values. Theres a lot of movies that i do, but i don´t like so much, so, if i can "save" the second pass, good for me.

I ask this stupid question because two things, the first one is that the discover of the Peniciline came to my crazy mind..he he....and the second one is more practical.....i don´t want to "switch" codec everytime i want to try this...

Maybe this "little bug" give us more choices to get better results.
Obviously "Better results" are not the same for everybody, but, who knows........

Please, don´t kill me, is just an idea.
Alx

[Koepi]

The file size difference has nothing to do with iframes.

*scratching head*

Koepi

[alx]

So??? any ideas?? oh well, i guess i continuing using your 03/01 build for sh** movies..... he he he

[CruNcher]

@ alx and koepi
Koepis 03/01 build blures the picture more then current CVS
the current CVS sharps the picture more i stated this on the channel but the reason is not the TOO_SMALL_LIMIT it's set in both builds on 1. I have also no idear why this is but it helps compresibillity alot i attached 2 pictures to show this as zip file

[alx]

blur?? sorry, i didn´t notice that. maybe is time to go to the eyes specialist.....he he
well, anyway, i love this build......its a shame that this bug has been fixed... :-)

[cweb]

Latest news: XviD has been discovered to cause eye vision problems. Please contact your eye specialist for help. :)

[Manao]

@cruNcher : I gave a look at your screenshots, and, _for my eyes_, the 030103's build gives better results than the 120103's one. If you look at the corns and the grass, you will find them less blured in the first than in the second. The only edges that seem blured are the trees in the background, but the rest is at least as sharp. And the way the red plane is shown seems almost to good to be true. It makes me wonder if you didn't invert the screenshots, because they tend to contradict you. Perhaps while watching the movie, the impressions are different.

[CruNcher]

@Manao
jep i looked closer only was fixed on the plane thats why i oversaw the backround but fact is that koepis new build does it now exactly like the CVS so this 1 uniquenes is gone only refdivx lumimasking and the Modulated Quantizer modes differ now :( its sad that koepi did a complete new checkout and didn't tried to save this uniquenes with all CVS features like GMC and Refdivx lumimasking it would rock but maybe it was two far away from the standard i don't know ?

[CruNcher]

ok good news tested CVS again with koepis newest build its back2normal in the 01/26/03 build thx koepi but please fix refdivx lumimasking it still crashes on my p4 don't know if its releated to the processor nobody else complaining about it here :(