PDA

View Full Version : Which codec you guys prefer Divx 5.0 or Xvid?



wargray
Mon, 05-10-2004, 11:15 AM
Which codec you guys prefer Divx 5.0 or Xvid?

I hope ANBU & AonE can stay on with Divx codec...

I don't know why this thread was in the Naruto section last year, but it doesn't belong there.

GotWoot Moderator

Assertn
Mon, 05-10-2004, 11:22 AM
i believe Xvid is the open source equivalent....which makes alot of encoders prefer it for legality reasons (i could be totally wrong, but i believe thats what i heard)

complich8
Mon, 05-10-2004, 01:54 PM
I talk about this in some detail in this thread: http://forums.gotwoot.net/messageview.cfm?catid=4&threadid=9984&STARTPAGE=1& enterthread=y

Long story short: we've never used divx5. You just think we have, because we normally do things in divx5 compatibility mode. And this new encoder we were testing decided to use all sorts of crap that's not dx50 compatible, and we didn't notice because our computers are for the most part properly set up to actually play video.

As far as "legality reasons" -- well, it's not illegal to use divx5. xvid is just better. Always has been (well, almost always).

Neji-Aniki-sama
Mon, 05-10-2004, 02:57 PM
I got this editing soft that no way will work with Xvid. No matter if the guy who made it says otherwise.
Why? I have no idea.
BTW, if anyone has chapter 34 in divX5 please let me know where I can get it. Or at least how can I encode that chapter in divX...

complich8
Tue, 05-11-2004, 03:24 PM
neji: you can always reencode it yourself. Just load in virtualdub, configure the codec you want, and do a fast recompress to whatever it is you want to work with.

chapter 34? Are you talking about episode 34? or something else? In any case, if it's an avi file, virtualdub (or virtualdubmod) will be able to turn it into pretty much whatever you want, assuming you have the codecs installed.

Noir
Wed, 05-12-2004, 12:17 PM
Originally posted by: AssertnFailure
i believe Xvid is the open source equivalent....which makes alot of encoders prefer it for legality reasons (i could be totally wrong, but i believe thats what i heard)

Nice to see some-one post a correct answer so fast. But yeah that's basically it: Xvid>DivX

I had some massive codec problems had way too many they were eating each other and I couldn't fix anything. So I uninstalled all my codecs, got the Windows Media 9 pack, and the latest XVid. Everything works fine.

supernoober
Thu, 06-16-2005, 09:19 PM
Hi,
Can you tell me how to uninstall and install codecs ? Also, DatteBayo naruto 137 and 138 don't work on my divx. Should I get xvid ?

Mut
Fri, 06-17-2005, 01:44 AM
You should try asking at a place where they are associated with... I don't know... DB???

Y
Fri, 06-17-2005, 02:16 AM
Originally posted by: complich8
I talk about this in some detail in this thread: http://forums.gotwoot.net/mess...GE=1&enterthread=y (http://forums.gotwoot.net/messageview.cfm?catid=4&threadid=9984&STARTPAGE=1& enterthread=y)

Long story short: we've never used divx5. You just think we have, because we normally do things in divx5 compatibility mode. And this new encoder we were testing decided to use all sorts of crap that's not dx50 compatible, and we didn't notice because our computers are for the most part properly set up to actually play video.



Huh, why would GSpot report it as Divx 5 and Open DivX?

Also nice hellbump.

complich8
Fri, 06-17-2005, 02:28 PM
yeah, that's like .... a full year bump, and some change. yikes.

GSpot trusts the fourcc, and reports a video as whatever those are. They're encoder-settable and easy to change.

Way back then (pre-1.0 xvid) the xvid decoder was craptastic. So, the choice was use a craptastic decode filter for a nice and versatile codec, or use divx 5's decoder instead.

around 1.0, xvid's native decoder matured quite nicely, and everyone who was paying attention stopped encoding with pre-1.0 xvid. most of them stopped changing the fourcc bits, too, so that it'd correctly identify.

Mose encoders didn't use the "DIVX" (opendivx) fourcc, which left it open to be decoded by even more inferior opendivx filters, and instead tried to force divx5 playback with "DX50" (divx5). Which is why people thought it was divx5, and why why it doesn't identify as opendivx or xvid.