similar to: Why the two decoder formats?

Hello Hope you don't mind another newbie's question. Further to GIE's email about problems compiling decoder_example.c example (MS VC 7) using debug static ogg/vorbis libs, we'd appreciate any help getting the example files to compile on MS VC 6. The zip files we have downloaded are: libao-0.8.2.zip libogg-1.0rc3.zip libvorbis-1.0rc3.zip vorbis-sdk-1.0rc3.zip

Hello, I've been looking to the libvorbisfile and got into troubles when trying to use it: I need to compile it on a PalmOS and the libvorbisfile must be compiled in ARM whereas calling code is in 68K. This implies that the interface ov_open_callback is not usable because the OggVorbis_File *vf must point to something in the target architecture (ARM) whereas the caller cannot do that. As

I've fixed a heck of a lot of stuff in the time frame of just over ten minutes. And you all care... right. I actually ran Vorbize, and discovered some stupid bugs (e.g., segfault???). Fixed. Both Vorbize and Ogg123 should now speak fluently in Monty's comment-eese. I'll be working on getting both to implement all the comment tags; I'm seriously considering dropping all comment

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm writing a simple application to decompress a set of Ogg files to raw PCM format, using vorbisfile, because that is the simplest way of doing it. These Ogg files are sounds for a game, and thus sometimes very short (about .25 s). However, vorbisfile has severe problems with Ogg files that are smaller than the CHUNKSIZE which is #defined

Hi, I put together a small a Visual C++ 6.0 project that uses the code from vorbisfile_example.c. I open an ogg file in binary mode and when ov_open gets called, it always fails. I then put together another project and compiled vorbisfile so I could see where the error was occuring. It is happening in _fetch_headers when it calls ogg_stream_packetout. The return values is -1, which means there

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

I am wondering if buffer size for my decoding to pcm can be predicted dependably as follows. So far, the one problem I have had is when I have played a file of only about 5k. The buffer was a little less than 10% too small. I "solved" that by padding the result with an extra 20 percent. However, I have been told that I should be able to rely on the value of ov_pcm_total. char*

Hello, I am currently developing a ogg vorbis decoding module for use in winlame (a LAME frontend), and I have some questions: To do a decoder I used most code in decoder_example.c, but I think there is something missing. I would be glad if someone could look at this code: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/winlame/winlame/source/winlame/wlOggVorbisDecoderModule.cpp and

Eddie, I have been reviewing vorbis list postings, because I have been spinning my wheels for a week, trying to make a simple insertion of ogg vorbis decoding (vorbisfile) in the audio class of my MFC/C++ program. I just read your thread from April 2004. Question: Do you have anything you could send me, since I assume you succeeded in getting results? And/or could you take a look at what I

Hello, All. I am making an Ogg Vorbis decoder based on Tremor. The Vorbisfile library provides a high-level API which enables us to seek in the file, but it needs to declare a pointer to OggVorbis_File structure. Because I am supposed not to use file, so I can't use the ov_pcm_seek() or ov_raw_seek() functions to seek in the file. For decoding an Ogg Vorbis file, I first put it in

Tony, I committed a new version of the XMMS plugin. This is a cleaned up and debugged version of the code you sent me with the conversion to the vorbisfile app library. At this point, it properly handles chaining (try concatenating two vorbis files with different serial numbers to see it work). The code also got alot smaller as alot of the hairy stuff is now done by vorbisfile.a. In the

I am having one frustrating time trying to decipher why ov_read is failing in my MFC/C++ application, and I see in Google results that others have had difficulty as well. These google discussions generally involve libraries, dll's and linking options, as though there are perhaps some basic incompatibilities between ogg vorbis and win32 and/or MFC/C++. Very confusing. If I pass fopen a

Hi, I have looked through the documentation available from the downloads and the web and haven't yet come across a block diagram which shows exactly how the process of going from a .wav file to a .ogg file works. I suspect it is the same as the mp3 process (with a different psychoacoustic model). I found this document:

Following a few months of lurking on the list, and vainly trying to get vorbis to compile on os/2, I finally managed to get the nightly gzip from saturday to compile (fairly) cleanly, and so have finally been able to play with Vorbis on my OS of choice :) Using the EMX runtime system, and bash for OS/2 (along with a few ported GNU apps), both configure and make work fine (except for ogg123

I’m running into a problem with my application crashing when I make a call to the ov_time_seek() function. The call includes the OggVorbis_File and it is indeed seekable, as I first check that using the ov_seekable() function. Everytime, however I try to seek forward, the application dies with a core dump. I’m working with the example from the “VorbisFile Documentation” site. The application

I'm updating my vorbis rpm spec file, and when I try to do "make -C vorbis-tools ogg123", due to rpm's build environment, I get lots of: gcc ogg123.o -o ogg123 -lm ../lib/libvorbis.a ../lib/vorbisfile.a ../lib/vorbisfile.a(vorbisfile.o): In function `_get_prev_page': vorbisfile.o(.text+0x54): undefined reference to `ogg_sync_reset' vorbisfile.o(.text+0xa9): undefined

Well, I updated the player to work with the branch_postbeta2, but it contains some nasty kludges to the project files that probably shouldn't be finalized. I'm going to put it in a separate file (http://oscar.the-rileys.net/programming/vorbis_pb2.tar.gz) for now. Unfortunately, this release doesn't seem to fix the "tearing sound" problem. I think this might be related to

I've been trying to tackle the vorbis source. I ran across what I think is a missing dependency in the vorbis-tools directory. Since ogg123 and vorbize are staticly linked to libvorbis and vorbisfile, when those file change, the executables should be rebuilt. Below I've attached a patch. (I hope it works. I am sort of new to patch and diff.) BTW, I've been trying to find a good

There isn't a lot of guidance on how exactly to run the codec I compiled out of cvs just now, but I expected the following to work: cat test.wav | encoder_example | decoder_example But the decoder fails with: End of file before finding all Vorbis headers! Is this a bug? Or am I missing something fundamental? Should I attach the test.wav? -- Daniel --- >8 ---- List

There isn't a lot of guidance on how exactly to run the codec I compiled out of cvs just now, but I expected the following to work: cat test.wav | encoder_example | decoder_example But the decoder fails with: End of file before finding all Vorbis headers! Is this a bug? Or am I missing something fundamental? Should I attach the test.wav? -- Daniel --- >8 ---- List