Ciao! (XviD-1.0-Beta2-05122003)

Koepi · 5th December 2003, 16:25

Aloha!

Finally, beta 2 is out - Codename Ciao.

Changelog:

XviD-1.0-Beta2-05122003:
- Fixed bitstream headers to be mpeg4-compliant again.
- Quant matrices are finally threadsafe.
- Interlaced encoding is fixed.
- VFW frontend fixes and misuses of core.
- Final tweaks to frame decision and motion estimation.
- Fixed overflow degeneration (Q31 problem with i-min-distance >1).
- Fixed CBR mode - the first frames weren't capped as wanted.

Please report further bugs (from this build) here, I closed the old thread as it was getting too huge.

Best regards
Koepi

tiki4 · 5th December 2003, 16:36

Thanks, testing...

tiki4

raz0r · 5th December 2003, 17:24

did first test, seems to be a lot faster.
always had ~5fps, now ~10.
encoded a very dark scene at ~1mbit, MSP-6 VHQ-4 H.263 trellis quant chroma motion adaptive quant (lumi masking) no GMC/QPEL/BVOP. source was pal progressive dvd (matrix reloaded), destination 640*272. quality is very good, but thats no wonder at 1mbit.

nice build, especially because of its speed. but still doesnt play on standalone

P0l1m0rph1c · 5th December 2003, 17:51

Great work guys!

I'm testing as I speak...some results in a few hours.

Keep up with the great work!

Manao · 5th December 2003, 17:55

Thanks a lot ! Right on time between my first and second pass

P0l1m0rph1c · 5th December 2003, 18:05

Quote:

Originally posted by Manao
Thanks a lot ! Right on time between my first and second pass

That's not very recomendable. You should finish your movie with beta1 and then move on to beta2. If i'm wrong, plz someone correct me.

Manao · 5th December 2003, 18:16

Well I don't think it will have a big influence on the result. And having an mpeg4-compliant header is (imho) more important than missing the wanted size by a few KB.

zettai · 5th December 2003, 18:20

Quote:

Originally posted by Manao
Well I don't think it will have a big influence on the result. And having an mpeg4-compliant header is (imho) more important than missing the wanted size by a few KB.

This release of the codec has had "tweaks to frame decision and motion estimation" and you dont think it will matter??

Prettz · 5th December 2003, 18:22

I have a question about GMC. Is there any way at all for GMC plus VHQ4 and MPEG quant to result in lowered quality? Or does it now either not help but not affect quality or save some bits but still not affect quality adversely?

What I'm getting at is if you don't mind the loss of speed in encoding and decoding, is there any reason NOT to always enable GMC just for the heck of it?

Manao · 5th December 2003, 18:29

zettai : I won't be sure until a developper answers that particular point, but AFAIK frame decision are made during the second pass ( and in the first when choosing between p & b & s frames ). Motion estimation is important in both passes, but since the previous ME was already very good, I don't think the ME in the beta 2 would be completely different. It may lead to a little imprecision in the final size, but I don't think it'll be sensitive.

HarryM · 5th December 2003, 18:32

Old good 'blooming' delay b-frame message ('WARNING: NOTHING TO OUTPUT, BFRAME DECODER LAG') at decoding (xvid.ax) is resolved/removed?

cipher · 5th December 2003, 18:33

Great work, guys!

But since it hasn't been fixed in beta2, I'm gonna state this again

-----LigH has found that, what should be "Global Motion Compen>>s<<ation" is now shown as "Global Motion Compenation", where an "s" is missing

Koepi · 5th December 2003, 18:35

Frame type decision is done in first pass, so you should redo the first pass - though since it is written in the first pass statsfile the encoder will oblige to that

About GMC, well, it's very slow and doesn't help too much. To be really useful it has to be tweaked a bit more. Bt sure, you can enable it if you don't mind the additional cpu power and memory necessary.

As the GUI will maybe change later we didn't give too much importance to a missing letter

Regards
Koepi

cipher · 5th December 2003, 18:41

Quote:

About GMC, well, it's very slow and doesn't help too much. To be really useful it has to be tweaked a bit more. Bt sure, you can enable it if you don't mind the additional cpu power and memory necessary.

is GMC now using 3 warping points or 4?
Thx.

Koepi · 5th December 2003, 18:45

I never heard of 4 warppoint GMC. This is "still" 3 warppoint GMC.

Ah, and about that decoder lag message: it'll stay in there as long as we don't do special DirectShow-coding for the decoder :-/ Using ffdshow (libavcodec) for decoding solves the issue.

Regards
Koepi

mfluder · 5th December 2003, 18:46

Quote:

Originally posted by mfluder
I noticed this during the testing of my dev-api-4 compiles but I wanted to wait for the official betas. When decoding dev-api-3 streams (Koepi's latest) and the height is not multiple of 16 (it's multiple of 8, 640x360) there is a bleeding at the bottom of the clip. I don't have any webspace so I can't post a screenshot but you can spot it easily. There is no problem when the clip is encoded with dev-api-4.

Sorry guys for bringing this up again but is it possible to add some kind of workaround for this problem? For example, add a condition in decoder so when bitstream version of dev-api-3 builds is detected then apply this workaround. I know it's possible to decode this kind of files correctly as ffdshow doesn't have any problem with them.

Thanks for all your work,
mfluder

Manao · 5th December 2003, 18:53

Ok, I'll do another first pass ( btw, I can keep both stats files if you want ). It'll only be the tenth time I made a first pass for this movie ( that's mainly why I was so reluctant

)

mf · 5th December 2003, 19:09

Still I find these betas slightly early. Wasn't it supposed to be so that 1.0 had core and vfw separate, and a proper GUI (ok well we know the story about the GUI..) ?

Koepi · 5th December 2003, 19:35

ok mf, you're right. I take back the betas and remove them from my site

(Or what do you expect as answer to such a [unconstructive] post?)

Regards
Koepi

AgeOfPanic · 5th December 2003, 19:45

Ik know now that I can't use Gordian Knot to control the proces, but can I still use it to setup my Avisynth-script?

5th December 2003, 16:25	#1 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,453	Ciao! (XviD-1.0-Beta2-05122003) Aloha! Finally, beta 2 is out - Codename Ciao. Changelog: XviD-1.0-Beta2-05122003: - Fixed bitstream headers to be mpeg4-compliant again. - Quant matrices are finally threadsafe. - Interlaced encoding is fixed. - VFW frontend fixes and misuses of core. - Final tweaks to frame decision and motion estimation. - Fixed overflow degeneration (Q31 problem with i-min-distance >1). - Fixed CBR mode - the first frames weren't capped as wanted. Please report further bugs (from this build) here, I closed the old thread as it was getting too huge. Best regards Koepi __________________ Koepi's new media development site Last edited by Koepi; 5th December 2003 at 19:36.

5th December 2003, 17:24	#3 \| Link
raz0r Registered User Join Date: Sep 2003 Posts: 11	did first test, seems to be a lot faster. always had ~5fps, now ~10. encoded a very dark scene at ~1mbit, MSP-6 VHQ-4 H.263 trellis quant chroma motion adaptive quant (lumi masking) no GMC/QPEL/BVOP. source was pal progressive dvd (matrix reloaded), destination 640272. quality is very good, but thats no wonder at 1mbit. nice build, especially because of its speed. but still doesnt play on standalone Last edited by raz0r; 5th December 2003 at 17:42.*

5th December 2003, 18:35	#13 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,453	Frame type decision is done in first pass, so you should redo the first pass - though since it is written in the first pass statsfile the encoder will oblige to that About GMC, well, it's very slow and doesn't help too much. To be really useful it has to be tweaked a bit more. Bt sure, you can enable it if you don't mind the additional cpu power and memory necessary. As the GUI will maybe change later we didn't give too much importance to a missing letter Regards Koepi __________________ Koepi's new media development site

