Cvs 2002-02-18

-h · 18th February 2002, 12:45

Figured I'd start a new thread.. "My XviD binaries" is getting too large.

I merged a bunch of stuff a few minutes ago, new credits modes, some of Koepi's mods (didn't get the 101-byte frame thing.. shouldn't it still be scaled down to 101 bytes instead of left as nns1->bytes?) and the quant_type modulation (requires core mod, which I think Isibaar will be committing some time soon with more mods).

Very experimental - if you download a 2002-02-18 build, you can be guaranteed that something will go wrong. You've been warned

I would've tested more, but I'm very tired and wanted users to test for me, ala microsoft. Ah it's a developer's life for me.

-h

Nic · 18th February 2002, 13:04

Guess what?

Get at:
www.freewebz.com/xvid
or
xvid.stormpages.com

Please test & inform -h of any errors here....

-Nic

rui · 18th February 2002, 13:12

Nic, you are faster than a speeding bullet

Koepi · 18th February 2002, 13:17

Very nice

Now I'm a little bit in trouble:
should I once more adopt my changes to the new CVS version or stick with the old binary?
Damn, a real changelog would be so useful

Since my binaries work well so far, I guess I wait until Isibaar introduces the new API?

Best regards,
Koepi

-h · 18th February 2002, 13:20

should I once more adopt my changes to the new CVS version or stick with the old binary?

Hrm. The quant_type modulation is still useful, but I don't know Isibaar's plans yet. I have to contact him about API support for interlacing too.

There's a kind of changelog in the CVS comments, I listed everything I changed for once! Felt weird.

-h

-h · 18th February 2002, 14:06

Well, since no one's machine has burst into flames yet (then again, how would I know if it had?), I'm off to bed.

-h

Koepi · 18th February 2002, 14:19

Sleep well, g'night -h!

If there don't show up any error messages until tomorrow I could adopt my changes (quant_type modulation,...) to the new CVS.

Best regards,
Koepi

rui · 18th February 2002, 15:29

I am doing a VERY small test, using again an AVI file as source file.
Again, i have some doubts that this is a valid test, so...
But here goes: the avi file is 10230 KB size, i choosed a final size of 3000 KB, and the codec gave me a file of 3032 KB. I used H.263, motion search precision 5, no lumi masking, no credits, and I-frame lock 2-6, with the smooth quantizer fluctuation enabled.

Then i did the same test using the same setings, but with no I-frame locking.
The final file size was 3024 KB. But Koepi once said that with the small size that we are dealing here, I-frame lock could create a little oversized final file

Regarding the quality, both files weren't good, because the source file was an avi already compressed (this is all i have to work right now, when in home i can make better tests).

Well, there you have it, i din't encounter any problems with this new build. For all this test is worth...

Koepi · 18th February 2002, 15:32

once again thanks a million rui for testing so constantly

Warm regards,
Koepi

rui · 18th February 2002, 22:42

I am just finishing a 1 cd rip from Independence Day.
i am still using Koepi's latest build, because i really like the modulated quantizer option.
I am doing 1 cd rip, because Gnot comp check says to me that by using a 512x... resolution i could try to put the all movie in 1 cd (i got 42%). Since my last 1 cd rip of "The Replacements" which didn't go so well, i am still trying to test XviD in 1 cd rips.

Koepi · 18th February 2002, 23:04

Heh

Since I'm only doing 1CD rips as well, most of the options I introduced are most useful for such "low bitrate conditions"...

Works very, very well for me up to now. Too bad that the DivX4 DS filter sucks this big time, the movies still look better with the XviD one!

Just finished "the emperors new groove" and had the first high bitrate situation in my life. Tweaked around a little... but at least 1 scene is asynch. The Intraframe starting that scene is too huge...

I need a faster compi .
But the quality... yumm yumm! Such a glitch caused by my compi doesn't disturb me at all!
...
well, i don't want to write a biography here, so..

