<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 2012-01-21, at 9:40 AM, Michael T. Dean wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">A planned change to the schema will allow multiple media files for any<span class="Apple-converted-space"> </span><br>given recording or video.</span></blockquote></div><br><div>Ooooo, that's a welcome development. Can you tell more? Like, when it might arrive.</div><div><br></div><div>In particular, will this tie together streaming with recording metadata? Right now the stream APIs are oriented around filenames while recording APIs want chanid/starttime. When you have a stream there's no obvious way to know what recording it pertains to without keeping your own filename -> metadata structure. That's easy enough but it feels like there's a missing link.</div><div><br></div><div>- George</div></body></html>