New 4cc code?

[sonofsantino]

I have tried the new developmental Koepi codec with B-frame support and noted dramatic improvement in the quality at bit rates comparable to what I can achieve with Divx. But the B-frame support causes incompatibilities with previous versions of the codec which do not support B-frames. My suggestion to the community -- once the new builds are stabilized, why not have a new FourCC code such as "xvd2" or "xvdb" to differentiate videos encoded with the new builds? Comments please

[bond]

Originally posted by sonofsantino
But the B-frame support causes incompatibilities with previous versions of the codec which do not support B-frames.i dont have such problems, for example koepis latest stable build is decoded fine by newest development build...

[Teegedeck]

Sorry to dampen your enthusiasm, sonofsantino, but such decisions are not ours to make. And apart from that, changing fourccs is a) unneccessary because we have full backward-compatibility (unlike DivX) and b) we want to keep it that way. Changing it would cause a lot of confusion and prevent older XviD-builds from playing encodes produced with later builds without a reason (the xvid fourcc has been used for encodes with and without B-frames), and that's something nobody could want. It would mean absolute chaos. Sorry but this is nonsense IMHO. As soon as XviD 1.0 is out, it will replace the 'stable' installs on people's machines, thus any B-frame playback problems (if there ever was one) will disappear.

[sonofsantino]

older builds cannot play back files encoded with the newer builds that's the whole point

[sonofsantino]

a problem i've been having is that the newest build can ONLY play back properly with Windows media player, not the others (partial compatibility with Winamp 2.91 and the Divx player -- but if the file is make into ogg vorbis media ONLT Windows media player decodes it properly

[Teegedeck]

Originally posted by sonofsantino
older builds cannot play back files encoded with the newer builds that's the whole point
Joe Average won't find it less confusing if Windows tells him that the XviD codec is not installed although he has installed XviD when he tries to play back an XviD file... Do you get my point?

Originally posted by sonofsantino
a problem i've been having is that the newest build can ONLY play back properly with Windows media player, not the others (partial compatibility with Winamp 2.91 and the Divx player -- but if the file is make into ogg vorbis media ONLT Windows media player decodes it properly
This only indicates that you had a problem with an xvid-ogg-winamp(?!?!)/DivX-Player(Junk) combination, not XviD. Don't generalize this because other people don't seem to have a problem with newer builds. I'd suggest you keep a fresh build of XviD (or use ffdshow instead) and use a reasonable player like bsplayer or media player classic. Maybe your problem will be just gone like magic. This certainly doesn't justify messing with XviD's fourcc naming conventions.

[mf]

Oh, the stupidity.

[Teegedeck]

temper, temper!

Edit: Is this profanity you're using against our poor mislead friend? :sly:

[CruNcher]

@sonofsantino

from what i can read your knowledge about what you are talking is very limited and to be so arrogant and open a poll about a thing you know nothing about is impudent so please stop it and think again about what you written here that has absolutely nothing to do with the video part.


Teegedeck: could u please lock this and stop this idiotic poll

[Nic]

The XviD FourCC will stay the same and forever. DivX 5.05 video doesn't appear to always decode right with DivX 5.02, but they've not changed they're FourCC and neither will we. People will just have to update to the latest versions. More FourCC's would just confuse matters.

End of Poll.

-Nic