HandBrake Abandons DivX As an Output Format
An anonymous reader writes "DivX was the first digital video format to really win mainstream acceptance, doing for movies what MP3 did for music (both good and bad). Eventually even Sony, the king of proprietary formats, caved into pressure and added DivX support to its DVD players and the PlayStation 3. Now HandBrake's developers have made an interesting choice for version 0.9.4 — they ditched support for AVI files using DivX and XviD. Your only option now is to convert DVDs and other media to MKV or MP4 files, with the option to save as Apple-friendly M4V files. So why is HandBrake ditching AVI and XviD support when it's a format that's won such widespread acceptance? In the words of the developers, 'AVI is a rough beast. It is obsolete.'"
Dropping all formats that Windows play by default is IMO a bad decision. It may make the CCCP Project more popular and spur more people to install Quicktime (yuck), but it'll also drive away lots of inexperienced users.
Streaming to my legacy device which cannot be easily reprogrammed such as my Xbox 360 really relies on XVid. So, for now, I guess Handbrake is the rough beast. Oh well, I use dvd::rip anyway and avidemux when I need to do some transcoding. Computers can be easily upgraded, devices not so much: that is something to keep in mind too.
Shh.
The [Handbrake DivX] code has not been actively maintained since 2005. Keeping it in the library while implementing new features means a very convoluted data pipeline, full of conditionals that make the code more difficult to read and maintain, and make output harder to predict. As such, it is now gone. It is not coming back, and good riddance."
They go on to explain that DivX quality isn't as good either. I am not sure if that is true or not, but I think the major reason they are dropping it is because they didn't want to be bothered. Which is as valid a reason as any, I suppose.
Qxe4
All we need now is for .flv to dry up and blow away...
I was surprised when this happened, but I can appreciate that, ultimately, it's a legacy format. Apparently, the AVI implementation is very convoluted to keep up with new features. Here's a selected quote from their release blog: "It does not support modern container features like chapters, muxed-in subtitles, variable framerate video, or out of order frame display....The code has not been actively maintained since 2005. Keeping it in the library while implementing new features means a very convoluted data pipeline, full of conditionals that make the code more difficult to read and maintain, and make output harder to predict. As such, it is now gone. It is not coming back, and good riddance." (sadly there didnt seem to be a permalink to the whole article - here's the current news page).
As such, I've moved on and figured out which flavor of mpeg-4 works best for me; and I'm happier with the improved picture quality as a result.
While technically true, that's functionally meaningless. If your program supports limited codecs that work with a particular container (for example... AVI) ditching one is the same as ditching the other.
For all intents and purposes DIVX is AVI as far as popular support goes. I'm not sure I can name another codec that I've seen used in the last few years as more than a intermediate step.
Because H.264/MPEG-4 AVC is Mature! We have availability of fast and reliable open source x264 H.264 / MPEG-4 AVC encoder and the wide spread usage of Matroska (MKV) container files and MPEG 4 (MP4) container files. Even some set-top boxes support playback of video and audio from both containers now and more are announced for this year. There is also a demand now for HD content in both 720p an and 1080i/p formats H.264 is required to give reasonable file sizes versus XviD/DivX (MPEG-4 ASP).
Also Audio Video Interleave (AVI) container files are problematic and have limitations since they don't allow the inclusion of chapters or subtitles, are not compatible with newer audio encoding formats such as AAC and lossless Dolby Digital or DTS audio formats, and don't work really well with some of the newer video formats.
It is time to move on from this old container format and also move away from older DivX and XviD (MPEG-4 ASP) formats onto the newer H.264 / MPEG-4 (x264) video encoding formats.
It's hardly a de-facto standard; it's just another utility using ffmpeg and x264.
It's not implying anything of the sort. It's making the point that DivX was so popular, even Sony (who loves creating proprietary, Sony-only formats) added support for it to the PS3.
First of all the original handbrake.fr article says nothing specifically about DivX. It talks about XviD and OGM. I guess OGM wasn't "controversial" enough for the editors so they ignored that and focused on DivX.
But the real issue is: Big deal, DivX themselves are moving to H.264/mkv with all deliberate speed. Even they realize there's no point in anyone holding on to codecs and containers which are inferior in every respect. So, since mkv is a legitimate container in DivX7, the writeup is in fact erroneous. Surprise.
There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
You could just use "greasemonky" plugin in Firefox and install the "YouTube Without Flash" script and videos will play using your default media player...
Laters Sol "Have you found the secrets of the universe? Asked Zebade "I'm sure I left them here somewhere"
I just renamed all my AVI files to MKV. It's, like, the same thing, right?
When you're afraid to download music illegally in your own home, then the terrorists have won!
This is not informative.
XviD is an MPEG-4 Part 2 implementation; it is one of many.
x264 is not a standard at all; it is an encoder for the H.264/MPEG-4 Part 10 standard, which is just as open as MPEG-4 Part 2.
This is a necessity; H.264 is suitable for encoding low-bitrate, low-resolution video or high-bitrate, high-resolution video. It is useful for 20 mbit/sec high definition streams, or 256 kbit/sec videoconferencing.
The standard defines various levels that various hardware decoders implement.
Possibly because they were out-of-spec, or not in a container the player supports. x264 isn't responsible for the user's ignorance.
AV-sync is still an issue for modern containers, like MKV, it's just that most GUI front ends automatically handle the parameters when encoding for you - command line pilots still need a calculator.
The biggest drawbacks of the dinosaur AVI container format include: it doesn't support chapters (ah, the hacks in Encarta to work around that); it doesn't support included subtitle streams; it doesn't support alternative video tracks; it doesn't support alternative audio tracks. Heck, in it's 1.0 version it didn't even support multi-gigabyte files. I'm all for covering it with another shovel-full of dirt.
If killing-off support for the AVI container means a few casualties like DivX/XviD codecs (and it doesn't, except for embedded solutions that don't have firmware upgrade paths) there'll be no tears here - there have been much better quality and higher efficiency codecs to replace them for a number of years.
The key benefit of divx is that it doesn't take bloody supercomputer in order to decode HD content in software.
You can get a nice amount of compression when compared to MPEG2 without requiring a beefy CPU or dedicated GPU hardware to handle it.
It's clearly inferior in terms of quality. That might be relevant to your particular requirements, or not.
It's nice to be able to choose for yourself rather than some Mac mindset weenies removing the option.
A Pirate and a Puritan look the same on a balance sheet.
The DivX people now also support DivX Plus, which is H.264/AAC/MKV including surround sound, multilingual subtitles, chapter points, metadata, multiple titles, and more :)
Check it out:
http://www.divx.com/en/electronics/solutions/high-definition/divx-plus-hd-showcase
DivX Plus devices were also announced at CES. Look for Blu-Ray players from Philips and the FreeAgent Theater+ HD Media Player from Seagate initially. There's even a Handbrake preset here.
- Al / DivX person ;)
That doesn't change the fact that a device with divx support will play nearly every divx/xvid file, and h264/x264 players are SOL with the majority of the encodes I've seen so far. Many only work properly on a computer, and not on mobile devices or dedicated gear (even though changing two encoding options while leaving the bitrate/filesize the same makes the file play...).
If it weren't for the fact that Android doesn't seem to have implemented a divx/xvid codec at all, I'd probably still be using it (and be watching my TV rips without needing to transcode first).
If your running Windows you might try a program called Format Factory its free and it is amazing in that it can convert almost any format with very little loss in quality.
FYI, Format Factory 2.2 (the newest version, released in December) appears to have the Generic.dx!kdh trojan, according to McAfee. This is a recently reported trojan, and is only discovered with DAT files less than 12 days old. I downloaded Format Factory 2.2 from 3 different sites and while the zip file names were slightly different, all three were reported as having an exe file infected with Generic.dx!kdh.
http://vil.nai.com/vil/content/v_252791.htm
There is not much information on this trojan right now, but it appears to be a member of a family which disable protective software and install IRC back doors for DDOS attacks or for later installation of other malware.
http://vil.nai.com/vil/content/v_141693.htm
Maybe it's a false positive. And maybe the developer's machine is spreading something unpleasant.
Those who can make you believe absurdities can make you commit atrocities. - Voltaire
Another comment which resulted from discovering a trojan signature in Format Factory. It may be "free as in beer", but it's yet another example of a Chinese company appropriating "free as in freedom" software, and claiming ownership of it. The Format Factory installer contains mplayer, mencoder and avcodec compiled with support for libamr, libfaac, xvid and x264. However, contrary to the licensing conditions for all of these, there are no sources provided or made available, and Format Factory claims copyright on everything (does not even acknowledge the FOSS items it includes).
Those who can make you believe absurdities can make you commit atrocities. - Voltaire
ROFL.
Maybe the de-facto standard on OSX, but this is the first time I even heard there is a Windows version of Handbrake. People are using ffmpeg and other programs that use the X264 library. Yeah, Handbrake is one of those programs that uses it, but Handbrake is not the front end folks are using on Windows.