You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What was the script that generated the content (reference)
What was the ffmpeg/x26x version that was used
any other information that is relevant to understand the origin of the content (machine, etc.)
This information is preferably added to the Content MPD or the content MPD references the MPD. For example we can use the @value of the AssetIdentifier
The text was updated successfully, but these errors were encountered:
@haudiobe
This concerns the information used to generate the content. The information is there to recreate the content if needed.
We have the date it was generated.
@haudiobe What information are you looking for? Can we add a field to the json database to capture any additional information needed. @haudiobe What information are you looking for?
We already note the version of the GPAC tool used.
2022-06-12 meeting: Deferred for video. The Mezzanine file and version is captured along with the GPAC version and the date. The concern is we don't know how the content was generated e.g. the script or exact command line used. Ideally there would be information in the MPD if we can come up with a way to do it in the future. Issue is the audio content/externally generated content. Revisit for audio when we are ready to release and can determine if this is still an issue.
This information is preferably added to the Content MPD or the content MPD references the MPD. For example we can use the @value of the AssetIdentifier
The text was updated successfully, but these errors were encountered: