4 ms·
But then you're not really naming it after the codec. Instead you create a standard that mandates container X, support for video codecs Y[, ...], and support f
by aepiepaey 9y ago
But then you're not really naming it after the codec.
Instead you create a standard that mandates container X, support for video codecs Y[, ...], and support for audio codecs Z[, ...]. Then you can document a player/device as supporting that standard and also name video files after it.
- WhitneyLand 9y agoThank you, that’s correct. I was questioning an argument you made in a way that was not technically analogous. The gist of the comment should have referred only to what I brought up, which as you point out is a minimum simple standard for packaging and contents as it could relate to a file extension.