The info on what the streams are and how they relate can be conveyed via PBCore, i.e.:
pbcore:instantiationTracks=1 video track, English and Spanish audio, Director's commentary audio ... pbcore:instantiationEssenceTrack[0]/pbcore:essenceTrackType=Video ... pbcore:instantiationEssenceTrack[1]/pbcore:essenceTrackType=Audio pbcore:instantiationEssenceTrack[1]/pbcore:essenceTrackLanguage=eng ... pbcore:instantiationEssenceTrack[2]/pbcore:essenceTrackType=Audio pbcore:instantiationEssenceTrack[2]/pbcore:essenceTrackLanguage=esp ... pbcore:instantiationEssenceTrack[3]/pbcore:essenceTrackType=Audio pbcore:instantiationEssenceTrack[3]/pbcore:essenceTrackLanguage=eng pbcore:instantiationEssenceTrack[3]/pbcore:essenceTrackAnnotation=Director's commentary ... The current FFmpeg parser wouldn't be able to extract things like annotations, but it was only targeting the intrinsic metadata. The informational metadata will be extracted by things like XMP parsers. Regards, Ray On July 22, 2014 at 7:39:12 AM, Nick Burch ([email protected]) wrote: > On Tue, 22 Jul 2014, Ray Gauss wrote: > > This is a few months old but I've been looking at this recently and > > since we're unlikely to move to a structured metadata store in the short > > term I've come up with what I think is an interim solution [1] that > > essentially allows nesting through XPath-like syntax: > > > > stream[0]/field1=someValue > > stream[0]/field2=otherValue > > stream[1]/field1=yetAnother > > stream[1]/field2=andSoOn > > Doesn't that loose information (from some formats at least) on what those > streams are, and how they relate to each other? > > It does have a certain simplicity that I like, and should be fairly easy > to write some simple wrappers to let you get access to per-stream stuff > easily > > Nick
