BS.2076-2 tracking issue

[tomjnixon]

To Do

• parse version -- in BS2076-2 support #59

  • how to model this, perhaps BS2076Version(version: int) or OtherVersion(name: str)
  • warn if the version is not standardised
  • error if the version is not supported at all (as BS.2076 makes forward-incompatible changes)

• new audioObject parameters

  • positionOffset -- in BS2076-2 support #59
  • gain -- in BS2076-2 support #59
  • mute -- in BS2076-2 support #59
  • alternativeValueSet -- in BS2076-2 support #59
    • gain, mute, positionOffset
    • parse alternativeValueSetIDRef
      • check that they are unique within audioProgramme and audioContent
      • check that they are unique within the matched set of audioProgrammes and audioCntents
        • presumably it's ok to reference an audioObject more than once as long as only one alternativeValueSetIDRef is used?
  • parse gainInteractionRange and positionInteractionRamge and check the gain and positionOffset are within the specified bounds -- parsing is done, but the checking isn't really a v2 feature and is not done
  • check that all these are only specified in leaf audioObject -- in BS2076-2 support #59

• track uid to channel reference: -- in BS2076-2 support #59 (originally Added audioStreamFormat and audioTrackFormat bypass for audioTrackUID… #32)

  • don't add audioChannelFormatIDRef in AudioID -- in BS2076-2 support #59
  • add support in item selection (specifically channel_format_for_track_uid) -- in BS2076-2 support #59
  • check for version >= 2 (or empty document) -- in BS2076-2 support #59

• gain in DirectSpeakers -- in BS2076-2 support #59

• gain in HOA -- in BS2076-2 support #59

• gain in Matrix -- in BS2076-2 support #59

• extend importance handling to DirectSpeakers/HOA/Matrix? -- in extra BS2076-2 changes #71

• fractional time format -- in BS2076-2 support #59

• gainUnit everywhere -- this is a really bad idea but needed for compatibility -- in BS2076-2 support #59

  • warn about compatibility when using this -- a719ca4
  • check it's only specified in a -2+ document

• change objectDivergence azimuth default from 45 to 0 -- in BS2076-2 support #59

  • warn about using default in any version -- in BS2076-2 support #59

things that don't need implementing

• no need to do anything with authoringInformation

• coordinates of screen which have changed are not used

• could remove the "more than one audioProgramme; selecting the one with the lowest id" warning, but it's still useful

• maximum divergence is not validated

• HOA

  • order and degree now override equation (good), so we could remove the exception when equation is specified, but I don't see the need and would have to change it to a warning in -2 anyway

• dynamic metadata for matrix is probably not a priority

misc

• add a mechanism to warn about use of non-standardised features?

  • this is mostly quite obvious, so I don't think there's any need

• warnings above are based on this policy: warn when using features which:

  • can cause silent differences in behaviour when interpreted according to different versions -- i.e. software is not going to break because of a new attribute or changed default, but the output may be wrong

  • and can easily be replaced by equivalent metadata which doesn't have the same problem

[tomjnixon]

all done except for #65 and #66, which are small enough to track separately