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
It is foreseeable that many newer standardized codec will be registered in mp4ra first (like v3c?), and doing so will also be backward compatible with the legacy codec supported by QuickTime 7 and the previous. This can be used as a mitigation measure for some encodings that were carried over before Matroska was standardized.
The text was updated successfully, but these errors were encountered:
However, its description is more inclined to be understood as the legacy coding format supported by QuickTime, rather than containing new codec recognition for mp4ra registration.
Yes, because the idea is to have proper mapping for each codec, using all the features available in Matroska. Not a wrapper of other codecs. For example you can put H264 as a Quicktime codec in Matroska, but noone is doing that (and it will likely not play in many places).
It is foreseeable that many newer standardized codec will be registered in mp4ra first (like v3c?), and doing so will also be backward compatible with the legacy codec supported by QuickTime 7 and the previous. This can be used as a mitigation measure for some encodings that were carried over before Matroska was standardized.
The text was updated successfully, but these errors were encountered: