|
| To: | xvid-devel@xxxxxxxx |
| Subject: | Re: [XviD-devel] Adaptive quantisation |
| From: | Dirk Knop <dknop@xxxxxxx> |
| Date: | Sun, 04 Aug 2002 21:27:39 +0200 |
| References: | <Pine.LNX.4.21.0208041846370.31758-100000@lieb.math.uni-bonn.de> <Pine.LNX.4.21.0208041855560.31816-100000@lieb.math.uni-bonn.de> <20020804171957.GA12025@leloo> <006d01c23bdf$c5f32fb0$1702a8c0@michipc> <3D4D7400.2030908@gwdg.de> <007501c23bea$56048cc0$1702a8c0@michipc> |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020731 |
Luma masking was activated, and I asked Doom9 to tell me where the quantizers range around. he took a short look and they were around 8-12 (and sometimes higher), which is definatly the cause for blockyness in my experience (even with XviD which in general handles higher quantizers more gracefully than any other codec I "played" around with).before. Now I have no idea what went wrong. Blockyness can be caused by a lot of things, simplest is that the quantizers were too high (could be caused by lumi masking - btw: was lumi masking activated for the SPR encode at all?), worst would be a serious problem within core. btw: I have SPR
myself and used a (longer) sequence of it for my qpel encoding tests: I hadWell, this problem of "annoying degrading quality after iframe" should be solved with the new "scene based" curve compression which foxer was so kind to implement. Now the quality should be stable if no consecutive keyframes occur (which is a generally hard to handle thing, I think the treatment we inserted there helps it a lot, at least it does when I head for 1CD with "action" movies).
no blockyness problems (but I had a problem where you can see a "quality
jump" whenever a keyframe is decoded - that's something doom9 mentioned
already in his last comparison and I didn't believed it at first, but I have
to admit it's really annoying) - So there's lots of work to do now...
Best regards, Dirk
| [Prev in Thread] | Current Thread | [Next in Thread] |