Interview With BBC Dirac Developer Thomas Davis 170
arclightfire writes "The subject of the BBC video codec Dirac has been here before, but we've managed to get an interview with Thomas Davies, Senior R&D Engineer at the BBC who devised the Dirac algorithm. Interesting to note that the codec should be with Mplayer soon; "As far as players go, we'll be submitting a patch to Mplayer to allow it to play Dirac pretty soon." And info about the tech developments in Dirac; "I used tried and techniques, like wavelets, which weren't in standards at the time, and tried to develop them. And that's what we'll continue to do as the algorithm develops. So we've tried to build on some pretty well-understood technology, and also tried to do some new things with it. We're patenting the new stuff, quite a bit of which hasn't got into the software yet. The license means that these patents are licensed for free within the Dirac software.""
Dirac's not the only new codec in the running (Score:5, Informative)
Why bother? (Score:5, Informative)
H.264/AVC is open and extremely powerful. Why bother with another protocol?
From Apple Tiger h.264 page [apple.com]:
Not only is H.264/AVC very efficient, providing extremely high quality in smaller files, but H.264/AVC is also scalable, producing video for everything from 3G for mobile phones to High Definition (HD). H.264/AVC can create great-looking 3G mobile content at 50-160 Kbps, excellent Standard Definition (SD) video at 800-1500 Kbps, beautiful HD video (1280x720, 24p) at 5-7 Mbps and full HD video (1920x1080, 24p) at 7-9 Mbps. So at today's SD DVD data rates, H.264/AVC can deliver full HD. In fact, H.264/AVC was ratified by the DVD Forum for inclusion in the next-generation HD DVD format.
Re:For Linux? (Score:2, Informative)
They plan on releasing open source and submit a patch for mplayer themselves.
Re:Dirac's not the only new codec in the running (Score:1, Informative)
H.264 is pricey even more than MS's WMV 9 (Score:5, Informative)
no. Here's why. (Score:3, Informative)
Until it supports the ogg bitstream format, you're not likely to see Vorbis audio support, let alone Theora.
Re:They could at least write it with ResEdit! (Score:1, Informative)
Thank you to parent and grandparent. I've been following the Adams Platform/MWC saga for some time, but hadn't seen the most recent ASX document...
Adam Clark and his father are total fruit loops. Quite a few big names (who should have had better-tuned bullshit detectors given their positions) got suckered by them but the smarter ones got out earlier when Adam refused to let even his company's own board independently review the technology.
Frankly from what I hear about Adam's behaviour, they should have been asking pretty hard questions about his mental stability straight away...
Now the Fraud Squad are investigating I'm really keen to see how he pulled off the scam! I know people who probably know how it was done, but I've so far had to play an annoying sort of "warmer/colder" guessing game with them as they're still bound by legal agreements.
Re:"legal in hungary" does not change anything (Score:3, Informative)
There is a Gentoo ebuild for it. The MPlayer files (source and DLL packs) aren't hosted by any of the Gentoo mirrors, but are retrieved from the MPlayer website. The same applies to most software for which ebuilds exist, though. Source for GNU programs gets pulled from GNU mirrors, source for SourceForge-hosted projects gets pulled from SourceForge mirrors, etc. Whether you could call this state of affairs "distribution" is open to debate, I suppose. While what Gentoo provides directly is in a sense little more than instructions and a patchfile, installing MPlayer is no more difficult than installing Emacs or KDE.
(It's worth mentioning that system-specific optimizations (-march=athlon-xp, or whatever) are disabled in the MPlayer ebuild, which goes against one of the main reasons people use Gentoo. With that said, it's behaved reasonably well IME.)
Re:mplayer is bloated and going nowhere (Score:4, Informative)
Those of us who prefer our keyboard to our mouse. And other folks.
It's bloated. On both linux and MacOS X, it consumes considerable CPU resources- and that's with the fancy interpolation it supposedly does turned off. My Powerbook G4, for example- mplayer consumes about 60% CPU, enough to bake my lap and turn on the fan after a while. VLC, on the other hand- needs about 20%, keeping my lap happy.
You misconfigured it. This is, admittedly, not hard to do, but mplayer is the fastest of movie players if used correctly.
Try using the following command: mplayer -vo xv -fs=yes moviename.
Hmm, upon checking the manual, perhaps if Mac OS X lacks support for xv you should be using -vo quartz.
Mplayer has been under "development" for several years. It hasn't seen any major or even minor feature additions.
You've got to be joking. What about the latest ChangeLog [mplayerhq.hu]?
The user interface sucks, especially on OS X.
Actually, mplayer has some kind of bitmapped interface, which I always compile out. I hate all of those damned bitmapped interfaces, the pseudo-VCR things. It has a CLI interface which is exactly the same on OS X as on the other platforms.
Re:What happened to BitTorrent plan? (Score:1, Informative)
Re:openness is hardly a concern to mplayer develop (Score:4, Informative)
Dirac + ogg in an mkv container could save your soul
I assume you mean Dirac + Vorbis in Matroska... Ogg is a container format like matroska... (what you said was akin to DivX + AVI in ASF
On a related topic, Matroska is an unfortunate format to use. It is very inefficient, both in CPU time, and in overhead. My computer can play a 640x480 divx in an avi, but can't play a 512x384 divx in matroska. Additionally, matroska has a higher file overhead than asf or quicktime.
Ogg is a good, basic format. It could be seen as a sturdy replacement for AVI. Matroska doesn't do anything beyond even the Quicktime format... and quicktime is vastly more efficient.
Anyway, moving on from that rant. I agree strongly with your other points. If you have a choice between two, largely equivalent codecs, one is unencumbered by laws and one is, why would you choose to use the one that is. Sure you might not get sued straight away, or even for a year or two, but why bother with that risk at all?
I am not particularly bothered with pirating certain commercial software, but if there is a free program that does everything I need, I will use that over a pirated of a commercial program. Why take the risk when there is another option?
The FAQ states... (Score:2, Informative)
Re:Is it in M*ENCODER* (Score:5, Informative)
Re:Patents (Score:4, Informative)
Re:"licensed for free within the Dirac software" (Score:2, Informative)
Re:The FAQ states... (Score:2, Informative)
when a licence is needed (& good for Dirac!) (Score:3, Informative)
There are minor exceptions for small, battery-only devices in caravans, and the like, and people have escaped where they could show that they could not receive broadcasts (like there was no aerial for their TV/Video, and neither were tuned in to TV channels), but it's not easy.
And the rules on multiple-occupancy are complex, and the way the BBC seeks to apply them seems to evolve. But the basic idea is that you need a licence if there are any tellies in a house.
It's enforced by automatic reminders, detector vans, £1000 fines (Grand if you have a licence, a grand if you don't), and TV sellers notifying the authorities when they sell a telly.
In my opinion it's great value, though. Even if it is being dumbed down, and the free internet-accessible archive seems to have stalled somewhere...
But developing a codec is sensible if it keeps the costs of streaming down - and especially if it's easier to implement on Open Source O/Ss. Hopefully some penny-driven accounting type at the Beeb won't feel the need to charge huge licence fees or impose Open-Source-incompatible licence terms.