<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="/blogs/shared/nolsol.xsl"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>

<title>
BBC Internet Blog
 - 
Phil Layton
</title>
<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/</link>
<description>Staff from the BBC&apos;s online and technology teams talk about BBC Online, BBC iPlayer, and the BBC&apos;s digital and mobile services. The blog is reactively moderated. Posts are normally closed for comment after three months. Your host is Eliza Kessler. </description>
<language>en</language>
<copyright>Copyright 2012</copyright>
<lastBuildDate>Fri, 04 Jun 2010 11:03:14 +0000</lastBuildDate>
<generator>http://www.sixapart.com/movabletype/?v=4.33-en</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 


<item>
	<title>Questions around surround sound on Freeview HD</title>
	<description><![CDATA[<p>Some people have asked why we don't currently use Dolby as the sound solution for <a href="http://www.freeview.co.uk/HD">Freeview HD</a>. As always there's a quite complex reason behind this decision so I thought it would be a good idea to do a post on it. </p>

<p>The BBC is required to provide an audio description service on BBC HD. Typically<br />
there are two to three programmes everyday which are audio described. In order to achieve this we have to use the HE-AAC/AAC audio codec present in Freeview HD receivers. The main audio is coded as AAC-LC and only the audio description is encoded as HE-AAC. There is a very common restriction in the silicon devices (which underpin all receivers) that only a single type of audio decoder can be working at any one time. So, the main audio and the audio description must use the same encoding family in order for them to be successfully combined together at the receiver. The current bitrates used for the AAC-LC audio are entirely commensurate with those that could have been used for a Dolby AC3 (Dolby Digital) solution.</p>

<p>In order to help manufacturers with their product development example streams with AAC-LC/HE-AAC audio description have been freely available to manufacturers since October 2009.</p>

<p>I've also been asked why we don't switch to using Dolby during the programmes which do not carry audio descriptions. Unfortunately the restriction I've just described around the ability only to have a single audio codec working at any one time means that changing audio codecs at programme junctions results in disruption to the decoded audio. This is because the receiver needs to detect the use of a different audio codec, load into its <a href="http://en.wikipedia.org/wiki/Digital_signal_processor">DSP</a> the firmware for decoding that audio codec and then start decoding the audio. This disruption is acceptable when tuning between different services but not acceptable at programme junctions. Even if there are some decoders that can run different audio decoders concurrently it would not be possible to mandate the use of these specific solutions.</p>

<p>Changing the characteristics of the broadcast stream at programme junctions can be very difficult to achieve reliably in a broadcast head-end as many different systems need to be synchronised. It therefore needs very comprehensive monitoring to ensure the operation is reliable. Experience shows that some receivers can also have issues detecting such<br />
changes unless the user tunes away and then reselects the service.</p>

<p>So the answer does lie in the need for the receiver to either transcode to a suitable format such as Dolby AC-3 or <a href="http://en.wikipedia.org/wiki/DTS_%28sound_system%29">DTS </a>or to output multi-channel linear <a href="http://en.wikipedia.org/wiki/PCM">PCM</a>. Earlier versions of the UK <a href="http://www.dtg.org.uk/dtg/objectives.html">D Book</a> were only able to recommend the presence of transcoding. But now that transcoding solutions are becoming available the UK is no different from all other European standards. No doubt receiver manufacturers are working hard to incorporate these into their products.</p>

<p>However to help manufacturers develop products sometimes it is necessary to mandate certain features only after a suitable period has elapsed after publication in the D Book. So transcoding will become mandatory in all product launched after April 2011.  In the meantime some manufacturers have already shown the capability of uploading this into existing deployed designs.</p>

<p>The use of an <a href="http://en.wikipedia.org/wiki/HDMI"></a>HDMI interface provides manufacturers with a choice of transcoding to Dolby AC-3 or DTS or delivering multi-channel linear PCM. The use of a <a href="http://en.wikipedia.org/wiki/Spdif">SPDIF</a> interface requires a transcoding operation as it cannot support the bitrates required for multi-channel linear PCM but can support bitstream formats.</p>

<p>Version 6.2.1 of the D Book requires receivers to support both the AAC (including<br />
HE-AAC) and Dolby EAC3 (Dolby Digital+) formats. It is possible that the EAC3 format may also provide a future means for delivering receiver mix audio description.</p>

<p>These things are never straight forward but I hope that this answers the questions and gives you a little insight into why such decisions are made.  </p>

<p><em>Phil Layton is Project Manager Digital Service Development BBC Research & Development. </em></p>]]></description>
         <dc:creator>Phil Layton 
Phil Layton
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2010/06/questions_around_surround_soun.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2010/06/questions_around_surround_soun.html</guid>
	<category>Freeview HD</category>
	<pubDate>Fri, 04 Jun 2010 11:03:14 +0000</pubDate>
</item>


</channel>
</rss>

 
