Ogg objections (2010)
hardwarebug.org
Ogg objections (2010)
1–5 of 5 posts
Re: Ogg objections (2010)
#2 Generality
Overhead
Latency
Random access
Timestamps
Complexity
I'd like to add one more:One of the worst examples of branding I've ever seen from an open source project. Ogg? It sounds kind of like a portmanteau of odd and egg. Who wants to use that?
Re: Ogg objections (2010)
#3"Streaming" can also mean "playback of and/or seeking within a partially downloaded file". It's awfully nice to start watching that multi-gigabyte video within seconds, rather than minutes or hours and be able to rewind and fast-forward through the parts that are already on (and continue to be delivered to) your system.
Re: Ogg objections (2010)
#4Re: Ogg objections (2010)
#5The good point is that the rest is simple and relatively flexible. 4 bytes as a number of tags each with a 4 byte length. Definitely excessive and perhaps should have some flag for different versions. 1, 2, 3, and 4 byte lengths and count. Keys being limited in the spec to ASCII printable is a downside but since it's utf8, 0x3d (the equals sign =) would still work as the key-value separator. The spec also says that they should be case insensitive which would make the utf8 comparisons harder.