Virtualdub Dts Codec For Divx
Cherrie Patete
I want .avi or .wmv output in order to be able to use them later in movie maker, so i excluded DivX pro although it gives good results. MP4 files with H.264 codec gives also good results when using eRightSoft Super.
I think you shouldn't have a problem opening VP7 encoded videos, but I'm not familiar with Movie Maker.
These codecs are better used for the final edited movie.
Is better that you edit you movies in their original m-jpg format.
These entries appear in the standard Windows codec dialog in the same order that they are listed in SYSTEM.INI, so if you're irritated at seeing Cinepak by default just switch the order of the lines.
First, keep in mind that this error message only applies to version 3 of the DivX codecs. Version 4 is completely different (see below). Microsoft has been improving their MPEG-4 codecs for some time; build 2700 introduced Microsoft MPEG-4, and when Windows Media Tools 4.0 beta appeared, version 4.00.0.3688 introduced the vastly improved V2 and V3 formats. Unfortunately, by the time 4.0 final came out, Microsoft locked the driver in the final 4.00.0.3845 build so that it would only work with Windows Media Encoder. DivX 3 is actually a copy of this driver with the lock hacked out, and the format tags changed to be distinct from the original. The most popular version of DivX, 3.11a, is a pair of drivers that derive from Microsoft's 4.1.00.3917 and 4.1.00.3920 builds. The "unhacked" version of DivX 3 is the Microsoft driver.
The problem with the Microsoft driver is that none of the final builds that are still being distributed (build 3920 is the latest of this writing) are unlocked for general use. The DirectShow decoder has been basically unlocked, but it won't encode. It's a shame that Microsoft won't unlock the codec, especially now that it's rather old, but since unfixed bugs remain in the driver it is probably best that people move on to other codecs.
DivX 4.0 isn't really related to 3.11a. It's a new codec that has been ramped up partly from scratch and partly from the MuMoSys reference code. Another major difference is that while DivX 3.11a worked with Microsoft's version of MPEG-4, this codec is supposedly based on a basic profile of real, true, ISO MPEG-4, and its streams should be decodable with other ISO MPEG-4 libraries. (I have not yet heard of anyone verifying this, however.) Up until recently DivX 3 and 4 were totally distinct and could not encode or decode each other's formats; DivX 4.0 now has the ability to decode MPEG-4 V3 (DivX3) streams, although with occasional glitches. Originally, the DivX 4.0 codec started as OpenDivX, with publicly available source code. (It wasn't open source, at least in the sense of the Open Source Definition, due to problems with its license.) However, DivXNetworks stopped releasing source code and thus the DivX 4.0 codec is closed-source like most other codecs. This is why VirtualDub identifies DivX 4.0 files as OpenDivX.
Remember that the people who hacked DivX 3 out of MS MPEG-4 V3 didn't have the source code -- Microsoft wrote the codec. The same work shouldn't be expected out of the DivX 4 team since they're different people, although it looks like they have a decent chance at surpassing the MPEG-4 V3 codec in quality.
Like DivX 3.11a, DivX Audio is really a hack of the Microsoft Windows Media Audio codec (V1 or V2, depending on version). Unlike the video codec, however, DivX Audio still uses the same tag as the original codec, so if you have both the original Microsoft codec and the DivX audio codec installed, VirtualDub cannot tell the difference between the formats of the two codecs. The result is that when VirtualDub does an inverse lookup of the format to find its name, it will stop at whichever one it finds first.
DivX audio is unfortunately a very buggy hack, and has a tendency to die when you try to compress with it, depending on the exact format you choose. Because of this instability and the conflict mentioned above, I recommend avoiding this codec even if legality is not a concern for you. As with DivX video, you cannot switch to the original Windows Media Audio codecs because they too are locked against general use.
AngelPotion Definitive isn't a new codec either -- it's yet another version of the Microsoft MPEG-4 V3 codec that someone modified to look original. While this in itself makes AngelPotion an illegitimate codec, it's not the reason it should be avoided.
The AngelPotion codec consists of two parts, the .APL file that stores a packed version of the Microsoft codec, and the DLL that acts as an intermediary between the Microsoft codec and the application. It turns out that this DLL has a major flaw in that, during certain calls, it modifies video formats passing through it to MP43 (MS MPEG-4 V3). As a result, all codecs after AngelPotion during codec negotation see that format. The effects of this can range from Windows Media Player's automatic codec download breaking, to some programs, notably Avisynth 0.3 and earlier, not decoding AVI files properly. Since video formats flow through some or all installed codecs when format negotation occurs, this means that AngelPotion can break any video format in an application.
Because AngelPotion isn't actually a new codec, its format can be decoded with any other version of Microsoft MPEG-4 V3, simply by changing the two instances of AP41 in the AVI header to the FOURCC of another MPEG-4 V3 codec. VirtualDub automatically attempts this during load as part of its codec equivalence mapping when a required codec is not found. You may find that AngelPotion files load as Microsoft MPEG-4 V3 if you do not have AngelPotion installed.
These are typically decompression codecs for formats that are generated during video capture. The codecs don't do encoding because the actual encoding is done during video capture on the capture chip, and so it never needs to be done by the CPU. Some other codecs tend to be installed by applications for playing back pregenerated video, and since they're not licensed for general use, they refuse to encode or even work at all outside of the application that installed them. For instance, Eidos' PC port of Final Fantasy VII installs a decode-only version of the Duck TrueMotion codec.
A Video for Windows codec on the Windows platform is pretty simple: shove one raw frame in, get one compressed frame out. Great fun for the whole family and works in reverse as well. This means that audio and video codecs are separate, and in addition, the frame order must be progressive in the compressed stream. Unfortunately, MPEG-1 uses a completely different file layout than AVI, and in addition, reorders I and P-frames relative to B-frames in display order. The different file order makes it impossible to retrofit MPEG-1 support onto applications with codecs alone, and the frame order issue means you can't truly fit MPEG-1 video into AVI.
All that is stored in an AVI with regard to video format is a four-character code (FOURCC) that identifies the format. The long name you see in most programs comes from the installed codec that is chosen to decompress the video. If you have a Motion-JPEG file, for example, it might show up as miroVIDEO MJPG[16], Pegasus PICVideo MJPEG, MainConcept MJPEG, etc. depending on which codec is installed for the MJPG format at the time.
With the current setup I can only open raw I420 videos converted with memcoder, but I can't open DivX/XVID videos, that I used to on my old PC. I tried ffdshow and K-Lite codec pack. Opening the videos in gspot shows that the codecs are indeed installed.
I installed VirtualDub recently (32bit) on 64bit Windows 10 machine. I decided to use 32bit version in term of using DeLogo filter, which is 32bit. I have already installed VLC Media Player in order to be able to play various video formats and I've already installed FFDShow codecs with VFW built-in tech. Settings for XviD and DivX are to use libavcodec and these codecs are also 32bit installation (well, should be, they're installed in Program Files (x86) folder). But VirtualDub can't seem to find these codecs and when I try to import a video, it says it couldn't locate XviD decoder. Everything important is installed, what could I miss?
Libav contains an Mpeg-4 codec, but not the Xvid or Divx codec specifically. I'd suggest installing the actual Xvid codec for encoding/decoding the Divx/Xvid format. Once installed, vdub should find it just fine.
DivX is a brand of video codec products developed by DivX, LLC. There are three DivX codecs: the original MPEG-4 Part 2 DivX codec, the H.264/MPEG-4 AVC DivX Plus HD codec and the High Efficiency Video Coding DivX HEVC Ultra HD codec. The most recent version of the codec itself is version 6.9.2, which is several years old. New version numbers on the packages now reflect updates to the media player, converter, etc.
The "DivX" brand is distinct from "DIVX", which is an obsolete video rental system.[1] The winking emoticon in the early "DivX ;-)" codec name was a tongue-in-cheek reference to the DIVX system. Although not created by them, the DivX company adopted the name of the popular DivX ;-) codec. The company dropped the smiley and released DivX 4.0, which was actually the first DivX version to trademark the term DivX.[2][3]
DivX ;-) (not DivX) 3.11 Alpha and later 3.xx versions refers to a hacked version of the Microsoft MPEG-4 Version 3 video codec (not to be confused with MPEG-4 Part 3) from Windows Media Tools 4 codecs.[4][5] The video codec, which was actually not MPEG-4 compliant, was extracted around 1998 by French hacker Jerome Rota (also known as Gej) at Montpellier. The Microsoft codec originally required that the compressed output be put in an ASF file. It was altered to allow other containers such as Audio Video Interleave (AVI).[6] Rota hacked the Microsoft codec because newer versions of the Windows Media Player would not play his video portfolio and résumé that were encoded with it. Instead of re-encoding his portfolio, Rota and German hacker Max Morice decided to reverse engineer the codec, which "took about a week".[7]
aa06259810