Wikimedia Community Debates H.264 Support On Wikipedia Sites.
bigmammoth writes "Wikimedia has been a long time supporter of royalty free formats, but is now considering a shift in their position. From the RfC: 'To support the MP4 standard as a complement to the open formats now used on our sites, it has been proposed that videos be automatically transcoded and stored in both open and MP4 formats on our sites, as soon as they are uploaded or viewed by users. The unencumbered WebM and Ogg versions would remain our primary reference for platforms that support them. But the MP4 versions 'would enable many mobile and desktop users who cannot view these unencumbered video files to watch them in MP4 format.'
This has stirred a heated debate within the Wikimedia community as to whether the mp4 / h.264 format should be supported. Many Wikimedia regulars have weighed in, resulting in currently an even split between adding the H.264 support or not. The request for comment is open to all users of Wikimedia, including the broader community of readers. What do you think about supporting H.264 on Wikimedia sites?"
It's an encyclopedia, not YouTube.
Wikimedia should stand their ground to provide a good reason for device manufacturers to add support for open video formats.
I am becoming gerund, destroyer of verbs.
Reminds me of the whole 'GIF vs PNG' battle in the mid 90's.
Yes they should do this. Sometimes, you can't fight City Hall - you just have to go with the flow so that your website becomes more useful to people. It's annoying that media files on Wikipedia don't "just work" on most devices, not even desktops.
I appreciate their position and somewhat support it, but they've been holding out for so long now with absolutely no effect. The only losers are the site's users. At least Mp4 is a standard, albeit not as free as idealists would like.
Is it also a form of censorship that they don't support everything else on this list?
What if I need my video in Indeo or Bink or RealVideo or WMV? They're denying me the ability to watch them! Ermahgerd!
This is not YouTube we're talking about, where its 100% about immediacy and convenience. People can download a free player--or use a non-Microsoft/Apple browser--when they're good and ready to view the Wikimedia content.
In every meaningful sense, MP4 is the most 'open' useful video CODEC every made available. The world's BEST video encoder, x264, is open-source and free. Every worthwhile tool you need to encode, process and watch H264 video is FREE. H264 decoding is supported almost universally in hardware by everything made today.
Meanwhile, the dreadful CODEC that Google bought was created illegally by using close-source development as a method of hiding the fact that it ripped off (badly) patented MPEG standards. After Google released the source, and the truth became obvious, Google simply used its billions to pay off the various IP owners whose patents the code infringed on. Google offers its CODEC for free ONLY because Google chooses to bear the IP costs inherent in the use of its CODEC.
It gets worse. The hardware support of Google's dreadful CODEC is almost non-existent, so Google class videos are frequently decoded on the CPU, using insanely greater amounts of energy. Encoding Google class video (which always gives worse results than x264 when other metrics are equivalent) also uses far more power. And you thought Google was "politically correct" and "green"?
All Google wants is control. And Google's incompetent rip-off of H264 and now their new rip-off of H265 are all about control. With H264 and H265, the user has control, and Google hates this. So Google seeds forums like this with the usual vile shills that seek to take advantage of people whose knowledge of the facts behind H264 and its horrifically bad, originally unlicensed copy, VP8, is non-existent.
PS putting Ogg (a TRUE free sound CODEC) and WebM (Google's licensed AFTER-the-fact terrible rip-off of H264) in the same sentence is as misleading an attempt at pro-Google propaganda as you can get.
By failing to support MP4/H264 they are defacto creating a means of censorship , i.e. denying the ability to watch the videos to those who do not share the same ideological stance.
This is bullshit. You're abusing the definition of censorship the way politicians abuse the word "terrorist".
But the MP4 versions 'ould enable...
I think you accidentally a etter.
Many wikimedia regulars
That should, of course, be Wikimedia, with a big wuh.
Can we replace the words "Posted by" with "Blindly rubber-stamped by"?
systemd is Roko's Basilisk.
And for these people the cost of paying for a H.264 encoder license is trivial compared to royalties they have to pay for images, video, and music.
And what about the developing world that is slowly coming online via shared community hubs? Won't they have the right to publish content too without paying exuberant rents compared to their income? The cost is trivial for everyone. I am sorry but open formats are the only way forward for a level playing field. All we are seeing with this WWF/H.264 debacle is a small amount of vested interests trying to justify extracting rents from the world population, when non are really required.
That these closed proprietary formats/DRM are clawing their way back into our "open" standards, services like Wikipedia and browsers is a testament to how committees, foundations (and once democratic institutions serving the public interest) can be infiltrated by vested interest and their purpose corrupted slowly from the inside out. It is a slippery slope, read todays news to see how absolutely low you can slide.
Now there is a category of people so disconnected from reality that are ok to overpay an already excessively rich phone manufacturer that refuse to support free format, and there only reaction to there frustration is to ask a poor free project to support commercial format. I wonder how many of them have donate something to Wikipedia.
But I am not so surprised. I have observed many times that a lot of people tend to be proud of what there have payed and disregards what there have not payed, even when the reality clearly show that there money was not worth the result. It's a childish behavior to ask others to fix your own false choice.
Why exactly is Apple not supporting the open standard? I'd really like to hear the defence of that decision, from both Apple and you. That's what this whole thing really comes down to ... why is Apple explicitly not supporting open formats.
The unencumbered WebM and Ogg versions would remain our primary reference for platforms that support them. But the MP4 versions 'ould[sic] enable many mobile and desktop users who cannot view these unencumbered video files to watch them in MP4 format.'
Something is fucking wrong with this situation...
This seemed like a reasonable sig at the time.
This doesn't answer the question.
probably because it is the WRONG question. The question is why should they support it? They already support the industry wide adopted standard, the community is asking them to support something that is not industry accepted at this point.
One of the biggest sites on the web uses it, as well as many others.
Never ever seen one.
Who logs in to gdm? Not I, said the duck.
Never, but it can add to a list of small frustrations, getting a user to switch manufacturers next contract renewal.
Someone who switches from an iPhone will lose all his purchased videos, all his purchased books, and all his purchased iPhone apps. Only the music is DRM-free. He would have to re-buy everything else on Android, provided that they're even available on Android and not exclusive to iTunes. The iPhone, for example, is the only phone that can stream video from Amazon.
Right now, there is NO advantage to WebM or VP8 over h.264. The only reason to choose it is purely philosophical, especially since it's inferiority.
Does "purely philosophical" include the simple fact that nobody has yet donated an encoder license to Wikimedia Foundation?
Is "strongarm" an appropriate word for what Apple is doing?
Apple has been strongarming on its mobile platform since around 1998 when the MessagePad 2000 came out.
What exactly is their reason for not supporting an open format?
One reason is battery life, as it'd have to be decoded on the CPU instead of on the dedicated MPEG ASIC. When you really need to make a call, you don't want to lose touch after having watched a bunch of videos earlier in the day. The other is Nokia's decision to assert its patents against the use of VP8.
The people upset are those who can't access the videos on there iDevices.
The HTC Dream didn't exist when the original iPhone came out, and when Android came out, iPod and iPhone were still using DRM on music. What viable alternative was there when people first started to get locked into the iEcosystem?
You must not have a lot of friends with land-line phones (which can't text) or flip phones (on whose numeric keypad texting is incredibly tedious).
Though the GIF battle ended, the war continues on the MPEG-LA front.
Let the contributor opt in/out.
Or doesn't anyone do compromise anymore?
--dant
I think you underestimate just how much I just dont care.
As far as I can see the formats have no technical, quality, or resource utilisation benefits, it comes down to licensing.
H.264 would require Wikimedia Foundation to utilize more of the resources (that is, money) donated to it.
H.265 is already planned to go into 2015 devices (TVs and BD players) in order to support upcoming features like 4k and HDR - but, there is still a chance to get VP9, etc in there.
Netflix and Amazon aren't waiting until 2015 to anchor their position as the leading providers of 4K video.
Netflix says video streaming of its programming in ultra-high definition will work for buyers of new UHD sets from LG, Sony, Samsung, Vizio and others upon purchase.
That's because Ultra HD models from those makers will include the Netflix app and chips that decode signals in the so-called High Efficiency Video Coding standard, or HEVC.
The chip is required to decode signals that Netflix Inc. will compress by more than 100 times and squeeze through the Internet at a speed of 15.6 megabits per second. That's a download speed widely available from Internet providers in the U.S.
Netflix app to stream "Ultra HD" 4K video on new TVs
That'd be fine if it were a programmable DSP or a pixel shader doing most of the work. But I've read that a lot of MPEG ASICs have the entropy codes, pixel predictors, transforms, and other parts of an MPEG codec baked directly into the silicon. Some of them just take an MPEG bitstream as input and spit out pixels and audio samples as output.
By failing to support MP4/H264 they are defacto creating a means of censorship , i.e. denying the ability to watch the videos to those who do not share the same ideological stance.
This is bullshit. You're abusing the definition of censorship the way politicians abuse the word "terrorist".
I can not view H.264 video on my system. I compile everything myself, and the source it is not available in a form that is legal for me to compile the codec, or interact with hardware that can decode it.
If the kerfuffle over this has one positive outcome - it will be the insufferable, ridiculously self-righteous Wikimedia users leaving en masse and making Wikimedia a much nicer place to contribute again...
Another non-functioning site was "uncertainty.microsoft.com."
The purpose of that site was not known.
If someone can take a principled stance against this, they should. Right now the only entities with a spine are the ones who aren't for-profit, and none of them can stand up to it, and end users should really be supporting them. Do we really want Google and the MPEG-LA to dominate like that, knowing what happens every time companies dominate something like that?
Well said. A reference on your betrayal of Google: http://news.cnet.com/8301-11386_3-57612525-76/vlc-steps-into-next-gen-video-wars-with-vp9-hevc-support/
Well, then, if it's not a sufficient reason to say H264 is unsafe and troublesome, then it's not sufficient reason to say WebM is unsafe or troublesome.
Except that Google ended up licensing the MPEG LA patents whilst AVC has been in use for ages and no one who has paid the license fee for the MPEG LA patents has successfully been sued by a third party.
If you look here
http://techcrunch.com/2013/03/07/google-and-mpeg-la-sign-licensing-agreement-covering-googles-vp8-video-codec-clearing-the-way-for-wider-adoption/
It looks like Google ended up paying the MPEG LA for the patents that WebM infringed. Google then licenses those patents out for free to anyone who wants to use WebM.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
Looks like a quotation from a press release advocating copyright extension or advertising a new DRM to users.
By failing to support MP4/H264 they are defacto creating a means of censorship , i.e. denying the ability to watch the videos to those who do not share the same ideological stance.
This is bullshit. You're abusing the definition of censorship the way politicians abuse the word "terrorist".
I can not view H.264 video on my system. I compile everything myself, and the source it is not available in a form that is legal for me to compile the codec, or interact with hardware that can decode it.
Thanks for this, but um, why did you post it to me? It's irrelevant to my point. It's meaningless.
Contributors: already have encoder
Not all of them do. Contributors might have a decoder for use with their cameras but not a licensed encoder to encode footage to the correct bitrate, profile, etc. Besides, the thumbnailer on Wikimedia's servers (for resizing HD video down to SD and LD) still needs an encoder.
The power to TAX something is the power to restrict or destroy it.
Ask why nearly ALL the device makers are so afraid of unencumbered, "untaxed", video and audio codex?
Technically, Apple does support motion JPEG as a video format on OSX which is a royalty free format. MPEG-1 is also probably royalty free as well and is supported on OSX Safari. However, even Ogg Theora beats those formats on compression.
(Of course, without Apple's objection to Ogg Theora, it would probably be a required codec for HTML5.)
As I understand that press release, MPEG-LA has committed to refrain from charging a royalty for making already encoded videos available to the public without charge. It didn't mention anything about royalties for obtaining lawfully made encoder software in the first place, such as the encoder needed to thumbnail a 1080p video down to 720p, 480p, 360p, and 240p.