Current Build of XVid Long Term Compatable?

[Teleri]

I remember reading that the newer versions were to include B-Frames. I just installed Nimo 5.08 and realized that my old videos no longer work so I will have to re-encode them. Any idea if the changes from here on out will be minor enough so that I wont have to worry about re-encoding what I make?

[-h]

What old videos stopped playing? Apart from the interlacing bug, I don't know of any past builds of XviD that produced content which can't be played by today's builds..

The goal of XviD is to be MPEG-4 compatible, and right now (without B-frames) we should be right there. So, anything you encode now is "MPEG-4 compatible", and can be played by anything else in the future that is "MPEG-4 compatible".

-h

[Koepi]

The NIMO codec pack is evil.

Simple uninstalling it doesn't work.

Reinstall a fresh system (!!!!) and just install the codecs you need (ffdshow, xvid, divx, freeDVD... that's nealy all, it should suffice for a usual system).

Regards,
Koepi

[Teleri]

Bingo,

That was the problem. After installing Nimo 5.08 on Windows XP it killed my Windows Media Player. I couldnt play ANY video files at all. After I Uninstalled it I'm golden though. Unfortunately I talked with two other guys about this, one was able to fix it by uninstalling but the other has a perma messed up Windows Media Player 7.1.

Xvid is a wonderful thing, I just hope that they keep some older drivers available when they add in B-frame support.

[sprit]

Originally posted by -h
The goal of XviD is to be MPEG-4 compatible, and right now (without B-frames) we should be right there. So, anything you encode now is "MPEG-4 compatible", and can be played by anything else in the future that is "MPEG-4 compatible".
[/B]
Is it so? A couple of weeks ago I tried putting a Xvid [1] in a mp4-movie, using mp4creator from MPEG4IP 0.9.5.1, without luck and according to 'DeXT' [2] is was Xvids "fault". If this was incorrect I'd be very happy, but no closer to making a working mp4. :-/

[1] Koepi's 20020818-1 build; 2-pass, lumi on both, tried H.263/MPEG/modulated as both XVID and DIVX
[2] Thread from 'New A/V Formats' (http://forum.doom9.org/showthread.php?s=&threadid=31533)

[-h]

Is it so? A couple of weeks ago I tried putting a Xvid [1] in a mp4-movie, using mp4creator from MPEG4IP 0.9.5.1, without luck and according to 'DeXT' [2] is was Xvids "fault". If this was incorrect I'd be very happy, but no closer to making a working mp4. :-/

If there's something in XviD that's not ISO complaint, we would be very interested in knowing what it is..

-h

[trbarry]

If there's something in XviD that's not ISO complaint, we would be very interested in knowing what it is..

Doesn't using the mpeg quant (and therefore also modulated) still cause problems playing back with Divx? Of course that could be Divx's fault, but I thought I noticed only a couple weeks ago there was still some problem with this.

- Tom

[SirDavidGuy]

Originally posted by trbarry


Doesn't using the mpeg quant (and therefore also modulated) still cause problems playing back with Divx? Of course that could be Divx's fault, but I thought I noticed only a couple weeks ago there was still some problem with this.

- Tom

It's included in the spec, so I suppose it's DivX's fault.

[-h]

It's included in the spec, so I suppose it's DivX's fault.

Yeah, I can't even remember what the problem is - either rounding or mismatch control during dequant. Either way, XviD, ffmpeg and MoMuSys work one way, DivX works another.

-h

[sprit]

Originally posted by -h
If there's something in XviD that's not ISO complaint, we would be very interested in knowing what it is..
-h
Oh? I "read" DeXT's answer as there was a known error, known to the mpeg4ip people atleast. I assumed they had notified you (you == Xvid developers)...

[-h]

Oh? I "read" DeXT's answer as there was a known error, known to the mpeg4ip people atleast. I assumed they had notified you (you == Xvid developers)...

Not that I recall on the mailing list. Either way, it will probably work now.

-h

[trbarry]

I remember something about a couple bits in a header talked about on the Xvid forum (is that still somewhere) but that was fixed many months ago.

- Tom

[DeXT]

I think I readed it on an older thread but it's also mentioned here:

http://sourceforge.net/forum/forum.php?thread_id=710793&forum_id=59136

However the latest MPEG4IP release (0.9.5.3) included a "XviD fix" according to CVS release notes. Don't know if this is the bug you talked about.

On (now dead) XviD forums there was a message from gruel I think about enabling B_FRAMES and setting max_bframes to -1 to output a bitstream with better compliance.

However I don't know if the latest builds are finally 100% compliant. But if people are still having troubles with QT6 playing XviD I'm afraid there is still a bug somewhere (either on XviD or QT6, who knows).

Latest builds: http://www.peque.org/dext

[MaTTeR]

You might send Everwicked a PM, I think he also has had some insight for quite awhile about some issues with ISO XviD compliancy. I can't recall the specifcs now unfortunately.

[-h]

Sounds like a low_delay issue, it should be alright now.

-h