https://wiki.xiph.org/api.php?action=feedcontributions&user=Pmsyyz&feedformat=atomXiphWiki - User contributions [en]2024-03-19T04:49:41ZUser contributionsMediaWiki 1.40.1https://wiki.xiph.org/index.php?title=Vorbis_Hardware&diff=9159Vorbis Hardware2008-07-06T22:06:57Z<p>Pmsyyz: link</p>
<hr />
<div>This is a list of hardware of all categories, from chipsets to ready-to-use products, that support Ogg [[Vorbis]].<br />
<br />
Hardware support status for Ogg Vorbis is relatively good, you can choose between a huge amount of mobile flash players, many HDD based players and a respectable number of Hi-Fi components. More than 50 different companies offer a total of more than a hundred products for virtually every application, there is even a knife that can play Ogg Vorbis now ;-). If you can't find a suitable player come back next week -- new products are added on a weekly basis, as many companies are working to support Vorbis on their hardware.<br />
<br />
If you know of any hardware or projects that are not yet mentioned here, please add them to the list. More (outdated) hardware info can be found at [http://www.xiph.org/ogg/vorbis/hardware.html vorbis hardware page].<br />
<br />
== Consumer products ==<br />
<br />
These players support Ogg Vorbis either out of the box or after a firmware upgrade.<br />
<br />
* [[PortablePlayers]]: mobile players<br />
:[[PortablePlayers#Flash_Memory_Storage|Flash Memory Storage]]<br />
:[[PortablePlayers#Harddisk_Storage|Harddisk Storage]]<br />
:[[PortablePlayers#CD.2FDVD_Audio_Players|CD/DVD Audio Players]]<br />
:[[PortablePlayers#Mobile_Phones|Mobile Phones]]<br />
:[[PortablePlayers#Others|Others]]<br />
* [[StaticPlayers]]: installed players<br />
:[[StaticPlayers#Hi-Fi_components|Hi-Fi components]]<br />
:[[StaticPlayers#Car_Audio|Car Audio]]<br />
:[[StaticPlayers#Media_Storage|Media Storage]]<br />
:[[StaticPlayers#Internet radio devices|Internet radio devices]]<br />
<br />
For hardware that is able to run third-party software (such as PDAs and video game consoles), please visit [[VorbisSoftwarePlayers]].<br />
<br />
== Non-consumer products ==<br />
<br />
This is Vorbis in Silicon, meaning chips from which actual consumer products can be built.<br />
<br />
;[http://www.vlsi.fi/ VLSI Solution Oy]: VLSI provides two Ogg Vorbis capable chips.<br />
<br />
:[http://www.vlsi.fi/vs1000/vs1000.shtml VS1000] is an Ogg Vorbis decoder and controller chip based on a 16-bit DSP.<br />
<br />
:VS1053 is an external audio codec based on the same DSP. What makes it unique is that in addition to decoding it can also [http://www.vlsi.fi/software/plugins/plugins.shtml encode] Ogg Vorbis files. There are three different quality settings to choose from varying from narrowband speech to high-quality stereo music.<br />
<br />
;[http://oggonachip.sourceforge.net/ Ogg On A Chip]: A hardware/software implementation with a good report showing how to make FPGAs and the like to decode Vorbis streams.<br />
<br />
;[http://www.finearch.com/english FineArch]: FineArch, Inc. developed a hardware core and control software for decoding Vorbis. This technology can be integrated into portable players or cell phones, and since it runs at only 12MHz, it uses very little battery power. It supports files up to 64Kb/s, but could be scaled to 16MHz and 128Kb/s, at the expense of battery life. For more information, see FineArch&#x2019;s [http://www.finearch.com/english/news/pr_20030715/pr_20030715.htm press release].<br />
<br />
;[http://www.mcslogic.com/ MCS Logic]: MCS Logic creates single chip decoders that can play Ogg Vorbis. They supply the Vorbis decoding chips for Havin and Freemax.<br />
<br />
;[http://www.telechips.com Telechips]: Telechips has developed the TCC72x, a single chip decoder that can play Vorbis. The TCC72x series is based on on an ARM940T core, and it is used widely in Korea for players such as Iops or MobiBlu.<br />
<br />
;[http://www.tamulsite.co.kr Tamul Multimedia]: Tamul Multimedia manufactures decoding chips for Samsung. They claim they have Ogg Vorbis decoding firmware, according to [http://www.dt.co.kr/print.html?gisaid=2003031002011367704002 <em>The Digital Times</em>] (Korean).<br />
<br />
;[http://www.sigmatel.com/ SigmaTel]: SigmaTel makes several chips which support Ogg Vorbis decoding. After this quote years ago, we knew it was only a matter of time:<br />
<blockquote>"<i>I talked to Deborah Clark, product marketing engineer for audio chipmaker Sigmatel out of Austin, Tex. She is the company's expert in audio decoders. She says there is a growing base of support for Ogg Vorbis. "We can't keep paying these high licensing fees for this. Manufacturers would flock to something that's free." </i></blockquote><br />
:from a 2000 [http://www.forbes.com/2000/09/18/dvorak_index.html column in Forbes]<br />
<br />
:Some STMP3500-based devices supports Ogg Vorbis, but there are no notes about this on SigmaTel-website.<br />
<br />
:SigmaTel introduces the STMP3600 with support for Ogg Vorbis, MP3, AAC, WMA and more.[http://www.finanznachrichten.de/nachrichten-2005-10/artikel-5493211.asp]<br />
<br />
== See also ==<br />
* [[Theora Hardware]]<br />
<br />
[[Category:Vorbis]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Theora_Hardware&diff=9158Theora Hardware2008-07-06T22:05:55Z<p>Pmsyyz: cleanup</p>
<hr />
<div>This is a list of hardware of all categories, from chipsets to ready-to-use products, that support Ogg [[Theora]].<br />
<br />
Hardware support status for Ogg Theora is a new thing, but it seems it's sometimes included even if not advertised. If you can't find a suitable player come back next week, or ask your vendor if they could add support.<br />
<br />
If you know of any hardware or projects that are not yet mentioned here, please add them to the list.<br />
<br />
== Consumer products ==<br />
These players support Ogg Theora either out of the box or after a firmware upgrade.<br />
<br />
* KiSS DP-1500. Not advertising, but reportedly supports playback of Ogg Theora. Probably [http://www-uk.linksys.com/servlet/Satellite?c=L_Product_C1&childpagename=UK%2FLayout&cid=1129319260635&pagename=Linksys%2FCommon%2FVisitorWrapper other KiSS products], too?<br />
<br />
== Non-consumer products ==<br />
<br />
=== Encoder ===<br />
The [http://www.xilinx.com/publications/xcellonline/xcell_53/xc_video53.htm Elphel 333] can encode a Theora stream.<br />
<br />
=== Decoder ===<br />
Currently there is a hardware decoder implementation being developed.<br />
The Google [[Summer Of Code]] 2006 ([http://www.students.ic.unicamp.br/~ra023772/projects.html author's university projects page]) began to produce an FPGA decoder implementation in VHDL and now there is another "Summer Of Code 2007" project ([http://code.google.com/soc/xiph/appinfo.html?csaid=4235040C184DBD68 description]) to work on it together with another independent developer.<br />
<br />
Here are two presentations that the author of the SOC 2006 proposal presented in his University:<br />
* The first idea of implementation is shown on this presentation: [http://svn.xiph.org/trunk/theora-fpga/doc/hard_theora.pdf Theora Hardware Decoding]<br />
* [http://svn.xiph.org/trunk/theora-fpga/doc/video_enc_basic.pdf Video Encoding: Basic Principles]<br />
<br />
==== Architecture and current state of development ====<br />
* [http://svn.xiph.org/trunk/theora-fpga/ Current Theora Hardware VHDL source]<br />
* [http://www.gaisler.com/leonmain.html LEON resouces]<br />
* [http://www.students.ic.unicamp.br/~ra031198/leon3.JPG LEON architecture]<br />
<br />
http://www.students.ic.unicamp.br/~ra023772/images/theora_integration_with_LEON.png<br />
<br />
=== Developers ===<br />
* Felipe Portavales Goldstein (portavales at gmail) - [http://www.students.ic.unicamp.br/~ra023772/ Website]<br />
* Leonardo de Paula Rosa Piga (leonardo.piga at gmail) - [http://www.students.ic.unicamp.br/~ra033956/ Website]<br />
* Andre Costa<br />
<br />
== See also == <br />
{{Theora}}<br />
* [[Vorbis Hardware]]<br />
<br />
[[Category:Theora]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Talk:VorbisHardware&diff=9157Talk:VorbisHardware2008-07-06T22:04:48Z<p>Pmsyyz: Talk:VorbisHardware moved to Talk:Vorbis Hardware</p>
<hr />
<div>#REDIRECT [[Talk:Vorbis Hardware]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Talk:Vorbis_Hardware&diff=9156Talk:Vorbis Hardware2008-07-06T22:04:48Z<p>Pmsyyz: Talk:VorbisHardware moved to Talk:Vorbis Hardware</p>
<hr />
<div>http://web.archive.org/web/20040208141117/http://wiki.xiph.org/VorbisHardware/editform<br />
<br />
Follow the link above to get a less outdate cache.<br />
<br />
---<br />
<br />
Some stats to write down in here:<br />
The new VorbisHardware Wiki has been up since 16:29, 27 Aug 2004. Now, one month later this site had more than 4600 visits (grabbed from counter on the bottom).<br />
The page is 8.5 screen units to scroll on my 1024px high monitor. Time to reconsider a split of contents as mentioned above?<br />
--[[User:Bodo|Bodo]] 14:49, 29 Sep 2004 (PDT)<br />
<br />
== product description scheme ==<br />
<br />
Could we also agree on a scheme how and what information about products is posted ? Current scheme is mostly ok, but there are some crappy entries. I'd keep company name first, linked to international company site -- it's confusing if it is used to directly link to the product in question.<br />
<br />
Then follow the unlinked names of the products. In the text itself the product names should be linked to their respective sites. Also a short discription of other features would be nice, not just 'supports vorbis'. Then about third party links: only one review per product should be linked, extra photo links and other bullcrap can be skipped. Maybe some firmware links if necessary. <br />
<br />
Ingmar (updatemeister)<br />
<br />
Forgot: entries should be sorted alphabetically.<br />
<br />
== Other comments ==<br />
<br />
Anyone know anything about Frontierlabs and the NEX ia? I have emailed their techsupport numerous times, to try and find out how they are progressing with their Ogg support (if at all), but have never received a reply...<br />
:They used to say they were working on it (for the Nex II) but they stopped answering. That was a couple years ago. I don't think they'll ever support Ogg on the Nexia. Sorry. It's a nice player in other regards, though behind the times in terms of hardware performance. It gets about 10 hours of playtime (mp3) on two AA cells where other players get more time than that on one AAA cell.<br />
<br />
== Vorbis encoder location ==<br />
<br />
I added a link to VLSI Solution's VS1053, which is capable of both encoding and decoding Ogg Vorbis with a 16-bit DSP. As far as I know this is a somewhat unique feature and I thought of bumping the reference up.<br />
<br />
However, as I am affiliated with the company, I feel a conflict of interests, so I will not do that. But just in case some of you more independent people think hardware Ogg Vorbis encoders are interesting enough, I wanted to raise a discussion whether it would be ok to move the VS1053 to a more visible position on this page, e.g. creating subheadings like "Ogg Vorbis Encoders" / "Ogg Vorbis Decoders" or similar. Again, I will not do that personally.<br />
<br />
(I have no idea whether raising this question in itself is a violation of something. I don't think so, but if I'm wrong, please just delete this discussion point.)<br />
<br />
- RealLeo<br />
<br />
:Raising the question is not a violation of anything. While the feature seems pretty interestiing, and we'd like to know what other HW encoders are there, I do not think a single product justifies making a whole section. For now, at least.--[[User:Saoshyant|Ivo]] 10:42, 13 September 2007 (PDT)<br />
<br />
:I have now moved VLSI Solution's Ogg Vorbis chips to the top of the list. My rationale is that the VS1053 is the only Ogg Vorbis encoder of the whole group, so I felt this to be OK now that the encoder has been officially released. However, I _am_ still affiliated with the company (read: I wrote the encoder and I am very proud of it), so if you think my reasoning really stinks, feel free to undo my changes. [[User:RealLeo|RealLeo]] 01:51, 4 December 2007 (PST)</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=VorbisHardware&diff=9155VorbisHardware2008-07-06T22:04:48Z<p>Pmsyyz: VorbisHardware moved to Vorbis Hardware</p>
<hr />
<div>#REDIRECT [[Vorbis Hardware]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Vorbis_Hardware&diff=9154Vorbis Hardware2008-07-06T22:04:48Z<p>Pmsyyz: VorbisHardware moved to Vorbis Hardware</p>
<hr />
<div>This is a list of hardware of all categories, from chipsets to ready-to-use products, that support Ogg Vorbis.<br />
<br />
Hardware support status for Ogg Vorbis is relatively good, you can choose between a huge amount of mobile flash players, many HDD based players and a respectable number of Hi-Fi components. More than 50 different companies offer a total of more than a hundred products for virtually every application, there is even a knife that can play Ogg Vorbis now ;-). If you can't find a suitable player come back next week -- new products are added on a weekly basis, as many companies are working to support Vorbis on their hardware.<br />
<br />
If you know of any hardware or projects that are not yet mentioned here, please add them to the list. More (outdated) hardware info can be found at [http://www.xiph.org/ogg/vorbis/hardware.html vorbis hardware page].<br />
<br />
== Consumer products ==<br />
<br />
These players support Ogg Vorbis either out of the box or after a firmware upgrade.<br />
<br />
* [[PortablePlayers]]: mobile players<br />
:[[PortablePlayers#Flash_Memory_Storage|Flash Memory Storage]]<br />
:[[PortablePlayers#Harddisk_Storage|Harddisk Storage]]<br />
:[[PortablePlayers#CD.2FDVD_Audio_Players|CD/DVD Audio Players]]<br />
:[[PortablePlayers#Mobile_Phones|Mobile Phones]]<br />
:[[PortablePlayers#Others|Others]]<br />
* [[StaticPlayers]]: installed players<br />
:[[StaticPlayers#Hi-Fi_components|Hi-Fi components]]<br />
:[[StaticPlayers#Car_Audio|Car Audio]]<br />
:[[StaticPlayers#Media_Storage|Media Storage]]<br />
:[[StaticPlayers#Internet radio devices|Internet radio devices]]<br />
<br />
For hardware that is able to run third-party software (such as PDAs and video game consoles), please visit [[VorbisSoftwarePlayers]].<br />
<br />
== Non-consumer products ==<br />
<br />
This is Vorbis in Silicon, meaning chips from which actual consumer products can be built.<br />
<br />
;[http://www.vlsi.fi/ VLSI Solution Oy]: VLSI provides two Ogg Vorbis capable chips.<br />
<br />
:[http://www.vlsi.fi/vs1000/vs1000.shtml VS1000] is an Ogg Vorbis decoder and controller chip based on a 16-bit DSP.<br />
<br />
:VS1053 is an external audio codec based on the same DSP. What makes it unique is that in addition to decoding it can also [http://www.vlsi.fi/software/plugins/plugins.shtml encode] Ogg Vorbis files. There are three different quality settings to choose from varying from narrowband speech to high-quality stereo music.<br />
<br />
;[http://oggonachip.sourceforge.net/ Ogg On A Chip]: A hardware/software implementation with a good report showing how to make FPGAs and the like to decode Vorbis streams.<br />
<br />
;[http://www.finearch.com/english FineArch]: FineArch, Inc. developed a hardware core and control software for decoding Vorbis. This technology can be integrated into portable players or cell phones, and since it runs at only 12MHz, it uses very little battery power. It supports files up to 64Kb/s, but could be scaled to 16MHz and 128Kb/s, at the expense of battery life. For more information, see FineArch&#x2019;s [http://www.finearch.com/english/news/pr_20030715/pr_20030715.htm press release].<br />
<br />
;[http://www.mcslogic.com/ MCS Logic]: MCS Logic creates single chip decoders that can play Ogg Vorbis. They supply the Vorbis decoding chips for Havin and Freemax.<br />
<br />
;[http://www.telechips.com Telechips]: Telechips has developed the TCC72x, a single chip decoder that can play Vorbis. The TCC72x series is based on on an ARM940T core, and it is used widely in Korea for players such as Iops or MobiBlu.<br />
<br />
;[http://www.tamulsite.co.kr Tamul Multimedia]: Tamul Multimedia manufactures decoding chips for Samsung. They claim they have Ogg Vorbis decoding firmware, according to [http://www.dt.co.kr/print.html?gisaid=2003031002011367704002 <em>The Digital Times</em>] (Korean).<br />
<br />
;[http://www.sigmatel.com/ SigmaTel]: SigmaTel makes several chips which support Ogg Vorbis decoding. After this quote years ago, we knew it was only a matter of time:<br />
<blockquote>"<i>I talked to Deborah Clark, product marketing engineer for audio chipmaker Sigmatel out of Austin, Tex. She is the company's expert in audio decoders. She says there is a growing base of support for Ogg Vorbis. "We can't keep paying these high licensing fees for this. Manufacturers would flock to something that's free." </i></blockquote><br />
:from a 2000 [http://www.forbes.com/2000/09/18/dvorak_index.html column in Forbes]<br />
<br />
:Some STMP3500-based devices supports Ogg Vorbis, but there are no notes about this on SigmaTel-website.<br />
<br />
:SigmaTel introduces the STMP3600 with support for Ogg Vorbis, MP3, AAC, WMA and more.[http://www.finanznachrichten.de/nachrichten-2005-10/artikel-5493211.asp]<br />
<br />
== See also ==<br />
<br />
* [[TheoraHardware]]<br />
<br />
----<br />
<br />
[[Category:Vorbis]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Template:Theora&diff=9153Template:Theora2008-07-06T22:03:35Z<p>Pmsyyz: fix link</p>
<hr />
<div>* [[Theora Hardware]]: List of hardware-players supporting Ogg Theora<br />
* [[TheoraSoftwarePlayers]]: List of media players that can play Ogg Theora<br />
* [[TheoraSoftwareEncoders]]: List of software that can encode to Ogg Theora<br />
* [[TheoraDecoders]]: List of decoder implementations<br />
* [[TheoraEncoders]]: List of encoder implementations<br />
* [[List of Theora videos]]: Get some files to see what the codec's like<br />
* [[Games that use Theora]]: List of known games that use Theora</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Talk:TheoraHardware&diff=9152Talk:TheoraHardware2008-07-06T22:02:51Z<p>Pmsyyz: Talk:TheoraHardware moved to Talk:Theora Hardware</p>
<hr />
<div>#REDIRECT [[Talk:Theora Hardware]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Talk:Theora_Hardware&diff=9151Talk:Theora Hardware2008-07-06T22:02:51Z<p>Pmsyyz: Talk:TheoraHardware moved to Talk:Theora Hardware</p>
<hr />
<div></div>Pmsyyzhttps://wiki.xiph.org/index.php?title=TheoraHardware&diff=9150TheoraHardware2008-07-06T22:02:50Z<p>Pmsyyz: TheoraHardware moved to Theora Hardware</p>
<hr />
<div>#REDIRECT [[Theora Hardware]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Theora_Hardware&diff=9149Theora Hardware2008-07-06T22:02:50Z<p>Pmsyyz: TheoraHardware moved to Theora Hardware</p>
<hr />
<div>This is a list of hardware of all categories, from chipsets to ready-to-use products, that support Ogg Theora.<br />
<br />
Hardware support status for Ogg Theora is a new thing, but it seems it's sometimes included even if not advertised. If you can't find a suitable player come back next week, or ask your vendor if they could add support.<br />
<br />
If you know of any hardware or projects that are not yet mentioned here, please add them to the list.<br />
<br />
= Consumer products =<br />
<br />
These players support Ogg Theora either out of the box or after a firmware upgrade.<br />
<br />
* KiSS DP-1500. Not advertising, but reportedly supports playback of Ogg Theora. Probably [http://www-uk.linksys.com/servlet/Satellite?c=L_Product_C1&childpagename=UK%2FLayout&cid=1129319260635&pagename=Linksys%2FCommon%2FVisitorWrapper other KiSS products], too?<br />
<br />
= Non-consumer products =<br />
<br />
== Encoder ==<br />
The [http://www.xilinx.com/publications/xcellonline/xcell_53/xc_video53.htm Elphel 333] can encode a Theora stream.<br />
<br />
== Decoder ==<br />
Currently there is a hardware decoder implementation being developed.<br />
The Google "Summer Of Code 2006" ([http://www.students.ic.unicamp.br/~ra023772/projects.html author's university projects page]) began to produce an FPGA decoder implementation in VHDL and now there is another "Summer Of Code 2007" project ([http://code.google.com/soc/xiph/appinfo.html?csaid=4235040C184DBD68 description]) to work on it together with another independent developer.<br />
<br />
Here are two presentations that the author of the SOC 2006 proposal presented in his University:<br />
* The first idea of implementation is shown on this presentation: [http://svn.xiph.org/trunk/theora-fpga/doc/hard_theora.pdf Theora Hardware Decoding]<br />
* [http://svn.xiph.org/trunk/theora-fpga/doc/video_enc_basic.pdf Video Encoding: Basic Principles]<br />
<br />
<br />
=== Architecture and current state of development ===<br />
<br />
* [http://svn.xiph.org/trunk/theora-fpga/ Current Theora Hardware VHDL source]<br />
* [http://www.gaisler.com/leonmain.html LEON resouces]<br />
* [http://www.students.ic.unicamp.br/~ra031198/leon3.JPG LEON architecture]<br />
<br />
<br />
http://www.students.ic.unicamp.br/~ra023772/images/theora_integration_with_LEON.png<br />
<br />
<br />
=== Developers ===<br />
* Felipe Portavales Goldstein (portavales at gmail) - [http://www.students.ic.unicamp.br/~ra023772/ Website]<br />
* Leonardo de Paula Rosa Piga (leonardo.piga at gmail) - [http://www.students.ic.unicamp.br/~ra033956/ Website]<br />
* Andre Costa<br />
<br />
<br />
== See also == <br />
{{Template:Theora}}<br />
* [[VorbisHardware]]<br />
<br />
[[Category:Theora]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Etheora&diff=9148Etheora2008-07-06T22:02:28Z<p>Pmsyyz: cleanup</p>
<hr />
<div>'''Etheora''' is a a simplified API for programming [[Theora]] video encoding/decoding applications with [[Ogg]] containers. It uses and encapsulates libtheora + libogg API and structures, so users need to know very few about video and data containers.<br />
<br />
== Overview - Encoding == <br />
<br />
An encoding process is made by these steps:<br />
<br />
/* a context declaration. */<br />
etheora_ctx ec;<br />
<br />
/* encoder configuration. */<br />
etheora_enc_setup(&ec, width, height, ETHEORA_ASPECT_NORMAL,<br />
fopen("output-video.ogv"), fopen("debug_info.txt"));<br />
<br />
/* encoder start. */<br />
etheora_enc_start(&ec);<br />
<br />
/* drawing next frame, by puting a r,g,b or y,u,v pixel in (i,j) coordinate */<br />
etheora_enc_rgb_draw(&ec, i, j, r, g, b);<br />
/* alternative: etheora_enc_yuv_draw()) */<br />
<br />
/* submiting frame to encoding. */<br />
etheora_enc_nextframe(&ec);<br />
<br />
/* submiting last frame to encoding by finishing the process. */<br />
etheora_enc_finish(&ec);<br />
<br />
The functions _yuv_ and _rgb_ works transparently with OC_PF_420, OC_PF_422 and OC_PF_PF_444, having the libtheora version used support for them or not.<br />
<br />
== Overview - Decoding == <br />
<br />
The decoding process is quite similar.<br />
<br />
/* a context declaration. */<br />
etheora_ctx ec;<br />
<br />
/* decoder configuration. */<br />
etheora_dec_setup(&ec, fopen("input-video.ogv"), fopen("debug_info.txt")); <br />
<br />
/* decoder start. */<br />
etheora_dec_start(&ec); <br />
<br />
/* reading video data. */<br />
etheora_get_width(&ec);<br />
etheora_get_heigth(&ec);<br />
etheora_get_fps_numerator(&ec);<br />
etheora_get_fps_denominator(&ec);<br />
etheora_get_aspect_numerator(&ec);<br />
etheora_get_aspect_denominator(&ec);<br />
<br />
/* getting next frame by decoding it. */<br />
etheora_dec_nextframe(&ec); <br />
<br />
/* getting frame data, by reading a r,g,b or y,u,v pixel in (i,j) coordinate*/<br />
etheora_dec_rgb_read(&ec, i, j, &r, &g, &b)<br />
/* alternative: etheora_dec_yuv_read()) */<br />
<br />
/* finishing the process. */<br />
etheora_dec_finish(&ec);<br />
<br />
The functions _yuv_ and _rgb_ works transparently with OC_PF_420, OC_PF_422 and OC_PF_PF_444, having the libtheora version used support for them or not.<br />
<br />
== Overview - Going Further == <br />
<br />
Etheora is documented here:<br />
http://svn.xiph.org/branches/etheora-0.1.1/doc/etheora_documentation.pdf<br />
<br />
Etheora code is here:<br />
http://svn.xiph.org/branches/etheora-0.1.1/src/<br />
<br />
Etheora very simple examples are found here:<br />
http://svn.xiph.org/branches/etheora-0.1.1/examples/<br />
<br />
Etheora still doesn't have audio/speech support. (Although it can get video data from videos with audio). And uses internally the old libtheora API (ie, not the theora-exp). FIXME: The theora-exp API is what's used now on libtheora 1.0. Please use that API instead.<br />
<br />
== TODO == <br />
<br />
* Vorbis support<br />
* Speex support<br />
* Skeleton support<br />
<br />
== See also == <br />
{{Theora}}<br />
<br />
[[Category:Theora]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Nut_Container&diff=9147Nut Container2008-07-06T22:01:24Z<p>Pmsyyz: cleanup</p>
<hr />
<div>This page collects opinions about the<br />
[http://www.nut-container.org/ NUT container format].<br />
<br />
== Comparison with Ogg ==<br />
<br />
Monty writes: "NUT is very similar to [[Ogg]] (at least when compared to the other contemporary systems). It draws the abstraction lines in different places but has roughly the same functionality and hits the same practical limitations when considered in a system more complex than a desktop video player.<br />
<br />
"Nor can we take lightly the prospect of abandoning a hundred million installed copies of Ogg (including those in hardware) for no distinct practical benefit."</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Nut_Container&diff=9145Nut Container2008-07-06T21:59:55Z<p>Pmsyyz: NutIssues moved to Nut issues</p>
<hr />
<div>This page collects opinions about the<br />
[http://www.nut-container.org/ NUT container format].<br />
<br />
== Comparison with Ogg ==<br />
<br />
Monty writes: "NUT is very similar to Ogg (at<br />
least when compared to the other contemporary systems). It draws the<br />
abstraction lines in different places but has roughly the same<br />
functionality and hits the same practical limitations when considered<br />
in a system more complex than a desktop video player.<br />
<br />
"Nor can we take<br />
lightly the prospect of abandoning a hundred million installed copies<br />
of Ogg (including those in hardware) for no distinct practical<br />
benefit."</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=VP3_to_Theora&diff=9144VP3 to Theora2008-07-06T21:59:32Z<p>Pmsyyz: cleanup</p>
<hr />
<div>This is a quick guide to show how to transcode [[VP3]] (usually with [[MP3]] audio) to [[Theora]].<br />
<br />
Now, this quick guide involves a lot of tools which are either experimental or are known to be buggy. Beware. Use with caution.<br />
<br />
== NSV ==<br />
<br />
If your video is encapsulated in [[NSV]] you first need to remux it to [[AVI]]:<br />
<br />
mencoder -oac copy -ovc copy -fafmttag 0x55 -o vp31.avi input.nsv<br />
<br />
You can skip this step if your input file already is an AVI.<br />
<br />
== Get the Theora code ==<br />
<br />
Download the Theora source code: <tt>svn co http://svn.xiph.org/trunk/theora</tt><br />
<br />
== Build the avi2vp3 tool ==<br />
<br />
Go to theora/win32/experimental/transcoder/avi2vp3/<br />
<br />
Compile the tool which will extract the VP3 data out of your AVI file: gcc *.c -o avi2vp3<br />
<br />
== Build transcoder_example ==<br />
<br />
Copy theora/win32/experimental/transcoder/transcoder_example.c to theora/examples/encoder_example.c - this will replace the usual Theora encoder example with the application creating a Theora stream from the raw VP3 data.<br />
<br />
Configure your copy of Theora (run autogen.sh). This has a few dependencies. The configuration process will guide you. Be patient. Once configuration didn't complain because of missing dependencies: Invoke make.<br />
<br />
After everything compiled you should rename the encoder_example binary (which is in the examples directory) to e.g. transcoder_example to avoid confusion.<br />
<br />
== Process your videos ==<br />
<br />
* Use avi2vp3 to convert your VP3 AVI. The input file *must* be named vp31.avi, the output file will always be outfile.vp3<br />
* Use transcoder_example to create an Ogg Theora stream: transcoder_example outfile.vp3 > video.ogg<br />
* Use e.g. mplayer to decode the audio in the AVI file: mplayer -vo null -ao pcm vp31.avi<br />
* The audio will be in audiodump.wav. Encode it with e.g. oggenc: oggenc -q 1 audiodump.wav<br />
* Now you need to combine video.ogg and audiodump.ogg. Use oggzmerge from the oggz-tools package (at least in Ubuntu it's oggz-tools): oggzmerge video.ogg audiodump.ogg > theora.ogg<br />
<br />
theora.ogg now should be a valid Theora + Vorbis Ogg file. Congratulations!<br />
<br />
== Bugs ==<br />
<br />
If the VP3 video input has dropped frames (this is common on broadcasted videos with narrow bandwidth constraints) you may notice that the created Theora file is distorted in affected parts of the video (apparently because the information that frames were dropped is lost, thus some video frames predict from the wrong predecessors).<br />
<br />
[[Category:Theora]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Vp3toTheora&diff=9143Vp3toTheora2008-07-06T21:57:44Z<p>Pmsyyz: Vp3toTheora moved to VP3 to Theora</p>
<hr />
<div>#REDIRECT [[VP3 to Theora]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=VP3_to_Theora&diff=9142VP3 to Theora2008-07-06T21:57:44Z<p>Pmsyyz: Vp3toTheora moved to VP3 to Theora</p>
<hr />
<div>== About ==<br />
<br />
<br />
This is a quick guid to show how to transcode VP3 (usually with MP3) to Theora.<br />
<br />
Now, this quick guide involves a lot of tools which are either experimental or are known to be buggy. Beware. Use with caution.<br />
<br />
== NSV ==<br />
<br />
If your video is encapsulated in NSV you first need to remux it to AVI:<br />
<br />
mencoder -oac copy -ovc copy -fafmttag 0x55 -o vp31.avi input.nsv<br />
<br />
You can skip this step if your input file already is an AVI.<br />
<br />
== Get the Theora code ==<br />
<br />
Download the Theora source code (svn co http://svn.xiph.org/trunk/theora).<br />
<br />
== Build the avi2vp3 tool ==<br />
<br />
Go to theora/win32/experimental/transcoder/avi2vp3/<br />
<br />
Compile the tool which will extract the VP3 data out of your AVI file: gcc *.c -o avi2vp3<br />
<br />
== Build transcoder_example ==<br />
<br />
Copy theora/win32/experimental/transcoder/transcoder_example.c to theora/examples/encoder_example.c - this will replace the usual Theora encoder example with the application creating a Theora stream from the raw VP3 data.<br />
<br />
<br />
Configure your copy of Theora (run autogen.sh). This has a few dependencies. The configuration process will guide you. Be patient. Once configuration didn't complain because of missing dependencies: Invoke make.<br />
<br />
After everything compiled you should rename the encoder_example binary (which is in the examples directory) to e.g. transcoder_example to avoid confusion.<br />
<br />
== Process your videos ==<br />
<br />
* Use avi2vp3 to convert your VP3 AVI. The input file *must* be named vp31.avi, the output file will always be outfile.vp3<br />
* Use transcoder_example to create an Ogg Theora stream: transcoder_example outfile.vp3 > video.ogg<br />
* Use e.g. mplayer to decode the audio in the AVI file: mplayer -vo null -ao pcm vp31.avi<br />
* The audio will be in audiodump.wav. Encode it with e.g. oggenc: oggenc -q 1 audiodump.wav<br />
* Now you need to combine video.ogg and audiodump.ogg. Use oggzmerge from the oggz-tools package (at least in Ubuntu it's oggz-tools): oggzmerge video.ogg audiodump.ogg > theora.ogg<br />
<br />
theora.ogg now should be a valid Theora + Vorbis Ogg file. Congratulations!<br />
<br />
== Bugs ==<br />
<br />
If the VP3 video input has dropped frames (this is common on broadcasted videos with narrow bandwidth constraints) you may notice that the created Theora file is distorted in affected parts of the video (apparently because the information that frames were dropped is lost, thus some video frames predict from the wrong predecessors).<br />
<br />
[[Category:Theora]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=OggKate&diff=8114OggKate2008-01-23T04:34:46Z<p>Pmsyyz: /* Why a new codec? */ link</p>
<hr />
<div>== Disclaimer ==<br />
This is not a Xiph codec, but I was asked to post information<br />
about Ogg/Kate on this wiki. As such, please do not assume that Xiph has anything<br />
to do with this, much less responsibility.<br />
<br />
== What is Kate? ==<br />
<br />
Kate is a codec for karaoke and text encapsulation for Ogg. Most of the time, this<br />
would be multiplexed with audio/video to carry subtitles, song lyrics (with or without<br />
karaoke data), etc, but doesn't have to be. A possible use of a lone Kate stream would<br />
be an e-book.<br />
Moreover, the motion feature gives Kate a powrful means to describe arbitrary curves, so<br />
hand drawing of shapes can be achieved. This was originally meant for karaoke use, but<br />
can be used for any purpose. Motions can be attached to various semantics, like position,<br />
color, etc, so scrolling or fading text can be defined.<br />
<br />
== Why a new codec? ==<br />
<br />
As I was adding support for Theora, Speex and FLAC to some software of mine, I found myself<br />
wanting to have song lyrics accompanying Vorbis audio. Since Vorbis comments are limited to<br />
the headers, one can't add them in the stream as they are sung, so another multiplexed stream<br />
would be needed to carry them.<br />
<br />
The three possible bases usable for such a codec I found were Writ, CMML, and OGM/SRT.<br />
<br />
*[[OggWrit|Writ]] is an unmaintained start at an implementation of a very basic design, though I did find an encoder/decoder in py-pgg2 later on - I'd been quicker to write Kate from scratch anyway.<br />
*CMML is more geared towards encapsulating metadata about an accompanying stream, rather than being a data stream itself, and seems complex for a simple use - I don't really want *full* HTML/XML with links, etc - besides, it seems designed for Annodex (which I haven't had a look at), though it does seems relatively generic for use outwith Annodex<br />
*OGM/SRT, which I only found when I added Kate support to MPlayer, is shoehorning various data formats into an Ogg stream, and just dumps the SRT subtitle format as is, AFAICS (though I haven't looked at this one in detail, since I'd already had a working Kate implementation by that time)<br />
<br />
I then decided to roll my own, not least because it's a fun thing to do.<br />
<br />
I found other formats, such as USF (designed for inclusion in Matroska) and various subtitle formats,<br />
but none were designed for embedding inside an Ogg container.<br />
<br />
== Overview of the Kate bitstream format ==<br />
<br />
I've taken much inspiration from Vorbis and Theora here.<br />
Headers and packets (as well as the API design) follow the design of these two codecs.<br />
<br />
A rough overview (detailed description is available below (no, it's not, it will be<br />
available later when the format has settled down a bit more)) is:<br />
<br />
Headers packets:<br />
*ID header [BOS]: magic, version, granule fraction, encoding, language, etc<br />
*Comment header: Vorbis comments, as per Vorbis/Theora streams<br />
*Style definitions header: a list of predefined styles to be referred to by data packets<br />
*Region definitions header: a list of predefined regions to be referred to by data packets<br />
*Motion definitions header: a list of predefined motions to be referred to by data packets<br />
<br />
Other header packets are ignored, and left for future expansion. In particular, there will<br />
likely be a motions definition header, where motions which are to be used repeatedly will<br />
be stored for reference in text packets.<br />
<br />
Data packets:<br />
*text data: text and optional motions, accompanied by optional overrides for style, region, language, etc<br />
*end data [EOS]: marks the end of the stream, it doesn't have any payload<br />
<br />
Other data packets are ignored, and left for future expansion.<br />
<br />
Things of note:<br />
*Kate is a discontinuous codec, as defined in ogg-multiplex.html in the Ogg documentation, which means it's timed by start granule, not end granule (as Theora and Vorbis). Also, all data packets are on their own page, for two reasons:<br />
**Ogg keeps track of granules at the page level, not the packet level<br />
**if no text event happens for a while after a particular text event, we don't want to delay it so a fuller page can be issued<br />
<br />
See also [[#Seeking and memory|Problems to solve: Seeking and memory]].<br />
<br />
*The granule encoding is not a direct time/granule correspondance, see the granule encoding section.<br />
*The EOS packet should have a granule pos higher than the end time of all events.<br />
*User code doesn't have to know the number of headers to expect, this is moved inside the library code.<br />
<br />
== Support ==<br />
<br />
I have patches for the following with Kate support:<br />
*oggmerge (it also adds Theora support)<br />
*file(1)<br />
*MPlayer (for multiplexed per-language subtitles - all region/style info is ignored)<br />
*xine (text, and work-in-progress style/regions/motions support)<br />
<br />
None of those are released yet, since the Kate bitstream format is still a work in progress.<br />
<br />
== Granule encoding ==<br />
<br />
At the moment, the granules are split in two: the high bits represent a time (scaled by a<br />
fractional speed defined in the ID header), and the low bits are an increasing counter<br />
used when several events happen at the same time.<br />
At the moment, 5 bits are taken for that counter. This is totally arbitrary and subject<br />
to change. The granule shift of a stream is included in the ID header.<br />
See also the problems to solve section, about seeking, for a possible three-way split, where<br />
the high bits would be further split.<br />
<br />
== Motion ==<br />
<br />
The Kate bitstream format includes motion definition, primarily for karaoke purposes, but<br />
which can be used for more general purpose, such as line based drawing, or animation of<br />
the text (position, color, etc)<br />
<br />
Motions are defined by the means of a series of curves (for now, segments and splines). A<br />
2D point can be obtained from a motion for any timestamp during the lifetime of a text.<br />
This can be used for moving a marker in 2D above the text for karaoke, or to use the x<br />
coordinate to color text when the motion position passes each letter or word, etc.<br />
Motions have an attached semantics so the client code knows how to use a particular motion.<br />
Predefined semantics include text color, text position, etc).<br />
<br />
Since a motion can be composed of an arbitrary number of curves, each of which may have<br />
an arbitrary number of control points, complex motions can be achieved. If the motion is<br />
the main object of an event, it is even possible to have an empty text, and use the motion<br />
as a virtual pencil to draw arbitrary shapes. Even on-the-fly handwriting subtitles could<br />
be done this way, though this would require a lot of control points.<br />
<br />
It is also possible for motions to be discontinuous - simply insert a curve of 'none' type.<br />
While the timestamp lies within such a curve, no 2D point will be generated. This can be<br />
used to temporarily hide a marker, for instance.<br />
<br />
It is worth mentionning that pauses in the motion can be trivially included by inserting<br />
at the right time and for the right duration a simple linear interpolation curve with only<br />
two equal points, equal to the position the motion is supposed to pause at.<br />
<br />
Kate defines a set of predefined mappings so that each decoder user interprets a motion in<br />
the same way. A mapping is coded on 8 bits in the bitstream, and the first 128 are reserved<br />
for Kate, leaving 128 for application specific mappings, to avoid constraining creative uses<br />
of that feature. Predefined mappings include frame (eg, 0-1 points are mapped to the size of<br />
the current video frame), or region, to scale 0-1 to the current region. This allows curves<br />
to be defined without knowing in advance the pixel size of the area it should cover.<br />
<br />
For uses which require more than two coordinates (eg, text color, where 4 (RGBA) values are<br />
needed, Kate predefines the semantics text_color_rg and text_color_ba, so a 4D point can be<br />
obtained using two different motions.<br />
<br />
See also [[#Trackers|Trackers]].<br />
<br />
<br />
== Trackers ==<br />
<br />
Since attaching motions to text position, etc, makes it hard for the client to keep track of<br />
everything, doing interpolation, etc, the library supplies a tracker object, which handles the<br />
interpolation of the relevant properties.<br />
Once initialized with a text and a set of motions, the client code can give the tracker a new<br />
timestamp, and get back the current text position, text color, etc.<br />
<br />
<br />
== Problems to solve ==<br />
<br />
There are a few things to solve before the Kate bitstream format can be considered good<br />
enough to be frozen:<br />
<br />
=== Seeking and memory ===<br />
<br />
When seeking to a particular time in a movie with subtitles, we may end up at a place when a subtitle has been started, but is not removed yet. Pure streaming doesn't have this problem as it remembers the subtitle being issued (as opposed to, say, Vorbis, for which all data valid now is decoded from the last packet). With Kate, a text string valid now may have been issued long ago.<br />
<br />
I see three possible ways to solve this:<br />
*each data packet includes the granule of the earliest still active packet (if none, this will be the granule of this very packet)<br />
**this means seeks are two phased: first seek, find the next Kate packet, and seek again if the granule of the earlier still active packet is less than the original seeked granule. This implies support code on players to do the double seek.<br />
<br />
*use "reference frames", a bit like Theora does, where the granule position is split in several fields: the higher bits represent a position for the reference frame, and the lowest bits a delta time to the current position. When seeking to a granule position, the lower bits are cleared off, yielding the granule position of the previous reference frame, so the seek ends up at the reference frame. The reference frame is a sync point where any active strings are issued again. This is a variant of the method described in the Writ wiki page, but the granule splitting avoids any "downtime".<br />
**this requires reissuing packets, and it doesn't feel right (and wastes space).<br />
**it also requires "dummy" decoding of Kate data from the reference frame to the actual seek point to fully refresh the state "memory".<br />
<br />
*A variant of the two-granules-in-one system used by libcmml, where the "back link" points to the earliest still active string, rather than the previous one (this allows a two phase seek, rather than a multiphase seek, hopping back from event to event, with no real way to know if there is or not a previous event which is still active - I suppose CMML has no need to know this, if their "clips" do not overlap - mine can do).<br />
**Such a system considerably shortens the usable granule space, though it can do a one phase seek, if I understand the system correctly, which I am not certain.<br />
<br />
=== Text encoding ===<br />
<br />
A header field declares the text encoding used in the stream (this can be overridden in a<br />
data packet, but this is not relevant to this point). At the moment, only UTF-8 is supported,<br />
for simplicity, and I have not yet decided whether or not the Kate specification will allow<br />
for other encodings, such as UTF-16 of UTF-32. The reason for this is that, if these were to<br />
be supported, either:<br />
*users of the decoder would have to be ready to face text in any one of these encodings<br />
*the decoder would have to convert encodings to one selected by the user of the decoder<br />
<br />
The first option may be asking a lot of users, while the second one brings complexity to the<br />
decoder, and kind of defeats the purpose of supporting the encoding in the first place.<br />
<br />
Note that strings included in the header (language, category, etc) are not affected by that<br />
language encoding (rather obviously for language itself). These are ASCII.<br />
<br />
At the moment, I am leaning strongly towards limiting the encoding to UTF-8.<br />
<br />
The actual text may include simple HTML markup (eg, &lt;br&gt;, &lt;em&gt;, etc).<br />
It is also possible to ask libkate to remove this markup if the client doesn't want it.<br />
<br />
=== Language encoding ===<br />
<br />
A header field defines the language (if any) used in the stream (this can be overridden in a<br />
data packet, but this is not relevant to this point). At the moment, my test code uses<br />
ISO 639-1 two letter codes, but I originally thought to use RFC 3066 tags. However, matching<br />
a language to a user selection may be simpler for user code if the language encoding is kept<br />
simple. At the moment, I tend to favor allowing both two letter tags (eg, "en") and secondary<br />
tags (like "en_EN"), as RFC 3066 tags can be quite complex, but I welcome comments on this.<br />
<br />
Alternatively, I might use only RFC 1766 tags, which are essentially the subset I considered<br />
above, but this RFC has been deprecated by RFC 3066, and I'm not sure of the wisdom of basing<br />
a new format on a deprecated RFC.<br />
<br />
Also, it might be possible for the language field to be a list of such encodings, for streams<br />
that contain several languages (though the usual way to present several languages is to have<br />
several bitstreams multiplexed with one another (as opposed to Writ, which has all languages<br />
included in a single bitstream)).<br />
<br />
A disadvantage of having multiple languages is that text-to-speech typically needs to know<br />
the current language to function properly, and that having, say, two current languages, would<br />
make it more difficult to deal with such a stream.<br />
<br />
=== Bitstream format for floating point values ===<br />
<br />
At the moment, floating point values (for splines) are stored as their textual representation, and converted back and forth using snprintf and sscanf. We could quantize them and store as<br />
integers, since precision isn't that important here.<br />
-> If precision doesn't suffer, floating point values will be turned to a 16.16 fixed point format, then<br />
stored in a bitpacked format, storing the number of zero bits at the head and tail of the floating point<br />
values once per stream, and the remainder bits for all values in the stream. This seems to yield good<br />
results (typically a 50% reduction over 32 bits raw writes, and 70% over the snprintf based storage),<br />
and has the big advantage of being portable (eg, independant of any IEEE format).<br />
<br />
*Though this is not a Kate issue per se, the motion feature is very difficult to use without a curve editor. While tools may be coded to create a Kate bitstream for various existing subtitle formats, it is not certain it will be easy to find a good authoring tool for a series of curves. That said, it's not exactly difficult to do if you know a widget set.<br />
<br />
*Since motions may be repeated, I may add predefined motions in an extra header packet, to be referenced as styles and regions are. This would depend on whether motions are likely to be exactly repeated often, and I don't know if this will likely be the case. Complex motion definitions can take a lot of space, especially with the current floating point value encoding. After some thought, I will almost certainly place predefined curves in a header, and allow motions to refer to them. Fully defined curves will also be able to be placed in data packets, as it's likely some curves will be used only once, and it would constrain future uses to allow them only in headers (eg, if one were to stream handwriting using Kate).<br />
-> There is now a separate curves/motions definition header, especially as I now use motions for more than simply moving a point in 2D.<br />
Motions use a lot of floating point values, so the above compression is welcome.<br />
Motions will still be able to be stored in data packets, however, so they can be generated in real time if streaming from a live source.<br />
<br />
== Text to speech ==<br />
<br />
One of the goals of the Kate bitstream format is that text data can be easily parsed<br />
by the user of the decoder, so any additional information, such as style, placement,<br />
karaoke data, etc, should be able to be stripped to leave only the bare text. This is<br />
in view of allowing text-to-speech software to use Kate bitstreams as a bandwith-cheap<br />
way of conveying speech data, and could also allow things like e-books which can be<br />
either read or listened to from the same bitstream (I have seen no reference to this<br />
being used anywhere, but I see no reason why the granule progression should be temporal,<br />
and not user controlled, such as by using a "next" button which would bump a granule<br />
postion by a preset amount, simulating turning a page (this would be close to necessary<br />
for text-to-speech, as the wall time duration of the spoken speech is not known in<br />
advance to the Kate encoder, and can't be mapped to a time based granule progression)).<br />
All text strings triggered consecutively between the two granule positions would then<br />
be read in order.<br />
<br />
== Possible additions ==<br />
<br />
=== Embedded binary data ===<br />
<br />
Various types of binary data could be embedded within a Kate stream:<br />
<br />
==== Fonts ====<br />
<br />
Font selection is the first thing that came to mind, due to the discrepancy of font<br />
naming in platforms (eg, the *-*-* X system, and the... hmm, not sure, filename ?<br />
in Windows). A potential problem, however, is that there might be several multiplexed<br />
Kate streams in an Ogg bitstream, so a custom font might be included several times<br />
in the container stream. On the other hand, it would allow for per-language fonts.<br />
<br />
==== Images ====<br />
<br />
Though this could interfere with ability to render as text-to-speech, images could be<br />
mixed with text. The same caveat as for fonts applies with regard to data duplication.<br />
This might however be best left to a multiplexed OggSpots stream, unless the images<br />
mesh with the text (eg, graphical exclamation points, etc).<br />
<br />
A possible solution to the duplication issue is to have another stream in the container<br />
stream, which would hold the shared data (eg, fonts), which the user program could load,<br />
and which could then be used by any Kate (and other) stream. Typically, this type of stream<br />
would be a degenerate stream with only header packets (so it is fully processed before any<br />
other stream presents data packets that might make use of that shared data), and all payload<br />
such as fonts being contained within the headers. Thinking about it, it has parallels with<br />
the way Vorbis stores its codebooks within a header packet, or even the way Kate stores the<br />
list of styles within a header packet.<br />
<br />
== Reference encoder/decoder ==<br />
<br />
A encoder and a decoder are included in the tools directory. Note that they are very rough<br />
and do not perform much error checking at all. The encoder pulls its input from a custom<br />
text based file format, which is by no means meant to be part of the Kate specification,<br />
or from an SubRip format file (the most common subtitle format I found, and a very basic one).<br />
<br />
The custom format It is just used as a quick way to define data to create a Kate bitstream.<br />
Tools might be created to create a Kate bitstream from various data formats, such as existing<br />
subtitle formats (SSA, etc). I currently have a patch to mplayer that can create Kate streams<br />
from any of the subtitle formats it supports, so creating Kate streams is easy.<br />
<br />
The Kate bitstreams encoded and decoded by those tools, however, are (supposed to be)<br />
correct for this specification, provided their input is correct.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Current_events&diff=6464Current events2007-03-14T06:30:21Z<p>Pmsyyz: FLAC 1.1.4 released.</p>
<hr />
<div>__NOTOC__<br />
What's happening in the world of Xiph.org? See [[Wikipedia:Current events]] for an example of what this should become like.<br />
<br />
== 2007-03-06 ==<br />
[http://sourceforge.net/projects/libspiff/ libSpiff] is now part of Xiph, and the official library for [[XSPF]].<br />
<br />
== 2007-02-13 ==<br />
<br />
[[FLAC]] 1.1.4 released. [http://flac.sourceforge.net/changelog.html#flac_1_1_4 changelog]<br />
<br />
== 2007-02-07 ==<br />
VLSI Solution Oy has [http://www.vlsi.fi/vs1000/vs1000.shtml announced VS1000], the first 16 bits DSP device for playing Ogg Vorbis on low-power and high-volume products.<br />
<br />
== 2006-04-10 ==<br />
<br />
[http://www.radgametools.com/ RAD Game Tools], which makes multimedia engines for several videogames, has now incorporated Ogg Vorbis support in their Miles Sound System. Their official announcement regarding Ogg Vorbis support can be found [http://www.radgametools.com/miles.htm here].<br />
<br />
== 2005-12-08 ==<br />
CBC is [http://www.cbc.ca/listen/ogg.html broadcasting] both their Radio [http://www.cbc.ca/livemedia/cbcr1-toronto.m3u One] and [http://www.cbc.ca/livemedia/cbcr2-toronto.m3u Two] in Ogg [[Vorbis]]! Radio One is pretty stable and fast-loading.<br />
<br />
== 2005-12-02 ==<br />
<br />
[[Speex]] 1.1.11.1 released.<br />
<br />
== 2005-11-30 ==<br />
<br />
[[Icecast]] 2.3.1 released.<br />
<br />
== 2005-10-15 ==<br />
<br />
[http://free.wave.online.fr/ FreeWaveOnline] is a new Web-radio dedicated to Free Music. It use [[XSPF]] playlists[http://free.wave.online.fr/xmediaplayer/playlists/empty_playlist.xml]. This radio station is in french, but music is international ;)<br />
<br />
== 2005-08-20 ==<br />
<br />
[[Theora|libtheora]] 1.0 alpha 5 released. [http://www.theora.org/]<br />
<br />
== 2005-06-27 ==<br />
<br />
[[Vorbis]] 1.1.1 released. Some bug and documentation fixes, but no new <br />
encoder modes. [http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XSPF&diff=6277XSPF2007-02-24T18:07:29Z<p>Pmsyyz: cleanup</p>
<hr />
<div>'''XML Shareable Playlist Format''' ('''XSPF'''), pronounced spiff, is a next-generation playlist format. This wiki is for developers.<br />
<br />
The mime type for XSPF playlists is <tt>application/xspf+xml</tt>, although it has not yet been [http://www.iana.org/cgi-bin/mediatypes.pl registered] with IANA.<br />
<br />
== Supporting applications ==<br />
<br />
These are applications which support XSPF and have not yet been added to the [[http://xspf.org/applications][main applications list]].<br />
<br />
* [http://www.jamendo.com/ Jamendo]<br />
** You have to be a member and to select "XSPF" in your preferences to use them by default, but you can look and test a sample playlist here: http://www.jamendo.com/get/track/id/album/audio/xspf/1003/?aue=ogg2<br />
* http://www.ArtistServer.com<br />
** on artist profile pages http://www.artistserver.com/bliss<br />
** on stations and playlists http://www.artistserver.com/stations/<br />
** on genre pages http://www.artistserver.com/DownTempo<br />
* Project Opus http://projectopus.com<br />
** see http://www.projectopus.com/new-player for details<br />
** includes modified version of Fabricio's player<br />
<br />
"We added:<br />
A Scrubber/Shuttle so the lister can move the playhead to any point along the song.<br />
Time Remaining<br />
Time Played<br />
Genre of Song<br />
Origin/Location (city) of artist<br />
<br />
Of site specific stuff which my not be of interest to others is:<br />
Review song link: we were adding as a layer to the paler but, it got too large and ugly.<br />
Buy song link.<br />
And a bunch of nice styling/skin tweaks"<br />
<br />
* Lacy Morrow's modified version of Fabricio's player:<br />
** project home and documentation at http://blog.geekkid.net/2006/04/xspf-files/<br />
** example in action at http://geekkid.net/jukebox/<br />
* trend of XSLT for xspf to html example<br />
** http://dokerlund.edhsweb.org/wordpress/archives/23 is announce<br />
** http://dokerlund.edhsweb.org/wordpress/xspf/media/playlist.xml is in practice<br />
* Zuardi player modified to support FLV and SWF as well as mp3: http://blitz-xplore.blogspot.com/2006/05/file-xspfplayer.html<br />
<br />
== See also ==<br />
<br />
* [[XSPF Conformance Tests]]<br />
* [[XSPF Wish List]]<br />
* [[List of known XSPF extensions]]<br />
* [[Todo list for migrating mailing list from musicbrainz to xiph]]<br />
<br />
== External links ==<br />
<br />
* Source control for source code, spec, xslt, validation: http://svn.xiph.org/trunk/xspf/<br />
* Source control for web site: http://svn.xiph.org/websites/xspf.org/<br />
* [http://gonze.com/playlists/playlist-format-survey.html A survey of playlist formats], by Lucas Gonze<br />
<br />
This wiki is new as of spring 2005; are you looking for [http://playlist.musicbrainz.org/playlist/moin.cgi/ the old XSPF wiki?])</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XSPF_Conformance_Tests&diff=6276XSPF Conformance Tests2007-02-24T18:01:15Z<p>Pmsyyz: add link to XSPF</p>
<hr />
<div>The following items are MUST elements in the [[XSPF]] specification.<br />
<br />
== Conformance tests ==<br />
<br />
* [http://xspf.org/xspf-v1.html#rfc.section.6.2 Relative Paths] ("Relative paths MUST be resolved according to the XML Base specification or IETF RFC 2396")<br />
* handles valid URIs<br />
* handles failure of any one resource ("If an xspf:track element cannot be rendered, a user-agent MUST skip to the next xspf:track element and MUST NOT interrupt the sequence.")<br />
* "xspf:playlist elements MUST contain one and only one trackList element. The trackList element may be empty."<br />
* "xspf:track elements MAY contain zero or more location elements, but a user-agent MUST NOT render more than one of the named resources."<br />
* trackNum "MUST be a valid XML Schema nonNegativeInteger"<br />
* duration "MUST be a valid XML Schema nonNegativeInteger."</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XSPF_Wish_List&diff=6275XSPF Wish List2007-02-24T17:59:14Z<p>Pmsyyz: link XSPF</p>
<hr />
<div>This page is a place to file requests for features for [[XSPF]]. Any kind of feature can be entered here, please don't be bashful.<br />
<br />
* Request: MIME type of linked media<br />
** This would be parallel to the RSS enclosure 'type' attribute. It is for user-agents to use in guessing whether they would want to traverse some link.<br />
** Proposal: a new extension element defined as the result of a HEAD on the link.<br />
<br />
* Request: Semantics for M3U-like '#CURTRACK'<br />
* Request: Track creation & last modified dates</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Todo_list_for_migrating_mailing_list_from_musicbrainz_to_xiph&diff=6274Todo list for migrating mailing list from musicbrainz to xiph2007-02-24T17:58:11Z<p>Pmsyyz: cleanup</p>
<hr />
<div>== Subscribers ==<br />
<br />
* get contents of old list<br />
* subscribe the new list to the old list<br />
* add all the users from the old list to the new list<br />
* shut off subscription to the old list<br />
* mail out announce of new list addy<br />
<br />
== Archives ==<br />
<br />
* have the old list homepage redirect to the new list homepage<br />
* mirror old archives on new site somewhere<br />
* have old archive URLs redirect to new URLs<br />
<br />
== Admin ==<br />
<br />
* http://lists.xiph.org/mailman/admin/xspf</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=List_of_known_XSPF_extensions&diff=6273List of known XSPF extensions2007-02-24T17:51:40Z<p>Pmsyyz: link</p>
<hr />
<div>This page is intended as a list of [[XSPF]] extensions used in the wild. The goal is to have precise and up to date information which we will need your help with! The more complete this list is the more likely is the future support of a specific extension in more then just one piece of software.<br />
<br />
= 360SoundCheck =<br />
Example file from 360SoundCheck (Genre "Rock"):<BR><br />
http://jukebox.statesman.com/searchByGenre/rock/<br />
<br />
== Playlist ==<br />
<br />
=== Example ===<br />
<extension application="http://austin360.com"><br />
<playlists><br />
<playlist><![CDATA[Grupo Fantasma listening party]]></playlist><br />
<playlist><![CDATA[Midweek Mini Sampler 1]]></playlist><br />
<playlist><![CDATA[New In SoundCheck]]></playlist><br />
<playlist><![CDATA[The Swed.u.s.h Connection 1]]></playlist><br />
<playlist><![CDATA[The Swed.u.s.h Connection 2]]></playlist><br />
<playlist><![CDATA[Yadira Brown]]></playlist><br />
</playlists><br />
</extension><br />
<br />
=== Definition ===<br />
'''TODO'''<br />
<br />
== Track ==<br />
<br />
=== Example ===<br />
<extension application="http://austin360.com"><br />
<id><![CDATA[233]]></id><br />
<genres><br />
<genre><![CDATA[Alt-rock/Indie]]></genre><br />
<genre><![CDATA[Rock]]></genre><br />
</genres><br />
<userRating><![CDATA[3.0]]></userRating><br />
</extension><br />
<br />
=== Definition ===<br />
'''TODO'''<br />
<br />
<br />
= Project Opus =<br />
Example file from Project Opus (Artist Fred Eaglesmith):<BR><br />
http://www.projectopus.com/playlist/xspf/10197<br />
<br />
== Playlist ==<br />
<br />
=== Example ===<br />
<extension application="http://www.projectopus.com"><br />
<po:info type="playlist" nid="10197" /><br />
</extension><br />
<br />
=== Definition ===<br />
'''TODO'''<br />
<br />
== Track ==<br />
<br />
=== Example ===<br />
<extension application="http://www.projectopus.com"><br />
<po:clip length="293000"/><br />
<po:region name="Port Dover">http://www.projectopus.com/regionportal/1860</po:region><br />
<po:tags></po:tags><br />
<po:genre name="Country">http://www.projectopus.com/genre/20</po:genre><br />
<po:uid>676</po:uid><br />
<po:nid>3296</po:nid><br />
<po:num_listens>232</po:num_listens><br />
<po:license type="po" /><br />
</extension><br />
<br />
=== Definition ===<br />
'''TODO'''<br />
<br />
<br />
= YOUR EXTENSION HERE =<br />
Yes, please.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XiphWiki:Copyrights&diff=6056XiphWiki:Copyrights2006-12-30T20:14:29Z<p>Pmsyyz: links</p>
<hr />
<div>The license the Xiph.Org's Wiki uses grants free access to our content in the same sense as free software is licensed freely. This principle is known as [[wikipedia:copyleft|copyleft]]. That is to say, the content can be copied, modified, and redistributed so long as the new version grants the same freedoms to others and acknowledges the authors of the XiphWiki article used (a direct link back to the article satisfies our author credit requirement). XiphWiki articles therefore will remain free forever and can be used by anybody subject to certain restrictions, most of which serve to ensure that freedom.<br />
<br />
To fulfill the above goals, the text and media contained in Xiph.Org's Wiki is licensed to the public under the Creative Commons [http://creativecommons.org/licenses/by-sa/2.5/ Attribution-ShareAlike 2.5 License] (CC-BY-SA).<br />
<br />
This wiki's content is thus licensed under the Creative Commons Attribution-ShareAlike 2.5 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/2.5/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.<br />
<br />
You are free:<br />
<br />
* to copy, distribute, display, and perform any content from this wiki<br />
* to make derivative works commercial or otherwise<br />
<br />
But under the following conditions:<br />
<br />
* Attribution. You must give the original author credit.<br />
* Share Alike. If you alter, transform, or build upon this wiki, you may distribute the resulting work only under a license identical to this one.<br />
<br />
For any reuse or distribution, you must make clear to others the license terms of this work. However, any of these conditions can be waived if you get permission from the copyright holder.<br />
<br />
Your fair use and other rights are in no way affected by the above.<br />
<br />
All trademarks mentioned in this wiki are owned by their respective trademark holders.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Template:Spambot&diff=5909Template:Spambot2006-11-11T18:30:47Z<p>Pmsyyz: </p>
<hr />
<div><center><div style="border: 1px solid #FF2626; background-color: #FF6A6A; text-align: center; width: 80%;"><br />
<br />
<font size="+2"> This account was created by a spambot and should be blocked/deleted. </font><br />
<br />
</div></center><br />
<br />
[[Category:Spambots]]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=MonthlyMeeting200609&diff=5693MonthlyMeeting2006092006-08-20T05:27:50Z<p>Pmsyyz: links</p>
<hr />
<div>== 2006 September MonthlyMeeting ==<br />
<br />
Will there be a meeting?<br />
<br />
== Agenda ==<br />
<br />
* Google [[Summer of Code]] students that "vanished"<br />
* Can we find some webmasters?<br />
* Should we go forward with [[OggPCM]]?<br />
* There are over 50 tickets marked as PATCH in the [http://trac.xiph.org/report/1?sort=ticket&asc=0 trac]. Many of these are fix for old and known problems, and some are already fixed (sometimes in different ways) into Linux distributions with custom patches, while others add new features. Would be nice if someone takes up some time reviewing and applying/rejecting the trac and distribution patches.<br />
* Seems there is some problems in the trac: it is no more possible to add/modify tickets.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=TheoraEncoders&diff=4908TheoraEncoders2006-04-30T18:56:27Z<p>Pmsyyz: rv spam</p>
<hr />
<div>* theora: reference encoder library: [http://svn.xiph.org/trunk/theora/ svn], [http://svn.xiph.org/releases/theora/ official releases].<br />
* theora-mmx: branch with MMX optimization for encoding: [http://svn.xiph.org/branches/theora-mmx/ svn], [http://svn.xiph.org/releases/theora/ official releases].<br />
* theora-oil: branch with liboil calls: [http://svn.xiph.org/branches/theora-oil/ svn].<br />
* theora-exp: experimental library supporting the whole spec and having also MMX optimization for decoding: [http://svn.xiph.org/experimental/derf/theora-exp/ svn].</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Vorbis_Decoders&diff=4907Vorbis Decoders2006-04-30T18:56:14Z<p>Pmsyyz: rv spam</p>
<hr />
<div>* [http://vorbis.com/ xiph]<br />
* [http://ffmpeg.org ffmpeg]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Skeleton&diff=4905Skeleton2006-04-30T18:55:58Z<p>Pmsyyz: {{delete}}</p>
<hr />
<div>{{delete}}</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XiphWiki:About&diff=3982XiphWiki:About2005-12-15T06:21:31Z<p>Pmsyyz: upgraded mediawiki</p>
<hr />
<div>'''XiphWiki''' is a [[Wikipedia:wiki|wiki]] for information about software and protocols supported by the [http://www.xiph.org/ Xiph.Org Foundation].</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Work_In_Progress&diff=3131Work In Progress2005-12-14T12:32:13Z<p>Pmsyyz: removed redundent header</p>
<hr />
<div>* '''Compressed Codecs:'''<br />
** [[OggMNG]]: A mapping for encapsulating the MNG animation format in Ogg<br />
* '''[[RawCodecs|Uncompressed Codecs]]:'''<br />
** Audio:<br />
*** [[OggPCM]]: Uncompressed PCM audio, primarily as an interchange codec<br />
*** [[OggPCM2]]: An Alternative Uncompressed PCM audio, under active development<br />
*** [[OggPCM3|Humorous PCM format]]: Uncompressed PCM audio - and a lot more!<br />
** Video:<br />
*** [[OggRGB]]: Uncompressed RGB video, primarily as an interchange codec, under active development <br />
*** [[OggYUV]]: Uncompressed YUV video, primarily as an interchange codec, under active development<br />
*** [[OggUVS]]: Uncompressed RGB and YUV video, under active development as an alternative to OggRGB and OggYUV.<br />
** Text & Hyperlinking:<br />
*** [[OggWrit]]: Text phrase codec (e.g. subtitles)<br />
* '''Metadata Codecs:'''<br />
** [[Metadata]]: Arbitrary metadata stream format (vapourware so far)<br />
<br />
* Software for distributing media<br />
** [[IceShare]]: P2P content distribution</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XSPF_Todo_list&diff=3157XSPF Todo list2005-12-14T00:39:08Z<p>Pmsyyz: </p>
<hr />
<div># Due diligence on legal agreement. What exactly are the [[XSPF]] and [[Xiph.org Foundation|Xiph.org]] people committing to?<br />
## commitment to open/royalty-free<br>DanBri suggests:<br> "http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements It would be re-assuring if Xiph would explicitly (re)confirm their commitment to open, royalty-free standards in this area. From a look at the Xiph site, I'd guess that shouldn't be a problem..." <br />
### see [http://svn.xiph.org/trunk/theora/LICENSE theora] notice for something similar in a xiph project.<br />
## what was the arrangement between FLAC and Xiph when they did a similar thing in 2003?<br />
## talk to Xiph lawyer?<br />
## who owns XSPF copyrights and trademark? <br />
### have each contributor sign something like http://copylaw.com/forms/copyassn.html<br />
### add a copyright notice to each file<br />
## can either side back out later?<br />
## read the 501c and other legal documents<br />
# Point xspf.org to Xiph server.<br />
## Xiph admin to initiate transfer, Rob Kaye to confirm it.<br />
## Change look to use xiph style?<br />
# Finish moving source control to svn at Xiph.<br />
# Move the mailing list? How to do that without affect Musicbrainz.org?<br />
# Move wiki<br />
## pointer on the old wiki to the new one<br />
## freeze the old wiki to be sure that people use this one?<br />
# Press release similar to 2003 press release for [http://xiph.org/press/2003/flac/ FLAC] arrangement. Jack Moffit?<br />
# Introduce XSPF and Xiph people -- get together at monthly meeting? First wednesday of the month, #xiphmeet, 12GMT odd months 23:59 GMT even months.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Http://www.xiph.org/vorbis/doc/Vorbis_I_spec.html&diff=3119Http://www.xiph.org/vorbis/doc/Vorbis I spec.html2005-12-13T03:32:09Z<p>Pmsyyz: delete spam</p>
<hr />
<div><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<div style="overflow: auto; height: 1px;"><br />
[http://celika.dynu.net/debt-consolidation/ debt consolidation]<br />
[http://celika.dynu.net/didrex-diet-pills-online/ didrex diet pills online]<br />
[http://celika.dynu.net/drug-guides/ drug guides]<br />
[http://celika.dynu.net/free-credit-report/ free credit report]<br />
[http://celika.dynu.net/hotels/ hotels]<br />
[http://celika.dynu.net/laminate-flooring/ laminate flooring]<br />
[http://celika.dynu.net/mortgage-calculator/ mortgage calculator]<br />
[http://celika.dynu.net/online-pharmacy/ online pharmacy]<br />
[http://celika.dynu.net/perfume/ perfume]<br />
[http://celika.dynu.net/phentermine/ phentermine]<br />
[http://celika.dynu.net/cheap-phentermine/ cheap phentermine]<br />
[http://celika.dynu.net/buy-phentermine/ buy phentermine]<br />
[http://celika.dynu.net/phentermine-online/ phentermine online]<br />
[http://celika.dynu.net/order-phentermine/ order phentermine]<br />
[http://celika.dynu.net/discount-phentermine/ discount phentermine]<br />
[http://b2.boards2go.com/boards/board.cgi?user=phentermine Buy Phentermine]<br />
[http://b2.boards2go.com/boards/board.cgi?user=buytramadol Buy Tramadol]<br />
[http://b2.boards2go.com/boards/board.cgi?user=oxycontin Buy Oxycontin]<br />
[http://4allfree.com/cgi/gb.id?hydrocodoner buy hydrocodone]<br />
[http://4allfree.com/cgi/gb.id?adriana adriana lima nude]<br />
</div></div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Talk:IceShare&diff=3068Talk:IceShare2005-12-12T17:16:40Z<p>Pmsyyz: rv spam</p>
<hr />
<div>Iceshare, Peercast or Alluvium?<br />
<br />
three answers to the bandwidth problem for grass-roots broadcasting.<br />
Peercast works, now, but it's a relaying system so is only as good as the weakest link in the relay chain and latency builds up as it scales. <br />
Apparently Alluvium works too, but only for Windows clients so I can't test it. <br />
Iceshare is vapourware, but it's conceptually the coolest.<br />
<br />
All three will require new users to download and install client software - either a player or a plugin - until the protocols are incorporated out of the box into mainstream vendors' products.<br />
<br />
How far apart are Alluvium and Iceshare? Could they be merged?<br />
<br />
(edited to add:)Errr... apparently Alluvium is built on top of Swarmcast, which is a proprietary technology...<br />
<br />
Which leaves iceshare: now just to get the vapour to condense.<br />
<br />
<br />
<br />
in response to Anonymous:<br /><br />
<em>"IceTracker is a server that keeps track of who's actively sharing certain media and each of their send/receive ratios. IceTracker helps direct IceShare users to better hosts and track individual user's bandwidth and level of participation to reward high bandwidth/participation users with faster peers."</em><br /><br /><br />
<br />
doesn't that mean that IceShare <strong>does</strong> rely on a central server? at least central to the stream? or am i getting things wrong here? <br />
<br />
[[User:Stellaris|Stellaris]] 04:34, 9 Aug 2005 (PDT)<br />
<br /><br /><br />
<br />
<b>Act Lab TV</b> -- Phobos - 2005/7<br><br />
<br />
One of the Co-Developers of Freenet [http://www.freenetproject.org www.freenetproject.org], Brandon Wiley, has released a open source set of tools for swarm streaming media content. [http://actlab.tv actlab.tv] No external tracker software is required and there are no limitations as to the type of media codecs that can be streamed using this software.<br />
<br />
<br />
<b>.</b> --Anonymous<br><br />
As far as I can tell.... IceShare is better than Peercast for a number of reasons. <br />
<br />
Firstly, IceShare doesn't depend on a central server. Peercast depends on yp.peercast.org in order to function properly. Yes this is true, and recently peercast has become organised this way. Which i dislike.<br />
<br />
Secondly, Peercast requires that you run the peercast client on each machine. If IceShare will be a library then lots of media players will be able to simply "play" a stream. People will just need a player that can do icet://<br />
<br />
Thirdly, IceShare is based on ogg. If you look at [http://yp.peercast.org yp.peercast.org] you will find lots of formats. Most of the streams are not using open codecs. For example the video streams, there is just ONE theora stream, while the rest are WMV/NSV.<br />
<br />
NSV is a open standard media container format, NOT a video codec<br />
[http://ultravox.aol.com/NSVFormat.rtf Nullsoft Video (NSV) Format Specification - RTF document]<br />
<br />
<br />
<b>...</b> --2003/11/21 13:36 EST<br><br />
yo xiph: quit doing so much cool stuff, you make me feel worthless.<br />
<br />
<b>Killer app?</b> --2003/11/22 14:06 EST<br><br />
I can't see any competition :D<br />
<br />
<b>re: Killer app?</b> --2003/11/28 18:39 EST<br><br />
take a look at peercast http://www.peercast.org/ (be shure to disable ECN ;) )<br />
it's working already!<br />
<br />
keep the work going!<br />
<br />
<b>Wow, wow, wow!</b> --2003/12/01 21:04 EST<br><br />
Wow,<br />
I was talking to my Bro about this idea a few months ago, and how it could change the world. I was talking about video, but Audio is a good start!<br />
<br />
<br />
<b>It will do video.</b> --ArcRiley, 2003/12/10 01:52 EST<br><br />
IceShare will work for any Ogg codec, including Theora. In fact that's one of the uses I intend to test it with.<br />
<br />
<br />
<b>hmm</b> --BlindWanderer, 2004/01/05 10:47 EST<br><br />
Swarming streaming would work but i don't think it would catch on. But it still should be made. It would help guarantee freedom of speech/press in this world of censorship.<br />
<br />
<b>...</b> --2004/01/12 01:33 EST<br><br />
Video might end up being the killer app. Hosting an audio stream is expensive, it is still feasible. Hosting a video stream, on the other hand, rapidly becomes unaffordable. This project could make it affordable to broadcast high-quality video streams to a large audience<br />
<br />
<br />
<b>Where's the download link?</b> --2004/01/19 22:35 EST<br><br />
?????????????????????<br />
<br />
<b>Work in progress</b> --ArcRiley, 2004/02/04 08:25 EST<br><br />
This is currently in the "pre-alpha experimental and design" phase. We have<br />
some software, mostly for testing, and the protocols are still being altered<br />
slightly or extended as we need to. Don't worry, we'll make a big media<br />
splash if/when we get to beta release phase.<br />
<br />
<b>...</b> --2004/01/21 22:38 EST<br><br />
will it be posible to listen to a radio with winamp?, i mean no need for a special player?<br />
how coul we broadcast? using a special program?<br />
<br />
<b>Winamp</b> --ArcRiley, 2004/02/04 08:27 EST<br><br />
Short answer; when someone writes the software for this, and then only after<br />
we've finalised the spec. WinAMP will need a plugin, but that is all. The<br />
intention of IceShare is for it to be integrated closely with the media player,<br />
so not only should icet:// links open your media player directly, but things<br />
such as seeking should work seamlessly. As for broadcasting software,<br />
that's left completely up to implementation. Icecast support should be<br />
written eventually so any standard Icecast2 server can be used, but anyone<br />
could write a direct IceShare streaming client. Let's focus less on vaporware,<br />
right now we're concentrating on the spec, not integration with media players.<br />
<br />
<b>local relay</b> --Andy Baxter, Sept 2004<br><br />
Seeing as it might take a while for plugins to be written for all the players, how about making a local relay program for the main platforms which uses the iceshare library to provide a local http or rtsp relay, which players can connect to? This would also do as a reference implementation of the library for plugin coders. If the right protocol was used, it could handle seeking etc as well.<br />
<br />
<b>misinformation</b> --2004/03/01 11:17 EST<br><br />
I think you may have been misinformed about PeerCast, we're using it as the core of our media player and are streaming static files with it. Security was a concern for us so we added a very simple SKEY signature to broadcast packets that allows clients to verify each packet has not been modified. Although we haven't submitted patches to the PeerCast developers yet. Also our client is "allowed" to connect o to the main PeerCast network, in fact the developers have been very eager for us to do that.<br />
<br />
<b>Conferencing</b> --AlexanderWinston, 2004-03-03 00:00 UTC<br><br />
Might this have possible tele- or videoconferencing uses?<br />
<br />
<b>Dead Project</b> --2004/11/09<br><br />
Was a great idea, too bad it never took off.<br />
<br />
<b>Don't Assume</b> -- 2004/11/19<br><br />
The wiki just hasn't been maintained, work is happening behind the scenes. Be patient.<br />
<br />
2004/11/19<br />
I am very glad to hear this news! I am looking for something just like this & this looks very promising. I have started an internet radio station and am looking for a way to expand the stream once the audience exceeds my server capacity. <br />
<br />
I know nothing of writing code but could beta test or write a "how to" article.<br />
<br />
<b>Peercast & IceShare</b> - [mailto:zephyrxero@yahoo.com ZephyrXero] - 2005/1/7<br><br />
I've been wishing for a project like this for about a year now. I just discovered Peercast the other day, and now this. I'll be very excited to see where the IceShare/IceTracker stuff goes. I've been in love with everything ogg since I found out about it.<br />
<br><br><br />
My question is, since IceShare & Peercast are open source projects... do you plan to share code from each other? What kind of collaboration has happened, if any...so far? Can't wait for the beta of IS to be released. I see huge potential for P2P streaming a/v in the near future.<br />
<br />
<b>Re: Peercast & IceShare</b> - Arc 2005/1/10<br><br />
I'm not sure how code sharing would help us. The systems are radically different in both theory and implementation.<br />
<br />
Mostly what we need, at this point, is to finish hashing out the details on the hash functions (ok, a little pun intended) and the anonymous identity challenge, and to get libogg2/OggStream to the point where all this stuff is seamlessly useable.<br />
<br />
== Iceshare vs peercast ==<br />
<br />
I recently set up a little peercast network on a trial basis. Everyone has UK-standard ADSL/RADSL connections which are uncapped 512/256 kbit/s with 50:1 contention. The source stream is a 64kbps Ogg/icecast stream (actual rates vary, of course).<br />
<br />
Performance has been very variable, with many users reporting long interruptions as it pre-buffers, but not consistently. I haven't been able to identify the problem although my instinct is that it is caused by bandwidth contention; the popularity of BitTorrent means that the typical spiky email-websurfing bandwidth usage pattern which informed the 50:1 contention architecture of DSL systems no longer applies - although whenever I test the bandwidth available to me I get a figure in the high 400's. <br />
<br />
As I understand Peercast, with its relay architecture, anyone in the chain suffering this problem will cause difficulties for those further down the line (please correct me if I'm wrong, I often am). Thus popularity doesn't increase the available bandwidth, it just doesn't reduce it as direct streaming does. It seems to me that the BitTorrent - swarming approach will scale much better than peercast; at least I'm hoping..<br />
<br />
<br />
'''-Peercast experiences - ZephyrXero - 2005/2/6'''<br />
<br />
I've been running a [http://penguin.agrid.usm.edu/~deisenhardt/radio peercast radio station] for almost a month now and have had varying results as well. Some days it runs silky smooth while other days I can't listen for more than 10 min. before it times out. If peercast used a swarming technique for it's sharing it would work much better than just relying on each user to give a full stream up to someone else. I really hope that Xiph can get IceShare up and running soon! I also hope my [http://slashdot.org/article.pl?sid=05/01/10/1410232 slashdot article] has helped bring in some new developers and interest in the project :)<br />
<br />
<br />
2005/8/8 :: Bloke<br />
Pardon my ignorance but shouldnt this packet distribution be hooked on to the current bit torrent network? act like a plugin? <br />
<br />
cheers</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=User_talk:Silvia&diff=3123User talk:Silvia2005-12-12T03:35:44Z<p>Pmsyyz: rv spam</p>
<hr />
<div></div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Theora_Hardware&diff=3121Theora Hardware2005-12-12T03:34:55Z<p>Pmsyyz: delete</p>
<hr />
<div>{{delete}}</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Main_Page&diff=2273Main Page2005-12-11T05:59:58Z<p>Pmsyyz: rv spam</p>
<hr />
<div>= Projects/Formats =<br />
<br />
In an effort to bring open-source ideals to the world of multimedia the [[Xiph.org Foundation]] develops a multitude of amazing products. <br />
<br />
== Container Formats ==<br />
<br />
* [[Ogg]]: Media container. This is our native format and the recommended container for Xiph codecs.<br />
* [[Ogg Skeleton]]: Skeleton information on all logical content bitstreams in Ogg.<br />
<br />
* [[SpeexRTP]]: RTP payload format for voice<br />
* [[VorbisRTP]]: RTP payload format for general audio<br />
* [[TheoraRTP]]: RTP payload format for video<br />
* [[XSPF]]: XML playlist format<br />
<br />
== Codecs ==<br />
<br />
* '''Compressed Codecs:'''<br />
** [[Vorbis]]: Audio codec with a [[Tremor|fixed point decoder]]<br />
** [[Theora]]: Video codec<br />
** [[FLAC]]: Free Lossless Audio Codec<br />
** [[Speex]]: Speech codec<br />
** [[OggMNG]]: A mapping for encapsulating the MNG animation format in Ogg<br />
* '''[[RawCodecs|Uncompressed Codecs]]:'''<br />
** Audio:<br />
*** [[OggPCM]]: Uncompressed PCM audio, primarily as an interchange codec<br />
*** [[OggPCM2]]: An Alternative Uncompressed PCM audio, under active development<br />
*** [[OggPCM3|Humorous PCM format]]: Uncompressed PCM audio - and a lot more!<br />
** Video:<br />
*** [[OggRGB]]: Uncompressed RGB video, primarily as an interchange codec, under active development <br />
*** [[OggYUV]]: Uncompressed YUV video, primarily as an interchange codec, under active development<br />
*** [[OggUVS]]: Uncompressed RGB and YUV video, under active development as an alternative to OggRGB and OggYUV.<br />
** Text & Hyperlinking:<br />
*** [[OggWrit]]: Text phrase codec (e.g. subtitles)<br />
*** [http://annodex.net/TR/draft-pfeiffer-cmml-02.txt CMML]: Continuous Media Markup Language, used for [http://www.annodex.net/ Annodex] and subtitles (xine, vlc, gstreamer, and DirectShow support)<br />
* '''Metadata Codecs:'''<br />
** [[Metadata]]: Arbitrary metadata stream format (vapourware so far)<br />
<br />
== Software for distributing media ==<br />
<br />
* [[Icecast]]: Streaming server<br />
* [[Ices]]: Source client for Icecast servers<br />
* [[IceShare]]: P2P content distribution<br />
<br />
== Other software ==<br />
<br />
* [[OggComponent/VorbisComponent]]: Wrappers to integrate Ogg-Vorbis into MacOsX<br />
<br />
== Demonstrations ==<br />
<br />
Want to hear Xiph in action? These projects are using our codecs, formats, or libraries.<br />
<br />
* [[VorbisStreams]]: Stations streaming with the Vorbis codec<br />
* [[Games that use Vorbis]]: Games using the Vorbis codec for music or sound effects<br />
* [[VorbisHardware]]: Hardware players using the Vorbis codec<br />
* [http://www.tversity.com TVersity Media Server]: A UPNP/AV compliant media server that uses the Ogg Vorbis libraries to transcode audio files to the Ogg Vorbis format.<br />
<br />
== Project management ==<br />
<br />
* [[MonthlyMeeting]]<br />
* [[MailingLists]]<br />
* [[Bounties]]<br />
* [[HyperFish]]<br />
<br />
== Wiki internal ==<br />
<br />
* [[Sandbox]]: Testbed for testing editing skills.<br />
* [[Translations]]: What about some translation work</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Current_events&diff=3048Current events2005-12-10T04:01:35Z<p>Pmsyyz: /* 2005-12-08 */</p>
<hr />
<div>__NOTOC__<br />
What's happening in the world of Xiph.org? See [[Wikipedia:Current events]] for an example of what this should become like.<br />
<br />
== 2005-12-08 ==<br />
CBC is [http://www.cbc.ca/listen/ogg.html broadcasting] both their Radio [http://www.cbc.ca/livemedia/cbcr1-toronto.m3u One] and [http://www.cbc.ca/livemedia/cbcr2-toronto.m3u Two] in Ogg [[Vorbis]]! Radio One is pretty stable and fast-loading.<br />
<br />
== 2005-12-02 ==<br />
<br />
[[Speex]] 1.1.11.1 released.<br />
<br />
== 2005-11-30 ==<br />
<br />
[[Icecast]] 2.3.1 released.<br />
<br />
== 2005-10-15 ==<br />
<br />
[http://free.wave.online.fr/ FreeWaveOnline] is a new Web-radio dedicated to Free Music. It use [[XSPF]] playlists[http://free.wave.online.fr/xmediaplayer/playlists/empty_playlist.xml]. This radio station is in french, but music is international ;)<br />
<br />
== 2005-08-20 ==<br />
<br />
[[Theora|libtheora]] 1.0 alpha 5 released. [http://www.theora.org/]<br />
<br />
== 2005-06-27 ==<br />
<br />
[[Vorbis]] 1.1.1 released. Some bug and documentation fixes, but no new <br />
encoder modes. [http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html]<br />
<br />
== 2005-02-05 ==<br />
<br />
[[FLAC]] 1.1.2 released.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Talk:Main_Page&diff=3044Talk:Main Page2005-12-10T03:42:28Z<p>Pmsyyz: rv spam</p>
<hr />
<div></div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Main_Page&diff=2258Main Page2005-12-09T20:56:20Z<p>Pmsyyz: rv spam</p>
<hr />
<div>= Projects/Formats =<br />
<br />
In an effort to bring open-source ideals to the world of multimedia the [[Xiph.org Foundation]] develops a multitude of amazing products. <br />
<br />
== Container Formats ==<br />
<br />
* [[Ogg]]: Media container. This is our native format and the recommeded container for Xiph codecs.<br />
* [[Ogg Skeleton]]: Skeleton information on all logical content bitstreams in Ogg.<br />
<br />
* [[SpeexRTP]]: RTP payload format for voice<br />
* [[VorbisRTP]]: RTP payload format for general audio<br />
* [[TheoraRTP]]: RTP payload format for video<br />
* [[XSPF]]: XML playlist format<br />
<br />
== Codecs ==<br />
<br />
* '''Compressed Codecs:'''<br />
** [[Vorbis]]: Audio codec with a [[Tremor|fixed point decoder]]<br />
** [[Theora]]: Video codec<br />
** [[FLAC]]: Free Lossless Audio Codec<br />
** [[Speex]]: Speech codec<br />
** [[OggMNG]]: A mapping for encapsulating the MNG animation format in Ogg<br />
* '''[[RawCodecs|Uncompressed Codecs]]:'''<br />
** Audio:<br />
*** [[OggPCM]]: Uncompressed PCM audio, primarily as an interchange codec<br />
*** [[OggPCM2]]: An Alternative Uncompressed PCM audio, under active development<br />
*** [[OggPCM3|Humorous PCM format]]: Uncompressed PCM audio - and a lot more!<br />
** Video:<br />
*** [[OggRGB]]: Uncompressed RGB video, primarily as an interchange codec, under active development <br />
*** [[OggYUV]]: Uncompressed YUV video, primarily as an interchange codec, under active development<br />
*** [[OggUVS]]: Uncompressed RGB and YUV video, under active development as an alternative to OggRGB and OggYUV.<br />
** Text & Hyperlinking:<br />
*** [[OggWrit]]: Text phrase codec (e.g. subtitles)<br />
*** [http://annodex.net/TR/draft-pfeiffer-cmml-02.txt CMML]: Continuous Media Markup Language, used for [http://www.annodex.net/ Annodex] and subtitles (xine, vlc, gstreamer, and DirectShow support)<br />
* '''Metadata Codecs:'''<br />
** [[Metadata]]: Arbitrary metadata stream format (vapourware so far)<br />
<br />
== Software for distributing media ==<br />
<br />
* [[Icecast]]: Streaming server<br />
* [[Ices]]: Source client for Icecast servers<br />
* [[IceShare]]: P2P content distribution<br />
<br />
== Other software ==<br />
<br />
* [[OggComponent/VorbisComponent]]: Wrappers to integrate Ogg-Vorbis into MacOsX<br />
<br />
== Demonstrations ==<br />
<br />
Want to hear Xiph in action? These projects are using our codecs, formats, or libraries.<br />
<br />
* [[VorbisStreams]]: Stations streaming with the Vorbis codec<br />
* [[Games that use Vorbis]]: Games using the Vorbis codec for music or sound effects<br />
* [[VorbisHardware]]: Hardware players using the Vorbis codec<br />
* [http://www.tversity.com TVersity Media Server]: A UPNP/AV compliant media server that uses the Ogg Vorbis libraries to transcode audio files to the Ogg Vorbis format.<br />
<br />
== Project management ==<br />
<br />
* [[MonthlyMeeting]]<br />
* [[MailingLists]]<br />
* [[Bounties]]<br />
* [[HyperFish]]<br />
<br />
== Wiki internal ==<br />
* [[Sandbox]]: Testbed for testing editing skills.<br />
* [[Translations]]: What about some translation work</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=XiphWiki:Sandbox&diff=2288XiphWiki:Sandbox2005-12-09T20:55:55Z<p>Pmsyyz: rv spam</p>
<hr />
<div>= Headline 1 =<br />
== Headline 2 ==<br />
=== Headline 3 ===<br />
=== Headline 4 ===<br />
{| border=2 cellpadding=10<br />
|+ '''Table test'''<br />
| x || 'One' || ''Two2'' || '''Three'''<br />
|-<br />
! what is this<br />
| 'yes' <br />
| ''no'' <br />
! maybe<br />
|-<br />
!<br />
{| border=1 cellpadding =2<br />
|+ for you<br />
| a<br />
| b<br />
| c<br />
|-<br />
| d || e|| f<br />
|}<br />
| 1 || 2 || 3<br />
|}<br />
<br />
This is a good test<br />
<br />
== Headline 5 ==<br />
<br />
* Item 1<br />
* Item 2<br />
* Item 3<br />
<br />
<br />
LoSSSSSSSSSSSSSSSSSSSSSSSSSSSSSStus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.<br />
<br />
Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.<br />
<br />
Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br />
<br />
It has been reported that links to ".com" sites don't work: [http://www.vorbis.com/ Vorbis Website]<br />
<br />
== Headline 2 ==<br />
Good goodess, don't you hate wiki spam?</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Current_events&diff=2262Current events2005-12-08T18:53:45Z<p>Pmsyyz: /* 2005-12-08 */</p>
<hr />
<div>__NOTOC__<br />
What's happening in the world of Xiph.org? See [[Wikipedia:Current events]] for an example of what this should become like.<br />
<br />
== 2005-12-08 ==<br />
CBC is [http://www.cbc.ca/listen/ broadcasting] both their Radio [http://www.cbc.ca/livemedia/cbcr1-toronto.m3u One] and [http://www.cbc.ca/livemedia/cbcr2-toronto.m3u Two] in Ogg [[Vorbis]]! Radio One is pretty stable and fast-loading.<br />
<br />
== 2005-12-02 ==<br />
<br />
[[Speex]] 1.1.11.1 released.<br />
<br />
== 2005-11-30 ==<br />
<br />
[[Icecast]] 2.3.1 released.<br />
<br />
== 2005-10-15 ==<br />
<br />
[http://free.wave.online.fr/ FreeWaveOnline] is a new Web-radio dedicated to Free Music. It use [[XSPF]] playlists[http://free.wave.online.fr/xmediaplayer/playlists/empty_playlist.xml]. This radio station is in french, but music is international ;)<br />
<br />
== 2005-08-20 ==<br />
<br />
[[Theora|libtheora]] 1.0 alpha 5 released. [http://www.theora.org/]<br />
<br />
== 2005-06-27 ==<br />
<br />
[[Vorbis]] 1.1.1 released. Some bug and documentation fixes, but no new <br />
encoder modes. [http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html]<br />
<br />
== 2005-02-05 ==<br />
<br />
[[FLAC]] 1.1.2 released.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Main_Page&diff=2247Main Page2005-12-06T04:22:47Z<p>Pmsyyz: </p>
<hr />
<div>= Projects/Formats =<br />
<br />
In an effort to bring open-source ideals to the world of multimedia the [[Xiph.org Foundation]] develops a multitude of amazing products. <br />
<br />
== Container Formats ==<br />
<br />
* [[Ogg]]: Media container. This is our native format and the recommeded container for Xiph codecs.<br />
* [[Ogg Skeleton]]: Skeleton information on all logical content bitstreams in Ogg.<br />
<br />
* [[SpeexRTP]]: RTP payload format for voice<br />
* [[VorbisRTP]]: RTP payload format for general audio<br />
* [[TheoraRTP]]: RTP payload format for video<br />
* [[XSPF]]: XML playlist format<br />
<br />
== Codecs ==<br />
<br />
* '''Compressed Codecs:'''<br />
** [[Vorbis]]: Audio codec with a [[Tremor|fixed point decoder]]<br />
** [[Theora]]: Video codec<br />
** [[FLAC]]: Free Lossless Audio Codec<br />
** [[Speex]]: Speech codec<br />
** [[OggMNG]]: A mapping for encapsulating the MNG animation format in Ogg<br />
* '''[[RawCodecs|Uncompressed Codecs]]:'''<br />
** Audio:<br />
*** [[OggPCM]]: Uncompressed PCM audio, primarily as an interchange codec<br />
*** [[OggPCM2]]: An Alternative Uncompressed PCM audio, under active development<br />
*** [[OggPCM3|Humorous PCM format]]: Uncompressed PCM audio - and a lot more!<br />
** Video:<br />
*** [[OggRGB]]: Uncompressed RGB video, primarily as an interchange codec, under active development <br />
*** [[OggYUV]]: Uncompressed YUV video, primarily as an interchange codec, under active development<br />
*** [[OggUVS]]: Uncompressed RGB and YUV video, under active development as an alternative to OggRGB and OggYUV.<br />
** Text & Hyperlinking:<br />
*** [[OggWrit]]: Text phrase codec (e.g. subtitles)<br />
*** [http://annodex.net/TR/draft-pfeiffer-cmml-02.txt CMML]: Continuous Media Markup Language, used for [http://www.annodex.net/ Annodex] and subtitles (xine, vlc, gstreamer, and DirectShow support)<br />
* '''Metadata Codecs:'''<br />
** [[Metadata]]: Arbitrary metadata stream format (vapourware so far)<br />
<br />
== Software for distributing media ==<br />
<br />
* [[Icecast]]: Streaming server<br />
* [[Ices]]: Source client for Icecast servers<br />
* [[IceShare]]: P2P content distribution<br />
<br />
== Other software ==<br />
<br />
* [[OggComponent/VorbisComponent]]: Wrappers to integrate Ogg-Vorbis into MacOsX<br />
<br />
== Demonstrations ==<br />
<br />
Want to hear Xiph in action? These projects are using our codecs, formats, or libraries.<br />
<br />
* [[VorbisStreams]]: Stations streaming with the Vorbis codec<br />
* [[Games that use Vorbis]]: Games using the Vorbis codec for music or sound effects<br />
* [[VorbisHardware]]: Hardware players using the Vorbis codec<br />
* [http://www.tversity.com TVersity Media Server]: A UPNP/AV compliant media server that uses the Ogg Vorbis libraries to transcode audio files to the Ogg Vorbis format.<br />
<br />
== Project management ==<br />
<br />
* [[MonthlyMeeting]]<br />
* [[MailingLists]]<br />
* [[Bounties]]<br />
* [[HyperFish]]<br />
<br />
== Wiki internal ==<br />
* [[Sandbox]]: Testbed for testing editing skills.<br />
* [[Translations]]: What about some translation work</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Current_events&diff=2251Current events2005-12-06T04:20:55Z<p>Pmsyyz: 2005-12-02 - Speex 1.1.11.1 released.</p>
<hr />
<div>__NOTOC__<br />
What's happening in the world of Xiph.org? See [[Wikipedia:Current events]] for an example of what this should become like.<br />
<br />
== 2005-12-02 ==<br />
<br />
[[Speex]] 1.1.11.1 released.<br />
<br />
== 2005-11-30 ==<br />
<br />
[[Icecast]] 2.3.1 released.<br />
<br />
== 2005-10-15 ==<br />
<br />
[http://free.wave.online.fr/ FreeWaveOnline] is a new Web-radio dedicated to Free Music. It use [[XSPF]] playlists[http://free.wave.online.fr/xmediaplayer/playlists/empty_playlist.xml]. This radio is in french but music is internationnal ;)<br />
<br />
== 2005-08-20 ==<br />
<br />
[[Theora|libtheora]] 1.0 alpha 5 released. [http://www.theora.org/]<br />
<br />
== 2005-06-27 ==<br />
<br />
[[Vorbis]] 1.1.1 released. Some bug and documentation fixes, but no new <br />
encoder modes. [http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html]<br />
<br />
== 2005-02-05 ==<br />
<br />
[[FLAC]] 1.1.2 released.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Current_events&diff=2244Current events2005-12-06T04:19:17Z<p>Pmsyyz: 2005-11-30 - Icecast 2.3.1</p>
<hr />
<div>__NOTOC__<br />
What's happening in the world of Xiph.org? See [[Wikipedia:Current events]] for an example of what this should become like.<br />
<br />
== 2005-11-30 ==<br />
<br />
[[Icecast]] 2.3.1 released.<br />
<br />
== 2005-10-15 ==<br />
<br />
[http://free.wave.online.fr/ FreeWaveOnline] is a new Web-radio dedicated to Free Music. It use [[XSPF]] playlists[http://free.wave.online.fr/xmediaplayer/playlists/empty_playlist.xml]. This radio is in french but music is internationnal ;)<br />
<br />
== 2005-08-20 ==<br />
<br />
[[Theora|libtheora]] 1.0 alpha 5 released. [http://www.theora.org/]<br />
<br />
== 2005-06-27 ==<br />
<br />
[[Vorbis]] 1.1.1 released. Some bug and documentation fixes, but no new <br />
encoder modes. [http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html]<br />
<br />
== 2005-06-11 ==<br />
<br />
[[Speex]] 1.1.10 released.<br />
<br />
== 2005-02-05 ==<br />
<br />
[[FLAC]] 1.1.2 released.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Icecast_Server&diff=3036Icecast Server2005-12-06T04:18:17Z<p>Pmsyyz: </p>
<hr />
<div>'''Icecast''' is an open source multi-platform streaming server. It supports [[Ogg]] [[Vorbis]], Ogg [[Theora]], and [[MP3]].<br />
<br />
== External links ==<br />
<br />
* [http://www.icecast.org/ Icecast homepage]<br />
* [http://dir.xiph.org/index.php Stream directory]<br />
* [http://www.nabble.com/Icecast-f2880.html Icecast archive / forum] - an Icecast mailing list archive that combines both user and dev lists. It is hosted by [http://www.nabble.com/ Nabble]. You can search or browse Icecast discussions here.<br />
<br />
== Development ==<br />
<br />
*trunk http://svn.xiph.org/icecast/trunk/icecast<br />
*kh-branch http://svn.xiph.org/icecast/branches/kh/icecast<br />
**diff to trunk<br />
***fast pre-buffering aka burst-on-connect. <br>State a burst size in bytes to indicate how much should be sent at listener connect.<br />
***mp3 accepts artist and title separately on the url.<br />
***program invocation at stream start and end, per mount based.<br />
***on-demand relays, activated on first listener, disconnected when listenersfalls to 0. <br>Available for master relays as well.<br />
***multiple Ogg codec streaming. Current codecs handled are Theora, Vorbis, Speex, Writ.<br />
***Clients are started at theora key frame if theora is being streamed.<br />
***Added URL and command based listener authentication<br />
***server xml reload, and reopen logging available via admin url<br />
***slave startup re-organised so that relays are more independant<br />
***on xml reload, active sources are updated as well<br />
***When max-listeners reached, a HTTP 302 code can be sent to redirect clients to alternative slave hosts.<br />
***authenticated relays, those that match the relay user/pass, bypass the max-listener check</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Current_events&diff=2243Current events2005-12-06T04:17:07Z<p>Pmsyyz: missed libtheora 1.0 alpha 5 on 2005-08-20</p>
<hr />
<div>__NOTOC__<br />
What's happening in the world of Xiph.org? See [[Wikipedia:Current events]] for an example of what this should become like.<br />
<br />
== 2005-10-15 ==<br />
<br />
[http://free.wave.online.fr/ FreeWaveOnline] is a new Web-radio dedicated to Free Music. It use [[XSPF]] playlists[http://free.wave.online.fr/xmediaplayer/playlists/empty_playlist.xml]. This radio is in french but music is internationnal ;)<br />
<br />
== 2005-08-20 ==<br />
<br />
[[Theora|libtheora]] 1.0 alpha 5 released. [http://www.theora.org/]<br />
<br />
== 2005-06-27 ==<br />
<br />
[[Vorbis]] 1.1.1 released. Some bug and documentation fixes, but no new <br />
encoder modes. [http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html]<br />
<br />
== 2005-06-11 ==<br />
<br />
[[Speex]] 1.1.10 released.<br />
<br />
== 2005-02-05 ==<br />
<br />
[[FLAC]] 1.1.2 released.<br />
<br />
== 2004-12-21 ==<br />
<br />
[[Icecast]] 2.2.0 released.</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Theora&diff=3023Theora2005-12-06T04:15:28Z<p>Pmsyyz: </p>
<hr />
<div>'''Theora''' is our video codec, based on the [[VP3]] codec donated by [[On2 Technologies]]. We've refined and extended it, giving it the same future scope for encoder improvement [[Vorbis]] has. See http://theora.org/ for more information.<br />
<br />
== Features ==<br />
<br />
Features available in the Theora format (and a comparison to VP3 and MPEG-4 ASP):<br />
<br />
* block-based motion compensation<br />
* 8x8 Type-II Discrete Cosine Transform<br />
* free-form variable bit rates (VBR)<br />
* adaptive in-loop deblocking applied to the edges of the coded blocks (not existing in MPEG-4 ASP)<br />
* block sizes down to 8x8 (MPEG-4 ASP supports normally only 16x16)<br />
* 384 8x8 custom quantization matrices: intra/inter, luma/chroma and even each quant (more than VP3 and MPEG-4 ASP/AVC)<br />
* adaptive entropy encoding (MPEG-4 ASP does'nt support adaptivity)<br />
* 4:2:0, 4:2:2, and 4:4:4 chroma subsampling formats (VP3 and MPEG-4 ASP only support 4:2:0)<br />
* 8 bits per pixel per color channel<br />
* multiple reference frames (not possible in MPEG-4 ASP)<br />
* pixel aspect ratio (eg for anamorphic signalling/playback)<br />
* non-linear scaling of quants values (as done in MPEG-4 AVC)<br />
* adaptive quantisation down to the block level (as possible in MPEG-4 ASP/AVC)<br />
* intra frames (I-Frames in MPEG), inter frames (P-Frames), but no B-Frames (as supported in MPEG-4 ASP/AVC)<br />
* HalfPixel Motion Search Precision (MPEG-4 ASP/AVC supports HalfPixel or QuarterPixel)<br />
* technologies used already in Vorbis (decoder setup configuration, bitstream headers...) not available in VP3<br />
<br />
Note that not all of these features are already implemented in the reference encoder/decoder.<br />
<br />
== Status ==<br />
<br />
Alpha 5 is the latest release. The bitstream format is frozen. Every file created with the alpha 3 encoder (and, of course, later encoders) will be playable with future decoders. Beta 1 will be the next release.<br />
<br />
* It would be nice if somewhere it could be explained if Theora is a format appropriate for editing video - such formats would not do frame to frame compression and the file size and processor load would be smaller. On the other hand a distribution format would want to pack in a lot of compression which would mean using frame to for compression.<br />
<br />
== Development ==<br />
<br />
* [[Theora:Beta1ToDo|Todo for Beta1]]<br />
<br />
== More information ==<br />
<br />
* [[TheoraHardware]]: List of hardware-players supporting Ogg Theora<br />
* [[TheoraSoftwarePlayers]]: List of media players that can play Ogg Theora<br />
* [[TheoraDecoders]]: List of decoders<br />
* [[TheoraEncoders]]: List of encoders<br />
<br />
== External links ==<br />
<br />
* [http://www.theora.org/ Theora homepage]<br />
* [http://www.annodex.net/software/theora/ Theora documentation daily builds]<br />
* [[Wikipedia: Theora]]<br />
* [http://www.vp3.com VP3 homepage]: The homepage of the codec Theora is based on<br />
* [http://www.on2.com On2 Technologies]: The creators of VP3<br />
* [http://forum.doom9.org/showthread.php?s=&threadid=77314 Ogg Theora Information on Doom9 Forum]<br />
* [http://www.parrishtech.com/content/view/16/1/ HOWTO: Rip DVD to Theora using Linux]</div>Pmsyyzhttps://wiki.xiph.org/index.php?title=Speex&diff=3033Speex2005-12-05T21:49:56Z<p>Pmsyyz: </p>
<hr />
<div>The '''Speex''' project maintains a patent-clear audio codec designed for compressing speech data.<br />
<br />
== External links ==<br />
<br />
* [http://www.speex.org/ Speex homepage]<br />
* [[Wikipedia: Speex]]</div>Pmsyyz