Unstable build vs, stable build

[xospecialk]

are there any risks to encoding with an unstable build versus a stable one? or the latest binary?

i had encoded with an unstable build once, and when i updated the codec, it was no longer viewable...or maybe those issues are unrelated? the builds only affect encoding rite? decode is a totally different story?

[iago]

Use ffdshow to decode, and all your problems are gone! ;)

[Teegedeck]

Iago! I'm ever so happy to see your face (well, avatar) here again, my friend! :) :) :)

(Not having been around much, myself.)

[symonjfox]

Originally posted by xospecialk
are there any risks to encoding with an unstable build versus a stable one? or the latest binary?
Use lastest builds. These are stable, but they won't be named "Stable" until some few options will be added.

To be out of risk, just use VHQ, B Frames (not more than 4), Chroma Motion, Lumimasking and stop. Other options may be unstable or giving you troubles.

[iago]

Originally posted by Teegedeck
Iago! I'm ever so happy to see your face (well, avatar) here again, my friend! :) :) :)

(Not having been around much, myself.) Hehe, heya Teegedeck, and thanks for the compliment regarding my cool image! ;)
If only I had more time, as in the past, to spend for our great forum, and especially for XviD matters...

Btw -referring to what symonjfox has said and though mostly agreeing with him- to be even more out of risk and on the safer side, you might avoid using Lumimasking as well.

Don't use luma masking. ATM it doesn't give any positive results.(Koepi);)

best regards,
iago

[Koepi]

Thanks iago for jumping in there... I was too "lazy" (like in "oh no, the 100st time...") to answer there ;)

And yeah - your presence is always very much appreciated :)

Serefe dostum *hicks*
Koepi

[Didée]

Iago, I am very sorry to correct you:Use ffdshow to decode, and all your problems are gone! ;) Alas, this is not 100% correct. Libavcodec still has problems with quantization tables containing coeffs < 16 (or maybe < 12). If you use such "high bitrate" matrices, still ffdshow shows occasional dequantization errors: big blocks. After all, the speed advantage ffdshow offers on decoding must come from somewhere... ;)
By now, I prefer to let the core DLL decode the streams ("use XviD" checked in ffdshow).

And, Iago, about your current 'enemy':

Don't take time too earnest.

Linearity of time is (one of) the biggest existing misassumptions.


Regards

Didée

[iago]

Didée,

Don't be sorry! ;) Thanks for the correction, I've always highly appreciated your comments and recommendations. From this day forth I'll keep it in mind.

Still, I have not experienced any such problems with ffdshow so far, possibly because I don't often use high-bitrate matrices and usually stick to h263 or hvs-good-picture matrix (for 1CD encodes, which I mostly do).

Therefore, except some rare cases, I still think that ffdshow is the most reliable decoder for compatibility purposes.

best regards,
iago

[xospecialk]

the only reason im asking is even with ffdshow, im having problems playing a movie i encoded using an earlier build...but i'll take your advice iago and not check off those things..thanks!