Hanty
6th March 2002, 23:57
Ok, I've gone through Koepi's XviD options explained, the XviD Q&A, had the opportunity to talk to Doom9 and Koepi at irc directly about XviD.
...and I still need to know more more more. ;)
Honestly, my tryouts of XviD so far has ended up in shitty looking encodes (only clips), I keep hearing people saying the get good stuff though with it. So somewhere it must be me doing something wrong. (I don't consider my own experiences to be empirical evidence that something rocks/sucks)
1. Quantization tuning
Can this be compared to the DRF levels in nandub? to me it sounds as if they appear to be similar if not in content then in usage. So far I've left the defaults on this (min 2 / max 31). What would be a "typical" range? for a 1 CD rip and a 2 CD rip respectively?
2. Debug / 2-pass
This is also a something I can't help to compare as possible DRF levels (I'm nandub damaged, agreed) I've had no reference point and played around with these treating them like DRF levels and held min 2 /max 9 for my clips.
Wishlist
(some of these suggestions are completely wild and I have no idea if they work in practise)
*Mentioned before, and adding my vote to the fray, something like
the anti-shit MinQ which recompresses the frame at a lower
compression level (I assume a drop in quantizizer would be
appropriate for Xvid) if the XX value is above the compared value
for the frame.
*A stats reader similar to Koepi's for Nandub ( I don't like
GKnots :b )
*Making a setting that detects even-colored fields. If a field is
largely even colored then the codec should compare it to earlier
frames to determine if it is a "stable" non-motion field and thus
supress shading changes. (The thought behind this is to steem walls
and background appearing "alive", something troublesome when encoding
animations which has lots of these fields)
*A XviD post-processing options Explained.
*XDub!!!! :D
Many thanks to the Xvid team for giving up large parts of your freetime in order to get this stuff for us. I sincerely hope that we are seeing the birth of something pace-setting here and I would have been proud to have been there from its conception...now get back to coding you and don't come back until we have the next build, I want to see you sweat blood and cry by the compiler! ;b
...and I still need to know more more more. ;)
Honestly, my tryouts of XviD so far has ended up in shitty looking encodes (only clips), I keep hearing people saying the get good stuff though with it. So somewhere it must be me doing something wrong. (I don't consider my own experiences to be empirical evidence that something rocks/sucks)
1. Quantization tuning
Can this be compared to the DRF levels in nandub? to me it sounds as if they appear to be similar if not in content then in usage. So far I've left the defaults on this (min 2 / max 31). What would be a "typical" range? for a 1 CD rip and a 2 CD rip respectively?
2. Debug / 2-pass
This is also a something I can't help to compare as possible DRF levels (I'm nandub damaged, agreed) I've had no reference point and played around with these treating them like DRF levels and held min 2 /max 9 for my clips.
Wishlist
(some of these suggestions are completely wild and I have no idea if they work in practise)
*Mentioned before, and adding my vote to the fray, something like
the anti-shit MinQ which recompresses the frame at a lower
compression level (I assume a drop in quantizizer would be
appropriate for Xvid) if the XX value is above the compared value
for the frame.
*A stats reader similar to Koepi's for Nandub ( I don't like
GKnots :b )
*Making a setting that detects even-colored fields. If a field is
largely even colored then the codec should compare it to earlier
frames to determine if it is a "stable" non-motion field and thus
supress shading changes. (The thought behind this is to steem walls
and background appearing "alive", something troublesome when encoding
animations which has lots of these fields)
*A XviD post-processing options Explained.
*XDub!!!! :D
Many thanks to the Xvid team for giving up large parts of your freetime in order to get this stuff for us. I sincerely hope that we are seeing the birth of something pace-setting here and I would have been proud to have been there from its conception...now get back to coding you and don't come back until we have the next build, I want to see you sweat blood and cry by the compiler! ;b