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.
All we need now is for .flv to dry up and blow away...
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.
Sure, it's an annoyance, but when you are the premiere open-source solution for something as like video encoding, I think there is (or at least should be) a duty to at least keep the older releases around. Especially if they are a dropping features that were supported in the older versions. If the developers arrangement is so cluttered that they can't be bothered to keep the old releases available, then that points to ineptitude and makes for poor relations with the user-base. File management is not that hard compared to the groundbreaking features these developers are implementing. If they can't be reasonable and/or nice about things, perhaps someone else will step up to the plate and fork the project, because that's probably what it would take to get things into a sane state of being.
Annoying the users just opens the window for someone else to step in.
Censorship is obscene. Patriotism is bigotry. Faith is a vice. Slashdot 2.0 sucks.
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).