In April, and 主播大秀 R&D launched what we believe is another world-first for a classical radio network: audio delivered directly to your web browser with completely lossless compression. We've brought together various technologies including MPEG DASH, FLAC compression, HTML5 and the Media Source Extensions to offer you a bit-perfect representation of Radio 3's live output, exactly as it left the studio. Radio 3 makes considerable investment in music performance and technical excellence, and this pilot enables the most transparent listening experience possible.
This post describes 主播大秀 R&D's involvement in bringing this pilot to our audiences.
Update - August 2017 - Google Chrome now supports this trial alongside Firefox. Details below.
We鈥檝e blogged about our work with , and it is our streaming technology of choice on which to innovate.Lossless audio is something we鈥檝e been talking about with other parts of the 主播大秀 for some time and here at R&D we had been doing some exploratory work around possible formats, but were unable to find a format totally suitable for delivery to the wide range of target devices the 主播大秀 serves.Open, royalty-free and well supported in both software and hardware, FLAC was an obvious choice for compression.
MPEG-DASH requires media to be encapsulated using either the , the format that underlies MP4, or MPEG2 Transport Stream. In reality only ISOBMFF has seen wide adoption, and that is the file format we use to distribute our existing video and audio streams. Unfortunately, until recently, there was no way to carry FLAC in a DASH-compliant manner. Additionally, without ISOBMFF encapsulation, we鈥檇 have to standardise, register and encourage implementation of a new bytestream format for use with the Media Source Extensions.
We shared our frustrations with some contacts from when they were in London last year, and they kindly agreed to do the standardisation work required. This has subsequently been published by Xiph as part of the latest release of FLAC in January 2017.
Technical Details
We are taking a raw uncompressed feed of Radio 3 from the project and we鈥檝e built a prototype that performs the FLAC encoding and ISOBMFF packaging in the cloud before forwarding the resulting stream to our standard media distribution platform.
Distributing uncompressed Radio 3 to the home would require bandwidth of around 1.5Mbit/s, considerably more than is typically used even for high quality audio distribution over broadcast or the Internet.To reduce the data rate to something more practical for distribution, we have traditionally used a compression codec, AAC, that delivers high quality audio at much lower bitrates.
For Radio 3, we offer a very high quality stream at a fixed rate of 320kbit/s for internet listeners, which is a significant saving both in terms of bandwidth and storage compared to the 1.5 Mbit/s original. Experts expect that, for the vast majority of material, this should be indistinguishable from the uncompressed source.
Lossy codecs such as AAC do change the audio signal, and there is the potential for noticeable artifacts with some material, whereas FLAC will always encode the signal transparently by employing a combination of channel decorrelation, linear prediction and residual and run-length encoding.
Our FLAC stream appears to average around 550kbit/s over an extended period, though this is highly variable, peaking up to around 1Mbit/s, and is dependant on the average complexity of the input. This is significantly lower than the uncompressed source, but some way off even the high bitrate AAC version.Several modern browsers now feature a built-in FLAC decoder and, once the audio data has been removed from its ISOBMFF wrapper, the decoder reconstitutes the original linear PCM samples bit-for-bit.
How To Listen
Mozilla have implemented the FLAC encapsulation specification provided by Xiph, and this is publicly available from upwards, on the desktop. Other browsers are considering support for FLAC in ISOBMFF and we hope that in time they will follow suit, and that mobile devices will also add the necessary functionality.
To demonstrate implementation on embedded devices, we鈥檝e also contributed a patch to the . This is available in 1.11 releases and above, which can be downloaded as pre-built binaries from the GStreamer website or built from source. We鈥檝e had great success playing the stream with a with a digital output board.We鈥檙e also in discussions with internet radio manufacturers, many of whom have expressed an interest in supporting lossless streaming.
Update - 11 August 2017
We noted above our hope that other browsers and mobile devices would add the necessary functionality to support our lossless streams, so we're really excited to report that, this week, Google have shipped a version of Chrome which does just that - Chrome 62. As well as desktop support, this brings Concert Sound to mobile devices for the first time via Chrome for Android. Chrome 62 should be available to all around mid-October, but the brave amongst you can try it out now using the bleeding edge build for Windows, OSX and Android.
Future Work
The purpose of the pilot is to determine whether listeners in real-world listening environments find any perceptible difference listening to the lossless stream compared to our standard high-quality streams, and whether they attribute value to that. We are also keen to find out how they are listening. , and feedback on your experience is really important to us.Whilst we currently have no plans to launch any service using lossless compression, data from this pilot will inform future strategy.AcknowledgementsWe鈥檙e really grateful to and for their efforts standardising FLAC encapsulation and providing support and early implementation in Firefox.
-
Broadcast and Connected Systems section
Broadcast & Connected Systems primarily focuses on how 主播大秀 content reaches our viewers through broadcast and Internet delivery. This involves the whole broadcast chain from playout, through coding and distribution to consumption on the end-user's device. Our work typically covers a period from now through to 3 years out from deployment.