Lib-Ray video standard: using Google/On2's VP8 video codec
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."
E-mail Print r 5   30 Comment(s) http://osne.ws/jy1
Thread beginning with comment 515114
To view parent comment, click here.
To read all comments associated with this story, please click here.
Digitante
Member since:
2012-04-21

"I'm currently working on the subtitle format (going to be SRT now, in separate files)


This I want some more clarification on: is there some specific reason for those files to be separate instead of inside the Matroska-container? "

Easy-patching. I mentioned that in the SDHC article.
Also -- transparency to the end user.

I personally always place cover-images, cast-details, description of the title, all the various subtitles etc. inside Matroska-containers.


It's true that Matroska supports that, but it makes it more opaque to the end user.

Also, do you plan to support italics, bold and non-white text in subtitles?


Those are the advantages of the Kate ("OggKate") format that I originally specified. In fact, it can handle vector graphics as well.

However, SRT is a far more popular format, and you're the first person who's seen the benefit of the extra features in Kate that I have heard from (though admittedly, that has been a small sample so far).

Will give it further thought.

E.g. Raspberry Pi would hardware-wise be perfectly capable of doing that up to 1080p resolution as the SoC does support VP8-decoding, the only limiting factor is the drivers that do not at the moment have support for that.


Interesting claim. Can you back it up?

The queries I made before in tech forums led me to believe this was not a realistic expectation. In fact, it appeared that no VP8 hardware support existed in any SoC that could also handle the 1920x1080x30fps 12-24mbps video through-put.

However, I'd be very happy to see it work. A player based on a low-cost open hardware platform like RPi would be extremely attractive.

I suspect writing the support code for it is out of my depth, however. I would need to find someone capable of doing that.

Reply Parent Score: 2

WereCatf Member since:
2006-02-15

However, SRT is a far more popular format, and you're the first person who's seen the benefit of the extra features in Kate that I have heard from (though admittedly, that has been a small sample so far).

Will give it further thought.


It just happens that in most cases such functionality isn't taken advantage of in any meaningful ways, but I have also seen cases where they have been used to atleast some advantage. For example, hearing-impaired subtitling could present sound-effects and such with different characteristics than speech, thereby making it easier to follow and clearer.

Interesting claim. Can you back it up?

The queries I made before in tech forums led me to believe this was not a realistic expectation. In fact, it appeared that no VP8 hardware support existed in any SoC that could also handle the 1920x1080x30fps 12-24mbps video through-put.


http://wiki.webmproject.org/hardware/arm-socs lists some of the SoCs that are already shipping and which support VP8. There's more of them coming in the future, and I can't remember which manufacturer it was, but someone was claiming their next chip would do 4k resolution decoding. Ie. there's quite good support now and it's only getting better in the near future.

RPi uses the Broadcom chip mentioned on that list. It does not mention the maximum bandwidth the SoCs can handle since such details are usually only given after you've signed NDA, but atleast in the case of BCM2835 I think I saw a Broadcom engineer claim it can do up to 24mbps. (I could remember wrong so don't take it as a fact, but that's how I remember it. You could possibly just try and ask them if you're interested.)

However, I'd be very happy to see it work. A player based on a low-cost open hardware platform like RPi would be extremely attractive.


The SoC is not open hardware, none of them are, so that could pose a problem. I am not aware of a single good-quality SoC that wouldn't require you signing NDA in order to gain full programming information and tools.

I suspect writing the support code for it is out of my depth, however. I would need to find someone capable of doing that.


I doubt that would be an issue once you settle on the spec, there's always someone out there to aid. I have been doing some coding here and there, including a few kernels and such, but I'm really rusty these days and I'm better at just bitching about things and trying to appear smarter than I actually am, so I wouldn't likely be able to aid much.

Reply Parent Score: 3