XiphWiki - User contributions [en]

Vorbis Hardware

2011-02-07T23:23:59Z

Conrad: Remove dead link to "more (outdated)" information

This is a list of hardware of all categories, from chipsets to ready-to-use products, that support Ogg [[Vorbis]].

Hardware support status for Ogg Vorbis is relatively good, you can choose between a huge number 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.

If you know of any hardware or projects that are not yet mentioned here, please add them to the list.

== Consumer products ==

All Android devices support Ogg Vorbis.

The following music players support Ogg Vorbis either out of the box or after a firmware upgrade:

* [[PortablePlayers]]: mobile players
:[[PortablePlayers/Flash|Flash Memory Storage]]
:[[PortablePlayers/Harddisk|Harddisk Storage]]
:[[PortablePlayers/Others#CD.2FDVD_Audio_Players|CD/DVD Audio Players]]
:[[PortablePlayers/Others#Mobile_Phones|Mobile Phones]]
:[[PortablePlayers/Others#Others|Others]]
* [[StaticPlayers]]: installed players
:[[StaticPlayers#Hi-Fi_components|Hi-Fi components]]
:[[StaticPlayers#Car_Audio|Car Audio]]
:[[StaticPlayers#Media_Storage|Media Storage]]

For hardware that is able to run third-party software (such as PDAs and video game consoles), please visit [[VorbisSoftwarePlayers]].

== Non-consumer products ==

This is Vorbis in Silicon, meaning chips from which actual consumer products can be built.

;[http://www.vlsi.fi/ VLSI Solution Oy]: VLSI provides two Ogg Vorbis capable chips.

:[http://www.vlsi.fi/en/products/vs1000.shtml VS1000] is an Ogg Vorbis decoder and controller chip based on a 16-bit DSP.

:[http://www.vlsi.fi/en/products/vs1053.shtml VS1053] is a low-power "MP3 decoder" chip based on the same DSP. What makes the IC unique is that it can both decode and [http://www.vlsi.fi/en/support/software/vs10xxapplications.html encode] Ogg Vorbis files. There are several different quality settings to choose from varying from narrowband speech to high-quality stereo music.

;[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.

;[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’s [http://www.finearch.com/english/news/pr_20030715/pr_20030715.htm press release].

;[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.

;[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.

;[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 The Digital Times] (Korean).

;[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:
<blockquote>"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." </blockquote>
:from a 2000 [http://www.forbes.com/2000/09/18/dvorak_index.html column in Forbes]

:Some STMP3500-based devices supports Ogg Vorbis, but there are no notes about this on SigmaTel-website.

:SigmaTel introduces the STMP3600 with support for Ogg Vorbis, MP3, AAC, WMA and more.[http://www.finanznachrichten.de/nachrichten-2005-10/artikel-5493211.asp]

== See also ==
* [[Theora Hardware]]

[[Category:Vorbis]]

Vorbis Hardware

2011-02-07T23:17:12Z

Conrad: /* Consumer products */ Add line about android

This is a list of hardware of all categories, from chipsets to ready-to-use products, that support Ogg [[Vorbis]].

Hardware support status for Ogg Vorbis is relatively good, you can choose between a huge number 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.

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].

== Consumer products ==

All Android devices support Ogg Vorbis.

The following music players support Ogg Vorbis either out of the box or after a firmware upgrade:

* [[PortablePlayers]]: mobile players
:[[PortablePlayers/Flash|Flash Memory Storage]]
:[[PortablePlayers/Harddisk|Harddisk Storage]]
:[[PortablePlayers/Others#CD.2FDVD_Audio_Players|CD/DVD Audio Players]]
:[[PortablePlayers/Others#Mobile_Phones|Mobile Phones]]
:[[PortablePlayers/Others#Others|Others]]
* [[StaticPlayers]]: installed players
:[[StaticPlayers#Hi-Fi_components|Hi-Fi components]]
:[[StaticPlayers#Car_Audio|Car Audio]]
:[[StaticPlayers#Media_Storage|Media Storage]]

For hardware that is able to run third-party software (such as PDAs and video game consoles), please visit [[VorbisSoftwarePlayers]].

== Non-consumer products ==

This is Vorbis in Silicon, meaning chips from which actual consumer products can be built.

;[http://www.vlsi.fi/ VLSI Solution Oy]: VLSI provides two Ogg Vorbis capable chips.

:[http://www.vlsi.fi/en/products/vs1000.shtml VS1000] is an Ogg Vorbis decoder and controller chip based on a 16-bit DSP.

:[http://www.vlsi.fi/en/products/vs1053.shtml VS1053] is a low-power "MP3 decoder" chip based on the same DSP. What makes the IC unique is that it can both decode and [http://www.vlsi.fi/en/support/software/vs10xxapplications.html encode] Ogg Vorbis files. There are several different quality settings to choose from varying from narrowband speech to high-quality stereo music.

;[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.

;[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’s [http://www.finearch.com/english/news/pr_20030715/pr_20030715.htm press release].

;[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.

;[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.

;[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 The Digital Times] (Korean).

;[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:
<blockquote>"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." </blockquote>
:from a 2000 [http://www.forbes.com/2000/09/18/dvorak_index.html column in Forbes]

:Some STMP3500-based devices supports Ogg Vorbis, but there are no notes about this on SigmaTel-website.

:SigmaTel introduces the STMP3600 with support for Ogg Vorbis, MP3, AAC, WMA and more.[http://www.finanznachrichten.de/nachrichten-2005-10/artikel-5493211.asp]

== See also ==
* [[Theora Hardware]]

[[Category:Vorbis]]

PortablePlayers/Others

2011-02-07T23:11:20Z

Conrad: /* Android-based phones */ Remove "presumably"

== CD/DVD Audio Players ==

=== [http://www.ifreemax.com/ Freemax's] FW-960 ===
:This CD-R portable supports Ogg Vorbis playback out of the box. It has 48 hours of WMA playback if an external battery pack (2 AA batteries) is used. The FreeMax FW-960 is also known as the mpman MP-CD550.

=== [http://www.exonion.com/ Havin's] (link dead) Exonion HVC-400E, [http://www.princeton.co.jp/ Princeton's] Pocket Beat airCD ===
:The Havin HVC-400E, also known as the Princeton airCD is probably on sale in Japan since late November, 2003.

=== [http://www.iriver.com iRiver] iMP-250, iMP-350, iMP-400, iMP-550, iMP-700(T) ===
:Ogg Vorbis is supported only through latest beta firmwares, still some bitrate restriction which may vary depending on the model (min=96kbps, max=160kbps). The iMP-550 supports maximum bitrate up to 256kps (still 96kbps as minimum). Also note the latest iMP-450 does not support OGG for the moment, a future upgrade may correct this... The iMP-700T with firmware 1.40 supports bitrates between 96 and 210 kbps, and .ogg files are generally not as loud as .mp3 files.

=== [http://www.roadstar.com/ Roadstar] PCD-5960WOMPT ===

=== [http://www.samsungusa.com/ Samsung's] MCD-CM600 ===
:The MCD-CM600 is now available in Korea. It is a CD portable that can play Vorbis, MP3, and WMA.

== Mobile Phones ==

=== Android-based phones ===

All Android devices including phones support Vorbis out-of-the-box. Here are some examples with references:
* Nexus One aka the "Google Phone" (User Guide page 329)
* T-Mobile G1 [http://support.t-mobile.com/knowbase/root/public/tm30234.pdf (User Guide page 105)]
* HTC Dream [http://member.america.htc.com/download/Web_materials/Manual/Rogers_Dream/090512_Dream_HTC_US_Rogers_HEP_English_UM.pdf (User Guide page 153)]
* HTC Magic [http://member.america.htc.com/download/Web_materials/Manual/HTC_Magic_Rogers/100128_Magic_MR_Rogers_English_UM.pdf (User Guide page 198)]
* Motorola Droid [http://www.motorola.com/staticfiles/Support/US-EN/Mobile%20Phones/DROID-by-Motorola/US-EN/Documents/Static-Files/DROID_UG_Verizon_00202474c.pdf (User Guide page 34)]
* Motorola Milestone [http://www.motorola.com/staticfiles/Support/CA-EN/Mobile_Phones/Milestone/CA-EN/_Documents/Static_Files/Milestone_Telus_CA_EN_UG_68000202482A.pdf (User Guide page 35)]

=== iPhone ===
:Third-party efforts are porting the [http://coreplayer.com/content/view/28/69/ CorePlayer] and the [http://www.zodttd.com/ VLC player]

=== [http://www.openmoko.com/ Openmoko] ===
:Openmoko produces phones with hardware and software as open as possible. They run GNU/Linux and software players such as mplayer and ogg123 can be used for vorbis playback. Because it runs GPL'ed software, ogg theora is also supported (but needs to be encoded with low frame rate as described at [http://wiki.openmoko.org/wiki/Video_Player Openmoko wiki]).

=== [http://www.samsung.com Samsung] introduced phones on the 2006 3GSM that play .ogg files: SGH-i320 and [http://www.engadgetmobile.com/2006/02/13/samsung-shows-off-sph-s4300-musicphone/ SPH-S4300] ===
:Also, Samsung i900 Omnia is known to play Vorbis, in Windows Media Player only. [http://es.samsungmobile.com/mobile/Samsungi200/spec Samsung SGH-i200], also plays Vorbis.

=== SymbianOS based mobile phones from '''Nokia''', '''Sony Ericsson''', '''Siemens''', '''Motorola''', '''Samsung''' etc.===
:Plays Vorbis files with the third-party, open source [http://symbianoggplay.sourceforge.net/ Symbian OggPlay Software]. For supported mobile phones please visit the project website. The software works very well — even the still-in-development version which is strongly recommended. There is also a [http://developer.symbian.com/main/documentation/example_app_code/cpp/ogg_vorbis.jsp plugin] to Symbian itself. See also [[VorbisSoftwarePlayers#Symbian]].

===Windows Mobile based phones===
:see [[VorbisSoftwarePlayers#PocketPC]]

== Automobiles ==

See [[StaticPlayers]] page.

== Others ==

=== [http://www.ipodlinux.org/ iPodLinux] ===
:You can install special Linux distribution on almost all of Apple iPods. In combination with Podzilla jukebox software it plays OGG (and many more audio file formats).

=== PDAs / Cell Phones / Game Consoles ===
:Other devices that run software to play Ogg Vorbis can be used as portable players as well. Please go to [[VorbisSoftwarePlayers]] page for more information.

=== [http://www.rockbox.org/ Rockbox] alternative firmware for iPods and other DAPs ===
:The Rockbox project works hard to provide an alternative firmware for some portable players. Rockbox has a rich feature set that is hard to find elsewhere, including gapless playback, Ogg Vorbis, FLAC and even [http://www.musepack.net/ Musepack] support. Currently many models by [http://www.iriver.com/ iRiver], [http://www.archos.com/ Archos], [http://www.apple.com/de/ipod/ Ipod], Cowon(iAudio X5, X5V, X5L, M5 and M5l), SanDisk(Sansa c200, e200 and e200R series) and Toshiba(Gigabeat X and F series) are supported.

====[http://www.rockbox.org/twiki/bin/view/Main/RockboxPlayer Rockbox Player] - Free/Open hardware audio player (DAP) and recorder====
:There is ongoing efforts to design and build a Free/Open hardware audio player (DAP) and recorder, for use with RockBox firmware. Developer interested in participating are encouraged to visit the [http://www.rockbox.org/twiki/bin/view/Main/RockboxPlayer project page].

=== NAViBLUE NBC3500 GPS Navigation Device ===
:According to [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=3123083&CatId=2374]

=== TomTom Navigation software (mentioned on e.g. [http://www.pocketgpsworld.com/tomtom-navigator-pda-5.php]) and hardware systems ===
------------

PortablePlayers/Others

2011-02-07T23:10:52Z

Conrad: /* Mobile Phones */ Sort alphabetically

== CD/DVD Audio Players ==

=== [http://www.ifreemax.com/ Freemax's] FW-960 ===
:This CD-R portable supports Ogg Vorbis playback out of the box. It has 48 hours of WMA playback if an external battery pack (2 AA batteries) is used. The FreeMax FW-960 is also known as the mpman MP-CD550.

=== [http://www.exonion.com/ Havin's] (link dead) Exonion HVC-400E, [http://www.princeton.co.jp/ Princeton's] Pocket Beat airCD ===
:The Havin HVC-400E, also known as the Princeton airCD is probably on sale in Japan since late November, 2003.

=== [http://www.iriver.com iRiver] iMP-250, iMP-350, iMP-400, iMP-550, iMP-700(T) ===
:Ogg Vorbis is supported only through latest beta firmwares, still some bitrate restriction which may vary depending on the model (min=96kbps, max=160kbps). The iMP-550 supports maximum bitrate up to 256kps (still 96kbps as minimum). Also note the latest iMP-450 does not support OGG for the moment, a future upgrade may correct this... The iMP-700T with firmware 1.40 supports bitrates between 96 and 210 kbps, and .ogg files are generally not as loud as .mp3 files.

=== [http://www.roadstar.com/ Roadstar] PCD-5960WOMPT ===

=== [http://www.samsungusa.com/ Samsung's] MCD-CM600 ===
:The MCD-CM600 is now available in Korea. It is a CD portable that can play Vorbis, MP3, and WMA.

== Mobile Phones ==

=== Android-based phones ===
Presumably all Android devices including phones support Vorbis out-of-the-box. Here are some examples with references:
* Nexus One aka the "Google Phone" (User Guide page 329)
* T-Mobile G1 [http://support.t-mobile.com/knowbase/root/public/tm30234.pdf (User Guide page 105)]
* HTC Dream [http://member.america.htc.com/download/Web_materials/Manual/Rogers_Dream/090512_Dream_HTC_US_Rogers_HEP_English_UM.pdf (User Guide page 153)]
* HTC Magic [http://member.america.htc.com/download/Web_materials/Manual/HTC_Magic_Rogers/100128_Magic_MR_Rogers_English_UM.pdf (User Guide page 198)]
* Motorola Droid [http://www.motorola.com/staticfiles/Support/US-EN/Mobile%20Phones/DROID-by-Motorola/US-EN/Documents/Static-Files/DROID_UG_Verizon_00202474c.pdf (User Guide page 34)]
* Motorola Milestone [http://www.motorola.com/staticfiles/Support/CA-EN/Mobile_Phones/Milestone/CA-EN/_Documents/Static_Files/Milestone_Telus_CA_EN_UG_68000202482A.pdf (User Guide page 35)]

=== iPhone ===
:Third-party efforts are porting the [http://coreplayer.com/content/view/28/69/ CorePlayer] and the [http://www.zodttd.com/ VLC player]

=== [http://www.openmoko.com/ Openmoko] ===
:Openmoko produces phones with hardware and software as open as possible. They run GNU/Linux and software players such as mplayer and ogg123 can be used for vorbis playback. Because it runs GPL'ed software, ogg theora is also supported (but needs to be encoded with low frame rate as described at [http://wiki.openmoko.org/wiki/Video_Player Openmoko wiki]).

=== [http://www.samsung.com Samsung] introduced phones on the 2006 3GSM that play .ogg files: SGH-i320 and [http://www.engadgetmobile.com/2006/02/13/samsung-shows-off-sph-s4300-musicphone/ SPH-S4300] ===
:Also, Samsung i900 Omnia is known to play Vorbis, in Windows Media Player only. [http://es.samsungmobile.com/mobile/Samsungi200/spec Samsung SGH-i200], also plays Vorbis.

=== SymbianOS based mobile phones from '''Nokia''', '''Sony Ericsson''', '''Siemens''', '''Motorola''', '''Samsung''' etc.===
:Plays Vorbis files with the third-party, open source [http://symbianoggplay.sourceforge.net/ Symbian OggPlay Software]. For supported mobile phones please visit the project website. The software works very well — even the still-in-development version which is strongly recommended. There is also a [http://developer.symbian.com/main/documentation/example_app_code/cpp/ogg_vorbis.jsp plugin] to Symbian itself. See also [[VorbisSoftwarePlayers#Symbian]].

===Windows Mobile based phones===
:see [[VorbisSoftwarePlayers#PocketPC]]

== Automobiles ==

See [[StaticPlayers]] page.

== Others ==

=== [http://www.ipodlinux.org/ iPodLinux] ===
:You can install special Linux distribution on almost all of Apple iPods. In combination with Podzilla jukebox software it plays OGG (and many more audio file formats).

=== PDAs / Cell Phones / Game Consoles ===
:Other devices that run software to play Ogg Vorbis can be used as portable players as well. Please go to [[VorbisSoftwarePlayers]] page for more information.

=== [http://www.rockbox.org/ Rockbox] alternative firmware for iPods and other DAPs ===
:The Rockbox project works hard to provide an alternative firmware for some portable players. Rockbox has a rich feature set that is hard to find elsewhere, including gapless playback, Ogg Vorbis, FLAC and even [http://www.musepack.net/ Musepack] support. Currently many models by [http://www.iriver.com/ iRiver], [http://www.archos.com/ Archos], [http://www.apple.com/de/ipod/ Ipod], Cowon(iAudio X5, X5V, X5L, M5 and M5l), SanDisk(Sansa c200, e200 and e200R series) and Toshiba(Gigabeat X and F series) are supported.

====[http://www.rockbox.org/twiki/bin/view/Main/RockboxPlayer Rockbox Player] - Free/Open hardware audio player (DAP) and recorder====
:There is ongoing efforts to design and build a Free/Open hardware audio player (DAP) and recorder, for use with RockBox firmware. Developer interested in participating are encouraged to visit the [http://www.rockbox.org/twiki/bin/view/Main/RockboxPlayer project page].

=== NAViBLUE NBC3500 GPS Navigation Device ===
:According to [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=3123083&CatId=2374]

=== TomTom Navigation software (mentioned on e.g. [http://www.pocketgpsworld.com/tomtom-navigator-pda-5.php]) and hardware systems ===
------------

OggVP8

2010-05-22T03:55:01Z

Conrad: indent bitfield diagram

Default field type: BIG ENDIAN unsigned integer

VMAJ=1, VMIN=0

0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| HDRID (0x4F) | Identifier char[4]: 0x56503830 = 'VP80' | 0-3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | HDRTYP (0x01) | VMAJ | VMIN | 4-7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FW (Stored frame width) | FH (Stored frame height) | 8-11
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PARN (Pixel aspect ratio numerator | PARD (Pixel | 12-15
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| aspect ratio denominator) | FPSN (Frame rate numerator) | 16-19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | FPSD (Frame rate denominator) | 20-23
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | 24-27
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

OggVP8

2010-05-22T03:52:07Z

Conrad: add BOS page bitfield diagram

How to do a release

2010-02-04T01:33:53Z

Conrad: /* Add new release files */ add svn propset info

You made a new release, the world is waiting for it.
Here is what to do:

== Update versions and CHANGES files ==

Verify all project release versions embedded throughout the source and build system have been updated to appropriate values for the release. For projects that use the autotools, this means checking configure.in/configure.ac for AC_INIT, *LIB_CURRENT, *LIB_REVISION and *LIB_AGE. Depending on the project, there might be a version.h file, vendor or lib version strings embedded in the source somewhere (eg, lib/info.c for libvorbis or lib/internal.h for libtheora) and various other build project files for non-UNIX platforms (eg, macosx/Info.plist).

Changes, additions, improvements, and major bugfixes should be summarized in the CHANGES file. A good way to avoid missing anything is to look through the SVN log since last release and cherrypick the bits that would be of interest to outside developers or project managers.

== Tag in version control ==

All official project releases must be tagged in their version control system.

=== Subversion ===

Tagging is done using the SVN copy tag; essentially a versioned copy of a specific module/brach is copied to the tags directory in SVN. For example, the libvorbis 1.2.2 release was tagged using:

svn copy http://svn.xiph.org/trunk/vorbis@16168 http://svn.xiph.org/tags/vorbis/libvorbis-1.2.2

=== Git ===

To create a tag called "1.0.0" for the commit at the HEAD of master:

git tag -a 1.0.0 master

You will be prompted to write a message describing the tag.

When you push your changes to git.xiph.org you must specify to also push tags; eg. for a remote named "xiph":

git push --tags xiph

== Prepare a tarball ==
./autogen.sh
make dist

If a distcheck target is available, then it should be used instead, as it can spot
common mistakes:
./autogen.sh
make distcheck

Ideally, offer binaries for the different systems. This is not required, and many packages (such as libvorbis, etc) ship only as source releases. If in doubt, do what previous releases did. If there are no previous releases, libs usually ship as source only, applications tend to offer binaries.

== Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==

If you are uploading the first release of a project to Xiph.org, then first create a release directory in the svn repository. You can do this using remote svn commands (rather than checking out the entire Xiph.org release archive):

<tt>svn mkdir https://svn.xiph.org/releases/PROJECTNAME</tt>

Then check that directory out locally:

<tt>svn co https://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>

== Add new release files ==

Add tarballs etc. to your local checkout of the release directory:

<tt>cd PROJECTNAME-releases</tt>
<tt>svn add PROJECTNAME-x.x.x.tar.gz</tt>

Depending on your svn client, you may need to explicitly set the mime-type:

<tt>svn propset svn:mime-type application/octet-stream *.tar.gz</tt>

Then, generate MD5 and SHA1 checksums for these files. Extending the checksum files is easy on a Unix machine:

<tt>md5sum PROJECTNAME-x.x.x.tar.gz >> MD5SUMS</tt>
<tt>sha1sum PROJECTNAME-x.x.x.tar.gz >> SHA1SUMS</tt>

Check that the only modifications to the checksums are for the new files:

<tt>svn diff</tt>

If everything is ok (and the checksums for other files have not changed), commit:

<tt>svn commit</tt>

== Website update ==
=== Add downloadable files ===
After about 30(?) minutes repository changes will be visible on
http://downloads.xiph.org/releases/YOUR-COMPONENT/

==== immediate mirror update ====
The mirrorpush is performed by an every-half-hour cron task. If, for some reason, it's important to update the mirrors immediately, the following may be run as root on Motherfish to force-push:

cd /home/mirrorpush; ./update_downloads.sh

The script must be run from the /home/mirrorpush directory.

=== Update HTML ===

==== Update [http://www.xiph.org/downloads/ http://www.xiph.org/downloads/] ====

Then you should update the [http://www.xiph.org/downloads/ download section] on the Xiph website.
The downloads page is in the normal svn repository for www.xiph.org:

<tt>svn co https://svn.xiph.org/websites/xiph.org/downloads/</tt>

Update it with your release tarball name and checksum, and commit.

==== News page ====
New releases of official projects should include an announcement. The same announcement that is sent to the email announcement lists is used as the basis for a 'press release' on the Xiph [http://www.xiph.org/press/index.shtml.en news/press page]. New news entries must be added seperately to the [http://www.xiph.org/press/index.shtml.en press page] and the [http://www.xiph.org/index.shtml.en Xiph front page]. Theora-related releases should also be added to the [http://www.theora.org/news/index.shtml.en Theora News page].

The various xiph.org web sites must be edited through SVN just like the release download files. The websites can be found under [https://svn.xiph.org/websites/ svn.xiph.org/websites/].

==== immediate HTML update ====

Website changes are updated by a cron script like the download mirrors. To force an immediate website update, perform the following as root on Motherfish:

cd /var/www; ./update_websites.sh

== Announcement ==
Announce your release where apropriate. This can include
* The various Xiph.Org website news pages; see above.
* The Xiph [http://lists.xiph.org/mailman/listinfo/announce Announce] mailing list
* your blog
* the project's FreshMeat page
* Linux Weekly News <lwn@lwn.net>
* comp.os.linux.announce <cola@stump.algebra.com>
* ''<other suitable places>''

It might also be a good idea to notify people maintaining ports of your project.

== See Also ==
* [[CodingGuidelines]]
* [[MIT approach to design and implementation]]

[[Category:Developers stuff]]

How to do a release

2010-02-04T01:31:32Z

Conrad: /* Tag in version control */ add info about tagging with git

You made a new release, the world is waiting for it.
Here is what to do:

== Update versions and CHANGES files ==

Verify all project release versions embedded throughout the source and build system have been updated to appropriate values for the release. For projects that use the autotools, this means checking configure.in/configure.ac for AC_INIT, *LIB_CURRENT, *LIB_REVISION and *LIB_AGE. Depending on the project, there might be a version.h file, vendor or lib version strings embedded in the source somewhere (eg, lib/info.c for libvorbis or lib/internal.h for libtheora) and various other build project files for non-UNIX platforms (eg, macosx/Info.plist).

Changes, additions, improvements, and major bugfixes should be summarized in the CHANGES file. A good way to avoid missing anything is to look through the SVN log since last release and cherrypick the bits that would be of interest to outside developers or project managers.

== Tag in version control ==

All official project releases must be tagged in their version control system.

=== Subversion ===

Tagging is done using the SVN copy tag; essentially a versioned copy of a specific module/brach is copied to the tags directory in SVN. For example, the libvorbis 1.2.2 release was tagged using:

svn copy http://svn.xiph.org/trunk/vorbis@16168 http://svn.xiph.org/tags/vorbis/libvorbis-1.2.2

=== Git ===

To create a tag called "1.0.0" for the commit at the HEAD of master:

git tag -a 1.0.0 master

You will be prompted to write a message describing the tag.

When you push your changes to git.xiph.org you must specify to also push tags; eg. for a remote named "xiph":

git push --tags xiph

== Prepare a tarball ==
./autogen.sh
make dist

If a distcheck target is available, then it should be used instead, as it can spot
common mistakes:
./autogen.sh
make distcheck

Ideally, offer binaries for the different systems. This is not required, and many packages (such as libvorbis, etc) ship only as source releases. If in doubt, do what previous releases did. If there are no previous releases, libs usually ship as source only, applications tend to offer binaries.

== Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==

If you are uploading the first release of a project to Xiph.org, then first create a release directory in the svn repository. You can do this using remote svn commands (rather than checking out the entire Xiph.org release archive):

<tt>svn mkdir https://svn.xiph.org/releases/PROJECTNAME</tt>

Then check that directory out locally:

<tt>svn co https://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>

== Add new release files ==

Add tarballs etc. to your local checkout of the release directory:

<tt>cd PROJECTNAME-releases</tt>
<tt>svn add PROJECTNAME-x.x.x.tar.gz</tt>

Then, generate MD5 and SHA1 checksums for these files. Extending the checksum files is easy on a Unix machine:

<tt>md5sum PROJECTNAME-x.x.x.tar.gz >> MD5SUMS</tt>
<tt>sha1sum PROJECTNAME-x.x.x.tar.gz >> SHA1SUMS</tt>

Check that the only modifications to the checksums are for the new files:

<tt>svn diff</tt>

If everything is ok (and the checksums for other files have not changed), commit:

<tt>svn commit</tt>

== Website update ==
=== Add downloadable files ===
After about 30(?) minutes repository changes will be visible on
http://downloads.xiph.org/releases/YOUR-COMPONENT/

==== immediate mirror update ====
The mirrorpush is performed by an every-half-hour cron task. If, for some reason, it's important to update the mirrors immediately, the following may be run as root on Motherfish to force-push:

cd /home/mirrorpush; ./update_downloads.sh

The script must be run from the /home/mirrorpush directory.

=== Update HTML ===

==== Update [http://www.xiph.org/downloads/ http://www.xiph.org/downloads/] ====

Then you should update the [http://www.xiph.org/downloads/ download section] on the Xiph website.
The downloads page is in the normal svn repository for www.xiph.org:

<tt>svn co https://svn.xiph.org/websites/xiph.org/downloads/</tt>

Update it with your release tarball name and checksum, and commit.

==== News page ====
New releases of official projects should include an announcement. The same announcement that is sent to the email announcement lists is used as the basis for a 'press release' on the Xiph [http://www.xiph.org/press/index.shtml.en news/press page]. New news entries must be added seperately to the [http://www.xiph.org/press/index.shtml.en press page] and the [http://www.xiph.org/index.shtml.en Xiph front page]. Theora-related releases should also be added to the [http://www.theora.org/news/index.shtml.en Theora News page].

The various xiph.org web sites must be edited through SVN just like the release download files. The websites can be found under [https://svn.xiph.org/websites/ svn.xiph.org/websites/].

==== immediate HTML update ====

Website changes are updated by a cron script like the download mirrors. To force an immediate website update, perform the following as root on Motherfish:

cd /var/www; ./update_websites.sh

== Announcement ==
Announce your release where apropriate. This can include
* The various Xiph.Org website news pages; see above.
* The Xiph [http://lists.xiph.org/mailman/listinfo/announce Announce] mailing list
* your blog
* the project's FreshMeat page
* Linux Weekly News <lwn@lwn.net>
* comp.os.linux.announce <cola@stump.algebra.com>
* ''<other suitable places>''

It might also be a good idea to notify people maintaining ports of your project.

== See Also ==
* [[CodingGuidelines]]
* [[MIT approach to design and implementation]]

[[Category:Developers stuff]]

OggIndex-Migration

2010-01-13T04:39:14Z

Conrad: add link to Ogg Index wiki page

This page is for collecting patches related to the [[Ogg Index]] introduction.

Please add links and information about your favorite applications to this page!

Applications which read (decode) Ogg files should be extended to additionally recognize the OggIndex.

=== Encoders ===

* ffmpeg2theora supports creating indexes

* what about other encoders? VLC, GStreamer

=== oggz-chop ===

* support error

==== GStreamer ====

* support missing, gives error

==== MPlayer ====

* support missing, no error

==== VLC ====

* support missing, no error

==== XiphQT ====

* support missing, not tested

==== FFMpeg ====

* support missing, not tested

Ogg Index

2009-09-24T05:52:25Z

Conrad: add {{draft}} template

{{draft}}

= Ogg Index Track Specification Version 1 =

'''DRAFT, last updated 24 September 2009'''

'''This specification is still a work in progress, and does not yet constitute an official Ogg track format.'''

== Overview ==

Seeking in an Ogg file is typically implemented as a bisection search
over the pages in the file. The Ogg physical bitstream is bisected and
the next Ogg page's end-time is extracted. The bisection continues until
it reaches an Ogg page with an end-time close enough to the seek target
time. However in media containing streams which have key frames and
interframes, such as Theora streams, your bisection search won't
necessarily stop at a keyframe, thus you can't simply resume playback
from that point. First you need to construct the keyframe's timestamp
from the last page's granulepos, and seek again to the start of the
keyframe and decode forward until you reach the frame at the seek
target.

This is further complicated by the fact that packets often span multiple
Ogg pages, and that Ogg pages from different streams can be interleaved
between spanning packets.

The bisection method above works fine for seeking in local files, but
for seeking in files served over the Internet via HTTP, each bisection
or non sequential read can trigger a new HTTP request, which can have
very high latency, making seeking very slow.

== Seeking with an index ==

The Ogg index bitstream attempts to alleviate this problem, by providing
an index of periodic keyframes in an Ogg file. The index is contained in
a separate track which is embedded in the Ogg file, so that players
which don't understand the index track can just ignore it. In streams
without the concept of a keyframe, such as Vorbis streams where each
sample is independent, the index can instead record the time position at
periodic intervals, which achieves the same result. When this document
refers to keyframes, it also refers to these independent periodic
samples from keyframe-less streams.

The Ogg index bitstream provides seek algorithms with an ordered table
of the Ogg page start-offsets and end-times of key points in the indexed
streams in an Ogg segment.

A key point k is defined as follows. Each key point has an 8 byte offset
o, an 8 byte time t, and a 4 byte checksum c. This specifies that in
order to render the media at presentation time t milliseconds, the last
page which lies before the start of all the packets containing all the
key frames required to render at time t begins at offset o. The checksum
c is the checksum of the page which begins at offset o, which enables
you to verify that you're seeking to the intended page.

To seek in an Ogg bitstream which contains an index, you find the last
key point in the index with time less than or equal to the target time.
You then seek to the key point's offset, check that the page found there
has checksum c, and then decode forward until you encounter the sample
which corresponds to your seek target time. You are guaranteed to pass
keyframes on all indexed streams with time less than or equal to your
seek target time while decoding up to the seek target.

Be aware that you cannot assume that any or all Ogg files will contain
an index, and so when implementing Ogg seeking, you must gracefully
fall-back to a bisection search or other seek algorithm when the index
is not present.

The index also only holds data for the segment in which it resides, i.e.
if two Ogg files are concatenated together ("chained"), the index track
in one Ogg segment does not contain information about the keyframes in
the other Ogg segment.

The index also stores meta data about the segment in which it resides.
It stores the start time and the end time, and also the length of the
segment in bytes. This is so that if the seek target is outside of the
indexed range, you can immediately move to the next/previous segment and
either seek using that segment's index, or narrow the bisection window
if that segment has no index.

== Format Specification ==

Unless otherwise specified, all integers and fields in the bitstream are
encoded with the least significant bit coming first in each byte.
Integers and fields comprising of more than one byte are encoded least
significant byte first (i.e. little endian byte order).

An Ogg index track starts with an identifier header packet which
contains the following data, in the following order:

* The identifier "index\0".
* The index version format number, as a 1 byte unsigned integer. This specification describes version 1, so this field should have the value 0x01.
* The playback start time, in milliseconds, as an 8 byte unsigned integer, this is the presentation time of the first frame.
* The playback end time, in milliseconds, as an 8 byte unsigned integer, this is the end time of the last frame.
* The length of the indexed segment, in bytes, as an 8 byte unsigned integer.
* The number of key points in the index, 'n', as a 4 byte unsigned integer.

The track then contains one secondary header packet, which contains the
actual index. This is the "index packet", and it must begin on a new
page, but it may span multiple pages. The index packet contains the
following:

* 'n' key points, each of which contain, in the following order:
** the page offset as an 8 byte unsigned integer, followed by
** the checksum of the page found at the offset, as a 4 byte field,followed by
** the presentation times in milliseconds of the key point, as an 8 byte unsigned integer.

The size of the data in the index packet is (n * (8 + 4 + 8)) bytes. The
key points are stored in increasing order by offset.

The track then contains one empty EOS packet, which must start on a new
page. The track therefore contains exactly three packets, on three or
more pages.

The offsets stored in the keypoints is relative to the start of the Ogg
bitstream segment. So if you have a physical Ogg bitstream made up of
two chained Oggs, the offsets in the second Ogg segment's bitstream's
index are relative to the beginning of the second Ogg in the chain, not
the first. Also note that if a physical Ogg bitstream is made up of
chained Oggs, the presence of an index in one segment does not imply
that there will be an index in any other segment.

The exact number of keyframes used to construct key points in the index
is up to the indexer, but to limit the index size, we recommend
including at most one key point per every 64KB of data, or every 500ms.

There can be only one index track per Ogg bitstream segment. The index
packet must occur before all non-metadata streams' content packets. In
practice this means that the index packet will occur along with other
secondary header pages, before the skeleton EOS page.

All pages in the index bitstream have their granulepos set as 0.

== Software Prototype ==

For a prototype indexer, see:

http://github.com/cpearce/OggIndex

To see how indexes improves network seeking performance, you can download a development
version of Firefox which can take advantage of indexes here:

http://pearce.org.nz/video/firefox-indexed-ogg-seek.linux.tar.bz2

http://pearce.org.nz/video/firefox-indexed-ogg-seek.macosx.dmg

http://pearce.org.nz/video/firefox-indexed-ogg-seek.win32.zip

Then point that browser here:

http://pearce.org.nz/video/indexed-seek-demo.html

OggDirac

2009-07-12T00:34:53Z

Conrad: dirac does not use vorbiscomment

Dirac is an advanced royalty-free video compression format designed for a wide range of uses, from delivering low-resolution web content to broadcasting HD and beyond, to near-lossless studio editing.

More information is available on the [http://diracvideo.org/ Dirac homepage].

See http://diracvideo.org/download/mapping-specs/dirac-mapping-ogg-1.0.pdf for the official Ogg Dirac mapping.

The Ogg Dirac mapping does NOT use VorbisComment metadata.

[[Category:Ogg Mappings]]

Category:Ogg Mappings

2009-07-12T00:33:52Z

Conrad: explain what an Ogg mapping is

[[Category:Ogg]]

The way that data for each codec is stored in an Ogg container is called its "mapping" into Ogg.

Data for a particular track of content is stored in a single Ogg logical bitstream. The mapping for each codec usually specifies:

* The structure of the beginning-of-stream (BOS) page
* Whether or not the codec uses [[VorbisComment]] metadata
* Any other headers

Additional information may be stored in a corresponding [[OggSkeleton]] fisbone entry.

OggDirac

2009-07-12T00:26:59Z

Conrad: add intro about Dirac, link to homepage

Theora

2009-07-12T00:24:06Z

Conrad: s/our/a : theora is not our only video codec

'''Theora''' is a 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.

== Features ==

Features available in the Theora format (and a comparison to VP3 and MPEG-4 ASP):

* 8x8 Type-II Discrete Cosine Transform
* block-based motion compensation
* free-form variable bit rates (VBR)
* adaptive in-loop deblocking applied to the edges of the coded blocks (not existing in MPEG-4 ASP)
* block sizes down to 8x8 (MPEG-4 ASP supports 8x8 only with 4MV)
* 384 8x8 custom quantization matrices: intra/inter, luma/chroma and even each quant (more than VP3 and MPEG-4 ASP/AVC)
* flexible entropy encoding (Theora supports 80 VLC tables selectable per-frame, MPEG-4 ASP has just one)
* 4:2:0, 4:2:2, and 4:4:4 chroma subsampling formats (VP3 and MPEG-4 ASP only support 4:2:0)
* 8 bits per pixel per color channel
* multiple reference frames (not possible in MPEG-4 ASP)
* pixel aspect ratio (eg for anamorphic signalling/playback)
* non-multiple of 16 picture sizes (as possible in ASP, but not in VP3)
* non-linear scaling of quants values (as done in MPEG-4 AVC)
* adaptive quantization down to the block level (as possible in MPEG-4 ASP/AVC, but not in VP3)
* intra frames (I-Frames in MPEG), inter frames (P-Frames), but no B-Frames (as supported in MPEG-4 ASP/AVC)
* HalfPixel Motion Search Precision (MPEG-4 ASP/AVC supports HalfPixel or QuarterPixel)
* technologies used already in Vorbis (decoder setup configuration, bitstream headers...) not available in VP3

Note that not all of these features are already implemented in the reference encoder. They will be probably implemented in 1.1.

== Status ==
* '''1.0''' is the latest stable release (2008-11-03).
* The bitstream format was frozen in 1.0 Alpha 3 on 2004-08-04: every file created with this encoder (and, of course, later encoders, including Theora 1.1 in future) will be playable by any compliant Theora 1.x decoder.
* The decoder in 1.0 Alpha 8 implements all planned features of the [http://theora.org/doc/Theora.pdf Theora Format Specification]: every file created by any compliant 1.x Theora encoder will be playable by the decoder in 1.0 Alpha 8 (and, of course, later decoders).

== Development ==

* [[OggTheora|Mapping in Ogg]]
* [[TheoraTodo|ToDo list for development]]

== More information ==
{{Template:Theora}}

It's possible to convert VP3 video to Theora. See [[vp3toTheora]].

== External links ==

* [http://www.theora.org/ Theora homepage]
* [http://www.annodex.net/software/theora/ Theora documentation daily builds]
* [[Wikipedia: Theora]]
* [http://www.vp3.com VP3 homepage]: The homepage of the codec Theora is based on
* [http://www.on2.com On2 Technologies]: The authors of VP3
* [http://forum.doom9.org/showthread.php?s=&threadid=77314 Ogg Theora Information on Doom9 Forum]
* [http://www.parrishtech.com/content/view/16/1/ HOWTO: Rip DVD to Theora using Linux]
* [http://www.doom9.org/index.html?/codecs-quali-105-1.htm Codec shoot-out 2005] Comparison of many video codecs, including Theora

[[Category:Theora]]

HTML5

2009-07-08T09:31:56Z

Conrad: add link to theora cookbook

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

See also the [http://en.flossmanuals.net/theoracookbook Theora Cookbook] for a guide to streaming and working with Ogg Theora.

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio." See [https://developer.mozilla.org/en/Using_audio_and_video_in_Firefox Using audio and video in Firefox] at the Mozilla Developer Center for more info.

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

Unstable builds are available from the
[http://dev.chromium.org/getting-involved/dev-channel dev-channel].
The first version supporting Ogg Theora was chrome 3.0.182.2.

=== Apple Safari ===

Install [[XiphQT]]

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.

=== Conferences ===

* [http://mirror.linux.org.au/linux.conf.au/ linux.conf.au]
* DebConf: on the individual conference pages, e.g. [http://wiki.debconf.org/wiki/DebConf8/Streams]
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed Mv_embed] is "a javascript library for easy embedding of ogg theora/vorbis media with the html5 tag. Once the script is included you can include an inline ogg theora clip with:

<video src="mymovie.ogg">

"Mv_embed will then rewrite the video tag to whatever playback method is available on the client be it native support, java cortado, mplayer or vlc".

* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html Demo and sample HTML].

See also [http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki].

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

== video4all ==

[http://code.google.com/p/video4all/ video4all at Google Code]

Uses browser specific technology (.htc, .xbl, or plain .js) to rewrite video tags to fall back to H.264 in Flash for legacy browsers, while providing H.264 natively to Safari and Theora for Mozilla. Roughly speaking a script version of Kroc Camen's pure HTML Video For Everybody solution. Doesn't (currently) use any Theora based fallbacks.

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

:*Comment: It's clear that this solution makes a few compromises in order to be JS-free. The code is both fragile and frightening for reasons that make sense with regard to the original author's goals but aren't relevant if e.g. promoting Theora adoption takes precedence over a distaste for Java and/or Javascript. --[[User:Bod|Bod]] 06:03, 6 July 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop] allows you to serve time ranges of Ogg media over HTTP by any web server that supports CGI. Examples of such time range requests are http://www.example.com/video.ogv?t=200/600 which serves the segment of video.ogv from 200s-600s. This allows users to instantly jump to any point in a video, and you can put links in your web application to play arbitrary scenes.

HTML5

2009-07-04T10:31:19Z

Conrad: /* Backend servers */ oggz-chop info

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio."

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

Unstable builds are available from the
[http://dev.chromium.org/getting-involved/dev-channel dev-channel].
The first version supporting Ogg Theora was chrome 3.0.182.2.

=== Apple Safari ===

Install [[XiphQT]]

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.

=== Conferences ===

* [http://mirror.linux.org.au/linux.conf.au/ linux.conf.au]
* DebConf: on the individual conference pages, e.g. [http://wiki.debconf.org/wiki/DebConf8/Streams]
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed Mv_embed] is "a javascript library for easy embedding of ogg theora/vorbis media with the html5 tag. Once the script is included you can include an inline ogg theora clip with:

<video src="mymovie.ogg">

"Mv_embed will then rewrite the video tag to whatever playback method is available on the client be it native support, java cortado, mplayer or vlc".

* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html Demo and sample HTML].

See also [http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki].

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop] allows you to serve time ranges of Ogg media over HTTP by any web server that supports CGI. Examples of such time range requests are http://www.example.com/video.ogv?t=200/600 which serves the segment of video.ogv from 200s-600s. This allows users to instantly jump to any point in a video, and you can put links in your web application to play arbitrary scenes.

HTML5

2009-07-04T10:28:38Z

Conrad: /* Google Chrome */ add info on chrome dev-channel, from kinetik on #theora

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio."

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

Unstable builds are available from the
[http://dev.chromium.org/getting-involved/dev-channel dev-channel].
The first version supporting Ogg Theora was chrome 3.0.182.2.

=== Apple Safari ===

Install [[XiphQT]]

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.

=== Conferences ===

* [http://mirror.linux.org.au/linux.conf.au/ linux.conf.au]
* DebConf: on the individual conference pages, e.g. [http://wiki.debconf.org/wiki/DebConf8/Streams]
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed Mv_embed] is "a javascript library for easy embedding of ogg theora/vorbis media with the html5 tag. Once the script is included you can include an inline ogg theora clip with:

<video src="mymovie.ogg">

"Mv_embed will then rewrite the video tag to whatever playback method is available on the client be it native support, java cortado, mplayer or vlc".

* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html Demo and sample HTML].

See also [http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki].

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:46:08Z

Conrad: /* Web Video sites */ split out conferences, add lca and debconf

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio."

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

=== Apple Safari ===

Install [[XiphQT]]

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.

=== Conferences ===

* [http://mirror.linux.org.au/linux.conf.au/ linux.conf.au]
* DebConf: on the individual conference pages, e.g. [http://wiki.debconf.org/wiki/DebConf8/Streams]
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed Mv_embed] is "a javascript library for easy embedding of ogg theora/vorbis media with the html5 tag. Once the script is included you can include an inline ogg theora clip with:

<video src="mymovie.ogg">

"Mv_embed will then rewrite the video tag to whatever playback method is available on the client be it native support, java cortado, mplayer or vlc".

* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html Demo and sample HTML].

See also [http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki].

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:31:26Z

Conrad: /* Apple Safari */ add a link to XiphQT wiki page

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio."

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

=== Apple Safari ===

Install [[XiphQT]]

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed Mv_embed] is "a javascript library for easy embedding of ogg theora/vorbis media with the html5 tag. Once the script is included you can include an inline ogg theora clip with:

<video src="mymovie.ogg">

"Mv_embed will then rewrite the video tag to whatever playback method is available on the client be it native support, java cortado, mplayer or vlc".

* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html Demo and sample HTML].

See also [http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki].

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:27:34Z

Conrad: /* mv_embed */ add info about mv_embed

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio."

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed Mv_embed] is "a javascript library for easy embedding of ogg theora/vorbis media with the html5 tag. Once the script is included you can include an inline ogg theora clip with:

<video src="mymovie.ogg">

"Mv_embed will then rewrite the video tag to whatever playback method is available on the client be it native support, java cortado, mplayer or vlc".

* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html Demo and sample HTML].

See also [http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki].

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:20:52Z

Conrad: /* Mozilla Firefox */ add blurb about Firefox 3.5 from release notes

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]
includes "support for the HTML5 <video> and <audio> elements including native support for Ogg Theora encoded video and Vorbis encoded audio."

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:19:15Z

Conrad: /* Browser Support */

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

Our list of [[TheoraSoftwarePlayers]] lists many general-purpose media players that support Ogg Theora.

These web browsers support HTML5 with Ogg video:

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:17:33Z

Conrad: /* Opera */ add info/links about Opera 9.52 builds

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]

=== Opera ===

In [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ A call for video on the web - Opera <video> release on Labs], Opera announce that they "have created an experimental build of our browser for Windows, Mac and Linux with ... support for the <video> element/Ogg Theora built in".

The article contains links to experimental builds of Opera 9.52, and provides some simple examples of HTML5 <video> markup.

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-04T06:13:32Z

Conrad: /* Web Video sites */ expand list of sites, with descriptions (merge from ginger's blog)

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]

=== Opera ===

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

For more examples of Ogg Theora video, see
[[List of Theora videos]].

The following web sites support HTML5 with Ogg Theora.

=== Community upload sites ===

These sites allow anyone to upload video, and provide transcoding
to Ogg:

* [http://www.dailymotion.com DailyMotion]. See also DailyMotion's [http://www.dailymotion.com/openvideodemo Open Video Demo] (restricted to Firefox 3.5)
* Chris Double's [http://tinyvid.tv Tinyvid] (transcoding via Firefogg)

=== Archival and Reference ===

Sites that curate video for general archival and reference purposes,
and allow anyone to upload relevant material:

* [http://www.archive.org/details/movies Archive.org’s videos]
* [http://commons.wikimedia.org/wiki/Category:Videos_by_format Wikipedia’s videos]

=== Projects ===

* [http://metavid.org metavid]: The Open Video archive of the US Congress
* [http://pad.ma pad.ma]: Public Access Digital Media Archive is an online archive of densely text-annotated video material, primarily footage and not finished films.
* The [http://www.foms-workshop.org/foms2009/pmwiki.php/Main/Proceedings FOMS workshop videos]: proceedings from a workshop on free and open multimedia software.

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

:*Comment: We really shouldn't be plugging a solution which eschews cortado as a fall back in favor of FLV. A pure HTML triple check video/java/youtube would be better, but no pure HTML solution perform a canplaytype so it will break for safari users without xiphqt. Is "possible to add raw HTML but no JS" a common enough situation that a JS free solution is really needed? --[[User:Gmaxwell|Gmaxwell]] 22:58, 30 June 2009 (PDT)

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-07-01T05:26:35Z

Conrad: /* Mozilla Firefox */ add link to firefox

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

[http://www.mozilla.com/en-US/firefox/firefox.html Firefox 3.5]

=== Opera ===

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 with ogg theora:

* [http://tinyvid.tv tinyvid.tv]
* [http://www.dailymotion.com DailyMotion]
* [http://metavid.org metavid.org]
* [http://pad.ma pad.ma]

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* The [http://www.mediawiki.org/wiki/Extension:OggHandler OggHandler extension] for MediaWiki provides video and audio support with automatic fallback and thumbnailing.
* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

ReleaseProcess

2009-06-30T08:28:27Z

Conrad: redirect to How to do a release

#REDIRECT [[How to do a release]]

How to do a release

2009-06-30T08:23:33Z

Conrad: merge in text from ReleaseProcess

You made a new release, the world is waiting for it.
Here is what to do:

== Update versions and CHANGES files ==

Verify all project release versions embedded throughout the source and build system have been updated to appropriate values for the release. For projects that use the autotools, this means checking configure.in/configure.ac for AC_INIT, *LIB_CURRENT, *LIB_REVISION and *LIB_AGE. Depending on the project, there might be a version.h file, vendor or lib version strings embedded in the source somewhere (eg, lib/info.c for libvorbis or lib/internal.h for libtheora) and various other build project files for non-UNIX platforms (eg, macosx/Info.plist).

Changes, additions, improvements, and major bugfixes should be summarized in the CHANGES file. A good way to avoid missing anything is to look through the SVN log since last release and cherrypick the bits that would be of interest to outside developers or project managers.

== Tag in SVN ==

All official project releases must be tagged in SVN. This is done using the SVN copy tag; essentially a versioned copy of a specific module/brach is copied to the tags directory in SNV. For example, the libvorbis 1.2.2 release was tagged using:

svn copy http://svn.xiph.org/trunk/vorbis@16168 http://svn.xiph.org/tags/vorbis/libvorbis-1.2.2

== Prepare a tarball ==
./autogen.sh
make dist

Ideally, offer binaries for the different systems. This is not required, and many packages (such as libvorbis, etc) ship only as source releases. If in doubt, do what previous releases did. If there are no previous releases, libs usually ship as source only, applications tend to offer binaries.

== Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==

If you are uploading the first release of a project to Xiph.org, then first create a release directory in the svn repository. You can do this using remote svn commands (rather than checking out the entire Xiph.org release archive):

<tt>svn mkdir https://svn.xiph.org/releases/PROJECTNAME</tt>

Then check that directory out locally:

<tt>svn co https://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>

== Add new release files ==

Add tarballs etc. to your local checkout of the release directory:

<tt>cd PROJECTNAME-releases</tt>
<tt>svn add PROJECTNAME-x.x.x.tar.gz</tt>

Then, generate MD5 and SHA1 checksums for these files. Extending the checksum files is easy on a Unix machine:

<tt>md5sum PROJECTNAME-x.x.x.tar.gz >> MD5SUMS</tt>
<tt>sha1sum PROJECTNAME-x.x.x.tar.gz >> SHA1SUMS</tt>

Check that the only modifications to the checksums are for the new files:

<tt>svn diff</tt>

If everything is ok (and the checksums for other files have not changed), commit:

<tt>svn commit</tt>

== Website update ==
=== Add downloadable files ===
After about 30(?) minutes repository changes will be visible on
http://downloads.xiph.org/releases/YOUR-COMPONENT/

==== immediate mirror update ====
The mirrorpush is performed by an every-half-hour cron task. If, for some reason, it's important to update the mirrors immediately, the following may be run as root on Motherfish to force-push:

cd /home/mirrorpush; ./update_downloads.sh

The script must be run from the /home/mirrorpush directory.

=== Update HTML ===

==== Update [http://www.xiph.org/downloads/ http://www.xiph.org/downloads/] ====

Then you should update the [http://www.xiph.org/downloads/ download section] on the Xiph website.
The downloads page is in the normal svn repository for www.xiph.org:

<tt>svn co https://svn.xiph.org/websites/xiph.org/downloads/</tt>

Update it with your release tarball name and checksum, and commit.

==== News page ====
New releases of official projects should include an announcement. The same announcement that is sent to the email announcement lists is used as the basis for a 'press release' on the Xiph [http://www.xiph.org/press/index.shtml.en news/press page]. New news entries must be added seperately to the [http://www.xiph.org/press/index.shtml.en press page] and the [http://www.xiph.org/index.shtml.en Xiph front page]. Theora-related releases should also be added to the [http://www.theora.org/news/index.shtml.en Theora News page].

The various xiph.org web sites must be edited through SVN just like the release download files. The websites can be found under [https://svn.xiph.org/websites/ svn.xiph.org/websites/].

==== immediate HTML update ====

Website changes are updated by a cron script like the download mirrors. To force an immediate website update, perform the following as root on Motherfish:

cd /var/www; ./update_websites.sh

== Announcement ==
Announce your release where apropriate. This can include
* The various Xiph.Org website news pages; see above.
* The Xiph [http://lists.xiph.org/mailman/listinfo/announce Announce] mailing list
* your blog
* the project's FreshMeat page
* Linux Weekly News <lwn@lwn.net>
* comp.os.linux.announce <cola@stump.algebra.com>
* ''<other suitable places>''

It might also be a good idea to notify people maintaining ports of your project.

== See Also ==
* [[CodingGuidelines]]
* [[MIT approach to design and implementation]]

[[Category:Developers stuff]]

VorbisComment

2009-06-30T07:02:31Z

Conrad: /* Implementations */ explain what vorbis-comment is

VorbisComment is a base-level [[Metadata]] format initially created for use with Ogg [[Vorbis]]. It has since been adopted in the specifications of
[[Ogg]] encapsulations for other Xiph.Org codecs including [[Theora]], [[Speex]] and [[FLAC]].

The use case for VorbisComment is given as:
<blockquote>
... much like someone jotting a quick note on the bottom of a CDR. It should be a little information to remember the disc by and explain it to others; a short, to-the-point text note that need not only be a couple words, but isn't going to be more than a short paragraph.[http://xiph.org/vorbis/doc/v-comment.html]
</blockquote>

VorbisComments are typically used to provide basic information like the title and copyright holder of a work.
As such the scope is similar to that of ID3 tags used with MP3 files.
VorbisComment is widely supported on [[VorbisHardware|portable Ogg Vorbis players]] as well as streaming, editing and playback software.

Although the syntax of VorbisComment is well-specified, various conventions exist for the field names in use.
The goal for this page is to codify best practices and collect proposals for standardization of VorbisComment field names.

VorbisComments are typically encoded as the second packet in a codec stream. When VorbisComments are included in the first (ie. Theora) stream of an Ogg Theora file, they are assumed to cover all streams in the multiplexed group. [http://lists.xiph.org/pipermail/vorbis-dev/2008-December/019676.html]

VorbisComment is the simplest and most widely-supported mechanism for storing metadata with Xiph.Org codecs. For other existing and proposed mechanisms, see [[Metadata]].

== Recommended field names ==

The current [http://xiph.org/vorbis/doc/v-comment.html VorbisComment recommendation] contains a recommended set
of field names for comments.

== Proposed field names ==

Some proposals for extra field names:

* [http://age.hobba.nl/audio/mirroredpages/ogg-tagging.html Ogg Vorbis Comment Field Recommendations]
* [http://gophernet.org/articles/vorbiscomment/ Proposals for extending Ogg Vorbis comments]

Comments are intended to be free-form, but for the purposes of interoperability, it is helpful to define tag sets for particular applications, and provide some guidelines for machine parsing. Note that some field names have to be non-free-form to achieve machine parsing.

=== Cover art ===

==== METADATA_BLOCK_PICTURE ====
The [http://flac.sourceforge.net/format.html#metadata_block_picture binary FLAC picture structure] is base64 encoded and placed within a vorbis comment with the tag name "METADATA_BLOCK_PICTURE". This is the preferred and recommended way of embedding cover art within vorbis comments. It has the following benefits:

* Easy to use for developers since the identical (or similar) structure is also used by FLAC and MP3.
* The cover art can either be linked or embedded within the stream.
* Common picture file formats are supported (jpg and png).
* A description may be included and the picture type (front cover, back cover...) and image mime type are provided.
* Base64 encoded data is invariant under UTF-8 and a valid UTF-8 string, so obeys the rules for comment data.

Implementations interpreting or writing picture blocks should note the following details:

===== General encoding/decoding =====
* Failure to decode a picture block should not prevent playback of the file (failure to deal with the particularly large packet required by the comment header is a separate problem with the player implementation).
* Base64 encoding is used as in section 4 of [http://www.faqs.org/rfcs/rfc4648.html RFC4648]. We note that line feeds are not allowed and padding characters ('=') are required.
* Applications adding picture blocks should inform users that some applications or hardware may not support them and should provide a method to remove the blocks (this is expected to be trivial for applications capable of adding them).

===== Block handling =====
* The unencoded format is that of the [http://flac.sourceforge.net/format.html#metadata_block_picture FLAC picture block]. The fields are stored in big endian order as in FLAC, picture data is stored according to the relevant standard.
* Picture data should be stored in PNG or JPEG formats or linked separately. It is recommended readers support both PNG and JPEG
* Allowed values for the MIME string are "image/", "image/png", "image/jpeg" and "-->" (the link indicator) and "" (length 0). An empty MIME string indicates type "image/"
* Fields present in the ID3V2.4.0 [http://www.id3.org/id3v2.4.0-frames#line-1085 Attached Picture Frame] (APIC Frame) take the same interpretation as in the ID3V2.4.0 format with the following exceptions (following the FLAC format):
** The description field is UTF-8 (encoded without ID3V2's initial 'encoding byte')
** String fields are not null terminated: their preceding length fields are used instead.

===== Linked images =====
Support for linked images is optional for applications handling picture blocks. When a linked picture is indicated the following rules are observed:
* The picture data is a complete URL indicating the picture to be used, relative URLs are allowed (note relative URLs do not start with a protocol specifier and are retrieved with the same protocol as the file being processed).
* Links are ISO-8859-1 encoded
* Applications MAY retrieve linked images via the file:// protocol.
* Applications MUST obtain user approval if they wish to retrieve images via remote protocols.
* Link targets may become unavailable: applications supporting linked images SHOULD recover gracefully from this and MAY report the absence to the user.
* The type of the linked file is not restricted to JPEG and JFIF and applications MAY support other formats
* If the application does not support linked images, the target is unavailable, not permitted or an unknown format the picture block should be skipped.
* Applications may make links available to users, this is of particular use when links are unsupported or of unsupported type

===== Image dimension fields =====
* The height, width, colour depth and 'number of colours' fields are for purely informational purposes. Applications MUST NOT use them for decoding purposes, but MAY display them to the user and MAY use them to make a decision whether to skip the block (for example if selecting the most appropriate among multiple blocks).
* Applications writing picture blocks MUST set these fields correctly OR set them all to zero.

===== Multiple blocks =====
* Multiple image blocks MAY be included as separate METADATA_BLOCK_PICTURE comments.
* There may only be one each of picture type (APIC type) 1 and 2 in a Vorbis stream.
* Block order is significant for some types and applications should preserve the comment order when reading or writing Vorbis comment headers. The block order may be used to determine the order pictures are presented to the user.

===== Playback tests =====
Embedding a picture into the file might break playback of existing players (especially hardware players, software players could be updated easily). A workaround would be to link the picture within the tag. Furthermore users should become informed in some way that embedding a picture COULD cause problems (as stated above).

In order to test if there are playback problems, there are test files available [http://www.audioranger.com/coverart_mk.ogg here] and [http://www.audioranger.com/coverart_im.ogg here]. You're invited to download one of these test files (or both), test playback on your software and hardware players, and report the results here on the wiki.

'''Tested software players'''
* Audacious 1.5.1: no problem
* foobar2000: no problems
* Gnome: built-in preview playback: no problem
* MediaMonkey: no problems
* Media Player Classic (unicode build) 6.4.9.1: no problem
* RoarAudio: no problems (server and client side)
* Rythmbox 0.11.6: no problem
* Totem 2.24.3: no problem
* VLC 0.9.4/0.9.6: doesn't play
** Patch send to VLC to fix this - should get in 1.0.0
* WinAmp: no problems
* Windows Media Player 11: no problem
* XMPlay 3.4.2: no problem
* Nero ShowTime: no problem

'''Tested hardware players'''
* Logitech Squeezebox: doesn't play this file (and all other oggs with embedded picture)
** Workaround: The needed Server Software (called SqueezeCenter) can convert ogg to mp3 on the fly, and has also no problem to convert oggs with embedded pictures
* Sandisk Sansa Fuze (Firmware 01.01.22): Hangs up when trying to playback the demo file - had to reset the player
** Note: The "Fuze" can play ogg vorbis files which have embedded pictures from "Easytag"
* Cowon iAudio U3 (Firmware 1.29, 4 GB): works
* Cowon D2: no problem (latest Firmware: 2.59, 8GB Version)
* iRiver E100: no problem (latest Firmware: 1.16 G_U, 8GB Version)

'''Tested tag editors'''
* Easytag 2.1.6: can open the file to edit the normal tag fields
* MP3Tag 2.42e: can open the file to edit the normal tag fields

'''Tested other software'''
* Total Recorder: can open the file without a problem.

==== Unofficial COVERART field (deprecated) ====
There also exists an unofficial, not well supported comment field named "COVERART". It includes a base64-encoded string of the binary picture data (usually a JPEG file, but this could be a different file format too). The disadvantages are that
* no additional information like a description about the cover art or its type (front cover, back cover etc.) is provided,
* the cover art can't be linked
* the base64 string is displayed within many tag editors as plain text because of their missing support for this "COVERART" field
* it may breaks the playback on hardware players because of a large vorbis comment header
The unofficial "COVERART" field is supported for example by such software as AudioShell (http://www.softpointer.com/AudioShell.htm) and Total Recorder (http://www.totalrecorder.com/).

===== Conversion to METADATA_BLOCK_PICTURE =====
Old "COVERART" tags should be converted to the new METADATA_BLOCK_PICTURE tag (see above for its specification). This conversion is straightforward and is suggested to be done the following way:

* Decode the COVERART tag. A program MAY check the signature of the embedded picture in order to determine whether it is an allowed type. Lossless conversion from disallowed types to allowed types MAY be carried out.
* Fill out the FLAC block with the binary picture data. If the MIME type of the picture is unknown or can't be determined, the MIME type "image/" MAY be used instead. Supplying image dimensions, color depth etc. is optional (see specification above).
* In the absence of other information the picture type 'Other' should be used. Applications may want to allow users to select a default type or specify the type to use.
* Encode the new picture block, remove the COVERART tag from the comments and add the METADATA_BLOCK_PICTURE entry.
* If multiple tags are being converted the order of the METADATA_BLOCK_PICTURE tags should be the same as that of the COVERART tags they are replacing.

=== Date and time ===

The goal is to specify '''one''' standard format for describing date and/or time.

==== ISO proposal ====
The date format for any field describing a date must follow the ISO scheme: YYYY-MM-DD, shortened to just YYYY-MM or simply YYYY.

We have been recommending this usage with the DATE tag for some time. It is proposed that the spec be amended to include this information for machinability.

The time format for any field '''except''' track duration must be specified with leading T and ending with a time zone. Schemas with and without dates:
<pre>
YYYY-MM-DDTHH:MM:SS+TS
</pre>
<pre>
THH:MM+TZ
</pre>

=== ENCODER ===

The goal is to attribute encoder software. This value can be used in the future to determine which files can be improved by being re encoded with a newer version.

:'''Comment''': What is lacking from the vendor string present in the spec from the start? All libvorbis and encoder tunings I'm aware of have recorded the encoder version here.

Rationale for not using the vendor string:
* The vendor string is usually used to store the name and version of the underlying codec library
* The idea of ENCODER is to store the name of the user-visible application, for example <tt>ffmpeg2theora</tt>.
* It can be useful for debugging to store the name and version of the calling application.
* The libvorbis API does not let applications override the vendor string.

==== Proposal: Inclusion of URL in ENCODER value ====

The encoder field name must be a unique URL providing both encoder software name and version. If no unique URL address is available were both name and version is available; then the version number can be specified by separating with a space character. For example:

<nowiki>ENCODER=http://flac.sourceforge.net/ 1.2.1</nowiki>

* Note that ffmpeg2theora uses ENCODER, but does not include a url. ''Added by Rillian on September 17, 2007''

==== Proposal: ENCODED_BY ====

I've also seen ENCODED_BY. ''Added by Rillian on September 17, 2007''
: ENCODED_BY is usually the person who did the encoding. This should not be part of the recommendation due to legal problems around deliberate and accidental distribution to third parties. Basically the name of the encoder should not be included to protect encoders from their own egos and possible legal prosecution. ''Added by Aleksandersen on September 20, 2007''

=== Improving license data ===

The goal is to provide a method for proclaiming license and copyright information (basically clarifying ‘distribution rights (if any) and ownership’).

The [http://xiph.org/vorbis/doc/v-comment.html specification document] describes LICENSE and COPYRIGHT fields. But is not clear enough about whether these should be machine-readable.

We should consider working together with Creative Commons to have complementary and interlinked information on the Creative Commons and Xiph wikis. Refer to the [http://wiki.creativecommons.org/Ogg Ogg page] in the Creative Commons wiki.

==== New RIGHTS field name proposal ====
One proposal is to replace the COPYRIGHT and LICENSE field names with RIGHTS. RIGHTS must be a human-readable copyright statement. Basic example:

<nowiki>RIGHTS=Copyright © Recording Company Inc. All distribution rights reserved.</nowiki>

But this is not machine-readable. Adding two complementary field names should do the trick: RIGHTS-DATE, describing the date of copyright; and RIGHTS-URI, providing a method for linking to a license. Software agents can assume that multiple songs uses the sameURIs, such as in the case for Creative Commons. Full example:

<nowiki>RIGHTS=Copyright © 2019 Recording Company Inc. All distribution rights reserved.</nowiki> 
<nowiki>RIGHTS-DATE=2019-04</nowiki> 
<nowiki>RIGHTS-URI=http://somewhere.com/license.xhtml</nowiki>

Software such as for multimedia management and playback are encouraged to display the RIGHTS statement as a linked phrase using RIGHTS-URI.

RIGHTS-DATE does not need to be displayed as it is required in the human readable version by international copyright agreements. RIGHTS-DATE can be used to determine when a copyrighted work falls under the public domain and related matters. (''The Beatles''' copyright on their original studio recordings (not the remixes) are soon expiering. So mechanisms such as the RIGHTS-DATE are indeed required in music management and filesharing software!)

To remain machine-readable it would be required to have at most one instance of each RIGHTS field name. All fields would of course remain optional.

The ''Dublin Core Metadata Initiative'' recommends the use of ‘rights’ to describe license and copyright matters. The web feed format Atom 1.0 has implemented a rights element in their specification.

==== Improving existing fields proposal ====
Similar to the DATE tag above, we have generally recommended that a URL uniquely identifying the license be included in the LICENSE field to allow machine identification of the license. This is in agreement with the proposal in the Creative Commons wiki. Since the COPYRIGHT field is a human-readable statement of the copyright, like the proposed RIGHTS tag above, some people include a license url there. Therefore if a url can't be found in a LICENSE tag if any, applications should use one from the COPYRIGHT tag, if any. Contact information for verification, attribution, relicensing, etc. can be obtained from the COPYRIGHT field, but Creative Commons also recommend a separate CONTACT tag for this information. This is reasonable, so we propose it be included.

=== Attributing involved parties ===

The goal is to attribute more persons and organisations involved in audio and music productions to make room for more advanced search and sorting.

'''NO PROPOSAL:''' VorbisComments need a lot of extension beyond just the ARTIST field name. See work at [[M3F]], the proposed XML replacement for VorbisComments for structured metadata.

=== Geo Location fields ===

The LOCATION field is meant to carry a human readable location for the recording/creation of the media file.

Having geographical coordinates according to [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] can be useful as well, especially in a form that can be machine parsed. The agreed format is similar to this [http://en.wikipedia.org/wiki/Geo_(microformat) geo microformat]:

GEO_LOCATION= ''latitude'' ; ''longitude'' [; ''elevation'' ]

where each value is a fixed point decimal number formatted in the C locale with a period (.) for the radix. Values are separated with a ';' and white space is not significant. The elevation is optional.

''latitude'' is the geo latitude location of where the media has been recorded or produced in decimal degrees according to WGS84 (zero at the equator, negative values for southern latitudes) (C double).

''longitude'' is the geo longitude location of where the media has been recorded or produced in decimal degrees according to WGS84 (zero at the prime meridian in Greenwich/UK, negative values for western longitudes). (C double).

''elevation'' is the geo elevation of where the media has been recorded or produced in meters according to WGS84 (zero is average sea level) (C double).

=== Replay Gain ===

The REPLAYGAIN_* fields implement the Replay Gain proposal for storing a track relative volume adjustment, which can be used to "fix" quiet or loud sounding Vorbis or FLAC streams. The set of tags is intended to be machine parsed, and has the following form:
<pre>
REPLAYGAIN_TRACK_GAIN=-7.03 dB
REPLAYGAIN_TRACK_PEAK=1.21822226
REPLAYGAIN_ALBUM_GAIN=-6.37 dB
REPLAYGAIN_ALBUM_PEAK=1.21822226
</pre>

See http://www.replaygain.org/ for detailed information about Replay Gain and how the different values are calculated.

== Implementations ==

* [http://sbooth.org/importers/ Spotlight importer]
* vorbiscomment
* [http://www.xiph.org/oggz/ oggz-comment]: commandline tool, can add comments to multitrack and video files

VorbisComment

2009-06-30T07:00:17Z

Conrad: /* Implementations */ add link to oggz-comment

VorbisComment

2009-06-30T06:56:06Z

Conrad: /* ENCODER */ add some rationale for ENCODER (vs. vendor string)

VorbisComment

2009-06-30T06:46:45Z

Conrad: /* New ENCODER field name proposal */ Sort ENCODER proposals

VorbisComment is a base-level [[Metadata]] format initially created for use with Ogg [[Vorbis]]. It has since been adopted in the specifications of
[[Ogg]] encapsulations for other Xiph.Org codecs including [[Theora]], [[Speex]] and [[FLAC]].

The use case for VorbisComment is given as:
<blockquote>
... much like someone jotting a quick note on the bottom of a CDR. It should be a little information to remember the disc by and explain it to others; a short, to-the-point text note that need not only be a couple words, but isn't going to be more than a short paragraph.[http://xiph.org/vorbis/doc/v-comment.html]
</blockquote>

VorbisComments are typically used to provide basic information like the title and copyright holder of a work.
As such the scope is similar to that of ID3 tags used with MP3 files.
VorbisComment is widely supported on [[VorbisHardware|portable Ogg Vorbis players]] as well as streaming, editing and playback software.

Although the syntax of VorbisComment is well-specified, various conventions exist for the field names in use.
The goal for this page is to codify best practices and collect proposals for standardization of VorbisComment field names.

VorbisComments are typically encoded as the second packet in a codec stream. When VorbisComments are included in the first (ie. Theora) stream of an Ogg Theora file, they are assumed to cover all streams in the multiplexed group. [http://lists.xiph.org/pipermail/vorbis-dev/2008-December/019676.html]

VorbisComment is the simplest and most widely-supported mechanism for storing metadata with Xiph.Org codecs. For other existing and proposed mechanisms, see [[Metadata]].

== Recommended field names ==

The current [http://xiph.org/vorbis/doc/v-comment.html VorbisComment recommendation] contains a recommended set
of field names for comments.

== Proposed field names ==

Some proposals for extra field names:

* [http://age.hobba.nl/audio/mirroredpages/ogg-tagging.html Ogg Vorbis Comment Field Recommendations]
* [http://gophernet.org/articles/vorbiscomment/ Proposals for extending Ogg Vorbis comments]

Comments are intended to be free-form, but for the purposes of interoperability, it is helpful to define tag sets for particular applications, and provide some guidelines for machine parsing. Note that some field names have to be non-free-form to achieve machine parsing.

=== Cover art ===

==== METADATA_BLOCK_PICTURE ====
The [http://flac.sourceforge.net/format.html#metadata_block_picture binary FLAC picture structure] is base64 encoded and placed within a vorbis comment with the tag name "METADATA_BLOCK_PICTURE". This is the preferred and recommended way of embedding cover art within vorbis comments. It has the following benefits:

* Easy to use for developers since the identical (or similar) structure is also used by FLAC and MP3.
* The cover art can either be linked or embedded within the stream.
* Common picture file formats are supported (jpg and png).
* A description may be included and the picture type (front cover, back cover...) and image mime type are provided.
* Base64 encoded data is invariant under UTF-8 and a valid UTF-8 string, so obeys the rules for comment data.

Implementations interpreting or writing picture blocks should note the following details:

===== General encoding/decoding =====
* Failure to decode a picture block should not prevent playback of the file (failure to deal with the particularly large packet required by the comment header is a separate problem with the player implementation).
* Base64 encoding is used as in section 4 of [http://www.faqs.org/rfcs/rfc4648.html RFC4648]. We note that line feeds are not allowed and padding characters ('=') are required.
* Applications adding picture blocks should inform users that some applications or hardware may not support them and should provide a method to remove the blocks (this is expected to be trivial for applications capable of adding them).

===== Block handling =====
* The unencoded format is that of the [http://flac.sourceforge.net/format.html#metadata_block_picture FLAC picture block]. The fields are stored in big endian order as in FLAC, picture data is stored according to the relevant standard.
* Picture data should be stored in PNG or JPEG formats or linked separately. It is recommended readers support both PNG and JPEG
* Allowed values for the MIME string are "image/", "image/png", "image/jpeg" and "-->" (the link indicator) and "" (length 0). An empty MIME string indicates type "image/"
* Fields present in the ID3V2.4.0 [http://www.id3.org/id3v2.4.0-frames#line-1085 Attached Picture Frame] (APIC Frame) take the same interpretation as in the ID3V2.4.0 format with the following exceptions (following the FLAC format):
** The description field is UTF-8 (encoded without ID3V2's initial 'encoding byte')
** String fields are not null terminated: their preceding length fields are used instead.

===== Linked images =====
Support for linked images is optional for applications handling picture blocks. When a linked picture is indicated the following rules are observed:
* The picture data is a complete URL indicating the picture to be used, relative URLs are allowed (note relative URLs do not start with a protocol specifier and are retrieved with the same protocol as the file being processed).
* Links are ISO-8859-1 encoded
* Applications MAY retrieve linked images via the file:// protocol.
* Applications MUST obtain user approval if they wish to retrieve images via remote protocols.
* Link targets may become unavailable: applications supporting linked images SHOULD recover gracefully from this and MAY report the absence to the user.
* The type of the linked file is not restricted to JPEG and JFIF and applications MAY support other formats
* If the application does not support linked images, the target is unavailable, not permitted or an unknown format the picture block should be skipped.
* Applications may make links available to users, this is of particular use when links are unsupported or of unsupported type

===== Image dimension fields =====
* The height, width, colour depth and 'number of colours' fields are for purely informational purposes. Applications MUST NOT use them for decoding purposes, but MAY display them to the user and MAY use them to make a decision whether to skip the block (for example if selecting the most appropriate among multiple blocks).
* Applications writing picture blocks MUST set these fields correctly OR set them all to zero.

===== Multiple blocks =====
* Multiple image blocks MAY be included as separate METADATA_BLOCK_PICTURE comments.
* There may only be one each of picture type (APIC type) 1 and 2 in a Vorbis stream.
* Block order is significant for some types and applications should preserve the comment order when reading or writing Vorbis comment headers. The block order may be used to determine the order pictures are presented to the user.

===== Playback tests =====
Embedding a picture into the file might break playback of existing players (especially hardware players, software players could be updated easily). A workaround would be to link the picture within the tag. Furthermore users should become informed in some way that embedding a picture COULD cause problems (as stated above).

In order to test if there are playback problems, there are test files available [http://www.audioranger.com/coverart_mk.ogg here] and [http://www.audioranger.com/coverart_im.ogg here]. You're invited to download one of these test files (or both), test playback on your software and hardware players, and report the results here on the wiki.

'''Tested software players'''
* Audacious 1.5.1: no problem
* foobar2000: no problems
* Gnome: built-in preview playback: no problem
* MediaMonkey: no problems
* Media Player Classic (unicode build) 6.4.9.1: no problem
* RoarAudio: no problems (server and client side)
* Rythmbox 0.11.6: no problem
* Totem 2.24.3: no problem
* VLC 0.9.4/0.9.6: doesn't play
** Patch send to VLC to fix this - should get in 1.0.0
* WinAmp: no problems
* Windows Media Player 11: no problem
* XMPlay 3.4.2: no problem
* Nero ShowTime: no problem

'''Tested hardware players'''
* Logitech Squeezebox: doesn't play this file (and all other oggs with embedded picture)
** Workaround: The needed Server Software (called SqueezeCenter) can convert ogg to mp3 on the fly, and has also no problem to convert oggs with embedded pictures
* Sandisk Sansa Fuze (Firmware 01.01.22): Hangs up when trying to playback the demo file - had to reset the player
** Note: The "Fuze" can play ogg vorbis files which have embedded pictures from "Easytag"
* Cowon iAudio U3 (Firmware 1.29, 4 GB): works
* Cowon D2: no problem (latest Firmware: 2.59, 8GB Version)
* iRiver E100: no problem (latest Firmware: 1.16 G_U, 8GB Version)

'''Tested tag editors'''
* Easytag 2.1.6: can open the file to edit the normal tag fields
* MP3Tag 2.42e: can open the file to edit the normal tag fields

'''Tested other software'''
* Total Recorder: can open the file without a problem.

==== Unofficial COVERART field (deprecated) ====
There also exists an unofficial, not well supported comment field named "COVERART". It includes a base64-encoded string of the binary picture data (usually a JPEG file, but this could be a different file format too). The disadvantages are that
* no additional information like a description about the cover art or its type (front cover, back cover etc.) is provided,
* the cover art can't be linked
* the base64 string is displayed within many tag editors as plain text because of their missing support for this "COVERART" field
* it may breaks the playback on hardware players because of a large vorbis comment header
The unofficial "COVERART" field is supported for example by such software as AudioShell (http://www.softpointer.com/AudioShell.htm) and Total Recorder (http://www.totalrecorder.com/).

===== Conversion to METADATA_BLOCK_PICTURE =====
Old "COVERART" tags should be converted to the new METADATA_BLOCK_PICTURE tag (see above for its specification). This conversion is straightforward and is suggested to be done the following way:

* Decode the COVERART tag. A program MAY check the signature of the embedded picture in order to determine whether it is an allowed type. Lossless conversion from disallowed types to allowed types MAY be carried out.
* Fill out the FLAC block with the binary picture data. If the MIME type of the picture is unknown or can't be determined, the MIME type "image/" MAY be used instead. Supplying image dimensions, color depth etc. is optional (see specification above).
* In the absence of other information the picture type 'Other' should be used. Applications may want to allow users to select a default type or specify the type to use.
* Encode the new picture block, remove the COVERART tag from the comments and add the METADATA_BLOCK_PICTURE entry.
* If multiple tags are being converted the order of the METADATA_BLOCK_PICTURE tags should be the same as that of the COVERART tags they are replacing.

=== Date and time ===

The goal is to specify '''one''' standard format for describing date and/or time.

==== ISO proposal ====
The date format for any field describing a date must follow the ISO scheme: YYYY-MM-DD, shortened to just YYYY-MM or simply YYYY.

We have been recommending this usage with the DATE tag for some time. It is proposed that the spec be amended to include this information for machinability.

The time format for any field '''except''' track duration must be specified with leading T and ending with a time zone. Schemas with and without dates:
<pre>
YYYY-MM-DDTHH:MM:SS+TS
</pre>
<pre>
THH:MM+TZ
</pre>

=== ENCODER ===

The goal is to attribute encoder software. This value can be used in the future to determine which files can be improved by being re encoded with a newer version.

:'''Comment''': What is lacking from the vendor string present in the spec from the start? All libvorbis and encoder tunings I'm aware of have recorded the encoder version here.

==== Proposal: Inclusion of URL in ENCODER value ====

The encoder field name must be a unique URL providing both encoder software name and version. If no unique URL address is available were both name and version is available; then the version number can be specified by separating with a space character. For example:

<nowiki>ENCODER=http://flac.sourceforge.net/ 1.2.1</nowiki>

* Note that ffmpeg2theora uses ENCODER, but does not include a url. ''Added by Rillian on September 17, 2007''

==== Proposal: ENCODED_BY ====

I've also seen ENCODED_BY. ''Added by Rillian on September 17, 2007''
: ENCODED_BY is usually the person who did the encoding. This should not be part of the recommendation due to legal problems around deliberate and accidental distribution to third parties. Basically the name of the encoder should not be included to protect encoders from their own egos and possible legal prosecution. ''Added by Aleksandersen on September 20, 2007''

=== Improving license data ===

The goal is to provide a method for proclaiming license and copyright information (basically clarifying ‘distribution rights (if any) and ownership’).

The [http://xiph.org/vorbis/doc/v-comment.html specification document] describes LICENSE and COPYRIGHT fields. But is not clear enough about whether these should be machine-readable.

We should consider working together with Creative Commons to have complementary and interlinked information on the Creative Commons and Xiph wikis. Refer to the [http://wiki.creativecommons.org/Ogg Ogg page] in the Creative Commons wiki.

==== New RIGHTS field name proposal ====
One proposal is to replace the COPYRIGHT and LICENSE field names with RIGHTS. RIGHTS must be a human-readable copyright statement. Basic example:

<nowiki>RIGHTS=Copyright © Recording Company Inc. All distribution rights reserved.</nowiki>

But this is not machine-readable. Adding two complementary field names should do the trick: RIGHTS-DATE, describing the date of copyright; and RIGHTS-URI, providing a method for linking to a license. Software agents can assume that multiple songs uses the sameURIs, such as in the case for Creative Commons. Full example:

<nowiki>RIGHTS=Copyright © 2019 Recording Company Inc. All distribution rights reserved.</nowiki> 
<nowiki>RIGHTS-DATE=2019-04</nowiki> 
<nowiki>RIGHTS-URI=http://somewhere.com/license.xhtml</nowiki>

Software such as for multimedia management and playback are encouraged to display the RIGHTS statement as a linked phrase using RIGHTS-URI.

RIGHTS-DATE does not need to be displayed as it is required in the human readable version by international copyright agreements. RIGHTS-DATE can be used to determine when a copyrighted work falls under the public domain and related matters. (''The Beatles''' copyright on their original studio recordings (not the remixes) are soon expiering. So mechanisms such as the RIGHTS-DATE are indeed required in music management and filesharing software!)

To remain machine-readable it would be required to have at most one instance of each RIGHTS field name. All fields would of course remain optional.

The ''Dublin Core Metadata Initiative'' recommends the use of ‘rights’ to describe license and copyright matters. The web feed format Atom 1.0 has implemented a rights element in their specification.

==== Improving existing fields proposal ====
Similar to the DATE tag above, we have generally recommended that a URL uniquely identifying the license be included in the LICENSE field to allow machine identification of the license. This is in agreement with the proposal in the Creative Commons wiki. Since the COPYRIGHT field is a human-readable statement of the copyright, like the proposed RIGHTS tag above, some people include a license url there. Therefore if a url can't be found in a LICENSE tag if any, applications should use one from the COPYRIGHT tag, if any. Contact information for verification, attribution, relicensing, etc. can be obtained from the COPYRIGHT field, but Creative Commons also recommend a separate CONTACT tag for this information. This is reasonable, so we propose it be included.

=== Attributing involved parties ===

The goal is to attribute more persons and organisations involved in audio and music productions to make room for more advanced search and sorting.

'''NO PROPOSAL:''' VorbisComments need a lot of extension beyond just the ARTIST field name. See work at [[M3F]], the proposed XML replacement for VorbisComments for structured metadata.

=== Geo Location fields ===

The LOCATION field is meant to carry a human readable location for the recording/creation of the media file.

Having geographical coordinates according to [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] can be useful as well, especially in a form that can be machine parsed. The agreed format is similar to this [http://en.wikipedia.org/wiki/Geo_(microformat) geo microformat]:

GEO_LOCATION= ''latitude'' ; ''longitude'' [; ''elevation'' ]

where each value is a fixed point decimal number formatted in the C locale with a period (.) for the radix. Values are separated with a ';' and white space is not significant. The elevation is optional.

''latitude'' is the geo latitude location of where the media has been recorded or produced in decimal degrees according to WGS84 (zero at the equator, negative values for southern latitudes) (C double).

''longitude'' is the geo longitude location of where the media has been recorded or produced in decimal degrees according to WGS84 (zero at the prime meridian in Greenwich/UK, negative values for western longitudes). (C double).

''elevation'' is the geo elevation of where the media has been recorded or produced in meters according to WGS84 (zero is average sea level) (C double).

=== Replay Gain ===

The REPLAYGAIN_* fields implement the Replay Gain proposal for storing a track relative volume adjustment, which can be used to "fix" quiet or loud sounding Vorbis or FLAC streams. The set of tags is intended to be machine parsed, and has the following form:
<pre>
REPLAYGAIN_TRACK_GAIN=-7.03 dB
REPLAYGAIN_TRACK_PEAK=1.21822226
REPLAYGAIN_ALBUM_GAIN=-6.37 dB
REPLAYGAIN_ALBUM_PEAK=1.21822226
</pre>

See http://www.replaygain.org/ for detailed information about Replay Gain and how the different values are calculated.

== Implementations ==

* [http://sbooth.org/importers/ Spotlight importer]
* vorbiscomment
* oggz-comment

People

2009-06-28T02:10:49Z

Conrad: add oggz, fishsound to my things

This page is meant to help with nickname to person lookup. ''Nickname'' can be a mail alias, an IRC nick, or a Subversion user — in most cases several of these. Please help to fill this table. Keeping your own entry up to date is a good start.

{| border="1" cellspacing="1" cellpadding="4" width="100%"
|+ Who is who
! Nickname
! Real name
! Keywords
|-
| arkadini
| Arek Korbik
| Quicktime, XiphQT
|-
| ben
| Benjamin Gérard
| libao
|-
| BjornW
| Björn Wijers
| [[Spread Open Media]], [[XSPF]]
|-
| [[User:Conrad|conrad]]
| [http://blog.kfish.org/ Conrad Parker]
| see ''[[#nick_kfish|kfish]]''
|-
| derf
| [http://people.xiph.org/~tterribe/ Timothy B. Terriberry]
| theora, CELT, video
|-
| dllmain
| Sebastian Pipping
| see ''[[#nick_sping|sping]]'', nick not used anymore
|-
| doublec
| Chris Double
| firefox, theora, Mozilla
|-
| drac667
| Cristian Adam
| DirectShow, oggcodecs, Windows
|-
| giles
| [http://people.xiph.org/~giles/ Ralph Giles]
| see ''[[#nick_rillian|rillian]]''
|-
| gmaxwell
| Gregory Maxwell
| Wikimedia, CELT, theora
|-
| [[User:Silvia|ginger]]
| Silvia Pfeiffer
| see ''[[#nick_nessy|nessy]]''
|-
| [[User:Imalone|imalone]]
| Ian Malone
| metadata
|-
| illiminable
| Zentaro Kavanagh
| DirectShow, dsfilters, Microsoft
|-
| [[User:Saoshyant|ivo]]
| Ivo Emanuel Gonçalves
| advocacy, [[Spread Open Media]], [[XSPF]]
|-
| jack
| Jack Moffitt
| libao, treasurer, Icecast
|-
| jcoalson
| Josh Coalson
| FLAC author
|-
| j, j^
| Jan Gerber
| v2v, ffmpeg2theora, sysadmin
|-
| [[User:jmspeex|jmspeex]]
| Jean-Marc Valin
| speex, ghost, VoIP
|-
| jmworx
| Jean-Marc Valin
| see ''[[#nick_jmspeex|jmspeex]]''
|-
| JoeyBorn
| Joe Born
| neuros
|-
| karl
| Karl Heyes
| Icecast
|-
| [[User:Conrad|kfish]]
| [http://www.kfish.org/ Conrad Parker]
| annodex, fishsound, hogg, oggz, vorbis-tools
|-
| laser13
| Marcin Lubonski
| annodex, oggplay, win32
|-
| lgonze
| Lucas Gonze
| [[XSPF]]
|-
| lu_zero
| Luca Barbato
| RTP Vorbis, RTP Theora, Gentoo
|-
| maikmerten
| Maik Merten
| theora, java, macos
|-
| MikeS
| Michael Smith
| fluendo, gstreamer, sysadmin, IceS
|-
| Monty
| Christopher Montgomery
| see ''[[#nick_xiphmont|xiphmont]]''
|-
| msmith
| Michael Smith
| see ''[[#nick_mikes|MikeS]]''
|-
| nessy
| Silvia Pfeiffer
| annodex, vquence, sysadmin, CMML
|-
| ozone
| André Pang
| annodex, macos
|-
| pjones
| Peter Jones
| cdparanoia, redhat
|-
| rillian
| [http://people.xiph.org/~giles/ Ralph Giles]
| metadata, video, theora, MNG, sysadmin
|-
| ribamar
| Ribamar Santarosa
| etheora
|-
| Saoshyant
| Ivo Emanuel Gonçalves
| see ''[[#nick_ivo|ivo]]''
|-
| segher
| Segher Boessenkool
| vorbis, audio
|-
| shans
| Shane Stephens
| annodex, oggplay
|-
| silvia
| Silvia Pfeiffer
| see ''[[#nick_nessy|nessy]]''
|-
| [[User:sping|sping]]
| Sebastian Pipping
| [[XSPF]], [http://libspiff.sourceforge.net/ libSpiff], [http://validator.xspf.org/ XSPF Validator]
|-
| tterribe
| [http://people.xiph.org/~tterribe/ Timothy B. Terriberry]
| See ''[[#nick_derf|derf]]''
|-
| thomasvs
| Thomas Vander Stichele
| fluendo, flumotion, gstreamer
|-
| volsung
| Stan Seibert
| libao
|-
| xiphmont
| Christopher Montgomery
| vorbis, ghost, audio, Ogg, cdparanoia
|-
| zen
| Zentaro Kavanagh
| see ''[[#nick_illi|illi]]''
|-
|}

[[Category:Developers stuff]]

TheoraSoftwarePlayers

2009-06-25T08:57:04Z

Conrad: /* Multi-platform */ s/Firefox 3.1 Beta/Firefox 3.5/ (needs link update on release)

== Multi-platform ==
* [http://www.videolan.org/vlc/ VLC Media Player]: Open Source media player and streaming server that support virtually every video and audio format
* [https://helixcommunity.org/projects/xiph/ Xiph Plugins for Real Player/Producer]
* Quicktime components for [http://qtcomponents.sourceforge.net/ Quicktime 6] and [http://www.xiph.org/quicktime/ Quicktime 7] – QuickTime and Macintosh OS X plug-ins
* [http://www.mplayerhq.hu/ Mplayer]: Open Source video player
* [http://www.coreplayer.com/ CorePlayer]: A multimedia platform for mobile and desktop computer systems
* [http://www.flumotion.net/cortado/ Cortado]: Java applet playing ogg/theora/vorbis
* [http://www.mozilla.org/developer/#builds Firefox 3.5]: Open Source web browser
* [http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/ Opera 9.52 Experimental build]: Web browser

== Windows ==
* [http://www.xiph.org/dshow/ DirectShow filter]: Adds support for Ogg Vorbis, Ogg Speex, Ogg Theora, Ogg FLAC, and native FLAC to any DirectShow-compliant player such as Windows Media Player and BSPlayer
* [http://www.visonair.tv/player.php Visonair.tv Player]: Freeware player - Plays Ogg Vorbis and Theora streams

== Linux/BSD ==
* [http://player.helixcommunity.org Helix Player] - an open source media player for Linux, Solaris, and Symbian based on the [http://helix-client.helixcommunity.org Helix DNA Client] media engine.
* [http://www.gnomefiles.org/app.php?soft_id=64 Totem] - a Free Software (GPL-licensed) media player based on [http://xinehq.de xine] or [http://gstreamer.freedesktop.org GStreamer] media engine.
* [http://xinehq.de Xine]: a Free Software (GPL-licensed) media player, complete with its own media engine and a long list of supported formats.

== Mac OS X ==

* [http://xinehq.de Xine]: a Free Software (GPL-licensed) media player, complete with its own media engine and a long list of supported formats. Supports Darwin/MacOS X (ppc) via the fink project.

== See also ==
{{Template:Theora}}

[[Category:Theora]]

HTML5

2009-06-25T07:12:50Z

Conrad: add link to ogg.org

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]]. It is also a place to collect ideas for [http://ogg.org/ ogg.org].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-06-25T00:54:16Z

Conrad: /* HTML5 <video> embedding */ add link to CELT presentations (example HTML)

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

You can include one of the scripts below, or modify source from an existing page such as the HTML of
[http://www.celt-codec.org/presentations/ CELT presentations].

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-06-25T00:50:32Z

Conrad: /* Technology for setting up your own site */ add link, info to firefogg

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Encoding, transcoding ===

==== Firefogg ====

[http://firefogg.org/ Firefogg] provides "video encoding and uploading for Firefox". This includes a Firefox extension that allows users to encode video to Ogg Theora on their own computer while uploading it to your site. This simplifies the upload for users as they can simply choose from their existing video files, and simplifies your web site by allowing you to deal with only one video format, and offloading the CPU cycles required for encoding to the user.

=== Content management ===

* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-06-25T00:42:48Z

Conrad: /* Browser Support */ add header for safari

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Apple Safari ===

=== Microsoft Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Content management ===

* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-06-25T00:41:58Z

Conrad: /* Backend servers */ add link to oggz

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Content management ===

* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* [http://www.xiph.org/oggz/ oggz-chop]

HTML5

2009-06-25T00:41:03Z

Conrad: /* Content management */ add link to MetaVidWiki

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Content management ===

* [http://metavid.org/wiki/MetaVidWiki_Software MetaVidWiki]

=== Backend servers ===

* oggz-chop

HTML5

2009-06-25T00:39:40Z

Conrad: /* HTML5 <video> embedding */

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

There are various ways to provide HTML5 video content with fallbacks for older browsers and non-free codecs.

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

==== Video for Everybody ====

[http://camendesign.com/code/video_for_everybody Video for Everybody] is
"a chunk of HTML code that embeds a video into a website
using the HTML5 <video> element."

=== Content management ===

* MetaVid

=== Backend servers ===

* oggz-chop

HTML5

2009-06-25T00:33:59Z

Conrad: /* HTML5 <video> embedding */

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

==== mv_embed ====

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

Example sites using mv_embed:
* [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

==== iTheora ====

[http://itheora.org/ iTheora]

Example sites using iTheora:
* [http://theorasea.org]

=== Content management ===

* MetaVid

=== Backend servers ===

* oggz-chop

HTML5

2009-06-25T00:31:46Z

Conrad: /* HTML5 <video> embedding */

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

* mv_embed

Example: [http://www.firefogg.org/make/mwEmbed/example_usage/Player_Simple_Video_Tag.html]

[http://metavid.org/w/index.php/Mv_embed mv_embed homepage]
and
[http://www.mediawiki.org/wiki/Media_Projects_Overview#MwEmbed mv_embed on MediaWiki]

* iTheora

=== Content management ===

* MetaVid

=== Backend servers ===

* oggz-chop

HTML5

2009-06-25T00:02:34Z

Conrad: add page aim

The HTML5 specification includes support for <video> and <audio>.
This page outlines use of HTML5 syntax with Xiph.Org codecs, particularly Ogg [[Theora]] and Ogg [[Vorbis]].

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

* mv_embed
* iTheora

=== Content management ===

* MetaVid

=== Backend servers ===

* oggz-chop

HTML5

2009-06-24T23:58:04Z

Conrad: start page, basic outline

The HTML5 specification includes support for <video> and <audio>.

== Browser Support ==

[[TheoraSoftwarePlayers]]

=== Mozilla Firefox ===

=== Opera ===

=== Google Chrome ===

=== Internet Explorer ===

=== Plugins ===

[http://itheora.org/?p=screens Compatibility]

== Web Video sites ==

The following web sites support HTML5 directly:

* tinyvid.tv

* DailyMotion

* MetaVid

For more examples of Ogg Theora video, see
[[List of Theora videos]].

== Technology for setting up your own site ==

=== HTML5 <video> embedding ===

* mv_embed
* iTheora

=== Content management ===

* MetaVid

=== Backend servers ===

* oggz-chop

VorbisComment

2009-06-22T01:45:13Z

Conrad: /* Proposed field names */

VorbisComment is a base-level [[Metadata]] format initially created for use with Ogg [[Vorbis]]. It has since been adopted in the specifications of
[[Ogg]] encapsulations for other Xiph.Org codecs including [[Theora]], [[Speex]] and [[FLAC]].

The use case for VorbisComment is given as:
<blockquote>
... much like someone jotting a quick note on the bottom of a CDR. It should be a little information to remember the disc by and explain it to others; a short, to-the-point text note that need not only be a couple words, but isn't going to be more than a short paragraph.[http://xiph.org/vorbis/doc/v-comment.html]
</blockquote>

VorbisComments are typically used to provide basic information like the title and copyright holder of a work.
As such the scope is similar to that of ID3 tags used with MP3 files.
VorbisComment is widely supported on [[VorbisHardware|portable Ogg Vorbis players]] as well as streaming, editing and playback software.

Although the syntax of VorbisComment is well-specified, various conventions exist for the field names in use.
The goal for this page is to codify best practices and collect proposals for standardization of VorbisComment field names.

VorbisComments are typically encoded as the second packet in a codec stream. When VorbisComments are included in the first (ie. Theora) stream of an Ogg Theora file, they are assumed to cover all streams in the multiplexed group. [http://lists.xiph.org/pipermail/vorbis-dev/2008-December/019676.html]

VorbisComment is the simplest and most widely-supported mechanism for storing metadata with Xiph.Org codecs. For other existing and proposed mechanisms, see [[Metadata]].

==Recommended field names==

The current [http://xiph.org/vorbis/doc/v-comment.html VorbisComment recommendation] contains a recommended set
of field names for comments.

==Proposed field names==

Some proposals for extra field names:

* [http://age.hobba.nl/audio/mirroredpages/ogg-tagging.html Ogg Vorbis Comment Field Recommendations]
* [http://gophernet.org/articles/vorbiscomment/ Proposals for extending Ogg Vorbis comments]

Comments are intended to be free-form, but for the purposes of interoperability, it is helpful to define
tag sets for particular applications, and provide some guidelines for machine parsing.

:: '''Some''' field names may have to be non-free-form to achieve machine parsing. Such as ENCODER, DATE, RIGHTS-DATE, and RIGHTS-URI. See reasoning below.

=== Cover art ===

==== METADATA_BLOCK_PICTURE ====
The [http://flac.sourceforge.net/format.html#metadata_block_picture binary FLAC picture structure] is base64 encoded and placed within a vorbis comment with the tag name "METADATA_BLOCK_PICTURE". This is the preferred and recommended way of embedding cover art within vorbis comments. It has the following benefits:

* Easy to use for developers since the identical (or similar) structure is also used by FLAC and MP3.
* The cover art can either be linked or embedded within the stream.
* Common picture file formats are supported (jpg and png).
* A description may be included and the picture type (front cover, back cover...) and image mime type are provided.
* Base64 encoded data is invariant under UTF-8 and a valid UTF-8 string, so obeys the rules for comment data.

Implementations interpreting or writing picture blocks should note the following details:
===== General encoding/decoding =====
* Failure to decode a picture block should not prevent playback of the file (failure to deal with the particularly large packet required by the comment header is a separate problem with the player implementation).
* Base64 encoding is used as in section 4 of [http://www.faqs.org/rfcs/rfc4648.html RFC4648]. We note that line feeds are not allowed and padding characters ('=') are required.
* Applications adding picture blocks should inform users that some applications or hardware may not support them and should provide a method to remove the blocks (this is expected to be trivial for applications capable of adding them).

===== Block handling =====
* The unencoded format is that of the [http://flac.sourceforge.net/format.html#metadata_block_picture FLAC picture block]. The fields are stored in big endian order as in FLAC, picture data is stored according to the relevant standard.
* Picture data should be stored in PNG or JPEG formats or linked separately. It is recommended readers support both PNG and JPEG
* Allowed values for the MIME string are "image/", "image/png", "image/jpeg" and "-->" (the link indicator) and "" (length 0). An empty MIME string indicates type "image/"
* Fields present in the ID3V2.4.0 [http://www.id3.org/id3v2.4.0-frames#line-1085 Attached Picture Frame] (APIC Frame) take the same interpretation as in the ID3V2.4.0 format with the following exceptions (following the FLAC format):
** The description field is UTF-8 (encoded without ID3V2's initial 'encoding byte')
** String fields are not null terminated: their preceding length fields are used instead.

===== Linked images =====
Support for linked images is optional for applications handling picture blocks. When a linked picture is indicated the following rules are observed:
* The picture data is a complete URL indicating the picture to be used, relative URLs are allowed (note relative URLs do not start with a protocol specifier and are retrieved with the same protocol as the file being processed).
* Links are ISO-8859-1 encoded
* Applications MAY retrieve linked images via the file:// protocol.
* Applications MUST obtain user approval if they wish to retrieve images via remote protocols.
* Link targets may become unavailable: applications supporting linked images SHOULD recover gracefully from this and MAY report the absence to the user.
* The type of the linked file is not restricted to JPEG and JFIF and applications MAY support other formats
* If the application does not support linked images, the target is unavailable, not permitted or an unknown format the picture block should be skipped.
* Applications may make links available to users, this is of particular use when links are unsupported or of unsupported type

===== Image dimension fields =====
* The height, width, colour depth and 'number of colours' fields are for purely informational purposes. Applications MUST NOT use them for decoding purposes, but MAY display them to the user and MAY use them to make a decision whether to skip the block (for example if selecting the most appropriate among multiple blocks).
* Applications writing picture blocks MUST set these fields correctly OR set them all to zero.

===== Multiple blocks =====
* Multiple image blocks MAY be included as separate METADATA_BLOCK_PICTURE comments.
* There may only be one each of picture type (APIC type) 1 and 2 in a Vorbis stream.
* Block order is significant for some types and applications should preserve the comment order when reading or writing Vorbis comment headers. The block order may be used to determine the order pictures are presented to the user.

===== Playback tests =====
Embedding a picture into the file might break playback of existing players (especially hardware players, software players could be updated easily). A workaround would be to link the picture within the tag. Furthermore users should become informed in some way that embedding a picture COULD cause problems (as stated above).

In order to test if there are playback problems, there are test files available [http://www.audioranger.com/coverart_mk.ogg here] and [http://www.audioranger.com/coverart_im.ogg here]. You're invited to download one of these test files (or both), test playback on your software and hardware players, and report the results here on the wiki.

'''Tested software players'''
* Audacious 1.5.1: no problem
* foobar2000: no problems
* Gnome: built-in preview playback: no problem
* MediaMonkey: no problems
* Media Player Classic (unicode build) 6.4.9.1: no problem
* RoarAudio: no problems (server and client side)
* Rythmbox 0.11.6: no problem
* Totem 2.24.3: no problem
* VLC 0.9.4/0.9.6: doesn't play
** Patch send to VLC to fix this - should get in 1.0.0
* WinAmp: no problems
* Windows Media Player 11: no problem
* XMPlay 3.4.2: no problem
* Nero ShowTime: no problem

'''Tested hardware players'''
* Logitech Squeezebox: doesn't play this file (and all other oggs with embedded picture)
** Workaround: The needed Server Software (called SqueezeCenter) can convert ogg to mp3 on the fly, and has also no problem to convert oggs with embedded pictures
* Sandisk Sansa Fuze (Firmware 01.01.22): Hangs up when trying to playback the demo file - had to reset the player
** Note: The "Fuze" can play ogg vorbis files which have embedded pictures from "Easytag"
* Cowon iAudio U3 (Firmware 1.29, 4 GB): works
* Cowon D2: no problem (latest Firmware: 2.59, 8GB Version)
* iRiver E100: no problem (latest Firmware: 1.16 G_U, 8GB Version)

'''Tested tag editors'''
* Easytag 2.1.6: can open the file to edit the normal tag fields
* MP3Tag 2.42e: can open the file to edit the normal tag fields

'''Tested other software'''
* Total Recorder: can open the file without a problem.

==== Unofficial COVERART field (deprecated) ====
There also exists an unofficial, not well supported comment field named "COVERART". It includes a base64-encoded string of the binary picture data (usually a JPEG file, but this could be a different file format too). The disadvantages are that
* no additional information like a description about the cover art or its type (front cover, back cover etc.) is provided,
* the cover art can't be linked
* the base64 string is displayed within many tag editors as plain text because of their missing support for this "COVERART" field
* it may breaks the playback on hardware players because of a large vorbis comment header
The unofficial "COVERART" field is supported for example by such software as AudioShell (http://www.softpointer.com/AudioShell.htm) and Total Recorder (http://www.totalrecorder.com/).

===== Conversion to METADATA_BLOCK_PICTURE =====
Old "COVERART" tags should be converted to the new METADATA_BLOCK_PICTURE tag (see above for its specification). This conversion is straightforward and is suggested to be done the following way:

* Decode the COVERART tag. A program MAY check the signature of the embedded picture in order to determine whether it is an allowed type. Lossless conversion from disallowed types to allowed types MAY be carried out.
* Fill out the FLAC block with the binary picture data. If the MIME type of the picture is unknown or can't be determined, the MIME type "image/" MAY be used instead. Supplying image dimensions, color depth etc. is optional (see specification above).
* In the absence of other information the picture type 'Other' should be used. Applications may want to allow users to select a default type or specify the type to use.
* Encode the new picture block, remove the COVERART tag from the comments and add the METADATA_BLOCK_PICTURE entry.
* If multiple tags are being converted the order of the METADATA_BLOCK_PICTURE tags should be the same as that of the COVERART tags they are replacing.

===Dates and time===
The goal is to specify '''one''' standard format for describing dates and time.

====ISO proposal====
The date format for any field describing a date must follow the ISO scheme: YYYY-MM-DD or shortened to just YYYY-MM or simply YYYY.

We have been recommending this usage with the DATE tag for some time. It is proposed that the spec be amended to include this
information for machinability.

The time format for any field '''except''' track duration must be specified with leading T and ending with a time zone. Schemas with and without dates: YYYY-MM-DDTHH:MM:SS+TS THH:MM+TZ

===New ENCODER field name proposal===
The goal is to attribute encoder software. This value can be used in the future to determine which files can be improved by being re encoded with a newer version.

:'''Comment''': What is lacking from the vendor string present in the spec from the start? All libvorbis and encoder tunings I'm aware of have recorded the encoder version here.
:: Note that ffmpeg2theora uses ENCODER, but does not include a url.
::: A URI/L—especially one with version numbering—will be more unique. See the above goal for this comment.
:: I've also seen ENCODED_BY.
::: ENCODED_BY is usually the person who did the encoding. This should not be part of the recommendation due to legal problems around deliberate and accidental distribution to third parties. Basically the name of the encoder should not be included to protect encoders from their own egos and possible legal prosecution.
:: I am trying to get the specification to include that this field '''must''' contain a unique URL and version number. For the reason listed above. Whether to including the field at all would of course be optional.

====Proposal====
The encoder field name must be a unique URL providing both encoder software name and version. If no unique URL address is available were both name and version is available; then the version number can be specified by separating with a space character. For examples:

<nowiki>ENCODER=http://flac.sourceforge.net/ 1.2.1</nowiki>

===Improving license data===
The goal is to provide a method for proclaiming license and copyright information (basically clarifying ‘distribution rights (if any) and ownership’).

The [http://xiph.org/vorbis/doc/v-comment.html specification document] describes LICENSE and COPYRIGHT fields. But is not clear enough about whether these should be machine-readable.

We should consider working together with Creative Commons to have complementary and interlinked information on the CC and Xiph wikis. Refer to the [http://wiki.creativecommons.org/Ogg Ogg page] in the CC wiki.

==== New RIGHTS field name proposal ====
One proposal is to replace the COPYRIGHT and LICENSE field names with RIGHTS. RIGHTS must be a human-readable copyright statement. Basic example:

<nowiki>RIGHTS=Copyright © Recording Company Inc. All distribution rights reserved.</nowiki>

But this is not machine-readable. Adding two complementary field names should do the trick: RIGHTS-DATE, describing the date of copyright; and RIGHTS-URI, providing a method for linking to a license. Software agents can assume that multiple songs uses the sameURIs, such as in the case for Creative Commons. Full example:

<nowiki>RIGHTS=Copyright © 2019 Recording Company Inc. All distribution rights reserved.</nowiki> 
<nowiki>RIGHTS-DATE=2019-04</nowiki> 
<nowiki>RIGHTS-URI=http://somewhere.com/license.xhtml</nowiki>

Software such as for multimedia management and playback are encouraged to display the RIGHTS statement as a linked phrase using RIGHTS-URI.

RIGHTS-DATE does not need to be displayed as it is required in the human readable version by international copyright agreements. RIGHTS-DATE can be used to determine when a copyrighted work falls under the public domain and related matters. (''The Beatles''' copyright on their original studio recordings (not the remixes) are soon expiering. So mechanisms such as the RIGHTS-DATE are indeed required in music management and filesharing software!)

To remain machine-readable it would be required to have at most one instance of each RIGHTS field name. All fields would of course remain optional.

The ''Dublin Core Metadata Initiative'' recommends the use of ‘rights’ to describe license and copyright matters. The web feed format Atom 1.0 has implemented a rights element in their specification.

==== Improving existing fields proposal ====
Similar to the DATE tag above, we have generally recommended that a URL uniquely identifying the license be included in the LICENSE field to allow machine identification of the license. This is in agreement with the proposal in the CC wiki. Since the COPYRIGHT field is a human-readable statement of the copyright, like the proposed RIGHTS tag above, some people include a license url there. Therefore if a url can't be found in a LICENSE tag if any, applications should use one from the COPYRIGHT tag, if any. Contact information for verification, attribution, relicensing, etc. can be obtained from the COPYRIGHT field, but CC also recommend a separate CONTACT tag for this information. This is reasonable, so we propose it be included.

=== Attributing involved parties ===
The goal is to attribute more persons and organisations involved in audio and music productions to make room for more advanced search and sorting.

'''NO PROPOSALS!''' Needs much extending beyond just ARTIST field name. See work at proposed XML replacement for Vorbis Comments, [[M3F]].

=== Geo Location fields ===
The LOCATION field is meant to carry a human readable location for the recording/creation of the media file.

Having geographical coordinates according to [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] can be useful as well, especially in a form that can be machine parsed. The agreed format is similar to this [http://en.wikipedia.org/wiki/Geo_(microformat) geo microformat]:

GEO_LOCATION= ''latitude'' ; ''longitude'' [; ''elevation'' ]

where each value is a fixed point decimal number formatted in the C locale with a period (.) for the radix. Values are separated with a ';' and white space is not significant. The elevation is optional.

''latitude'' is the geo latitude location of where the media has been recorded or produced in decimal degrees according to WGS84 (zero at the equator, negative values for southern latitudes) (C double).

''longitude'' is the geo longitude location of where the media has been recorded or produced in decimal degrees according to WGS84 (zero at the prime meridian in Greenwich/UK, negative values for western longitudes). (C double).

''elevation'' is the geo elevation of where the media has been recorded or produced in meters according to WGS84 (zero is average sea level) (C double).

== Character encoding ==
The goal is to be offer better support for more languages and make machine processing faster.

The specification should be a little more strict to achieve this.

==== Proposals ====
''Field names may be UTF-8 and all UPPERCASE for easier machine processing.''

Allowing tag names to be UTF-8 instead of ASCII is a backwards-incompatible spec change. If we did this, requiring that the case mapping happen in the tagging application rather than in decoders is reasonable, since case mapping in unicode is non-trival.

The original argument for ASCII was that we need standardized tag names for interoperability, so there's no point in being able to localize them, and we might as well go with our native prejudice. Localizing the values should be done by appending a language code to the tag, since this is both machinable and there may be collisions between translated tag names.

:UTF-8 is a bad idea in field names. The field names are for machine interpretation, localisation should be done on the software side. UTF-8 introduces matching problems (canonical form) and encoding/decoding problems (difficulty in finding length of a string). Please sign comments; I ''think'' the above is a cumulative set of comments, but no idea.--[[User:Imalone|Imalone]] 01:11, 17 September 2007 (PDT)

== Implementations ==

* [http://sbooth.org/importers/ Spotlight importer]
* vorbiscomment
* oggz-comment

ReleaseProcess

2009-05-09T03:44:21Z

Conrad: add info on /downloads and update.sh from Sebastian Pipping

= Process =

== Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==

If you are uploading the first release of a project to Xiph.org, then first create a release directory in the svn repository. You can do this using remote svn commands (rather than checking out the entire Xiph.org release archive):

<tt>svn mkdir http://svn.xiph.org/releases/PROJECTNAME</tt>

Then check that directory out locally:

<tt>svn co http://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>

== Add new release files ==

Add tarballs etc. to your local checkout of the release directory:

<tt>cd PROJECTNAME-releases</tt>
<tt>svn add PROJECTNAME-x.x.x.tar.gz</tt>

Then, generate MD5 and SHA1 checksums for these files:

<tt>md5sum *.tar.gz > MD5SUMS</tt>
<tt>sha1sum *.tar.gz > SHA1SUMS</tt>

Check that the only modifications to the checksums are for the new files:

<tt>svn diff</tt>

If everything is ok (and the checksums for other files have not changed), commit:

<tt>svn commit</tt>

== Update [http://www.xiph.org/downloads/ http://www.xiph.org/downloads/] ==

The downloads page is in the normal svn repository for www.xiph.org:

<tt>svn co http://svn.xiph.org/websites/xiph.org/downloads/</tt>

Update it with your release tarball name and checksum, and commit.

== Mail appropriate lists ==

Mail your release notes to appropriate project lists. You may also want to send news to:

<tt>Linux Weekly News <lwn@lwn.net></tt>
<tt>comp.os.linux.announce <cola@stump.algebra.com></tt>

= Tools =

Sebastian Pipping has a script to add tarballs and update the appropriate web pages for libxspf:
[https://trac.xiph.org/browser/releases/xspf/update.sh update.sh]. You may want to adapt this for your project.

ReleaseProcess

2009-05-09T02:25:54Z

Conrad: first cut at documenting release process

== Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==

If you are uploading the first release of a project to Xiph.org, then first create a release directory in the svn repository. You can do this using remote svn commands (rather than checking out the entire Xiph.org release archive):

<tt>svn mkdir http://svn.xiph.org/releases/PROJECTNAME</tt>

Then check that directory out locally:

<tt>svn co http://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>

== Add new release files ==

Add tarballs etc. to your local checkout of the release directory:

<tt>cd PROJECTNAME-releases</tt>
<tt>svn add PROJECTNAME-x.x.x.tar.gz</tt>

Then, generate MD5 and SHA1 checksums for these files:

<tt>md5sum *.tar.gz > MD5SUMS</tt>
<tt>sha1sum *.tar.gz > SHA1SUMS</tt>

Check that the only modifications to the checksums are for the new files:

<tt>svn diff</tt>

If everything is ok (and the checksums for other files have not changed), commit:

<tt>svn commit</tt>

== Mail appropriate lists ==

Mail your release notes to appropriate project lists. You may also want to send news to:

<tt>Linux Weekly News <lwn@lwn.net></tt>
<tt>comp.os.linux.announce <cola@stump.algebra.com></tt>

Summer of Code 2009

2009-03-22T13:26:36Z

Conrad: /* OpenMAX IL components for Ogg codecs */ flesh out proposal

This is our ideas page for [http://code.google.com/soc/ Google Summer of Code 2009] projects with [http://xiph.org Xiph.org] and [http://annodex.org/ Annodex]. The two projects participate jointly this year under Xiph's name.

'''Students''' please use the template at [[Summer of Code Applications]] when applying for a GSoC position.

'''Mentors''' please visit [[Summer of Code Mentoring]] and help us prepare our application as a mentoring organization.

== General Ideas ==

=== Codecs ===

* OpenMAX IL components for Ogg codecs
* Get skeleton patches upstream so players stop choking on it.
* Portable listening application for codec MOS/MUSHRA comparisons (Win32, MacOS, Linux; FF3.1 web application?).

=== Web Video ===

* Proof of concept liboggplay-based media patch for Google's Chrome browser.
* Metavid improvements
* Kate to HTML & CSS overlay library in javascript.
* Firefox extension to record locally and stream to icecast.
* Firefox extension to support RTP for conferencing.
** also consider applying [https://wiki.mozilla.org/Community:SummerOfCode09#Firefox under Mozilla SOC org].
* mod_duration apache module to generate X-Content-Duration headers for Ogg files. ''(We should get people to use '''oggz_chop''' instead ... oggz_chop provides this functionality and more, is already relatively lightweight.)'' Perhaps this project could be more focused on packaging oggz_chop for other web servers like lightpd and maybe a fastCGI version and or maybe push for an mod_ogg to be adopted upstream in apache to improve distribution.

== Detailed Project Descriptions ==

These ideas were suggested by various members of the developer community as projects that would be beneficial and which we feel we can mentor. Students should feel free to select one of these, develop a variation, or propose their own ideas. Here, ideally.

=== Proof of Concept liboggplay (html5 video) support in Chromium Browser ===

This project would focus on integrating support for liboggplay into chrome. This project would only need to be a proof of concept with the end result being some frames decoded in the browser. We have some direct contacts with people on the Chromium project in Google, but would expect the student mostly to work through the Xiph on Chromium online communities.

[http://code.google.com/chromium/ Chromium Home Page]

=== Metavid related projects ===

see [http://metavid.org/wiki/Summer_of_Code_2009 full page on metavid.org]
* Improve transcript import / export system:
** Wiki to SRT
** SRT to Wiki
** CMML to Wiki
** Extend oggz_chop or other tool for exporting transcript encapsulated in the ogg file.

=== Javascript Library for Subtitles, Captions and other time-aligned text ===

The main focus of the project is on enabling video accessibility for Ogg in Firefox.

==== Problem / Intro ====

Captions, subtitles and other categories of time-aligned text are starting to become relevant to HTML5. In Ogg, we currently encapsulate such data in OggKate and can use SRT or Kate as input formats. Display of OggKate is currently supported in VLC and there are patches for various other media players. We now want to enable Web browsers to also deal with these time-aligned text tracks in those Web Browsers that support the HTML5 video tag.

==== Solution / Task ====

There is a proof of concept patch for Firefox 3.1 (now called 3.5) and liboggplay through which Firefox is capable of decoding Ogg Kate tracks and either overlay them onto the video, or handing the raw text to the browser (eg, for text to speech). However, there is no display of OggKate in Firefox 3.5 using HTML5. This can be fixed through the creation of a javascript library that can deal with Kate output and convert it to HTML and CSS. Example libraries exists for displaying SRT for HTML5 video, but they will need to be extended to Kate in this project.

This project includes the creation of example files for different types of time-aligned text. These are then encapsulated into Ogg through Kate encoding. Firefox 3.5 with the applied OggKate patch can decode these files and hand the textual data to the Web browser. It will be necessary to extend liboggplay to pass non textual Kate data (eg, styling, etc) to the browser, as currently the only two ways of dealing with a Kate track is to render it, or pass raw text, ignoring extra styling information. This could be part of the project, or done before the GSoC projects begins. The browser receives the text and styling information, and a javascript library implemented by the student will take care of the display. This will include an implementation of default display mechanisms for the different types of time-aligned text that we decide to deal with.

==== Requirements ====

The project requires a student with experience in javascript development, HTML and CSS, but also with some understanding of C for liboggplay and libkate, and of C++ for Firefox. The student will learn how to deal with Ogg and Ogg tracks, including Ogg Kate. He/she will also get some insight into Firefox development. He/she will work with the developer of Ogg Kate and the video accessibility expert of Xiph, as well as having access to the whole Xiph community including the core developer of Ogg support in Firefox.

The project is adaptable to the qualifications of the student - it may consist in simply implementing a tool-chain for handling srt through OggKate, or it may go much further and include richer forms or time-aligned text such as audio annotations, Karaoke, ticker text, clickable text etc.

==== Mentors ====

* Silvia Pfeiffer (nessy / ginger)
* ogg.k.ogg.k

=== OpenMAX IL components for Ogg codecs ===

OpenMAX is a set of low-level C APIs for media codecs. It is specified by the Khronos Group (who also co-ordinate standards like OpenGL and OpenAL) and is used by many mobile devices, in platforms like [http://www.maemo.org/ Maemo] and [http://source.android.com/ Android]. As we'd like to encourage the use of free codecs on mobile and embedded devices, we want to develop a set of components using our codec libraries.

==== Project goals ====

This project would implement free codec support for the lowest of the three OpenMAX layers, OpenMAX IL (Integration Layer). This is an interface to multimedia codecs implemented in hardware or software. It does not provide any interfaces for synchronized capture or playback of video and audio -- typically this is handled by higher OpenMAX layers, or by a framework like GStreamer.

Developing software OpenMAX IL components will allow application developers to implement Ogg support ahead of hardware support. It would also give hardware manufacturers a set of specific, well-defined goals for implementing Ogg support, with the understanding that the hardware components, when shipped with these software control APIs, will work in a variety of open source applications with minimal modifications.

==== Implementation ====

Your project proposal should cover a reasonable portion of these steps:

* Implement generic Ogg mux/demux components (instead of single Ogg Vorbis component)
* Implement IL components for each codec (Theora, Dirac, Speex, CELT, FLAC)
* Implement GStreamer OpenMAX plugins for each codec

For details, including the motivation for this project and links to related projects, see
[http://blog.kfish.org/2009/02/is-openmax-important-for-free-software.html Is OpenMAX important for Free Software?]

==== Mentors ====

* Conrad Parker (kfish)

=== XSPF-related projects ===

==== XSPF import and export for Songbird ====

===== Problem/Intro =====
* Songbird cannot read XSPF playlists
* Songbird cannot write XSPF playlists

===== Solution/Task =====
* Extend the development line of Songbird by XSPF read and write support.
* Read support should be able to tolerate most above-XML-level errors so users don't get frustrated with XSPF. That's the short version :-)
* Communication with upstream will be needed
* Solution should use whatever solution upstream is likely to accept as a patch. If you get them to accept a libxspf-based solution it's C++, otherwise probably JavaScript.

===== Mentors =====
* Sebastian Pipping (sping)

==== Python library / Online validator refactoring ====

===== Problem/Intro =====
* The [http://validator.xspf.org/ Online XSPF Validator]'s [https://trac.xiph.org/browser/websites/validator.xspf.org code] (Python >=2.4) is a procedural spaghetti mix of logic and presentation.
* There is no Python XSPF library around.

===== Solution/Task =====
* Refactor the current validator code and separate it into a OOP XSPF reading library/API
* Adapt the validator to use former library
* Separate presentation and logic in validator code possibly involving a popular light-wight LGPLv3-compatible Python framework of your choice

===== Mentors =====
* Sebastian Pipping (sping)

=== CELT-related projects ===

==== Conference bridge using CELT ====

When a conference takes place, the voice from all participants is often decoded, mixed together, and re-encoded. The goal of this project is to do better. We would like to have only partial decoding and re-encoding of CELT and reuse as much as possible from the already-encoded streams. This not only decreases the CPU load but also improves quality. The project is specific to the [http://www.celt-codec.org CELT] codec, and during the course of the project, the student will learn the internals of the CELT codec.

==== Reference SIP client for CELT ====

The RTP profile for CELT is currently being written and to ensure that SIP clients with CELT support are really compliant, we would need a reference client that is 100% compliant with the RTP profile. This would provide:
* A reference to test for compatibility
* Some reference C code to copy directly

==See Also==
*[[Summer of Code 2008]]
*[[Summer of Code 2007]]
*[[Summer of Code 2006]]

Summer of Code 2009

2009-03-22T13:15:41Z

Conrad: /* OpenMAX IL components for Ogg codecs */ add me to mentors

This is our ideas page for [http://code.google.com/soc/ Google Summer of Code 2009] projects with [http://xiph.org Xiph.org] and [http://annodex.org/ Annodex]. The two projects participate jointly this year under Xiph's name.

'''Students''' please use the template at [[Summer of Code Applications]] when applying for a GSoC position.

'''Mentors''' please visit [[Summer of Code Mentoring]] and help us prepare our application as a mentoring organization.

== General Ideas ==

=== Codecs ===

* OpenMAX IL components for Ogg codecs
* Get skeleton patches upstream so players stop choking on it.
* Portable listening application for codec MOS/MUSHRA comparisons (Win32, MacOS, Linux; FF3.1 web application?).

=== Web Video ===

* Proof of concept liboggplay-based media patch for Google's Chrome browser.
* Metavid improvements
* Kate to HTML & CSS overlay library in javascript.
* Firefox extension to record locally and stream to icecast.
* Firefox extension to support RTP for conferencing.
** also consider applying [https://wiki.mozilla.org/Community:SummerOfCode09#Firefox under Mozilla SOC org].
* mod_duration apache module to generate X-Content-Duration headers for Ogg files. ''(We should get people to use '''oggz_chop''' instead ... oggz_chop provides this functionality and more, is already relatively lightweight.)'' Perhaps this project could be more focused on packaging oggz_chop for other web servers like lightpd and maybe a fastCGI version and or maybe push for an mod_ogg to be adopted upstream in apache to improve distribution.

== Detailed Project Descriptions ==

These ideas were suggested by various members of the developer community as projects that would be beneficial and which we feel we can mentor. Students should feel free to select one of these, develop a variation, or propose their own ideas. Here, ideally.

=== Proof of Concept liboggplay (html5 video) support in Chromium Browser ===

This project would focus on integrating support for liboggplay into chrome. This project would only need to be a proof of concept with the end result being some frames decoded in the browser. We have some direct contacts with people on the Chromium project in Google, but would expect the student mostly to work through the Xiph on Chromium online communities.

[http://code.google.com/chromium/ Chromium Home Page]

=== Metavid related projects ===

see [http://metavid.org/wiki/Summer_of_Code_2009 full page on metavid.org]
* Improve transcript import / export system:
** Wiki to SRT
** SRT to Wiki
** CMML to Wiki
** Extend oggz_chop or other tool for exporting transcript encapsulated in the ogg file.

=== Javascript Library for Subtitles, Captions and other time-aligned text ===

The main focus of the project is on enabling video accessibility for Ogg in Firefox.

==== Problem / Intro ====

Captions, subtitles and other categories of time-aligned text are starting to become relevant to HTML5. In Ogg, we currently encapsulate such data in OggKate and can use SRT or Kate as input formats. Display of OggKate is currently supported in VLC and there are patches for various other media players. We now want to enable Web browsers to also deal with these time-aligned text tracks in those Web Browsers that support the HTML5 video tag.

==== Solution / Task ====

There is a proof of concept patch for Firefox 3.1 (now called 3.5) and liboggplay through which Firefox is capable of decoding Ogg Kate tracks and either overlay them onto the video, or handing the raw text to the browser (eg, for text to speech). However, there is no display of OggKate in Firefox 3.5 using HTML5. This can be fixed through the creation of a javascript library that can deal with Kate output and convert it to HTML and CSS. Example libraries exists for displaying SRT for HTML5 video, but they will need to be extended to Kate in this project.

This project includes the creation of example files for different types of time-aligned text. These are then encapsulated into Ogg through Kate encoding. Firefox 3.5 with the applied OggKate patch can decode these files and hand the textual data to the Web browser. It will be necessary to extend liboggplay to pass non textual Kate data (eg, styling, etc) to the browser, as currently the only two ways of dealing with a Kate track is to render it, or pass raw text, ignoring extra styling information. This could be part of the project, or done before the GSoC projects begins. The browser receives the text and styling information, and a javascript library implemented by the student will take care of the display. This will include an implementation of default display mechanisms for the different types of time-aligned text that we decide to deal with.

==== Requirements ====

The project requires a student with experience in javascript development, HTML and CSS, but also with some understanding of C for liboggplay and libkate, and of C++ for Firefox. The student will learn how to deal with Ogg and Ogg tracks, including Ogg Kate. He/she will also get some insight into Firefox development. He/she will work with the developer of Ogg Kate and the video accessibility expert of Xiph, as well as having access to the whole Xiph community including the core developer of Ogg support in Firefox.

The project is adaptable to the qualifications of the student - it may consist in simply implementing a tool-chain for handling srt through OggKate, or it may go much further and include richer forms or time-aligned text such as audio annotations, Karaoke, ticker text, clickable text etc.

==== Mentors ====

* Silvia Pfeiffer (nessy / ginger)
* ogg.k.ogg.k

=== OpenMAX IL components for Ogg codecs ===

OpenMAX is a set of low-level C APIs for media codecs. It is used by many mobile devices, in platforms like [http://www.maemo.org/ Maemo] and [http://source.android.com/ Android]. As we'd like to encourage the use of free codecs on mobile and embedded devices, we want to develop a set of components using our codec libraries.

For details, including the motivation for this project and links to related projects, see
[http://blog.kfish.org/2009/02/is-openmax-important-for-free-software.html Is OpenMAX important for Free Software?]

==== Mentors ====

* Conrad Parker (kfish)

=== XSPF-related projects ===

==== XSPF import and export for Songbird ====

===== Problem/Intro =====
* Songbird cannot read XSPF playlists
* Songbird cannot write XSPF playlists

===== Solution/Task =====
* Extend the development line of Songbird by XSPF read and write support.
* Read support should be able to tolerate most above-XML-level errors so users don't get frustrated with XSPF. That's the short version :-)
* Communication with upstream will be needed
* Solution should use whatever solution upstream is likely to accept as a patch. If you get them to accept a libxspf-based solution it's C++, otherwise probably JavaScript.

===== Mentors =====
* Sebastian Pipping (sping)

==== Python library / Online validator refactoring ====

===== Problem/Intro =====
* The [http://validator.xspf.org/ Online XSPF Validator]'s [https://trac.xiph.org/browser/websites/validator.xspf.org code] (Python >=2.4) is a procedural spaghetti mix of logic and presentation.
* There is no Python XSPF library around.

===== Solution/Task =====
* Refactor the current validator code and separate it into a OOP XSPF reading library/API
* Adapt the validator to use former library
* Separate presentation and logic in validator code possibly involving a popular light-wight LGPLv3-compatible Python framework of your choice

===== Mentors =====
* Sebastian Pipping (sping)

=== CELT-related projects ===

==== Conference bridge using CELT ====

When a conference takes place, the voice from all participants is often decoded, mixed together, and re-encoded. The goal of this project is to do better. We would like to have only partial decoding and re-encoding of CELT and reuse as much as possible from the already-encoded streams. This not only decreases the CPU load but also improves quality. The project is specific to the [http://www.celt-codec.org CELT] codec, and during the course of the project, the student will learn the internals of the CELT codec.

==== Reference SIP client for CELT ====

The RTP profile for CELT is currently being written and to ensure that SIP clients with CELT support are really compliant, we would need a reference client that is 100% compliant with the RTP profile. This would provide:
* A reference to test for compatibility
* Some reference C code to copy directly

==See Also==
*[[Summer of Code 2008]]
*[[Summer of Code 2007]]
*[[Summer of Code 2006]]

Summer of Code 2009

2009-03-20T00:54:04Z

Conrad: group general ideas into codecs and web video