XviD1.0b issue wrt MPEG-4 decoding, may interest devs.

[b00zed]

I've noticed an issue with XviD1.0b, which may of may not have been mentioned but I can't find it here.

Since giving XviD1.0b a try, WMP seems to want to use XviD to decode DivX files (with both "DIVX" and "DX50" FourCC codes.) This is usually fine, except for some captured files in DivX format that refuse to run unless I view them in MPC, or uninstall XviD1.0b.

The main problem is of course if I try to load the file in Avisynth it fails, and it just plain crashes VDM. Looks like I'm going to have to give my XviD1.0b testing a break for a while :(

Edit: Reporting requirements as per Sticky are on their way :)

[b00zed]

Koepi's 30/11/2003 v1.0b1

DShow filter *should* be the standard DivX5.11 filter, but it isn't, that's the problem :)

Win2k SP4 + all critical updates. Capturing through a GF4 Ti4200 (Philips 7108)

Problem occurs with everything I capture in VDM. Capture settings: Video is DivX 5.11 quality based single pass, with B-frames enabled and an I-frame interval of 2. Audio is "uncompressed" PCM; 44.1kHz 16-bit Stereo. Container format is AVI.

Doesn't work in WMP 6.4 at all. Error: "The file format is invalid. (Error=8004022F)"
Works in MPC 6.4.6.9 Every time.
Works in VDM only after the aforementioned XviD build has been uninstalled. The error is below:

An integer division by zero occurred in module 'xvid'...
...while decompressing video frame 0 with "XviD MPEG-4 Codec" [biCompression=30355844] (VideoSource.cpp:1812).

And I don't need to be told any more that I should have done this in the first place. :)

[Koepi]

Can you verify with the mpc properties when playing such a file that the xvid decoder filter is used to decompress the video?

It might be an issue with conflicting colour space conversion routines from first sight.

Regards
Koepi

[b00zed]

Thankyou for your reply Koepi.

Both WMP and MPC are using (or trying to use, as the case may be) the DivX decoder. Is there a possibility that my capture file might be causing the problem with the current settings?

[tiki4]

Maybe XviD got registered on your system to handle YV12 colour space. I guess it is used to do a YV12 -> RGB conversion for display. Maybe it helps to uninstall XviD and DivX and then install DivX as first codec. This should register DivX to handle YV12. Please correct me someone, if I'm wrong here.

tiki4

[Doom9]

I noted something about the yv12. I installed the 1.0 beta over koepi's latest dev-api3 build, and I ended up having 2 xvid codecs, one registered as xvid, one as yv12. Divx5.11 was installed prior to XviD 1.0 but I'm not sure whether it was prior to the XviD alpha or not.

[Tuning]

Originally posted by Doom9
I noted something about the yv12. I installed the 1.0 beta over koepi's latest dev-api3 build, and I ended up having 2 xvid codecs, one registered as xvid, one as yv12. Divx5.11 was installed prior to XviD 1.0 but I'm not sure whether it was prior to the XviD alpha or not.

This twin codecs were found since early CVS build from october. (Since I started compiling in october). I think this is a feature of new codec. Some older version (I cannot remember exactly -may be DivX 5.01)of Divx too installed like this.

[tiki4]

I have installed DivX 5.1.1 on my system (XP Pro SP1) and DivX shows up two times in VirtualDubMod: One Time with FourCC 'divx' and one time with 'yv12'.

tiki4

[b00zed]

I had DivX registered under YV12 while an earlier XviD build was installed, but it looks like XviD 1.0b1 took over the YV12 FourCC, but since the files I'm playing with are either "DX50" or "DIVX," you wouldn't think it was a problem.

Thanks for your thoughts, I'll keep battling on for the moment. :)

Your suggestion about reinstalling DivX might help tiki4, I'll give it a try. I might install XviD first and then DivX as well to see whether it makes a difference.

[Gazza]

bOOzed,

I'm seeing exactly the same issues with duplicate registrations of xvid. I have also noticed that replay of the video is now very system resource hungry regardless of which player I try (MPC, zoomplayer, etc). Maybe with the exception of bsplayer? Now my CPU is 100% loaded and the video is running at half speed. I think this is to do with decoding in yv12 but am unable to stop it. I have tried un-installing and re-installing Koepi's XviD-24062003-1.exe and xvid 1.0 beta but cannot see any improvements. I have tried various re-configurations of fddshow (with and without xvid, etc) but have not been able to hit the winning combination. I haven't tried un-installing Divx 5.1 yet. Maybe that's my next thing to try.


Cheers

Gazza

[b00zed]

I didn't have any of this trouble with Koepi's 24/06/2003 build.

Even removing both XviD and DivX, rebooting, installing XviD, rebooting, then installing DivX and rebooting hasn't helped. :D

[el divx]

Guys, I think I found the solution. Just open the Registry Editor and then go to this one: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 and there should be a list with all the codecs installed on your system. Search for something like "vidc.yv12" that has "xvid.dll" as its value. Just delete that and you should now see only one xvid codec with "XVID" as its FOURCC in VirtualDub or any other app you use.

[Gazza]

Further to my message above and for your information, I suspect that using the standard profile "DSPguru_Ogg_Vorbis_6ch" within besweet to generate the ogg sound track is behind the slow playback issues and high cpu loading. It looks as if a combination of the 6 channel vorbis soundtrack and installing xvid 1.0 beta maxes out my cpu (Pentium 3, 1 mhz, 512 mb) during playback.


Cheers

Gary

[b00zed]

A number of things to report:

To el divx: Thankyou for the suggestion. I had a fiddle around in the registry earlier but didn't get anywhere since I wasn't too sure what I was looking for. Renaming the VIDC.YV12 key value to "DivX.dll" fixed VDM's problem. I think I'll leave it there for as long as I capture in DivX.

Removing the first frame of my captured file makes it readable in WMP, as this frame appears completely pink in VDM and may be corrupted. The repaired file also works in VDM with xvid set to the YV12 decoder. XviD apparently doesn't like broken frames, which is understandable from a testing point of view. It also suggests my capture settings need to be looked at to fix that broken first frame...

I'm sorry if this caused an undue waste of your time Koepi. Thanks to everyone for your suggestions and help.