search for: ov_com

...(stdin), _O_BINARY); _setmode (_fileno (stdout), _O_BINARY); #endif if (ov_open_callbacks (stdin, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) < 0) { fprintf (stderr, "Input does not appear to be an Ogg bitstream.\n"); exit (1); } { char** ptr = ov_comment (&vf, -1)->user_comments; vorbis_info* vi = ov_info (&vf, -1); while (*ptr) { fprintf (stderr, "%s\n", *ptr); ++ptr; } fprintf (stderr, "\nBitstream is %d channel, %ldHz\n", vi->channels, vi->...

...(stdin), _O_BINARY); _setmode (_fileno (stdout), _O_BINARY); #endif if (ov_open_callbacks (stdin, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) < 0) { fprintf (stderr, "Input does not appear to be an Ogg bitstream.\n"); exit (1); } { char** ptr = ov_comment (&vf, -1)->user_comments; vorbis_info* vi = ov_info (&vf, -1); while (*ptr) { fprintf (stderr, "%s\n", *ptr); ++ptr; } fprintf (stderr, "\nBitstream is %d channel, %ldHz\n", vi->channels, vi->...

...e Java->JNI->OggVorbis thing. As a test to get me going, I've just written a quick routine that dumps info about the file test.ogg in the current directory. The problem arises when I call ov_clear. I get a segfault everytime. Note that I am *not* doing any decoding (ov_read) at all, just ov_comment and ov_info. Should I only call ov_clear if I have called ov_read? If I comment out the ov_clear, everything works fine. This is good, as it means I'm on the right track and I at least *partially* know what I'm doing. :) Here's the code [try and ignore all the Java required stuff]...

I've been working towards a mp3info like tool, OggInfo, which will surplant vorbiscomment in functionality, and also incorportate mp3info like featuers. Looking at existing vorbis api calls, i find: vorbis_comment_add() /* unsupervised string insertion */ vorbis_comment_add_tag() /* formated TAG=text insertion */ vorbis_comment_query() /* scans for matching tag (up to count duplicates) and

...t;> >> if (ov_open_callbacks (stdin, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) < 0) >> { >> fprintf (stderr, "Input does not appear to be an Ogg bitstream.\n"); >> exit (1); >> } >> >> { >> char** ptr = ov_comment (&vf, -1)->user_comments; >> vorbis_info* vi = ov_info (&vf, -1); >> >> while (*ptr) >> { >> fprintf (stderr, "%s\n", *ptr); >> ++ptr; >> } >> >> fprintf (stderr...

...(stdout), _O_BINARY); > #endif > > if (ov_open_callbacks (stdin, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) < 0) > { > fprintf (stderr, "Input does not appear to be an Ogg bitstream.\n"); > exit (1); > } > > { > char** ptr = ov_comment (&vf, -1)->user_comments; > vorbis_info* vi = ov_info (&vf, -1); > > while (*ptr) > { > fprintf (stderr, "%s\n", *ptr); > ++ptr; > } > > fprintf (stderr, "\nBitstream is %d channel, %...

I'm considering patching my copy of ogg123 to support vorbisgain tags. Is there any interest in folding this sort of patch into the main line ogg123? Has anyone done this already (or to another command line ogg player)? John --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

...Vorbis stream 1: Total data length: 4875041 bytes Playback length: 3m:21s Average bitrate: 193.160180 kbps Logical stream 1 ended Why is there a slight difference between the two values ? b) ov_bitrate interprets "link == -1" as "the entire bitstream" ov_comment interprets "link == -1" as "the current bitstream" why the different behaviour ? Is there a reason behind this ? c) am i correct in assuming that each logical bitstream in the phyiscal one can contain at most one COMMENT tag ? Thanks, Thomas <p> -- The Dave/Dina...

Why ov_open_callbacks(fd_, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) takes so long to open OGG file? The OGG file has just 210 MB. It takes a lot of time open the file. I am working on OGG audio recorder and player. Thanks in advance! With kind regards, Pavel

...t* trying to use ID3 tags, just pure Ogg Vorbis comments) Now I cannot figure out how to do the following: 1) I detect that the intended target file (foobar.ogg) already exists, open it, read any Ogg tags which might be inside the file, and save these for later use. This is easy using ov_open(), ov_comment(), etc. 2) I encode the file using the external oggenc.exe. Also easy. 3) I then want to add the saved tag values to the fresh file. I thought that I could just open the Ogg file, get a handle to the comments structure, and then use vorbis_comment_add_tag() for each saved tag. But the I canno...

...I just downloaded "SDK for MacOS9" and tried to compile the "vorbisfile_example.c" sample with CodeWarrior for Mac 8 on a Mac OS 9.2 machine. I included the libOgg and libVorbis libraries in my project, but the linker cannot file ov_clear(), ov_read(), ov_pcm_total(), ov_info(), ov_comment() and ov_open(). I looked at the Windows SDK and noticed that there are far more library files in that package, including a vorbisfile.lib. Is it possible that the MacOS9 SDK doesn't include a vorbisfile lib? Is this by design? Thanks, --jr <p>__________________________________ Do...

...09:50:38 2000 @@ -502,6 +502,10 @@ /* Throw the comments plus a few lines about the bitstream we're ** decoding */ + { + void next(int i) { eof = eos = 1; } + signal(SIGUSR1, next); + } while (!eof) { int i; vorbis_comment *vc = ov_comment(&vf, -1); @@ -581,6 +585,7 @@ } } } + signal(SIGUSR1, SIG_DFL); ov_clear(&vf); -=-=-- -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/ --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg pro...

...ostream.h> #include <vorbis/vorbisfile.h> int main() { FILE *fp; OggVorbis_File *ovFile; vorbis_comment *ovComment; // ovFile=malloc(sizeof(OggVorbis_File)); ovFile=new OggVorbis_File; fp=fopen("foo.ogg","rw"); ov_open(fp,ovFile,NULL,0); ovComment=ov_comment(ovFile,-1); if(ovComment->user_comments) { printf("has comments - %i\n",ovComment->comments); for(int i=0;i<ovComment->comments;i++) { cout << ovComment->user_comments[i] << endl; } // vorbis_comment_add...