BBC Wants Help With Dirac Codec
Number Ten Ox writes "According to The Register the BBC wants help to develop their open source video codec Dirac. '[Lead developer Dr. Thomas] Davies said the codec could live on anything from mobile phones to high-definition TVs but not before a lot of further work is completed. For one thing, Dirac doesn't currently work in real-time. Davies also reckons that the compression offered by the technology could be further optimised. The BBC is working on integrating the technology with its other systems, but the corporation would welcome more help in developing Dirac.' Sounds like something worth helping with."
Compared to many other broadcoasters the BBC has a long and excellent record of producing great programms AND embracing the web/technology.
... compared to companies like Real ...
Certainly a good 'partner' to support
If they want to make an open source video codec, why don't they just support and help further develop the ogg video codec? Would the two codecs be so different that they are both needed?
Have there been any comparisons? Do we really need two fully scalable open-source video codecs?
Also - the BBC is funded by the British government. When did they get a mandate to spend money developing video codecs. I don't have a problem with government-funded "arts" but this seems a bit beyond the normal scope of things
What's the advantage to using Dirac over a standard?
What the major difference with this codec is. Why is the BBC developing their own codec instead of, for instance, throwing a few bucks towards OGM or XVid, or $YOUR_FAVORITE_OSS_CODEC?
I don't need no instructions to know how to rock!!!!
AKAIK, it's the only high compression video codec to not be encumbered by patents. (Although I've heard whispers from the OGG/Vorbis team.) That right there makes it worth development. Once the codec reaches a stable version, it can be integrated into free player solutions like HelixPlayer and VLC.
Javascript + Nintendo DSi = DSiCade
Unlike licenses for MPEG standards, some licenses for the Dirac codec will be available royalty-free.
BLING BLING. Meet the architecture that's changing everything.
But none supported by an entity as large or influential as the BBC.
Codecs like Theora are great, but it's unlikely they'll enter the mainstream in the same way as something like DivX has - just as Vorbis is lagging behind other closed source audio codecs.
If the BBC started using Dirac for all its streaming video feeds, for example, then suddenly millions of users will have an excellent incentive to download the codec and if people already have it on their machines then others can produce Dirac based media without having to worry that people won't want to view it because it means downloading something extra.
The BBC isn't a business, and isn't trying to make money. It's a state-funded channel, and is paid for by a license fee. I think it is actually a violation of their charter to get money from anywhere else: I know they're not allowed to run commercial advertisements.
American's don't get the concept of a Crown corporation. They don't act like any other "rational business". They don't really have to make a profit, and the way most are run, making a profit is a secondary objective.
I remember the sucking money hole that was Air Canada before the government chopped it up and sold it off. All of a sudden it's a profitable business, turns out they didn't need to be sending 737s to Beaversnatch, Alberta thrice a day.
I don't need no instructions to know how to rock!!!!
Sourceforge project
BBC's Dirac homepage
Check the sourceforge project
I am NaN
Anyone wondering why we need more Open Source Codecs should read the excellent companion article on today's register, a long OP Ed piece on Steve Ballmer entitled Love DRM or my family starves: why Steve Ballmer doesn't Get It.
In it Steve explains why the Digital Home has to come from Microsoft and specifically Microsoft's committment to DRM everywhere. A facinating, if biased piece.
The BBC, just like any other rational business, is out to make money off of this while the rest of the world could benifit greatly from it.
Nope. The BBC need the codec in order to save themselves a bucketload of cash in the future when they make their digital program archive available over the internet (something they have to do according to their Charter). They're not intending to make pots of money from the codec, they just want it to exist so they can use it themselves.
http://twitter.com/onion2k
The only truly open video codec worth mentioning is Theora. XviD's source may be open, but the codec itself is a patent minefield. Theora is patent free, as is Dirac. Even if the BBC did take out some patents, the license Dirac uses means these patents would be harmless.
So yes, we do need this codec and others like it. Theora is nice but it dosen't hold up against any of the new generation of commercial codecs that are coming out now.
Can you please list all of the Open and non patent encumbered codecs? I can only think of Theora. Of all the codecs out there just about every one is enbumbered by a patent or license fee or DRM which hinders thier usage for distribution of public content such as documentaries.
If Tyranny and Oppression come to this land,
it will be in the guise of fighting a foreign enemy. -James Madison
Dirac is a wavelet codec. The technology is far more advanced than Theora's. In fact, until On2 came along, Ogg were working on a video wavelet codec called Ogg Tarkin. They want with open sourcing VP3 because it would be quicker and easier, nothing more. As the BBC are demonstrating, putting together a competent wavelet-based video codec is non-trivial to say the least.
Put simply, Ogg Theora is already outdated. The source material (On2's VP3 codec) does not match any decent MPEG-4 codec. The BBC would be wasting their time by messing around with dated tech.
That said, Theora is usable and just about the only decent patent unencumbered video codec in existance. Until Dirac is finished, Theora will remain the sane choice for those who want to stay legal without paying through the teeth.
If and when Dirac is ready, it will blow everything else away. It will be worth the wait.
I will trade codec engineering time for TARDIS technology. In fact, that's where I got my TARDIS from!
--
make install -not war
Don't we already have enough codecs, including open source ones?
While I agree strongly that there are a lot of reinvented wheels in OpenSource that add nothing new or unique, audio codecs are a wide open area for innovation. There is a lot of complex mathematical theory involved and while many very smart people have more than just scratched the surface, we could see considerable improvement with more development. Each project serves as a test case for the methods it uses.
Personally, I'm dissappointed that the idea of using genetic programming (or related technology) to develop or improve CODECs has not, at least to my knowlege, taken off. Hopefully the people with the expertise in both fields will at some point come together. That would be a worthy use for the resources we have at our disposal these days, IMO.
I used to think this would only be good for lossless CODEC developement, but perhaps automated fitness tests for lossy CODECs could also be practical.
Someone had to do it.
If you knew anything about the way the BBC runs and operates you'd realise how dumb a comment that was.
Wrong. Theora is nearly there, whereas Dirac isn't even working in realtime (RTFS). And, it lets them stay with one paradigm (I can't believe I just used that word) because Theora has an audio analogue (ogg) whereas Dirac doesn't.
And that's ignoring the benefit of being involved with an OSS project that, while rough around the edges, has a large development community already (both Theora devs and the potential pool of Ogg devs who could be enticed to work on Theora), rather than starting a new OSS project.
I'm wary of the fact that this "call for help" comes just days after over 1400 BBC technology staff were out sourced to Siemens
Codecs are modules that fit into apps. Consistent with the three-tier architecture, they have APIs called by apps, and data access to the streams on which they operate, both of which are fairly generic (and ought to be completely standard). Their cores are different, depending on their transformation, their source/destination data formats, and their transformation technique, as well as metadata produced/consumed.
New codecs come along infrequently, and are usually too little, too late. There's a lot of duplicated effort across these projects. It seems a better strategy for everyone to share a skeleton that gets populated with codec core "plugins". An easy install mechanism might even let new datatypes deliver the smaller cores for codec'ing on the fly.
--
make install -not war
If Tyranny and Oppression come to this land,
it will be in the guise of fighting a foreign enemy. -James Madison
I saw them at the Linux expo at Olympia yesterday, it looked pretty decent and its still alpha, they said they sometimes get people helping and pointing out bugs, its pretty rockin that they're getting funding considering the direction the BBC is going, definately better than suns java desktop, but damnit they wernt giving away any penguins or anything >:(
This comment does not represent the views or opinions of the user.
I don't normally feed trolls... but what the hell.
a) the BBC isn't just a "company" - it's the highest quality broadcaster in the world. They always have done research and been at the forefront of new technology throughout their history. This is a project that anybody can help contribute to - as it'll benefit the community as a whole when it's complete.
b) they have put effort into it already - they've put out quite a few releases already (SF page) and have been working on it for a couple of years
c) although they want it to improve their online streaming services (currently done using Real technology), an open standard, no encumbrance from patents, with technology that other codecs at present don't use, is a very important project for not only the BBC, but for all of the computing community
If you are seeing ATSC video that looks like crap, I'd be careful what you blame. It could be the MPEG-2 video, but it's more likely a low bitrate encode.
ATSC gives each RF channel 19.392658 megabits/second... very few broadcasters use all of that, in fact the majority tend to stay under 10 even with multiple programs in their broadcast.
Sporting events, like high motion/action movies often need more bandwidth to look good than a soap opera or day time talk show, it's likely that someone either was lazy and didn't up the rate for the game or they just don't do that ever.
Take a look at DirecTV sometime, you'll notice that many of the movie and tv channels are pretty low bitrate, but for major sporting events (ie super bowl, boxing, etc) they up it very high to ensure a pristine signal and picture.
Help Brendan pay off his student loans
Tell that to the people on the black list. YOU would have to ba a moron to not recognize what is going to happen there.
Personally, I'm dissappointed that the idea of using genetic programming (or related technology) to develop or improve CODECs has not, at least to my knowlege, taken off.
The problem is that the evaluation loop is too expensive. It is _trivial_ to develop a system that attempts to eveolve various mechanisms to encode data, but to iterate each generation you need some sort of way to determine the winners and the losers. If you could figure out a way to use a program to determine which was the better of two video encoding mechanisms it would be worthy of a PhD or two. The simple way to think about this is that if you could perform this evaluation with a computer you would have figured out a practical mechanism for general-application computer vision.
One possibility is to corral ten thousand or so friends and get them to view three encoded clips (the original source and the versions produced by the two population members you are testing) but keeping this up long enough to end up with a decent encoder is an unlikely proposition. Making this harder is that once your population of encoding algorithms weeds out the obviously broken solutions you need evaluators who can determine things like which codec produced the fewest artifacts and other details that would shrink your potential pool of human evaluators.
The hard part about using evolutionary computing techniques is not the evolution engine, it is all about figuring out how to test the population members your engine generates. If you do not already have a well-defined target that is easy to describe mathematically (or a test environment in which you can pit two population members against each other) you are basically screwed.
It's named after a Paul Dirac, a British scientist who worked on quantum mechanics.
The BBC need the codec in order to save themselves a bucketload of cash in the future
Yet ironically we're moving some DHCP servers from linux to windows, plan to move the central image server from Linux/SGI to Windows/SGI and then finally Windows/Windows, have just implemented a multi million pound project, in java, but put in windows servers for most of it, refuse to consider Open Office, refuse to have Mozilla as part of the standard desktop (and you have to jump through hoops to "legally" install it), and have half an intranet that's unavailable to the (few) Mac, Linux and Mozilla users, and the entire of Research and Development.
The BBC is a large company, some sectors are run my MCSEs living up Bill Gates' ass, others are at the forefront of technology.
Well if it was commercially owned I think it would guarantee failure. The BBC's culture is quite unique and probably not particularly understandable unless you're a Brit as they're a hangover from the days of the Establishment - a belief (however pompous and misguided) in public service for the good of the nation (and who's good has always been hotly contested).
--
USA: home of the world's largest terrorist training camp.
Remember that the famous Lena image, which was cut from a Playboy magazine, was a *major* still image compression benchmark for a long time. It was a pretty bad choice -- it has a duplicate line at the top, it doesn't necessarily have the ideal color range, and worst of all, it was copyrighted.
The urge to benchmark with smut is strong, but should be resisted.
May we never see th
How does dirac compare to MPEG-4 when it comes to compression? And how about performance?
TimoT
Do not confuse the codec itself with the designated player.
Unless the copyrights and patents in the codec itself are licensed only in conjunction with the designated player.
I'd think that the argument someone made in an early post about the BBC not being a software development company applies. It only makes sense for the BBC to be involved in media distribution development to a very limited extent. Hiring a single person (or a few people) to coordinate the CODEC development makes sense. Hiring a full blown programming team wouldn't. They will need a continual progression of work over a long-term. They will also not be licensing the technology or getting a revenue for it. So why would they hire anybody to develop it?
I would be surprised to find any BBC worker who was laid off from a BBC 'software CODEC programming job' because of OS development. If anything, it will boost the productivity of employees working on the CODEC, by allowing them to develop the CODEC more quickly and robustly. This is a matter of asking the community to help develop a tool that it would like to use, without footing the full bill.
Besides that, why shouldn't I be allowed to give my own time? I can volunteer in a hospital, a shelter or as a tutor, why shouldn't I be able to volunteer my high-tech skills for a cause I believe to be worthwhile. Isn't it worthwhile to reduce the cost of disseminating the 'free press'?
"BEGIN TROLL FILTER" The US & britain are bombing other countries in the hopes of bringing them freedom. Why not support a better dissemination of information to them, to help distribute a picture of what is going on in the rest of the world. Change can be voluntary instead. "END TROLL FILTER"
Should a large portion of the BBC IT staff be paid to develop CODECs? I believe not, it's not the BBC's task to develop distribution media. However, you are raising a completely extraneous point, since I'm in no way replacing in-house IT staff. But if I felt that I could volunteer time for replacing IT staff, why should I feel bad about it?
I'm not quite sure what upsets you about this whole issue, but please feel free to explain to me how developing a useful, novel open-source CODEC puts IT staff out of work.
They may actually be weightless! Zero-G aircraft, private spaceflights....the possibilites are endless!
Don't pick up the pho*(@)$*@&@!@ NO CARRIER
If the BBC started using Dirac for all its streaming video feeds, for example, then suddenly millions of users will have an excellent incentive to download the codec and if people already have it on their machines then others can produce Dirac based media without having to worry that people won't want to view it because it means downloading something extra.
But if the BBC started using Theora now then that would help Theora get off the ground for exactly the same reason you outline above. A move like this would give the open source movement confidence the BBC were serious and exposure to the concept of a government agency sponsoring truly open source video codecs. Then in a few years we would all have two excellent and (more) widely used open source video codecs. More power to them, and us. As long as they keep using Real and WMA they are not endearing open source developers. I use an AMD64 machine and can't be bothered setting up a dual 32-bit environment, so I can't use Real, therefor I don't get to view any BBC content at all. Not that this means anything other than I'm one extra open source zealot that can't view BBC video.