Linked by David Adams on Fri 20th Apr 2012 01:31 UTC, submitted by fsmag
Multimedia, AV "When I started working on a no-DRM, open-standards-based solution for distributing high-definition video on fixed media ('Lib-Ray'), I naturally thought of Theora, because it was developed as a free software project. Several people have suggested, though, that the VP8 codec would be a better fit for my application. This month, I've finally gotten the necessary vpxtools and mkvtoolnix packages installed on my Debian system, and so I'm having a first-look at VP8. The results are very promising, though the tools are somewhat finicky."
Permalink for comment 514927
To read all comments associated with this story, please click here.
WereCatf
Member since:
2006-02-15

First off, here's two links that were not included in the submission and that I think should have been: http://lib-ray.org/ explains what Lib-Ray is, and http://lib-ray.org/spec.html explains what the spec is like.

Now, my own take on this: it's a generally rather good idea, but the spec is not well-defined enough.

Problem one: there is no file defined with a clear enough name that would immediately indicate that the media contains a Lib-Ray product. "meta.cnf" is just too ambiguous, I've already seen ".cnf" -files used by multiple different applications and games, and "meta" is.. well, clearly meta. A more clearly-defined file present on the media should be included and would make it very easy to determine if there is a Lib-Ray product on the media or on another location. My suggestion would simply be "Lib-Ray.media" - file, containing information such as what codecs are used, number of titles, chapters, audiotracks and so on included, and most importantly, the Lib-Ray specification version the media adheres to so that the specification can in the future be extended without breaking support for older media.

Second problem: the specification defines a combination of VP8/Vorbis as mandatory, whereas a much more flexible and future-proof approach would list VP8 - and Vorbis - support in the player mandatory in this version of the specification and the VP8/Vorbis combination the default, but would allow for the use of different codecs at users' own discretion. This would obviously give users some flexibility on these matters if they have one or another specific need for using a different combination of codecs, and it would make it simple to extend the spec in the future; you'd only need to bump the spec version up and define a new set of codecs that must be supported in order to be compliant with that new spec.

Basically there's plenty things in the spec that are mandated instead of mandating the support for atleast those values presented and making them the default, but allowing for values outside that range in future versions of the spec.

I am also somewhat uncertain if the way the menus are done is all that good and flexible enough, but I suppose that remains to be seen. One thing that springs to mind at first is that I do not see anything that would allow for multiple full titles, each with their own subtitle and audio settings, on one media. Personally I would like such a feature to be added to the spec, it would allow for the creation of collections where the titles are in one way or another related to each other, but do not share the same characteristics when it comes to audio and subtitling.

Reply Score: 5