I would add speex as a codec for human voice content. I can pack about an hour worth of audiobook into ~7mb using speex, and have it fairly nice. Gstreamer on sugar plays .spx files just fine. They are an ogg varient and developed by xiph.<br>
<br>Ideally we could use the 1500+ hours of Human Read audiobook that Librivox has produced and stored on <a href="http://archive.org">archive.org</a> in some of our deployments.<br><br>--Seth<br><br><div class="gmail_quote">
On Sun, Feb 1, 2009 at 10:21 PM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
SJ gave me a heads up recently, and quite timely, about the need to<br>
discuss what formats we can support on the XS and the XO.<br>
<br>
My high level goals are that<br>
<br>
1 - Local teams are able to include enormous amounts of gorgeous<br>
content coming from untold number of sources on the XS and XO. The<br>
teams handling deployments get to pick and choose content from many<br>
sources repositories repositories.<br>
<br>
2 - The content is in such a format that we can serve it from the XS<br>
to XOs (and other clients) and we can also provide it as a bundle (or<br>
similar) so you can download it to the XO and take it with you.<br>
<br>
3 - What we do is interoperable with the rest of the world as it<br>
exists. (ie: use established standards)<br>
<br>
In general, this means that we need content to be in the simplest,<br>
most standard formats possible. Project Gutemberg clearly gets this.<br>
ASCII, HTML, PNG, SVG and DublinCore metadata are my friends.<br>
Super-simple package formats based on them (think IMS-CP) make me<br>
happy.<br>
<br>
The XS is going to grow a "browse-and-download library content" leg<br>
sometime soon. It will be a facility that knows how to unpack and<br>
index the IMS-CP and SCORM metadata (which is all DublinCore stuff),<br>
and it'll be transparent to users how to browse, search and use any<br>
such content placed on the XS.<br>
<br>
It's about the content. No special client software, no special server<br>
software. This levels the ground for all the projects -- so you don't<br>
need to worry that your outrageously fantastic content won't be used<br>
because the player ain't sexy. Local teams don't have to worry about<br>
the burden of a particular content requiring special software.<br>
Teachers don't have to worry about the confusion of a different<br>
content player.<br>
<br>
My plan is to make that XS feature so that it can also automagically<br>
make a bundle for the XO to download -- after all, happiness is a warm<br>
bundle ( <a href="http://blog.laptop.org/2009/01/13/happiness-is-a-warm-bundle/" target="_blank">http://blog.laptop.org/2009/01/13/happiness-is-a-warm-bundle/</a><br>
) :-)<br>
<br>
This also means that XS and XO can leverage the large existing pools<br>
of IMS-CP and SCORM content. And that any content you prepare for<br>
OLPC, you are also preparing for the world...<br>
<br>
That's my plan at least :-) -- no plan ever survives contact with reality.<br>
<br>
cheers,<br>
<br>
<br>
<br>
<br>
m<br>
--<br>
<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a><br>
<a href="mailto:martin@laptop.org">martin@laptop.org</a> -- School Server Architect<br>
- ask interesting questions<br>
- don't get distracted with shiny stuff - working code first<br>
- <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br>
_______________________________________________<br>
Library mailing list<br>
<a href="mailto:Library@lists.laptop.org">Library@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/library" target="_blank">http://lists.laptop.org/listinfo/library</a><br>
</blockquote></div><br>