At 17:23 04/02/2007, you wrote: >On 2/2/07, Sean Dillon <<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]> wrote: >> <type> and <url> would obviously be mandatory. Are there any views on >> whether <bitrate> and <network> should be optional or mandatory? >If bitrate is include how would you define variable and constant >bitrates? Or is there actually a need to define this? > > >[Might make sense if <network> always defaults to unicast unless stated?] > >Bitrate: Sean, your point about variable bitrates makes sense. That adds >complexity, I suspect. For example (and sorry for using VR as an example), our >Windows Media stream is a total of 132k, of which 128k is audio. Yet it is an >intellistream which will knock all the way down to 20k if it needs to. What do >I put in the bitrate there? 132k? 128k? 20-128k? (Our Real streams are >similar: 8k up to 32k). > >Similarly, our Ogg Vorbis streams are variable, we quite one as "around 20k" >and one as "around 160k".
James, Presumably the purpose of the bitrate field would be purely informative? e.g. to allow the end user to choose between low and high bitrate streams to suit the bandwidth of their connection. If so, the maximum bitrate would be sufficient. Chris _______________________ Chris Newell Lead Technologist BBC Research Kingswood Warren Tel: +44 (0)1737 839659
