Slashdot Mirror


BBC Brings DRM-Free Content To Linux Users

eldavojohn writes "The BBC is planning to release some of its programmes to users of GNU & Linux. You won't see Doctor Who or Dragons' Den on there anytime soon, but they have been working with Canonical & Collabora on getting this out there for Totem users. The developer blog mentions that the sheer number of options in the open source world actually makes this difficult to accomplish."

131 comments

  1. I hope they made the freedom choice. by gnutoo · · Score: 4, Insightful

    Multiplicity of platform is not a problem for free software, so I'm confused. Every distro is able to use xorg, for example, and people who want to help out go there not to a distribution. If BBC releases free software, everyone else will be able to use it. It's nice of them to dive deeper, but if the backend work to totem is free, I expect it to turn up in my favorite distribution soon. They seem to understand this:

    The whole stack is free software - from URIplay through to Totem, the media player. Some codecs will involve a download, and in some territories (mainly outside the UK) may be restricted, but the underlying framework is free and open.

    The question then, is why they worked with a specific distro rather than upstream. The Totem plugin says it uses Dirac, that's cool.

    1. Re:I hope they made the freedom choice. by Ethanol-fueled · · Score: 2, Insightful
      TFA said that other distros will be worked on. They chose to start with Ubuntu as it appears to be the most popular desktop(Joe user) distro.

      This news is a pleasant surprise and I hope more media outlets catch on, but the article makes it clear that it does take a lot of work to make it happen:

      Lots of this work involved changes to the underlying infrastructure of Gstreamer, as well as developing the plugin for Totem.

      That sounds unfortunate, because most people perceive something as ubiquitous as streaming media to be a given, so the complexity of making it Just Work(tm) sounds intimidating. It's bad for Linux desktop adoption as it perpetuates the notion that everything takes tinkering and trial-and-error to properly function and this will be no exception.

      As the service develops, we will start supplying content in several different formats - some of these are totally free and open, some aren't - we've reflected the wishes of content owners here, obviously.

      Sounds like that's going to be a mess. Note that TFA mentions that totem will need a proprietary plug-in. It may be free now, but who's to say that they won't later tighten their grip for profit and/or pressure from content providers?

      Some codecs will involve a download, and in some territories (mainly outside the UK) may be restricted.

      A non-issue for most savvy Linux users but it may scare off some curious folks.

    2. Re:I hope they made the freedom choice. by Ed+Avis · · Score: 2, Interesting

      The thing is, when people are faced with more than two choices, they tend to panic and dither and get put off. It's surely a bug in the way the human mind is designed, but given that the original maintainer seems to have gone quiet for a while, I don't think a patch will be forthcoming. So we have to work around the bug. One way to do that is to reduce the number of choices that have to be made, or at least, as the Python folk say, 'There should be one obvious way to do it'. Even if what you end up with is technically inferior to one of the options that could have been chosen (and let's face it, the C language, X11, Qwerty keyboards, SMTP, and pretty much everything else is less than perfect), there is massive value in simply eliminating the number of decisions a developer has to make.

      I realize this isn't quite a direct reply to what you wrote, but I felt like a bit of a rant anyway :-p.

      --
      -- Ed Avis ed@membled.com
    3. Re:I hope they made the freedom choice. by Ethanol-fueled · · Score: 1

      You should have quit while you were ahead with your decent first post. We're not talking about Microsoft this time, this thread is about Linux.

      Please stay on topic, do not derail good threads, and save the paranoid vitriol for the Windows articles, please. Yes, I know who you are.

    4. Re:I hope they made the freedom choice. by ShieldW0lf · · Score: 2, Informative

      The thing is, when people are faced with more than two choices, they tend to panic and dither and get put off.

      Tell me about it. Should I use the BBC, or should I just stick to getting my fix of British culture off bittorrent sites...

      Yeah, too confusing. I'm going to stick to torrents. No one ever told me that they had to erect barriers around me in the name of other peoples 'interests' on a torrent site.

      --
      -1 Uncomfortable Truth
    5. Re:I hope they made the freedom choice. by Anonymous Coward · · Score: 0

      Vmware. Nuff said.

    6. Re:I hope they made the freedom choice. by osu-neko · · Score: 3, Interesting

      TFA said that other distros will be worked on. They chose to start with Ubuntu as it appears to be the most popular desktop(Joe user) distro.

      Joe the User supports Microsoft, even though his current computer and the computer he's thinking of buying would benefit more from Ubuntu. :p

      --
      "Convictions are more dangerous enemies of truth than lies."
    7. Re:I hope they made the freedom choice. by aztracker1 · · Score: 1

      I know it isn't free (GPL) software, but I really don't so much get why they didn't just use Flash, or even Moonlight for that matter...

      --
      Michael J. Ryan - tracker1.info
    8. Re:I hope they made the freedom choice. by Anonymous Coward · · Score: 0

      hi twitter. You just *had* to whip out three accounts to post here, didn't you.

      honest question - why do you insist on doing this when everyone knows exactly who you are and what you do on slashdot?

    9. Re:I hope they made the freedom choice. by Anonymous Coward · · Score: 0

      I know it isn't free (GPL) software, but I really don't so much get why they didn't just use Flash, or even Moonlight for that matter...

      Flash - Crap quality, no 64 bit version for linux
      Moonlight - Crap quality, MS proprietary rubbish that'll always be a version behind SL.

      But probably because there are quite a few plugins for Firefox/IE that let you save a flash video to disk. If theres not one for ML/SL it wont be hard to make one.

      Using a proprietary binary only codec they can stall/prevent its adoption and blame issues on Linux or incompatibilities.

      BBC wants to use MS crapware so making it harder to view under Linux is the best way.

    10. Re:I hope they made the freedom choice. by Anonymous Coward · · Score: 0

      You were actually having an interesting conversation, why the fuck did you have to ruin it with sockpuppets and anti-Microsoft bullshit?

    11. Re:I hope they made the freedom choice. by aztracker1 · · Score: 1

      Yeah, but it's still easier to get flash in 64-bit (ns wrapper) than a lot of other media plugins, and in a consistent manner for the player. As to crap quality, it *can* be better, not HD, but better than youtube by far. As to moonlight, the quality scales to very high HD quality, as the VC-1 codec is comparable to mp4+avc. As to the proprietary, VC-1 is a published standard, and MS is allowing (even helping) with the Moonlight development in this regard.

      As to things being downloaded, that's a true area for concern, not to me, and probably no real reason to be concerned over it.. but still. My main point was, why not use something that's already widely available, even if not opensource, or use something that is opensource, that could be widely available. Both of those options would offer a consistant interface for users, and developers in question.

      Far be it for me to question the brilliance that is the BBC, however.

      --
      Michael J. Ryan - tracker1.info
    12. Re:I hope they made the freedom choice. by LingNoi · · Score: 0, Offtopic

      twitter just STFU. It's about Linux, not windows.

      Take you're windows promotion elsewhere.

    13. Re:I hope they made the freedom choice. by TheABomb · · Score: 2, Funny

      Or you could pay good money for a cable or satellite provider to deliver BBC America directly to your telly, and then only have to wait anywhere from four months (Doctor Who) to nine years (Spaced) to see them. Gotta be faster and easier than either BitTorrent or the Beeb just using Flash, right?

      --
      MSIE: The world's most standards-complaint web browser.
    14. Re:I hope they made the freedom choice. by jonbryce · · Score: 1

      I would have thought Xandros was the most popular desktop distro as it ships with the Eee, and most other netbooks. The HP one has SuSE. I haven't seen any with Ubuntu.

      I am typing this on Ubuntu here, but Slashdotters who install their own OS are very much in the minority.

    15. Re:I hope they made the freedom choice. by jonbryce · · Score: 1

      They are using flash video at the moment. I guess this is for the download option, which currently is DRM infected wma.

    16. Re:I hope they made the freedom choice. by awrowe · · Score: 1

      Have a look at the elonex webbook - ubuntu from the get go, although they are now shipping a windows xp version (which is a bit of a shame).

      --
      A.I. Research. The peculiar science in which we know the question and we know the answer, but can't show the working
    17. Re:I hope they made the freedom choice. by Tubal-Cain · · Score: 1

      I haven't seen any with Ubuntu.

      I am typing this on Ubuntu here, but Slashdotters who install their own OS are very much in the minority.

      Uhh, Dell?
      Oh, and they now have Ubuntu (and FreeDOS) right there in the side bar!

  2. This could be good news by Anonymous Coward · · Score: 0, Funny

    If it weren't for the fact that the BBC is controlled, secretly, by a cabal of nefarious Italian interests who embed secret, subliminal advertisements for their nefarious ices in the Beeb's "impartial" reporting. Danger! Danger! Stop the Italian mind-control before it crushes freedom everywhere! I have modemes.

  3. what is so hard about it? by viridari · · Score: 5, Insightful

    The developer blog mentions that the sheer number of options in the open source world actually makes this difficult to accomplish.

    h.264 video, AAC/AC3 audio tracks, in an MPEG4 container. It'll play on almost anything modern.

    Announce new content via RSS feeds.

    Distribute it via BitTorrent and allow the consumers to foot the bandwidth bill for distribution.

    Until it is this simple and straightforward, you're doing it wrong, BBC.

    1. Re:what is so hard about it? by abigsmurf · · Score: 4, Insightful

      .h264 is an incredibly CPU intensive codec. It would increase the cost of players and make it harder for most mobile phones to cope. Bittorrent is awful for streaming (although I believe there is work on a p2p streaming protocol) and could you imagine bittorrent on someone using a 3G data connection(either a phone or laptop)? It would cost them a fortune.

    2. Re:what is so hard about it? by sam0737 · · Score: 1

      It's might still be CPU intensive today. But not next year.

      Moore law works on CPU, and I am confident that 1080p will still stand for at least one decade. (DVD quality already did, right?)

    3. Re:what is so hard about it? by Anonymous Coward · · Score: 0, Funny

      Spot the ipod loving pirate.

    4. Re:what is so hard about it? by viridari · · Score: 5, Insightful

      h.264 is handled quite nicely by nearly every Apple product, many new cell phones, modern flavors of Windows and Linux, modern PC's without any additional hardware offloading. Television providers around the world are bracing to switch over to h.264 streaming and I believe some are already there. This is, effectively, the prevailing standard for broadcast quality high definition digital video.

      Sure, BBC can provide a streaming option for those who prefer it. But I'd wager quite a few will opt for downloading the whole show and watching it stutter-free, which also gives them the option to keep it or discard it when done.

    5. Re:what is so hard about it? by Winckle · · Score: 1

      this isn't about streaming, I think the GP refers to the download version. The streaming version uses flash.

    6. Re:what is so hard about it? by Neil · · Score: 5, Insightful

      They are doing it wrong.

      The problem is that they are trying to control the "user experience", as always. The blog doesn't actually say anything about the codecs or transport streams used. It is all about the Totem plugin that lets one browse the list of programmes on offer.

      Dear BBC: Use open formats. Make it easy to get at the files or streams. You will not need to worry about the diversity found in various Linux distributions and different desktop environments - the development communities associated with the various desktops and media players will write all the user interface tools for you!

    7. Re:what is so hard about it? by YesIAmAScript · · Score: 1

      H.264 isn't too much more CPU intensive than MPEG-4, but it's far more memory intensive. That's what makes it tough for phones.

      --
      http://lkml.org/lkml/2005/8/20/95
    8. Re:what is so hard about it? by SanityInAnarchy · · Score: 1

      Well, they're trying to use Dirac...

      BitTorrent is likely a bad idea...

      But either way, I agree, I don't see the problem. I've been streaming video for years on Linux.

      --
      Don't thank God, thank a doctor!
    9. Re:what is so hard about it? by Ethanol-fueled · · Score: 1

      Some devices, such as the Linux-friendly Popcorn Hour perform well for h264 because they have built-in hardware decoders for that purpose.

    10. Re:what is so hard about it? by TheRaven64 · · Score: 1

      H.264 is designed to scale from handheld devices to beyond HD. It has all sorts of tuneable options that trade CPU usage for bitstream size or quality. Make each episode available in three options - high, moderate, and low quality. If you're on a mobile phone with a 3G connection you pick low quality. If you're watching on your HDTV on a good Internet connection, with a fast CPU, pick high. Otherwise pick medium.

      --
      I am TheRaven on Soylent News
    11. Re:what is so hard about it? by poot_rootbeer · · Score: 3, Insightful

      Oh God. The LAST thing the Linux communities need is more developers creating their own user interfaces.

    12. Re:what is so hard about it? by camperdave · · Score: 4, Insightful

      A year from now my 800MHz pentium will still process as if it were an 800MHz pentium, regardless of Moore and his oft-quoted "Law". So the codec will be just as CPU intensive then as now.

      --
      When our name is on the back of your car, we're behind you all the way!
    13. Re:what is so hard about it? by tepples · · Score: 1

      It's might still be CPU intensive today. But not next year.

      But if you have 84 million of today's devices in the field, you can't easily replace them all next year. Heck, some devices barely manage to decode 256x192 pixel DivX at 12 fps because they have a 67 MHz CPU.

    14. Re:what is so hard about it? by Skapare · · Score: 2, Insightful

      What are you afraid of? That you might have to choose more than one for yourself?

      --
      now we need to go OSS in diesel cars
    15. Re:what is so hard about it? by sketerpot · · Score: 1

      Ah, see, there's your problem. Most users of streaming video aren't still stuck on an 900 MHz pentium, and they would actually like to trade some of their spare CPU cycles for better video quality. That may suck for you, but you're in a minority. Hell, my computer is like four years old and underspecced, and it can still play most H.264 videos without an issue.

    16. Re:what is so hard about it? by David+McBride · · Score: 3, Informative

      The BBC is using open formats, protocols and systems to provide this service.

      See:

      http://uriplay.org/
      http://open.bbc.co.uk/rad/uriplay/availablecontent
      http://bugzilla.gnome.org/show_bug.cgi?id=555823

      This is a source plugin for content made available by the BBC, kindly sponsored
      by the BBC and Canonical. It's still quite basic, but functional.

      (Note: this has nothing to do with the iPlayer, it mostly just makes content
      available in totem which is already available in some form or other on the BBC
      website now, at least for the time being; server-side things are also still
      work-in-progress, so expect the occasional hiccups and problems with the
      content in the feed.)

      The totem plugin's implemented in open-source python. Go play!

    17. Re:what is so hard about it? by harlows_monkeys · · Score: 1

      h.264 video, AAC/AC3 audio tracks, in an MPEG4 container. It'll play on almost anything modern

      That will draw major criticism from the "free software" people (as opposed to the "open source" people), as most of those technologies are patented.

    18. Re:what is so hard about it? by Anonymous Coward · · Score: 0

      So.. the American "free software" people, because in the UK there are no software patents. An important distinction to make seeming as this is about the BBC.

    19. Re:what is so hard about it? by jonbryce · · Score: 1

      No, they're not stuck on a 900MHz pentium, but a lot of them are stuck on a 400MHz Arm chip.

    20. Re:what is so hard about it? by Anonymous Coward · · Score: 0

      ... you're doing it wrong ...

      Nearly straight off the Troggs Tape!

    21. Re:what is so hard about it? by spyder913 · · Score: 1

      ...and a 320x240 display most likely. And smaller storage space than a full computer. Not to mention it's not a good place to run BitTorrent. Those people should probably use a different version of the media. I'm sure they could distribute a 'mobile' version, or someone else could do it if provide the full resolution H.264 video.

    22. Re:what is so hard about it? by ZerdZerd · · Score: 1

      The decoders' performance often improves over time.

      --
      I'm not insane! My mother had me tested.
    23. Re:what is so hard about it? by sketerpot · · Score: 1

      Those devices should probably not be trying to view a higher-definition video stream, H.264 or no. In contrast, most ordinary (non-embedded) computers for the past few years have been able to play H.264 pretty easily at near-DVD quality. Mine can, and it's creaky and aging.

    24. Re:what is so hard about it? by mustafap · · Score: 1

      >"It's might still be CPU intensive today. But not next year." Why do people still come out with this shit? Software should be written properly. If you write a bad algorithm then you should correct it rather than wait for CPU power / Memory / whatever to become cheap enough. Anything else is lazyness.

      --
      Open Source Drum Kit, LPLC deve board - mjhdesigns.com
    25. Re:what is so hard about it? by Tweenk · · Score: 1

      Better: Dirac video, OGG audio, Matroska container. Every piece of your proposition is patented.

      --
      Those who would give up liberty to obtain working drivers, deserve neither liberty nor working drivers.
    26. Re:what is so hard about it? by Anonymous Coward · · Score: 0

      Out of the various internet methods of accessing the iPlayer content, the BBC recently said that 90% of users are watching their output using the RTMP/Flash/H.264 streams on their iPlayer website. A handful (less than 7%) download using the Windows/kontiki/p2p method and 3% use the iPhone/HTTP/h.264 method.

      So clearly the Flash streaming player version is the most accessible and widely used.

      The iPhone method, I reckon, also includes quite a number of users utilizing one of the unofficial download clients like get_iplayer which spoof being an iPhone so I question whether downloading is really that popular when most people just want to watch a TV programme once, at a time that suits them, and then just delete it.

      You also have to consider that many UK based ISPs have volume caps (typically 1GB - 10GB for the cheaper deals) which include upload as well as download usage in their quotas and therefore p2p is not necessarily very acceptable.

    27. Re:what is so hard about it? by squiggleslash · · Score: 1

      Nitpick: H.264 is an MPEG4 standard. H.264 is MPEG 4 Part 10. What you're probably comparing it to is MPEG 4 Part 2, though the latter is actually more CPU intensive than H.264 for the same level of quality due to the complex macroblock compensation algorithm it employs. In practice, most implementations of Part 2 ignore that part of the standard, leading to poor quality at the same bitrates compared to Part 10.

      --
      You are not alone. This is not normal. None of this is normal.
    28. Re:what is so hard about it? by evilviper · · Score: 1

      h.264 is handled quite nicely by nearly every Apple product, many new cell phones, modern flavors of Windows and Linux, modern PC's without any additional hardware offloading.

      Most hardware devices (iPod/iPhone included) impose numerous serious restrictions on which H.264 features can be used.

      It's common that you have to disable B-frames, disable CABAC, set a low IDC, etc., for compatibility with the above devices.

      At that point, you've eliminated practically ALL the benefits of H.264 over older video codecs like MPEG-4 ASP (aka. Divx/Xvid) or even H.263p.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    29. Re:what is so hard about it? by evilviper · · Score: 1

      Software should be written properly. If you write a bad algorithm then you should correct it rather than wait for CPU power / Memory / whatever to become cheap enough. Anything else is lazyness.

      We're talking about video here... One of a handful of normal user applications that is still completely CPU (and bus-speed) bound. H.264 decoders are already almost as optimized as they can get, and no skilled programmer is going to step in and make any significant headway there.

      I generally agree with you... software development should focus a lot more on optimization. The payback is in lower-end hardware, less user time wasted, slightly higher prices, and/or larger product sales, will likely more than make up for the effort. The industry has simply become short-sighted, and squeezing a piece of crap out the door quickly takes priority over quality.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    30. Re:what is so hard about it? by evilviper · · Score: 1

      H.264 isn't too much more CPU intensive than MPEG-4, but it's far more memory intensive. That's what makes it tough for phones.

      I don't know where you got that information from, but it's utterly untrue. On a very fundamental level, H.264/AVC is vastly more computationally intensive than MPEG-4 ASP/Divx.

      See half-pel, in-loop deblocking, CABAC, arithmetic coding, 16 B-frames, multiple reference frames, etc. Numerous iterative processes that are highly computationally intensive, none of which are used with MPEG-4 ASP/Divx.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    31. Re:what is so hard about it? by harlows_monkeys · · Score: 1

      ... because in the UK there are no software patents

      There are software patents in the UK.

    32. Re:what is so hard about it? by YesIAmAScript · · Score: 1

      16 B-Frames and multiple reference frames are memory intensive, not CPU intensive. That was my main point.

      During decode, there's no additional CPU work to reference against a 2nd (or 3rd) frame, but it does take a lot more memory.

      Aritmatic coding/CABAC I think is only used in the main profiles, most H.264 content the BBC would be sending would be baseline profile.

      --
      http://lkml.org/lkml/2005/8/20/95
    33. Re:what is so hard about it? by trawg · · Score: 1

      h.264 video, AAC/AC3 audio tracks, in an MPEG4 container. It'll play on almost anything modern.

      h264 isn't 'open'. It's a proprietary, patented system that requires licensing fees. This is why it's not supported out of the box in Ubuntu (or at least, why it wasn't - I assume it's still not supported in 8.10 ,but haven't checked).

      The BBC has Dirac though; I wish they'd start using it!@#

    34. Re:what is so hard about it? by evilviper · · Score: 1

      During decode, there's no additional CPU work to reference against a 2nd (or 3rd) frame, but it does take a lot more memory.

      Yes, it does take additional "CPU work".

      Aritmatic coding/CABAC I think is only used in the main profiles, most H.264 content the BBC would be sending would be baseline profile.

      By the same token, you could say that the BBC would be restricting the video to 1 or 2 references frames, and a single B-frame (much like Quicktime does). Even then, you'll still have to deal with qpel.

      And after all of these restrictions, you're probably not any better off with H.264 than you would be with ASP.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    35. Re:what is so hard about it? by YesIAmAScript · · Score: 1

      I do agree these restrictions (which are very common) do reduce H.264 to not much better than Xvid-era CODECs.

      However, I again state it doesn't take additional CPU work to reference against a different frame. You just have multiple frames in memory and make your changes against a different buffer. No individual macroblock depends on more than one reference frame, so you don't have to do any extra work, just keep two (or more) different references in memory to work against.

      Of course, this is all on decode. On encode, multiple reference frames makes the amount of work go up exponentially.

      --
      http://lkml.org/lkml/2005/8/20/95
  4. Little new? by abigsmurf · · Score: 1, Flamebait
    Seems to be almost entirely radio programs.

    However they've offered DRM free streams and podcasts for years now, are they just intergrating these into iplayer?

    Someone needs to invest in an open source DRM mechanism. You have people like the BBC who have good intentions regarding the availability of content but the lack of any DRM at all means their hands are tied when it comes to Linux.

    If some of the more talented OSS devs got off their high horse, they'd realise that if they were the first to create a true secure DRM format, they would be free to shape it in a way that is best for consumers whilst still being good for content producers. Being first would mean the chances of adoption were much greater.

    1. Re:Little new? by Anonymous Coward · · Score: 0

      Suggesting an open source DRM, hope you like getting flamed.

      However most things are better in open source form. And I agree that open source DRM is better than closed source, but still not as good as none at all.

    2. Re:Little new? by Anonymous Coward · · Score: 0

      I was under the impression that sun had developed some DRM solution and so had the azureus developers, only, i think most content producers see them as too much effort, BBC just bought a crap off the shelf product for iplayer and stuck some logos on it, or not restrictive enough.

      This totem sidebar support looks neat but it's nothing that a random dev couldn't have hacked together in a couple of afternoons, the BBC just can't be bothered to put real effort into the software side of things, there are no good intentions just an attempt to improve the image. If they want to do something positive they can hire programmers to work on gnash and get it compatible with the iplayer streaming service, as it stands flash based iplayer is useless for most linux users because the linux port of the adobe flash player is so poorly written, i mean come on, anyone can scale video on a linux system but adobe just seem to screw it up, and the excuses aren't good enough.

      http://bugs.adobe.com/jira/browse/FP-7

    3. Re:Little new? by Xtifr · · Score: 1

      a true secure DRM

      This is what we in the trade call "an oxymoron. :)

      The best you can really do is obscure things as much as possible and hope that slows people down. The obvious problem there is that providing the source code doesn't help to obscure things. And if you don't provide source, about the only Linux vendor who's going to work with you is SCO, whose OpenLinux Server is not exactly flying off the shelves these days. :)

      Something like TPM can help, but even there, the leading provider of TPM-based systesm (IBM) admits that it doesn't provide real security against people who have access to the hardware. TPM, despite all the paranoia about it, is really more reliable for locking people out than in. Enhanced Tripwire, yes; enhanced DRM, not so much.

      Basically, DRM is snake-oil thats being sold to the big content producers. Open-source DRM would simply be inviting them to watch the snakes being squeezed. :)

    4. Re:Little new? by Anonymous Coward · · Score: 0

      Its impossible to make an open-source drm, the whole point of drm is security through obscurity.

      Thats not exactly true. The point of DRM is just that, Digital Rights Management.

      A system could be created that uses public-private keys. A central server would be needed. Each "user" could have a separate key for each of their downloaded media documents.

      There is the issue of caching keys, so the key fetch and decryption should be done in kernel space.

      There are probably more issues I can't think of right now, but it could be done. The media company would have to trust the OS.

      --Gattman

    5. Re:Little new? by SanityInAnarchy · · Score: 5, Insightful

      Someone needs to invest in an open source DRM mechanism.

      Open source is fundamentally incompatible with DRM.

      Either you have security-through-obscurity (in which case, I can just look at the source code), or you have at least some of the DRM implemented in hardware -- in which case, it's severely crippled your computer and your ability to run arbitrary software, including modified versions of the original "open source" code.

      Which pretty much kills the point of open source. Look at Tivo for an example.

      Not that it's stopped other people from trying...

      if they were the first to create a true secure DRM format,

      That is impossible. DRM, by its very nature, cannot be secured. The more "secure" you get, the closer you get to having a console or a set-top box, instead of a computer -- and it's still not secure, just that much more of a pain to crack.

      they would be free to shape it in a way that is best for consumers whilst still being good for content producers.

      "Best for consumers" means being able to do whatever you want with it, except pirate it. One of the things I want to be able to do with my media is use it on entirely open systems. This is a reasonable request, I think, and it is not itself piracy. However, an entirely open system would by definition make piracy possible.

      And "best for content producers" generally means "not pissing off your customers".

      So, the best for both parties is to abandon DRM. The content producers haven't realized this yet, and you aren't helping the situation by pretending that DRM can work.

      --
      Don't thank God, thank a doctor!
    6. Re:Little new? by FourthAge · · Score: 1

      What is really needed is not so much "open source DRM" but rather (1) standard protocol for transferring digital rights from one person to another, and (2) an "intellectual property registry" to record who has which rights. Think OpenID, plus a list of content you've purchased.

      Having "bought a licence" for some music or a movie, you should always be able to listen to it or watch it. But that's not guaranteed when the publisher is the one running the IP registry: we've seen several recent examples of publishers shutting down DRM services and leaving the customers high and dry. If information truly is property, then the IP registry needs to be managed by a trusted third party, independent of publishers and consumers. That way, your IP always retains its value, even as you upgrade your computer, reinstall your OS, accidentally lose files, and so on.

      An IP registry doesn't necessarily have to involve DRM. In an ideal world, all files would be trivial to copy, but piracy would be pointless because unauthorised copies would be worth nothing: they wouldn't be recorded in the IP registry, so you'd have no "rights" to them. Maybe they are still worth something to you because you can still watch them on your PC, but everyone else can see that they've been stolen, using a simple check against the registry.

      To conclude, I agree that IP rights are important, and I agree with the general sentiment that open rights management systems are needed. In this industry, almost all of us are content creators of some sort: it's in our interests to get paid! But I'd say that these don't necessarily have to involve DRM: the notion of a real distinction between an authorised and an unauthorised copy should be enough.

      --
      The tao of democracy: the government you can vote for is not the real government.
    7. Re:Little new? by Stormwatch · · Score: 4, Funny

      Someone needs to invest in an open source DRM mechanism.

      That's like asking the Red Cross to build a torture device.

    8. Re:Little new? by abigsmurf · · Score: 1
      The Red Cross frequently use tools that inflict incredibly amounts of pain on people and can also be used for torture.

      A scalpel has good uses and it has sinister uses. Don't blame the tools for their misuse.

    9. Re:Little new? by abigsmurf · · Score: 0, Flamebait
      There are plenty of encryption mechanisms out there where people know exactly how they work yet are unable to break them without insane amounts of computational power.

      A private key system with a truly random engine behind key generation could potentially be as tough to crack as a closed source one.

    10. Re:Little new? by Anonymous Coward · · Score: 0

      Walter, you're living in a dream world.

      If some of the less talented slashdot commenters cared to learn a little about the subject of DRM, they'd realise that DRM whether open, closed or whatever source, is just plain bad for freedom.

      Freedom software.

    11. Re:Little new? by ratboy666 · · Score: 3, Insightful

      Quoting:

      "Someone needs to invest in an open source DRM mechanism. You have people like the BBC who have good intentions regarding the availability of content but the lack of any DRM at all means their hands are tied when it comes to Linux.

      If some of the more talented OSS devs got off their high horse, they'd realise that if they were the first to create a true secure DRM format, they would be free to shape it in a way that is best for consumers whilst still being good for content producers. Being first would mean the chances of adoption were much greater."

      And now the answer:

      Holy shit! I cannot believe I actually read that.... We develop an OPEN platform, in all senses of the word OPEN. Indeed, the ONLY rule is that it cannot be closed. When someone finds a away around this, vast parts are re-licensed to prevent it.

      The ONLY purpose of "DRM" is to close off the media. It does not make sense to use "OSS devs" and "create a true secure DRM format" in the same sentence.

      Now, its NOT the kernel: the linux kernel remains under an older GPL -- the desktop being targeted is GNOME. Think about that for a millisecond. Now you should be laughing; if not, I'll let you in on the joke here -- the entire stack between the kernel and the X server is controlled by the GNU.

      Now, you could go with KDE (QT) and Trolltech -- but I don't think you are going to get a (much) better reception.

      Go ahead, try... it's purely political. (those "OSS devs" aren't getting off that high horse).

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    12. Re:Little new? by abigsmurf · · Score: 1

      So, what's your view on open source encryption software like TrueCrypt then? Encryption is just another form of DRM.

    13. Re:Little new? by Xtifr · · Score: 5, Insightful

      Encryption, yes, but with DRM, the goal is to provide decrypted data without letting the person in physical control of the machine know how to decrypt it. I can easily provide you with encrypted audio/video files and no key, but that won't be very useful to you since you won't be able to play them. If I want to allow you to listen to/view the files, I have to provide you with the key, so you can decrypt the data. But then it's no longer encrypted (by definition). My only real option at that point is to try to hide the decryption mechanism so you don't know how to apply the key to the data (and may not even know exactly where the key is), and the decryption will only happen behind the scenes, as it were. But if you have the source to the decryption tool, I haven't done a very good job of hiding the decryption mechanism.

      The entire problem with DRM is that it's trying to prevent access by the same people that it's trying to grant access to. If you can't see the inherent contradiction there, I don't know how I can make it any more clear.

      The most secure key system in the world doesn't help you if you need to give the decryption key to the same people that you're trying to encrypt the data against.

    14. Re:Little new? by JesseMcDonald · · Score: 3, Insightful

      The problem with DRM isn't the strength of the encryption, it's the fact that some component of the user's (presumably hostile) hardware must possess both the key and the data in order to display the DRMed content. There's no need to break any encryption when you already have the key.

      A closed-source system at least has the option of obscuring the key and decrypted content inside a binary program with a draconian anti-reverse-engineering EULA (and even that doesn't work in practice). Truly open-source DRM software could be trivially modified to just dump the decrypted data to a file.

      Ultimately, DRM can't possibly work unless the content provider has full control over the data path, from decryption all the way through the viewer's senses. Such control is plainly incompatible with the open-source mindset. In order to remain effective, some part of any DRM system much always remain closed to inspection and modification by the owner of the device it's running on.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    15. Re:Little new? by abigsmurf · · Score: 1
      But then there are also plenty of one way encryption mechanisms which mean you NEVER have access to your own data, most commonly used in passwords. In a large portion of systems with fairly secure login systems it's impossible to retrieve a password.

      This is an example of someone's own data being deliberately made inaccessible to them by rights management. It may seem trivial but if you go by the pure OSS principles being thrown around a lot here, 1 way encryption is immoral and should never be used in GPL software.

    16. Re:Little new? by Anonymous Coward · · Score: 0

      But this has nothing to do with DRM. The entire point of DRM is to allow only certain, liscensed people to have access. If you can't undo the encryption and retrieve the original data, it is utterly useless as DRM.

      The problem with DRM is that you want the content to be secure, but you hand the keys to the very same people who you don't want to copy it. If it can be played, it can be copied; all possible DRM schemes just make it harder.

    17. Re:Little new? by deraj123 · · Score: 2, Insightful

      It's actually fairly different. A more accurate statement is that DRM is just another form of encryption - one where the decrypting algorithm/tool is a black box. As soon as you figure out how to implement a black box in open source, an open source DRM will be possible.

      Also, the GP missed the point a bit as well. It's more than political, there's a logical barrier.

    18. Re:Little new? by Draek · · Score: 1

      Yeah, but the difference is, in those encryption mechanisms it's assumed that the attacker and the recipient aren't the same person.

      Simply put, DRM is cryptographically stupid, and no amount of OSS devs will ever be able to change that.

      --
      No problem is insoluble in all conceivable circumstances.
    19. Re:Little new? by marcosdumay · · Score: 1

      No way anybody would say that 1-way encryption (AKA hash) is immoral. But DRM is not about that, DRM is about granting access to YOU read the data, while denying access for YOU to read it. Giving access to nobody is quite easy, giving access to some specific person is a solved problem, but giving access to the same person you want to deny access can't be solved.

      In related news, on Soviet Russia DRM gives YOU access to the data while it denies YOU access to it! Hey, I never tought I'd ever repeat that meme :p

    20. Re:Little new? by marcosdumay · · Score: 1

      "So, the best for both parties is to abandon DRM."

      Yes, but it is not better for the DRM provider, and this one is the party with the hightest publicitary* spendings

      * Publicitary spending is composed by golf sessions, strip clubs and old plain bribery.

    21. Re:Little new? by Anonymous Coward · · Score: 0

      Either you have security-through-obscurity (in which case, I can just look at the source code), or you have at least some of the DRM implemented in hardware -- in which case, it's severely crippled your computer and your ability to run arbitrary software, including modified versions of the original "open source" code.

      Or.. you use "lossy" encryption.

    22. Re:Little new? by david_thornley · · Score: 1

      Maybe they could solve the Halting Problem, too.

      A free/open source DRM mechanism is impossible by its very nature.

      Consider a DRMed song. Assume it's in encrypted form, so I can't just look at the data.

      In order to play it, I have to have something that will decrypt it, or it can't get to my speakers. Therefore, it will exist in plaintext format somewhere in the software while it is running.

      Now, since this DRM software is open source, I can get me a copy of the source, and I can change it so that it puts its output to a disk file instead of (or in addition to) my speakers. Therefore, the DRM scheme doesn't work. I didn't need to specify a particular DRM scheme to show this, so no open-source software DRM scheme can possibly work.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    23. Re:Little new? by Anonymous Coward · · Score: 0

      Mod grandparent "-1 Confused to Buggery" or "Not even Wrong" rather than "flamebait".

    24. Re:Little new? by SanityInAnarchy · · Score: 2, Interesting

      Or.. you use "lossy" encryption.

      The quickest link I could find there was this one.

      That fails "best for the consumer", because now I'm getting a degraded product -- and yet, once we know it's being done, it's usually possible to circumvent.

      But if you can do non-lossy watermarking, or if it actually doesn't impact quality (for example, it is applied during the encoding process, and produces no lossier output than without it), I have no problem with it. Still possible to circumvent, but impossible to be sure that it's circumvented until you release enough copies for them to check the watermark. At the same time, it doesn't affect legitimate use.

      I generally categorize watermarking outside of DRM, however -- it's the only kind of "DRM" which doesn't also require specific software to play the media back. And it's that requirement for specific software that is what bothers me the most about DRM. (After all, I don't mind Steam so much, because you already need specific software (the game itself) to play any games. But I want to play my media on anything that has the right codecs.)

      --
      Don't thank God, thank a doctor!
    25. Re:Little new? by Anonymous Coward · · Score: 0

      Looks like a few people beg to differ:

    26. Re:Little new? by SanityInAnarchy · · Score: 1

      Yeah, I did mention that it hasn't stopped people from trying.

      It's still a stupid idea.

      I see your argument from authority, and raise you a go-back-and-read-my-post.

      --
      Don't thank God, thank a doctor!
  5. Wha? by JustinOpinion · · Score: 5, Insightful

    The developer blog mentions that the sheer number of options in the open source world actually makes this difficult to accomplish.

    I call BS.

    The diversity of options is only a problem if you try to specifically target a particular configuration. Doing so is dumb--In fact I can't think of any good reason to do so. (Hint: DRM is not a good reason.)

    For instance, if you just have a link to a standard media file (e.g. mpeg) that the user can download, then you're done. The user can then use whatever browser they want, with whatever media player they want, and whatever operating system they want. The diversity of options is then the user's problem, not the distributors.

    Invariably these "there are too many options to support" complaints arise because people have ulterior motives in wanting to target the OS/software/format more specifically (DRM, lockin, user tracking, advertising, promoting a particular OS/software/format, etc.).

    (Note that I don't want the negative tone of my post to take anything away from the announcement. It is surely a good thing that they are working to make their shows available to us Linux users. That's great! But if they are truly going with a non-DRM solution, then why the heck don't they just skip the middleman and let everyone just download a simple file?)

    1. Re:Wha? by Curmudgeonlyoldbloke · · Score: 1

      The bloke whose blog it is is the "Portfolio Manager, Rapid Application Development". He's not going to go very far if he just says "there's lots of free stuff that does this already" and then buggers off down the pub.

      He has to make it look like he's doing something, and make sure that the buzzword quotient is high enough (hence, I suspect, namechecking Canonical - not widely known as content suppliers).

      A "link to a standard media file" may be ideal for you, but to a user who doesn't know that there are alternatives to Windows Media Player / Realplayer / Whatever-their-nephew-installed-for-them-last-week may well be a problem. That's why the existing BBC Podcast links have all the guff about "iTunes, Zencast, Zune" first and only later and mp3 link.

      You and I are not target market for his blog - his boss is.

    2. Re:Wha? by scott_karana · · Score: 1

      Advertising is hardly an ulterior motive, at least when it comes to television networks.

    3. Re:Wha? by Anonymous Coward · · Score: 0

      It is surely a good thing that they are working to make their shows available to us Linux users. That's great!

      No, it isn't. It's just one more step along the road to justifying extending the TV licence in this country to anything that can possibly display a video stream. That is their primary motivation and anyone who believes otherwise is delusional.

  6. difficult? HUH? by Lumpy · · Score: 2, Insightful

    Um pick a open and common streaming format and to hell with wasting time writing a client. They click on the episode name and let it stream.

    Come on, this is so easy a webprogramming 101 student can do it.

    --
    Do not look at laser with remaining good eye.
  7. i had no idea by wud · · Score: 0, Troll

    I didnt realize there was people who didnt use vlc

    --
    wud
    1. Re:i had no idea by CompMD · · Score: 1

      Only the people who love having slow media players use VLC. Sure, it works decently well as media player, but not for slower boxes. Mplayer is MUCH faster. I can play 720p xvid files back on a 300MHz G3 in Mplayer without trouble. VLC on the other hand completely craps itself. Heck, my main media playback computer is a P3-667 that uses mplayer and plays everything.

    2. Re:i had no idea by Anonymous Coward · · Score: 0

      huhwhuaa?
      i had no trouble playing my mpeg4's on a 500mhz celeron (only 128kb l2 cache) in vlc.

    3. Re:i had no idea by deraj123 · · Score: 1

      And you have brilliantly illustrated why service providers should focus on providing the service, not the user interface. A streaming video service? Why would the BBC go about developing a user interface when, just by providing the raw data, a user can leverage VLC, or Mplayer, or Windows Media, or whatever best suits their needs. As an added bonus, you now have zero platforms to support, and your users have the potential for a much better experience than you could ever provide them.

    4. Re:i had no idea by sketerpot · · Score: 1

      I've noticed that same thing. Does anybody know why this is so? (This has been bugging me for months.)

    5. Re:i had no idea by Ant+P. · · Score: 1

      Why do all these media players have their own codecs with their own sets of bugs if they're all supposed to be open source free software?
      I tried to use VLC for one of the BBC radio streams a few days ago and no matter what I did, the connection would eventually drop after a few minutes. mplayer can do it just fine, just as long as I remember to put $(curl ...) around the URL since it doesn't understand playlist files...

    6. Re:i had no idea by Curmudgeonlyoldbloke · · Score: 1

      As an added bonus, you now have zero platforms to support ...

      ...and the bloke who wrote the article, who's the "Portfolio Manager, Rapid Application Development" is out of a job. You and I may not see this as a bad thing, but I suspect that he would.

    7. Re:i had no idea by Anonymous Coward · · Score: 0

      At a guess, your mplayer is using XvMC to render the video, while your version of VLC either doesn't support it or has it disabled.

      I am unable to playback 720p content at full speed in either VLC or mplayer, although mplayer does perform slightly better (about 50% full framerate rather than about 45% for VLC.) My CPU is 2.4GHZ but my video card does not support XvMC for mpeg4.

  8. Does the iplayer copyrights issue apply to news? by Toffins · · Score: 5, Insightful
    The reason the BBC gave for why it could make its programs available on iplayer for 7 days only was that they didn't own the copyright on the content of the programs, and a period of 7 days was all they could negotiate from the copyright owners.

    I can see how that would apply especially to any programs the BBC uses which were produced using subcontractors who usually put their copyright notices (not the BBC's) at the end of their shows. However, the BBC puts its own BBC copyright notice at the end of all of its current affairs programs such as "Panorama" and "Newsnight".

    Doesn't that imply the BBC owns the copyright to the programs? If so, why doesn't it release all of them on iplayer for longer than 7 days? Programs like Newsnight and Panorama which have a lot of analysis and detailed investigative journalism can remain of interest even long after they are first broadcast. There is a demand for watching those programs much beyond 7 days. So, why the 7 days limit on these programs?

  9. Number of options available? by Skapare · · Score: 1, Redundant

    This is a bogus issue. Just choose a STANDARD FORMAT that is openly documented and unencumbered by patents (such as OGG with Vorbis and Theora). Since this is a non-DRM project, this will work. Then let the application developers make sure their products work right.

    This whole idea of standards is so that data can be produced by any of a wide range of programs, and then accepted by any of a wide range or programs. Instead of targeting their product to a specific player, they need to target it to a specific standard, open, and unencumbered format. Standards are there to avoid this very problem BBC claims to have.

    Then if BBC wants to be sure a player presents their product well, they should consider contacting the developers and financially sponsoring the project.

    --
    now we need to go OSS in diesel cars
  10. Must we use Totem? by Enderandrew · · Score: 1, Interesting

    Nice first step, but I just don't like using GTK apps if I can help it, because they look out of place. The only GTK app I really make an exception for is Firefox, and thankfully that is getting a QT4 port from Nokia.

    Is there any chance someone could develop a Firefox extension, or a plugin for Kaffeine, Amarok, etc?

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Must we use Totem? by Anonymous Coward · · Score: 0

      You're free to pay someone to work on a Qt4 plugin, if that's your prerogative. Shuttleworth just exercised his and had Collabora whip up one for Ubuntu (read: Gtk+, Totem).

      To be honest, it's a bit silly, as it would also be great to have one for Rhythmbox and for, well, any media player by open standards like RSS, but until then...

    2. Re:Must we use Totem? by jonaskoelker · · Score: 1

      Firefox, and thankfully that is getting a QT4 port from Nokia.

      Will it be rebranded as firefoks? ;)

    3. Re:Must we use Totem? by Enderandrew · · Score: 1

      The QT4 branch will be supported by Mozilla and live within the Mozilla repositories.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  11. Re:difficult? HUH? by Anonymous Coward · · Score: 0

    Um pick a open and common streaming format and to hell with wasting time writing a client. They click on the episode name and let it stream.
    Come on, this is so easy a webprogramming 101 student can do it.


    Well gee Lumpy. Why didn't they think of that? You'd think they've got the Beav working for them or something...

  12. OMG - I can listen to The Archers!!! by Anonymous Coward · · Score: 0

    Who knew! 150 years of technology development from the industrial revolution onward. Thousands of hours devoted to Linux development, fiber optic cables run under the ocean.

    All, all I tell you, so that I could listen to the lives and stories of simple country folk.

  13. i dont get it by Anonymous Coward · · Score: 0

    if they want to make available to the public some of their shows, why dont they simply encode it with, say, mpeg4 or theora, and it will play in totem, vlc, etc right away.

  14. It's a simple RDF feed. It's not limited to totem by Anonymous Coward · · Score: 0

    First of all, here's the feed, check it out:

    http://open.bbc.co.uk/rad/uriplay/availablecontent

    This is accessible to any client and comes in an open and well-documented format. The Totem plugin is just an example implementation to make use of that. I imagine there will be more clients to make use of this feed in future. You can easily write your own even, if you feel like it.

    To the "just put up H.264/theora/whatever files and list the links on some website" crowd: you can assume the BBC folks have thought about this. It's not really something that's useful to everyone though: small portable devices have different requirements than desktops (e.g. use MPEGy-formats which can be decoded in hardware vs. use free formats and don't require codecs which can't easily be distributed legally). Also the RDF above is really just that, isn't it: it links directly to content with some additional information like descriptions and audio/video format.

  15. Re:Does the iplayer copyrights issue apply to news by bongomanaic · · Score: 1

    The BBC may own the copyright to the programmes but that doesn't mean they have the right to make them available in any format. A few bars of music or a few seconds of sports coverage in a news or current affairs programme will bring the rights-holding industries and their lawyers into play. It's easier (and cheaper) just to have a uniform 7 day limit rather than pay copyright lawyers to vet the 400 hours per week of iPlayer content.

  16. BBC World Service by photomonkey · · Score: 3, Informative

    Would it be too much to ask to get BBC World Service in something other than WMP/Real format?

    Right now, Vermont Public Radio has a transcoder that takes the Real and rebroadcasts it in streaming MP3, but even after donating to them, I still feel bad that the burden is on them to re-encode the stream.

    I'd transcode the stream myself but, a) don't want to go to the trouble and b) suspect it's against their TOS anyway.

    I'm sure the Beeb poured a ton of money into the Real platform years ago (to the extent that they may still be locked-in), but I'd really love to see such an important service be more accessible.

    --
    Message contains 1 attachment: spam.gif
    1. Re:BBC World Service by Curmudgeonlyoldbloke · · Score: 1

      (insert rant about Realplayer here), but it's better-supported by transcoders than some platforms.

      I'd transcode the stream myself but, a) don't want to go to the trouble and b) suspect it's against their TOS anyway

      I'd be surprised if they're that bothered. The BBC World Service is designed to be heard outside the UK - that's why it's made available to pretty much anyone who wants to retransmit it. It's supposed to be the "voice of the UK government" in a "aren't we all nice and democratic and allow public criticism" kind of way.

      I think that it's unlikely that Mark Thompson* is going to fly over to Vermont to stop you running mplayer at home - he's a bit busy at the moment fighting the Daily Mail.

      * At the time of writing the director-general of the BBC. Possibly not at the time that you read this.

    2. Re:BBC World Service by wrook · · Score: 1

      BBC World Service podcasts are available here:

      http://www.bbc.co.uk/radio/podcasts/directory/station/worldservice/

      I looked at a couple of them (including the World News) and they were all MP3.

      I'm not sure if that's what you're looking for, but at least it's a start.

  17. Use Miro. Multiplatform. Open, uses BitTorrent by atrimtab · · Score: 1

    http://www.getmiro.com/

    It has almost all the qualities that a broadcaster could want.... except DRM.

    It is open source.
    It runs on Windows, *nix and Macs
    It uses Bitorrent to distribute content
    It use RSS feeds to provide episodes.
    It supports multiple codecs.

    Seems like that would be a pretty simple way to provide content for ALL platforms. It meets almost all needs except instant streaming and DRM.

    And if you must have DRM figure out a way to layer it on top of a working system, rather than re-inventing yet another DRM scheme with yet another proprietary codec, player, etc. etc. etc.

    --
    Facebook is billions of individual "Skinner Boxes." And if you use it you are the pigeon!
  18. Options don't make things difficult by BhaKi · · Score: 1

    the sheer number of options in the open source world actually makes this difficult to accomplish

    That's precisely why open standards and open protocols exist. Unlike the microsoft world, wherein a protocol/standard is tied to a single vendor, you wont be locking your customers whatever you choose. So stop bothering about the number of options available to your customers.

    --
    The largest prime factor of my UID is 263267.
  19. MOD UP by Anonymous Coward · · Score: 0

    LOL

  20. DRM-Free? by DrPoodle · · Score: 2, Informative

    We already have that...it's called the iplayer downloader...

  21. License Fee for Broadband by Anonymous Coward · · Score: 0

    I suspect this may have something to do with the push to force anyone with broadband to get a TV license fee. Helps get rid of the "but I use Linux" defence.

  22. Re:Does the iplayer copyrights issue apply to news by Anonymous Coward · · Score: 0

    The problem is that the BBC's content is only part of it.

    Screenwriters, actors and content producers have contracts that enable them to have royalties.

    Any musical scores or video clips within the media may have restrictive licensing that the BBC cannot control.

    So it's all well and good looking at the overall BBC copyright, but there's a whole legal minefield behind this.

    They probably could negotiate each part, but I bet that it'll be monsterously expensive even in the simplest cases (track down and get approval from everyone involved) and not a good use of a publically funded organisation.

  23. Twitter troll, mod down. by Anonymous Coward · · Score: 0

    n/t

  24. Re:Does the iplayer copyrights issue apply to news by mpcooke3 · · Score: 1

    Perhaps the BBC sells the rights to some of their shows to other TV channels and media outlets abroad.

    If this is the case I'm not sure these companies would be so keen to pay for the rights to play the content if the BBC was also giving it away free and without any DRM.

    If the BBC keeps a 7 day limit on all programs, it's simple for people to remember and it also means they may still be able to license it.

    Personally though I hope the media companies end up giving up on DRM.

  25. Re:Does the iplayer copyrights issue apply to news by Curmudgeonlyoldbloke · · Score: 1

    ... So, why the 7 days limit on these programs?

    Because when you've got a hammer in your hand, everything looks like a nail.

    They already go through the "what can be made available for longer" process for radio - quite a few radio programs (including most of the main news and current affairs ones) are available as podcasts. Where there are differences it's usually where e.g. The Now Show has licensed a bit of music as the payoff for a joke, and whoever owns the dibs on that doesn't want it freely available as an MP3. It wouldn't be rocket science to do the same for e.g. Panorama - no harder than radio's Analysis (not unlike Panorama without the pictures and Paxman), which is already available.

  26. Re:Does the iplayer copyrights issue apply to news by Anonymous Coward · · Score: 1, Informative

    There is a demand for watching those programs much beyond 7 days. So, why the 7 days limit on these programs [sic]?

    It's a condition of the approval granted by the BBC Trust after conducting a (legally mandated) public value test. (Although series stacking is permitted within a limit of 15%.)

  27. Re:amazing! by JohnBailey · · Score: 4, Interesting

    i didn't even know that brits had computers yet. it's fantastic news.

    Yep.. After inventing them, they kinda lost interest..

    --
    It is difficult to get a man to understand something when his job depends on not understanding it.
  28. Correct. by meringuoid · · Score: 1

    Just masquerade as an iPhone, and you get a nice high-quality .MOV file. You can download it and store it as long as you like, and play it using standard free software.

    --
    Real Daleks don't climb stairs - they level the building.
  29. Re:Does the iplayer copyrights issue apply to news by Toffins · · Score: 1
    You explain some of the bureaucratic, edict-from-on-high-driven processes involving the BBC Trust that led to the 7-day limit, but of course it's still a secretive process conducted behind closed doors, with a strong bias - no surprise given the disturbing conflicts of interest of some BBC Trust members - for the interests of rightsholders, commercial confidentiality, and the exclusion of members of the public (I mean what would they know - no experience of commercial broadcasting, unclean, noisy, ask awkward questions all the time, etc! :-)

    If the BBC ever dared to allow the public at large to participate directly and fairly in such debates, I am certain the public would not agree with the BBC Trust's assessment that there is insufficient "public value" in this case to extend the 7-days limit specifically for current affairs programs.

    programs [sic]

    "programs" - US spelling
    "programmes" - British spelling
    slashdot - a website where people from the US are in the majority, and people from Britain in the minority.

  30. Sigh, BBC ALREADY HAS A MULTI-OS STREAMING SYSTEM by Cougem · · Score: 1

    It's called the iPlayer. Check it out.
    http://www.bbc.co.uk/iplayer/

    I use it on my laptop with ubuntu all the time