search for: ov_

...and divides by 4. Q2. How does vcut's get_blocksize() work? ---- The spec says that the stream starts at an offset greater than zero if there are less samples in the first page than the granulepos of the first page. For on-disk streams that have this characteristic, how will the vorbisfile ov_*_seek() and ov_*_tell() functions behave? Will they act as though the file begins at offset 0, or will they expose the >0 starting offset? Q3. How does vorbisfile deal with >0 offsets? Thanks for all the answers you have already provided. Josh --- >8 ---- List archives: http://www.xi...

Hi, I'm experiencing a serious problem when trying to replace libvorbis with tremor (from svn): premitting that I don't want to use the ov_* functions, calling vorbis_synthesis_headerin() on the 3 initial packets works with libvorbis but immediately fails with tremor. At first sight it seems that the function in tremor either receives a leading \n before every header (that shouldn't be there, IIUC), or that it should be there b...

...y OS's. The question is how to do this Correctly. *** It is dangerous to replace system functions *** If the authors are resistant to putting in configure tests for the getopt_long() function, it would be *MUCH* better to prefix all the symbols in getopt.c, getopt.h, and getopt1.c with "ov_" to prevent collisions with any potential OS versions of the same functions. This would both obviate the need for any configure tests, and would guarantee that there were safe versions of the functions for ogg123, oggenc, and vorbiscomment to use. Also, <ov_getopt.h> would always be fo...

I passed a valid FILE* (from fopen() with "rb") and the address of an OggVorbis_File struct, but an access violation occured when ov_open is called. I have enabled the Multithreaded, but it still doesn't fix the problem. I look at the vorbis_comment.exe source and I see vcedit_open() function and other vcedit_*() functions everywhere. I am assuming that there is known issue with VC and ov_open that's why vorbis_comment i...

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *