Solving The XVD Puzzle

I downloaded a multimedia file a long time ago (at least, I strongly suspected it was a multimedia file which is why I downloaded it). It went by the name of ‘lamborghini_850kbps.vg2’. I have had it in my collection for at least 7 years. I couldn’t remember where I found it. I downloaded it before it occurred to me to take notes about this sort of stuff.

I found myself staring at the file again today and Googled the filename. This led me to a few Japanese sites which also contained working URLs for a few more .vg2 samples. Some other clues led me to a Russian language forum where someone had linked to a site that had Win32 codec modules that could process the files. The site was defunct but the Internet Archive Wayback Machine kept a copy for me, as well as copies of several more .vg2 samples from a defunct Japanese site previously involved with this codec.

Sometimes this internet technology works really well. But I digress.

Anyway, through all this, I finally found a clue: XVD. and wouldn’t you know, there is already a basic page on the MultimediaWiki describing the technology. In fact, while VG2 is a custom container, the MultimediaWiki states that the video component has a FourCC of VGMV, and there is already a file named VGMV.avi in the root V-codecs/ samples directory, something I vow to correct (that’s a big pet peeve of mine– putting samples in the root V-codecs/ or A-codecs/ directories).

XVD… XVD… XVD… why does that sound so familiar? Oh, of course; there is a company named XVD and they have an office in the Bay Area which I have passed on numerous occasions, like this morning:


Someone originally connected with the multimedia technology in question operates a website which contains an unofficial history of the XVD tech. At first, I was wondering if the technology was completely defunct (and should therefore be open sourced). But if XVD’s solutions page (dated 2010) is to be believed, the technology is still in service, and purported to be better than H.264 and VC-1: “The current generation of XVD video compression technology provides better video quality at any given data rate than standards-based codecs (H.264 or VC-1) with four times lower encoding complexity (when compared with H.264 Main Profile).”

If they say so. For my part, I’m just happy that I have finally figured out what this lamborghini_850kbps.vg2 is so that I can properly catalog it on the samples site, which I have now done, along with other samples and various codecs modules.

This episode reminds me that there’s a branch office of Zygo Corporation close to my home (though the headquarters are far, far away). The companies you see in Silicon Valley. Anyway, long-time open source multimedia hackers will no doubt recognize Zygo from the ZyGo FourCC & video codec transported in QuickTime files that was almost decode-able using an H.263 decoder.

I may never learn what Zygo’s core competency actually is, but I will always remember their multimedia tech every time I run past their office.

7 thoughts on “Solving The XVD Puzzle

  1. Multimedia Mike Post author

    @compn: I honestly searched the archive, but didn’t think to look in that location. I’m glad someone was already on top of this, but I really wish it was mentioned on the wiki. These resources need to operate in unison. :-)

    I’ll try to get the rsync’ing settled. Fortunately, s.ffmpeg has not synced my recent changes yet.

  2. compn

    can you also put a mirror of the java decoder in there? before that dissapears off the internet. :)

  3. Peter

    Hey Mike, any of these files useful? I looked into the format way back around 2004, concluded that it was total junk, trading on the XviD name. IIRC, the encoder user interface was all in Japanese.

    d17f424fe0a2932c227ae720044d666e XVDEncoder.exe
    cbf23d394f0d2f77f038931ef7369aab XVDencoderplusTrial102EN.exe
    0ca362ac2cff5c7d7a2f4449373fdd7e XVDPlayer120EN.exe
    97bd9ed2ba364900c7d197e8c7410cde XVDPlayer.exe

  4. Multimedia Mike Post author

    @Peter: Sure, we may as well archive them for posterity. Someone, someday, will certainly need them.

  5. compn

    codecs are dissapearing from the internet. if there werent sites that archived old drivers for old hardware, and, they’d be gone.

Comments are closed.