annotate src/libvorbis-1.3.3/doc/libvorbis/vorbis_comment.html @ 1:05aa0afa9217

Bring in flac, ogg, vorbis
author Chris Cannam
date Tue, 19 Mar 2013 17:37:49 +0000
parents
children
rev   line source
Chris@1 1 <html>
Chris@1 2
Chris@1 3 <head>
Chris@1 4 <title>libvorbis - datatype - vorbis_comment</title>
Chris@1 5 <link rel=stylesheet href="style.css" type="text/css">
Chris@1 6 </head>
Chris@1 7
Chris@1 8 <body bgcolor=white text=black link="#5555ff" alink="#5555ff" vlink="#5555ff">
Chris@1 9 <table border=0 width=100%>
Chris@1 10 <tr>
Chris@1 11 <td><p class=tiny>libvorbis documentation</p></td>
Chris@1 12 <td align=right><p class=tiny>libvorbis version 1.3.2 - 20101101</p></td>
Chris@1 13 </tr>
Chris@1 14 </table>
Chris@1 15
Chris@1 16 <h1>vorbis_comment</h1>
Chris@1 17
Chris@1 18 <p><i>declared in "vorbis/codec.h"</i></p>
Chris@1 19
Chris@1 20 <p>
Chris@1 21 The vorbis_comment structure defines an Ogg Vorbis comment.
Chris@1 22 <p>
Chris@1 23 Only the fields the program needs must be defined. If a field isn't
Chris@1 24 defined by the application, it will either be blank (if it's a string value)
Chris@1 25 or set to some reasonable default (usually 0).
Chris@1 26 <p>
Chris@1 27 <i>Note:</i> When encoding, while it <i>is</i> supported to modify a
Chris@1 28 vorbis_comment structure directly, be sure to read the notes on the
Chris@1 29 <a href="vorbis_comment_init.html">vorbis_comment_init</a> and
Chris@1 30 <a href="vorbis_comment_clear.html">vorbis_comment_clear</a> pages for
Chris@1 31 considerations on memory allocation and freeing before you do so. Rule of
Chris@1 32 thumb: call vorbis_comment_init, then <i>either</i> do all allocation,
Chris@1 33 freeing, and modification yourself and <i>do not</i> call
Chris@1 34 vorbis_comment_clear, <i>or</i> do all modification using libvorbis
Chris@1 35 functions and <i>do</i> call vorbis_comment_clear.
Chris@1 36 <p>
Chris@1 37
Chris@1 38 <table border=0 width=100% color=black cellspacing=0 cellpadding=7>
Chris@1 39 <tr bgcolor=#cccccc>
Chris@1 40 <td>
Chris@1 41 <pre><b>typedef struct vorbis_comment{
Chris@1 42 /* unlimited user comment fields. */
Chris@1 43 char **user_comments;
Chris@1 44 int *comment_lengths;
Chris@1 45 int comments;
Chris@1 46 char *vendor;
Chris@1 47
Chris@1 48 } vorbis_comment;</b></pre>
Chris@1 49 </td>
Chris@1 50 </tr>
Chris@1 51 </table>
Chris@1 52
Chris@1 53 <h3>Parameters</h3>
Chris@1 54 <dl>
Chris@1 55 <dt><i>user_comments</i></dt>
Chris@1 56 <dd>Unlimited user comment array. The individual strings in the array are 8 bit clean, by the Vorbis specification, and as such the <tt>comment_lengths</tt> array should be consulted to determine string length. For convenience, each string is also NULL-terminated by the decode library (although Vorbis comments are not NULL terminated within the bitstream itself).</dd>
Chris@1 57 <dt><i>comment_lengths</i></dt>
Chris@1 58 <dd>An int array that stores the length of each comment string</dd>
Chris@1 59 <dt><i>comments</i></dt>
Chris@1 60 <dd>Int signifying number of user comments in user_comments field.</dd>
Chris@1 61 <dt><i>vendor</i></dt>
Chris@1 62 <dd>Information about the Vorbis implementation that encoded the file. Stored in a standard C 0-terminated string. Libvorbis will fill this in itself when encoding a comment packet from this structure; when decoding, this contains the vendor string that was in the comment packet.</dd>
Chris@1 63 </dl>
Chris@1 64
Chris@1 65
Chris@1 66 <br><br>
Chris@1 67 <hr noshade>
Chris@1 68 <table border=0 width=100%>
Chris@1 69 <tr valign=top>
Chris@1 70 <td><p class=tiny>copyright &copy; 2000-2010 Xiph.Org</p></td>
Chris@1 71 <td align=right><p class=tiny><a href="http://www.xiph.org/ogg/vorbis/">Ogg Vorbis</a></p></td>
Chris@1 72 </tr><tr>
Chris@1 73 <td><p class=tiny>libvorbis documentation</p></td>
Chris@1 74 <td align=right><p class=tiny>libvorbis version 1.3.2 - 20101101</p></td>
Chris@1 75 </tr>
Chris@1 76 </table>
Chris@1 77
Chris@1 78 </body>
Chris@1 79
Chris@1 80 </html>