Add ADM metadata to ouput files, when rendering (production) ADM to channel-based configuration

[WernerBleisteiner]

It'd be very valuable, in order to avoid ambiguties, if any rendering of mostly rather complex production ADM files into channel-based loudspeaker setups acording to BS.2051, that the respective ADM metadata of the target loudspeaker set-up will be added in axml and chna.
Legacy equipment may not benefit directly from that. But inserting ADM metadata will enable workflow processes, like gaining technical parameters for archive metadata, control encoding etc.

[tomjnixon]

I absolutely agree; I thought there was already an issue for this, but apparently not.

We would have to work out exactly what the metadata would be. There would be an audioProgramme with a selection of fields from the input file (to be determined). I'm not sure exactly what the audioContent and audioObject would be called though; probably something generic like "rendered content".

[WernerBleisteiner]

Thanks @tomjnixon
Yeah, I'll have a look into possible use cases and try to find some suggestions.