5th December 2003, 18:45	#15 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,453	I never heard of 4 warppoint GMC. This is "still" 3 warppoint GMC. Ah, and about that decoder lag message: it'll stay in there as long as we don't do special DirectShow-coding for the decoder :-/ Using ffdshow (libavcodec) for decoding solves the issue. Regards Koepi __________________ Koepi's new media development site

5th December 2003, 19:35	#19 \| Link
Koepi Moderator Join Date: Oct 2001 Location: Germany Posts: 4,453	ok mf, you're right. I take back the betas and remove them from my site (Or what do you expect as answer to such a [unconstructive] post?) Regards Koepi __________________ Koepi's new media development site

5th December 2003, 16:36	#2 \| Link
tiki4 Registered User Join Date: Dec 2001 Location: Who Knows? Posts: 929	Thanks, testing... tiki4

5th December 2003, 17:51	#4 \| Link
P0l1m0rph1c h4x0r5 0n teh yu0r pC? Join Date: Nov 2003 Posts: 156	Great work guys! I'm testing as I speak...some results in a few hours. Keep up with the great work!

5th December 2003, 17:55	#5 \| Link
Manao Registered User Join Date: Jan 2002 Location: France Posts: 2,760	Thanks a lot ! Right on time between my first and second pass

5th December 2003, 18:16	#7 \| Link
Manao Registered User Join Date: Jan 2002 Location: France Posts: 2,760	Well I don't think it will have a big influence on the result. And having an mpeg4-compliant header is (imho) more important than missing the wanted size by a few KB.

5th December 2003, 18:22	#9 \| Link
Prettz easily bamboozled user Join Date: Sep 2002 Location: Atlanta Posts: 364	I have a question about GMC. Is there any way at all for GMC plus VHQ4 and MPEG quant to result in lowered quality? Or does it now either not help but not affect quality or save some bits but still not affect quality adversely? What I'm getting at is if you don't mind the loss of speed in encoding and decoding, is there any reason NOT to always enable GMC just for the heck of it?

5th December 2003, 18:29	#10 \| Link
Manao Registered User Join Date: Jan 2002 Location: France Posts: 2,760	zettai : I won't be sure until a developper answers that particular point, but AFAIK frame decision are made during the second pass ( and in the first when choosing between p & b & s frames ). Motion estimation is important in both passes, but since the previous ME was already very good, I don't think the ME in the beta 2 would be completely different. It may lead to a little imprecision in the final size, but I don't think it'll be sensitive.

5th December 2003, 18:32	#11 \| Link
HarryM Registered User Join Date: May 2002 Location: Czech rep. Posts: 380	Old good 'blooming' delay b-frame message ('WARNING: NOTHING TO OUTPUT, BFRAME DECODER LAG') at decoding (xvid.ax) is resolved/removed?

5th December 2003, 18:33	#12 \| Link
cipher Registered User Join Date: Feb 2003 Location: Atlantis Posts: 87	Great work, guys! But since it hasn't been fixed in beta2, I'm gonna state this again -----LigH has found that, what should be "Global Motion Compen>>s<<ation" is now shown as "Global Motion Compenation", where an "s" is missing

5th December 2003, 18:53	#17 \| Link
Manao Registered User Join Date: Jan 2002 Location: France Posts: 2,760	Ok, I'll do another first pass ( btw, I can keep both stats files if you want ). It'll only be the tenth time I made a first pass for this movie ( that's mainly why I was so reluctant )

5th December 2003, 19:09	#18 \| Link
mf · Join Date: Jan 2002 Posts: 1,729	Still I find these betas slightly early. Wasn't it supposed to be so that 1.0 had core and vfw separate, and a proper GUI (ok well we know the story about the GUI..) ?

5th December 2003, 19:45	#20 \| Link
AgeOfPanic Registered User Join Date: Nov 2001 Posts: 30	Ik know now that I can't use Gordian Knot to control the proces, but can I still use it to setup my Avisynth-script?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode