OSCON 2010 Brendan Quinn - Ingex:bringing open source to the broadcast industry 2010-07-21


Published on

Ingex is an open source project that can replace tens of thousands of dollars worth of equipment in TV studios and archive operations. Created in the BBC's research labs, we are now aiming to transfer it into the wider industry as a sel-sustaining open source project. We look at business models around partnerships, issues with licensing, and how to partner with non-software markets such as the TV production industry.

Published in: Technology
1 Comment
  • Hi there,

    I have some questions about this document and Ingex.

    slide 22: what do you mean by 'we can trademark a logo,.....' ?

    Is it possible to sell 'Ingex + Hardware' with a new product name ?

    Is it possible to brand ingex with a logo (different than Ingex logo ) ?

    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Lots of good business model stuff in Marten Mickos, Open Source Business Conference 2007: http://stephesblog.blogs.com/presentations/MySQL_OSBC_200705_handout.pdf
  • The definitive post on Open Core: http://alampitt.typepad.com/lampitt_or_leave_it/2008/08/open-core-licen.htmlSome of this came from Eric Raymond ”The Magic Cauldron” (1999) andFeller, “(Meta) business models for open source software”Cutter Business-IT advisory, vol 10 no 24, 2007
  • The definitive post on Open Core: http://alampitt.typepad.com/lampitt_or_leave_it/2008/08/open-core-licen.htmlhttp://www.slideshare.net/Alex.Osterwalder/business-model-canvas-poster
  • Thinking about which models apply to us leads to some interesting directions
  • Stallman on GPLv3: http://www.gnu.org/licenses/rms-why-gplv3.html
  • BT now often adopts open source software, according to a simple pyramid rule. “The bottom slice is commodity software; that should be open sourced,” he explains. “The middle slice is software that is unique to our industry; it is best to get that from a proprietary vendor, although they may themselves use open source code. The very top minitriangle consists of things that are unique to us, and that’s what we build for ourselves.” -- Jeremy Ruston, OsmoSoft (aqcuired by BT)We’re in that middle sliceIs this the beginning of a new trend in the industry..? Or does this mean we will fail? (Or both!)Is this telling us we need to move down (commodity video? What is that?) or go proprietary to succeed?Source for pyramid rule idea: http://www.information-age.com/channels/development-and-integration/perspectives-and-trends/1065692/accidental-open-source-hero.thtmlImage credit: http://www.flickr.com/photos/khalid-almasoud/2497604365/sizes/o/ (CCBY-NC-SA)
  • OSCON 2010 Brendan Quinn - Ingex:bringing open source to the broadcast industry 2010-07-21

    1. 1. Ingex: Bringing Open Source to the Broadcast industry<br />Brendan Quinn, Technology Transfer Executive<br />OSCON 2010<br />
    2. 2. Outline…<br />Quick overview of the BBC<br />What is ingex, why is it useful<br />The search for a business model<br />Building a partner programme in this industry<br />Potential issues around open source licensing<br />What’s next<br />
    3. 3. BBC Research & Development<br />The UK’s public broadcaster<br />Funded by a TV licence paid by every UK TV owner, plus income from commercial activities outside the UK<br />Income ~ £4 billion pa<br />R&D Labs<br />Pursuing research since 1924<br />150 engineers in London & Manchester<br />Create open standards with SMPTE, EBU, ITU etc<br />160 patents, 7 Queen’s Awards, 4 Emmys<br />~50 active technology licences<br />
    4. 4. Audience Experience<br />BBC Research Portfolio<br />Work Area<br />Media Management<br />Distribution<br />Production<br />Teams<br />1. Production Magic<br />1. Audience Exp <br />2. Prototyping<br />1. Automated Prodn & Media Mgt<br />2. Archives<br />1. Core technologies<br />2. Network Layer<br />3. Application Layer<br />Project highlights<br />DVB-T2<br />Video compression<br />Revenue protection<br />HD radio cameras<br />Service innovation<br />TV over internet<br />Ingex tapeless production<br />Tech standards<br />Archive storage & retrieval<br />Canvas platform & UI<br />Accessibility<br />Metadata<br />Dual screens<br />3D content creation<br />3D graphics<br />On-air-effects<br />HD production tech<br />Ambisonics & periphony<br />
    5. 5. We make cool things like…<br />Hand-held augmented reality<br />Keying without a blue screen<br />Pattern-based camera tracking<br />Real-time texture tracking<br />
    6. 6. What is Ingex?<br />Tapeless capture and recording system<br />Runs on commodity hardware and software<br />Standard PC with capture card<br />Linux operating system<br />Modular: can integrate with<br />Metadata syncing (catalogue integration, barcode scanner etc)<br />Automatic metadata tagging (Photo-Sensitive Epilepsy detection, shot detection etc)<br />Tape deck control<br />and more…<br />Creates MXF files<br />open standard for video exchange<br />Studio, Archive and card-reader versions (in various states of readiness)<br />
    7. 7. Ingex Archive<br /><ul><li> Ingests from SDI inputs
    8. 8. Tape deck control
    9. 9. D3 and DigiBeta support
    10. 10. Error channel input/storage
    11. 11. PAL transform decoder integration
    12. 12. Metadata catalogue integration using barcode scanner
    13. 13. QC integration
    14. 14. Ingex Player
    15. 15. DigiBeta dropout detection
    16. 16. Photo-Sensitive Epilepsy analysis
    17. 17. Output to LTO-3 tape:
    18. 18. uncompressed videowrapped in MXF OP-1A
    19. 19. h.264 browse format
    20. 20. Used in BBC Information & Archives since 2007
    21. 21. Users
    22. 22. BBC Information & Archives (since 2007)
    23. 23. Other UK and European archives trialling</li></li></ul><li>Ingex Studio<br /><ul><li> Takes input directly from cameras
    24. 24. SD: Tested 4 simultaneous camera feeds
    25. 25. HD: Tested 3 simultaneous camera feeds
    26. 26. (only limited by CPU/disk)
    27. 27. Simultaneous recording of all sources
    28. 28. No re-shoots after bad camera changes
    29. 29. Creates MXF files (OP-Atom)
    30. 30. Enables “production logging”
    31. 31. marking good/bad takes, noting script directions
    32. 32. Stores all logging metadata inside MXF/AAF stream
    33. 33. Creates browse/online versions in real time
    34. 34. Used on programmes such as:
    35. 35. EastEnders
    36. 36. Dragon’s Den
    37. 37. HD Jazz Shorts
    38. 38. The Bottom Line
    39. 39. BamZOOKi</li></li></ul><li>What we’re working on<br />Amore modular architecture<br />An “ecosystem” of components for tapeless video management<br />Support new hardware, system integrations<br />Enablepluginssuch as:<br />Automatic image detection<br />Face recognition, shot/scene detection<br />Object detection (boom mics, pictures, cars etc)<br />Metadata / workflow integration<br />Making the production process easier<br />Error detection/ correction (especially useful for archives)<br />Integration with other workflow tools, storage etc<br />Whatever else people can think of…<br />
    40. 40. Benefits of Ingex<br />Much cheaper than multiple tape decks and professional video tape<br />Saves huge amounts of time ingesting tape for edit<br />Can create files for any edit system (Avid, FinalCut Pro etc)<br />Don’t need to use proprietary storage<br />Can utilise ever-cheaper hard drives etc<br />Can easily scale to multiple recorders<br />Can expand and add features as they are delivered<br />Increases quality of programmes<br />
    41. 41. BBC Strategy for Ingex<br />To save the BBC money through making Ingex the preferred platform for ingesting content into tapeless workflows, using open standards and avoiding vendor lock-in<br />To ensure that we can continue to innovate upon the platform, enabling the BBC to realise the benefits of continued innovations from BBC R&D and from third-party providers<br />To give the benefits of the Ingex system to the broadcast and production community in the UK and around the world, driving down cost and enabling innovation through promoting open, standards-based media workflows<br />
    42. 42. Long-term vision<br />Ingex as the “beach-head” for creating an IP-based studio suite<br />File-based production using commodity hardware<br />MPEG over IP rather than over SDI cables etc<br />From acquisition through editing to playout and archive, all IP & files<br />Forms the basis of a disruptive technology in broadcasting<br />Bring studio-quality tech to the hands of non-traditional producers:<br />Schools / universities<br />Very small production companies (YouTube publishers etc)<br />Companies outside broadcast industry<br />Internal/external training, conferences, promotions, …<br />To achieve this, we have to make Ingex a “platform” rather than just a product<br />
    43. 43. Making it sustainable<br />We want the Ingex project to be self-sustaining<br />Integrate new features from developers inside and outside the BBC<br />Handle packaging, documentation, support<br />Let the researchers go and invent the next new thing<br />How to do that?<br />Appeal to volunteer developers<br /><ul><li>Difficult in this industry
    44. 44. Universities, community television?</li></ul>Appeal to charitable donors<br /><ul><li>Anyone want to give us some money?</li></ul>Do something that covers our costs<br />So we need some kind of business model…<br />
    45. 45. The broadcast production “value chain”<br />
    46. 46. The broadcast production “value chain”<br />Potential partners / customers<br />
    47. 47. Open Source Business Models - 1<br />
    48. 48. Open Source Business Models – 2<br />Also see “Business Model Generation” – Alexander Osterwalder<br />www.businessmodelgeneration.com<br />
    49. 49. So which model(s) are we trying?<br />
    50. 50. Support model: the Ingex “ecosystem”<br />
    51. 51. Ingex Solutions<br />Controls / coordinates architecture and development work<br />Governed by Ingex Steering Group (partners and key customers)<br />Provides 3rd-level support to partners and customers<br />Provide internal support within the BBC<br />But only where an external supplier can’t meet the need<br />Manages partnership programme<br />Certifies new partners<br />Creates/commissions training and certification materials<br />Runs showcase website<br />Manages user community (forums etc)<br />Runs Ingex community events<br />Webcasts, phone/IRC/real-life meetings, conferences<br />For partners and customers<br />
    52. 52. Building a partner scheme<br />If we want partners to work with us, they need to know what’s in it for them<br />Variety of potential partners:<br />Development partners<br />OEM partners<br />Embed Ingex in other systems<br />Wrap Ingex in hardware and sell it<br />Complementary product vendors<br />eg face recognition plugin<br />Hobbyist / hacker developers<br />Production companies<br />Technical (specialist interfaces)<br />Non-technical (just provide support to their customers)<br />Open source consultancies that want to branch out into broadcast industry<br />
    53. 53. Building a partner scheme<br />We can’t stop anyone from offering services as an integrator, hardware partner etc<br />But we can trademark a logo, and license use of the logo according to criteria<br />“Certified Ingex support partner”<br />“Certified Ingex hardware partner” etc<br />Means we have to work hard to build a brand and make it worthwhile for partners to sign up<br />Partners are sometimes uneducated in the ways of open source<br />Or even software-based systems generally…<br />(Many customers are uneducated as well, but that doesn’t matter as much for us)<br />
    54. 54. Building a partner scheme<br />Offers to partners<br />Early access to roadmap<br />Input to roadmap<br />Closer access to developers<br />Advanced (level 3) technical support<br />Marketing support (via our website, events, promotional material)<br />Licence to use partner logo<br />Requirements of partners<br />Adhere to hardware, software, business guidelines<br />Best practice partner schemes<br />Alfresco, SugarCRM<br />
    55. 55. Licence propagation issues<br />
    56. 56. Licence propagation…<br />
    57. 57. Licence propagation…<br />
    58. 58. Licence propagation…<br />
    59. 59. Licence propagation…<br />
    60. 60. GPL / LGPL overview – our options<br />“Deriving from” GPL means we have to GPL our project as well<br />It’s a fuzzy area, not really tested in court, so best to be conservative<br />We retain rights to our own code so we can re-licence if necessary<br />Within the constraints of other licences<br />We want to allow others to build on top of our systems, egface recognition software<br />Options:<br />We can ensure that we keep x264 optional, and the tool should work fine without it (usingonly pure LGPL components)<br /><ul><li>This means following LGPL compliance rulessuch as http://www.ffmpeg.org/legal.html, egdynamic-linking to ffmpeglibraries</li></ul>Build a wrapper library to allow use of FFmpeg or other encoder libraries<br /><ul><li>Removes “derivative” status – maybe!</li></ul>Keep it GPL, don’t work with people who don’t like it<br /><ul><li>Limits capabilities of our software</li></li></ul><li>Choosing the right licence<br />Try to make the licence decision as early as possible<br />If you’re building on top of another system that is GPL or LGPL, you might not have much choice<br />But you should still make the decision carefully<br />Think about why you are releasing your code<br />“Open Source” is not necessarily “GPL”<br />Many commercial-friendly licences are available<br />Apache Licence, Mozilla MPL, BSD licence<br />Opensource.org lists them all including pros and cons<br />You could write your own (but please don’t!)<br />There’s usually a way to use a regular OS licence<br />Google VP8 codec example<br />People like http://www.softwarefreedom.org/ can help you to choose/manage<br />
    61. 61. Patents<br />Are completely separate from questions about open source or not – they’re about the algorithms, not the implementations of them<br />Anyone who sells a box that contains patented code (eg h264 codecs) must adhere to patent rules<br />Mostly it’s easy to conform to the rules…<br />Simple payment per encoder/decoder pair<br />Patent holders group together in pools, eg MPEG LA<br />Often there are minimum limits which you don’t meet unless you sell a LOT of “devices”<br />… but you have to be careful<br />For example, MPEG LA doesn’t necessarily licence allof the patents you need for MPEG4<br />
    62. 62. Osmosoft Pyramid rule<br />Unique to company – proprietary, internal<br />Unique to industry – buy from a proprietay vendor(which may in turn use open source)<br />Commodity – use open source<br />We’re breaking this model – are we pioneers or fools?!<br />
    63. 63. The start of a full open source stack for video production<br />3D animation<br />Web editing, publishing, ad management<br />3D animation<br />
    64. 64. The story continues…<br />Research version reaches 1.0.0 late July 2010 (ie next week)<br />Website (www.ingex.tv) launching at International Broadcasting Convention September 2010<br />Ingex Solutions team has started work on managing ongoing releases, documentation, installers etc<br />Working on internal BBC projects in both Archives and Studio deployments<br />Still looking for partners around the world…<br />Maybe you are interested?<br />
    65. 65. Thanks<br />Questions, suggestions, feedback very welcome!<br />http://ingex.sourceforge.net/<br />http://www.ingex.tv/ (coming soon)<br />Brendan.Quinn@bbc.co.uk<br />Image credits:<br />Khalid Al Masoudhttp://www.flickr.com/photos/khalid-almasoud/2497604365/ <br />