feature content distribution
It is a given today that broadcasters will need to take their television news content and repurpose and repackage it for other platforms. Certainly this will be for the web, and increasingly broadcasters are developing special services for tablets, like the iPad and Android devices, as well as for varied smartphone platforms. Scott Matics, product manager at Grass Valley, reports.
Preparing content for multi-platform delivery
hese services may be a way of building and retaining audience loyalty through the ubiquity of the brand. Now, new revenue opportunities are developing, including highly tailored advertising and subscription models, which make what were originally secondary outputs for the content into primary delivery points which demonstrate a real return.
T
Whatever the business model, though, it hardly needs stating that, in today’s highly competitive world, the delivery of content to multiple platforms has to be accomplished with little or no increase in head count or operating expenditure. How can this be reconciled with the need to actively repurpose the content, both editorially and technically?
The material itself may need to be re-edited. Some stories may be better run longer online, shorter on mobile devices. There may be rights issues: a
MediaFUSE: the original version was designed as a companion product to the Grass Valley Ignite integrated production system, and a significant number of broadcasters worldwide are using this
combination. But in recognition that the requirement for repurposing is common to all broadcasters, whatever
production system they are using for news, Grass Valley has developed an open version of the same technology, MediaFUSE FX.
broadcaster could have access to a sports event for broadcast highlights but not the Internet.
Technically, each output will require a different format. Each device has its own optimum resolution, and each platform has a preferred codec and wrapper. Apple’s choice is H.264, while Google and many others still embrace Flash. In the future HTML 5 may take the problem away, which only serves to underline the challenge: this is a constantly shifting situation. Finally, publishing on other platforms is not just about transcoding the essence. It has to be combined with the appropriate metadata. First, this is vital to tell the downstream systems how to interpret the data stream. Second, packed metadata also drives search engine optimisation, ensuring that casual viewers will find your version of the story rather than that from your competitor.
The trend in television newsrooms is to hand sole responsibility for a story to the journalist, giving them the tools to edit and publish it on the desktop. The reasons that make this the logical solution - the journalist knows best how to tell the story - make it equally logical to hand them the responsibility for distributing it to other platforms.
The key question is how technology can provide the underlying platform which allows the journalist to distribute to every appropriate
50 l ibe l march/april 2011 l
www.ibeweb.com
platform, without adding significantly to the workload which would divert him or her from the task in hand: identifying the next big story.
MediaFUSE
The Grass Valley solution is a proven product called MediaFUSE. The original version was designed as a companion product to the Grass Valley Ignite integrated production system, and a significant number of broadcasters worldwide are using this combination. But in recognition that the requirement for repurposing is common to all broadcasters, whatever production system they are using for news, we have developed an open version of the same technology, MediaFUSE FX. This uses industry standard interfaces to connect with other devices, and provides broadly the same functionality, minus the automated content replacement in the live stream.
MediaFUSE ingests the video for each story then prompts the journalist to add the required additional information. Much of this will come from pre-prepared templates, with the journalist simply adding the text version of the story. Categorisation, standard background information and publishing details are added automatically to pre-populate the metadata.
Tools in the workstation allow the
Continued on Page 52.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68