a good start:
But... Example: missing H265/HEVC
timecodeEncoding? TimecodeCompressionCode? No...
MXF has time code in an MXF track, or SDTI, or ANC, or Line21
How to show the difference in a standard manner?
For MXF, we arbitrary choose %EssenceContainer%-%EssenceCompression%
without first part of UMID
IMF: sometimes several files for 1 track, several tracks
No specific place:
OP-xx, wrapping mode, channels layout, color space, chroma subsampling, transfer characteristics, HDR, BWF OriginatorReference, BWF History, BWF TimeReference...
EBUCore:technicalAttribute with MediaInfo field names (=arbitrary)
Not all for the moment, we selected some metadata requested by some users
Content per frame
Where? EBU updated EBUCore 1.8 specs with an acquisitionData part; FIMS?
Which strategy? parameter name then time slices? time slices then parameter name?
We offer both
First we map to MediaInfo format
Then from MediaInfo format to EBUCore/FIMS
Do we lose information during conversion? We think we don't.
But we use EBUCore:technicalAttribute (our field names)
Different "Muxing mode"
Several services in 1 stream
1 stream in 1 track, 2 half-tracks, 2 streams in 1 track...
Player support depends on such detail
How to show that?
trackId for such coupound data?
Good for prototyping!
If there is interest, better to have a standard EBUCore/FIMS element name
EBUCore and FIMS are similar
Why 2 formats?
Why not including EBUCore metadata in FIMS?
Extending EBUCore/FIMS (2)
"Many forms of Government have been tried, and will be tried in this world of sin and woe. No one pretends that democracy is perfect or all-wise. Indeed it has been said that democracy is the worst form of Government except for all those other forms that have been tried from time to time." (Churchill)