best regards,
Koepi

rui · 18th February 2002, 23:56

I just finished my Independence Day 1 cd rip.
The quality, taking in consideration that the movie has 2H33m, is very good.
Much better than the movie "The Replacements" 1 cd rip. That goes with my idea that "The Replacements" just can't be done in 1 cd.
I used for 1 pass H.263, motion search 5, no lumi of course, end credits enabled. For 2 pass i enabled modulated quantization, I-frame lock 2-6 with smooth quantizer fluctuation enabled. Still no lumi (i think i will never use it again).
I targeted a final size of 572564 and got 576110. This is the biggest difference i ever encountered with XviD. Maybe is the movie, or my I-frame lock parameters weren't the best.
But when joining with the audio, i couldn't reach the 700MB.
The value i pointed to the codec (572564) was given to me by Gnot (beware that i didn't use the external 2 pass, i only used Gnot to have some value to point to the codec). I configured it by indicating the final size of the audio, then choose to calculate the interleaving & AVI overhead (1 vbr-mp3), but, in spite of getting a final video filesize bigger than expected i still didn't reach the 700MB when muxed with the audio.
Maybe something in Gnot calculations weren't right?

I want to apologize to -h, because this thread was supposed to be testing his new build, but instead i am posting results of Koepi's build

P.S. I still didn't encounter any problems with the colour, in spite of using the Div4 post processing. But i didn't saw the all movie yet, so i could still have some errors that i still haven't spotted

wing1 · 19th February 2002, 04:09

Well, I ran -h's & nic's new CVS build, and I've not seen any problem. Capture went perfect ( is it a little faster? or is it just my imagination? ). Encode also went perfect and no halucination issue either

This is getting better and better with each build.

-h · 19th February 2002, 06:20

Capture went perfect ( is it a little faster? or is it just my imagination? ).

Were you capturing in quality mode? If so, there was a bug in the pre-18th feb builds whereby it would always use lower quantizers, thus increasing file size and slowing itself down (due to more bitstream functions being called).

The interlacing code is "done", I just have to see if the guys like the changes I made to core.

-h

rui · 19th February 2002, 10:24

Okay, i did a quick test with the -h and Nic latest build, using a riped chapter from a PAL movie "The Haunting", and coudn't find any problems. The final size was off only 10KB (oversized), it was only a small chpater but i don't think this represents any problems.
My settings were, as usual, first pass motion precision search 5, H.263. For the 2 pass, i choosed no lumi, and I-frame lock 2-5 with the smooth quantizer fluctuation enabled.
The quality was very good, in spite that my average video bitrate was only 600Kb.
So, i agree with wing1 words.
I believe that it's time for Koepi to step in and include his modulated quantization method

P.S. I am noticing that with the latest builds, i am getting the video file a little oversized. This could be because with the latest builds i am allways using the I-frame lock quantizer. In this specific test i made, it could be atributed to the small files size, but i already did some tests in full movies, and allways got a oversized files. I am using the 2-5 I-frame lock after reading a post by -h indicating this values for a 1 cd rip, and 2-3 for a 2 cd rip.

Koepi · 19th February 2002, 10:57

Oversize up to a few 100kb is absolutely possible and natural when using iframe quant lock+quantizer smoothing.

(let's say, about 200kb oversized is well in range).

Or is it MBs we're talking about?

Regards,
Koepi

Ripe73 · 19th February 2002, 11:47

@Koepi
Do you use XviD DSfilter and if you do how do you change the brightness?
I really want to use the XviD DSfilter but its to dark, when i use Divx4 DSfilter i use brightness 58.
I have tried to change the brigtness in the Nvidia but it dont change the brightness in Mplayer2.
BTW now i get the exactly filesize,i encoded Dungeons & Dragons 108min on 1cd and did a Oggcontainer with subbs and the quality was very good(Koepis latest).

Koepi i use your statsreader will it show correct on a XviDstasfile?

Thanks

Koepi · 19th February 2002, 11:53

The statsreader is somewhat flawed since I read the luma values in a wrong way (incompaitble data types in delphi and c++....)
But for the rest it is accurate.
I use it for determing the compression ratio (first pass filesize as shown in stats reader (and now by debug output as well

) against the desired size...)

I can't change the brightness either and I'm still investigating how to add such support to the DShow project. since the class wizard isn't involved it's very hard for me to insert anything there :-(

-h must step in here again

Regards,
Koepi

Nic · 19th February 2002, 12:09

I was thinking of looking at adding brightness code to the DShow filter, it shouldn't be tooooo tricky (famous last words)

If no one does it by the weekend then I will give it a real try....Did -h ever get anywhere with adding postprocessing support??

-Nic

-h · 19th February 2002, 12:12

-h must step in here again

He must?

I'd say Nic's your man, dshow is all voodoo to me at the moment. I can honestly say I have no idea how such a brightness control should work (overlay tweaking? internal brightness filter? SendMessage(WORKNOWDAMNIT)? )

And this interlacing stuff is fun to debug.

-h

18th February 2002, 12:45	#1 \| Link
-h Kilted Yaksman Join Date: Oct 2001 Location: South Carolina Posts: 1,303	Cvs 2002-02-18 Figured I'd start a new thread.. "My XviD binaries" is getting too large. I merged a bunch of stuff a few minutes ago, new credits modes, some of Koepi's mods (didn't get the 101-byte frame thing.. shouldn't it still be scaled down to 101 bytes instead of left as nns1->bytes?) and the quant_type modulation (requires core mod, which I think Isibaar will be committing some time soon with more mods). Very experimental - if you download a 2002-02-18 build, you can be guaranteed that something will go wrong. You've been warned I would've tested more, but I'm very tired and wanted users to test for me, ala microsoft. Ah it's a developer's life for me. -h

18th February 2002, 13:12	#3 \| Link
rui Registered User Join Date: Dec 2001 Location: Portugal Posts: 730	Nic, you are faster than a speeding bullet __________________ Rui

18th February 2002, 13:17	#4 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,454	Very nice Now I'm a little bit in trouble: should I once more adopt my changes to the new CVS version or stick with the old binary? Damn, a real changelog would be so useful Since my binaries work well so far, I guess I wait until Isibaar introduces the new API? Best regards, Koepi __________________ Koepi's new media development site

18th February 2002, 14:19	#7 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,454	Sleep well, g'night -h! If there don't show up any error messages until tomorrow I could adopt my changes (quant_type modulation,...) to the new CVS. Best regards, Koepi __________________ Koepi's new media development site

18th February 2002, 15:29	#8 \| Link
rui Registered User Join Date: Dec 2001 Location: Portugal Posts: 730	I am doing a VERY small test, using again an AVI file as source file. Again, i have some doubts that this is a valid test, so... But here goes: the avi file is 10230 KB size, i choosed a final size of 3000 KB, and the codec gave me a file of 3032 KB. I used H.263, motion search precision 5, no lumi masking, no credits, and I-frame lock 2-6, with the smooth quantizer fluctuation enabled. Then i did the same test using the same setings, but with no I-frame locking. The final file size was 3024 KB. But Koepi once said that with the small size that we are dealing here, I-frame lock could create a little oversized final file Regarding the quality, both files weren't good, because the source file was an avi already compressed (this is all i have to work right now, when in home i can make better tests). Well, there you have it, i din't encounter any problems with this new build. For all this test is worth... __________________ Rui

18th February 2002, 13:04	#2 \| Link
Nic Moderator Join Date: Oct 2001 Location: England Posts: 3,285	Guess what? Get at: www.freewebz.com/xvid or xvid.stormpages.com Please test & inform -h of any errors here.... -Nic

18th February 2002, 13:20	#5 \| Link
-h Kilted Yaksman Join Date: Oct 2001 Location: South Carolina Posts: 1,303	should I once more adopt my changes to the new CVS version or stick with the old binary? Hrm. The quant_type modulation is still useful, but I don't know Isibaar's plans yet. I have to contact him about API support for interlacing too. There's a kind of changelog in the CVS comments, I listed everything I changed for once! Felt weird. -h

18th February 2002, 14:06	#6 \| Link
-h Kilted Yaksman Join Date: Oct 2001 Location: South Carolina Posts: 1,303	Well, since no one's machine has burst into flames yet (then again, how would I know if it had?), I'm off to bed. -h

18th February 2002, 15:32	#9 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,454	once again thanks a million rui for testing so constantly Warm regards, Koepi __________________ Koepi's new media development site

18th February 2002, 22:42	#10 \| Link
rui Registered User Join Date: Dec 2001 Location: Portugal Posts: 730	I am just finishing a 1 cd rip from Independence Day. i am still using Koepi's latest build, because i really like the modulated quantizer option. I am doing 1 cd rip, because Gnot comp check says to me that by using a 512x... resolution i could try to put the all movie in 1 cd (i got 42%). Since my last 1 cd rip of "The Replacements" which didn't go so well, i am still trying to test XviD in 1 cd rips. __________________ Rui

18th February 2002, 23:04	#11 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,454	Heh Since I'm only doing 1CD rips as well, most of the options I introduced are most useful for such "low bitrate conditions"... Works very, very well for me up to now. Too bad that the DivX4 DS filter sucks this big time, the movies still look better with the XviD one! Just finished "the emperors new groove" and had the first high bitrate situation in my life. Tweaked around a little... but at least 1 scene is asynch. The Intraframe starting that scene is too huge... I need a faster compi . But the quality... yumm yumm! Such a glitch caused by my compi doesn't disturb me at all! ... well, i don't want to write a biography here, so.. best regards, Koepi __________________ Koepi's new media development site

18th February 2002, 23:56	#12 \| Link
rui Registered User Join Date: Dec 2001 Location: Portugal Posts: 730	I just finished my Independence Day 1 cd rip. The quality, taking in consideration that the movie has 2H33m, is very good. Much better than the movie "The Replacements" 1 cd rip. That goes with my idea that "The Replacements" just can't be done in 1 cd. I used for 1 pass H.263, motion search 5, no lumi of course, end credits enabled. For 2 pass i enabled modulated quantization, I-frame lock 2-6 with smooth quantizer fluctuation enabled. Still no lumi (i think i will never use it again). I targeted a final size of 572564 and got 576110. This is the biggest difference i ever encountered with XviD. Maybe is the movie, or my I-frame lock parameters weren't the best. But when joining with the audio, i couldn't reach the 700MB. The value i pointed to the codec (572564) was given to me by Gnot (beware that i didn't use the external 2 pass, i only used Gnot to have some value to point to the codec). I configured it by indicating the final size of the audio, then choose to calculate the interleaving & AVI overhead (1 vbr-mp3), but, in spite of getting a final video filesize bigger than expected i still didn't reach the 700MB when muxed with the audio. Maybe something in Gnot calculations weren't right? I want to apologize to -h, because this thread was supposed to be testing his new build, but instead i am posting results of Koepi's build P.S. I still didn't encounter any problems with the colour, in spite of using the Div4 post processing. But i didn't saw the all movie yet, so i could still have some errors that i still haven't spotted __________________ Rui Last edited by rui; 18th February 2002 at 23:59.

19th February 2002, 04:09	#13 \| Link
wing1 Registered User Join Date: Feb 2002 Posts: 280	Well, I ran -h's & nic's new CVS build, and I've not seen any problem. Capture went perfect ( is it a little faster? or is it just my imagination? ). Encode also went perfect and no halucination issue either This is getting better and better with each build.

19th February 2002, 06:20	#14 \| Link
-h Kilted Yaksman Join Date: Oct 2001 Location: South Carolina Posts: 1,303	Capture went perfect ( is it a little faster? or is it just my imagination? ). Were you capturing in quality mode? If so, there was a bug in the pre-18th feb builds whereby it would always use lower quantizers, thus increasing file size and slowing itself down (due to more bitstream functions being called). The interlacing code is "done", I just have to see if the guys like the changes I made to core. -h Last edited by -h; 19th February 2002 at 06:23.

19th February 2002, 10:24	#15 \| Link
rui Registered User Join Date: Dec 2001 Location: Portugal Posts: 730	Okay, i did a quick test with the -h and Nic latest build, using a riped chapter from a PAL movie "The Haunting", and coudn't find any problems. The final size was off only 10KB (oversized), it was only a small chpater but i don't think this represents any problems. My settings were, as usual, first pass motion precision search 5, H.263. For the 2 pass, i choosed no lumi, and I-frame lock 2-5 with the smooth quantizer fluctuation enabled. The quality was very good, in spite that my average video bitrate was only 600Kb. So, i agree with wing1 words. I believe that it's time for Koepi to step in and include his modulated quantization method P.S. I am noticing that with the latest builds, i am getting the video file a little oversized. This could be because with the latest builds i am allways using the I-frame lock quantizer. In this specific test i made, it could be atributed to the small files size, but i already did some tests in full movies, and allways got a oversized files. I am using the 2-5 I-frame lock after reading a post by -h indicating this values for a 1 cd rip, and 2-3 for a 2 cd rip. __________________ Rui Last edited by rui; 19th February 2002 at 10:38.

19th February 2002, 10:57	#16 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,454	Oversize up to a few 100kb is absolutely possible and natural when using iframe quant lock+quantizer smoothing. (let's say, about 200kb oversized is well in range). Or is it MBs we're talking about? Regards, Koepi __________________ Koepi's new media development site

19th February 2002, 11:47	#17 \| Link
Ripe73 DVDR Freak! Join Date: Oct 2001 Location: Sweden Posts: 351	@Koepi Do you use XviD DSfilter and if you do how do you change the brightness? I really want to use the XviD DSfilter but its to dark, when i use Divx4 DSfilter i use brightness 58. I have tried to change the brigtness in the Nvidia but it dont change the brightness in Mplayer2. BTW now i get the exactly filesize,i encoded Dungeons & Dragons 108min on 1cd and did a Oggcontainer with subbs and the quality was very good(Koepis latest). Koepi i use your statsreader will it show correct on a XviDstasfile? Thanks __________________ Drugs,Sex & Encoding

19th February 2002, 11:53	#18 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,454	The statsreader is somewhat flawed since I read the luma values in a wrong way (incompaitble data types in delphi and c++....) But for the rest it is accurate. I use it for determing the compression ratio (first pass filesize as shown in stats reader (and now by debug output as well ) against the desired size...) I can't change the brightness either and I'm still investigating how to add such support to the DShow project. since the class wizard isn't involved it's very hard for me to insert anything there :-( -h must step in here again Regards, Koepi __________________ Koepi's new media development site

19th February 2002, 12:09	#19 \| Link
Nic Moderator Join Date: Oct 2001 Location: England Posts: 3,285	I was thinking of looking at adding brightness code to the DShow filter, it shouldn't be tooooo tricky (famous last words) If no one does it by the weekend then I will give it a real try....Did -h ever get anywhere with adding postprocessing support?? -Nic

19th February 2002, 12:12	#20 \| Link
-h Kilted Yaksman Join Date: Oct 2001 Location: South Carolina Posts: 1,303	-h must step in here again He must? I'd say Nic's your man, dshow is all voodoo to me at the moment. I can honestly say I have no idea how such a brightness control should work (overlay tweaking? internal brightness filter? SendMessage(WORKNOWDAMNIT)? ) And this interlacing stuff is fun to debug. -h