search for: disciplezero

I noticed that, when decoding an ogg vorbis file that was encoded with the xiph library, that the comment header and setup header are encoded on one page. Okay, the vorbis documentation says you can do this, no problem. My question is, the lacing values seem to indicate where the packet boundaries for the two of these are, is this required, or is this just a hint? Further, I'm seeing

Hey guys, I've finished my work on reading vorbis files (straight reading at either PCM sample lengths, or time lengths). However, I've run across a question. When you call vorbis_synthesis_read, I assume that increments the internal ptrs so you don't get the same data twice. The question is, what happens if you call vorbis_synthesis and vorbis_synthesis_blockin? Does the next call

Hey guys, Maybe its cause I'm using older tools, but I've noticed a minor problem building the ogg libraries on a mac. I'm using Codewarrior 8. In os_types.h on line 60, it says "#include <sys/types.h>" where it should be "#include <types.h>" I'm guessing this isn't an issue for all compilers, just codewarrior. Possibly only codewarrior 8

It seems to me that running ogg_sync_pageout doesn't automatically advance the page. This is good if you haven't worked with the given page, makes coding somewhat easier. However, when does a page advance. Is it after a call to ogg_stream_pagein? On a side note, I need to do seeking on top of libvorbis, I'd love to use vorbisfile but sadly I can't. Is there a reasonable way to

I have a couple of questions with respect to "vorbisfile_example.c" in the ov sdk. 1) Near the end, there is a comment that says "we don't bother dealing with sample rate changes, etc, but you'll have to." I assume the author is regarding to different sample rates as a whole, not dynamic sample rates. Am I correct in that assumption? 2) That etc