similar to: small mistake in docs

I've been experimenting with the ideas of Replay Gain[1] and find that ogg123 doesn't have a way of specifying the scaling applied to replayed samples (like -f in mpg123). Looking at libvorbisfile, I see no function exactly matching this possibly desirable behaviour. ov_read() scales by either 128 (byte output) or 32768 (word output), but there's nothing in between. ov_read_float()

Hello, Am I missing something? float** pcm_channels; int bitstream; int where = ov_pcm_tell(&vf); -> The Result is "0"; ov_read_float(&vf, &pcm_channels, 1, &bitstream); -> pcm_channels[0][0] is "0.000338580" ov_pcm_seek(&vf, 0); char* buffer = new char[2]; ov_read(&vf, buffer, sizeof(buffer), 0, 2, 1, &bitstream); short temp =

Greetings, I'm having some sort of problem using ov_read_float(). Everything looks good to me, but I'm trashing memory somehow, so clearly I'm screwing something up. What confuses me is why it takes a ***float for the buffer. I call it like so: float **buffer bytes_read = ov_read_float(&vf, &buffer, 0) memcpy (b, *buffer, 0); This compiles fine, but after a few reads,

Is there any particular reason why ov_read() packs floats to integer PCM inline, rather than being implemented in terms of ov_read_float() and a separate packing fucntion? There are obviously many advantages doing audio manipulation on the floats before packing, but right now you have to reinvent the packing stage yourself - in a replaygain backend that I'm working on, I ended up copying

Ok here is the breakdown. I am trying to impliment streaming into our game using openAL and ogg-vorbis. In the non-streaming function when I call ov_read on the file I should be streaming the buffer gets filled with the correct data. However, when I run ov_read on the same OggVorbis_File when I read the buffer gets filled with 0's. The buffer has not been zero'd and starts filled

Hello. I noticed that when reading data with ov_read_float(), you can get values outside [-1..1] when the stream is encoded at lower quality, but with higher quality, the values trim down to inside [-1..1]. Looking at the plot from -q10, the data from ov_read_float seems clipped. I've made some plots of encoding the start of Rammsteins Feuer from the xXx soundtrack (it's a pretty loud

Hello all. I'm new to this list. I'm also new to coding with libvorbis and things, so please bear with me. :) I've been having trouble with libvorbisfile. My use of it is fairly simple, but when I try to ov_clear the vorbis file, it segfaults. I can attach or otherwise make availible some demo source code, but for now I'll just pull out relevant lines: //BEGIN PSEUDO CODE

Hello, hope you're fine. And hopefully someone can help me. I wrote a short demonstration to show you my problem (see below). I'm asking always for 64 samples. When "ov_read_float()" is finished, I want to seek back to sample 1, and ask immediately for the next 64 samples. But when I run this small app, I get an totally high CPU load. Is there a way to it speed up? Or do I

Hi, I have this code to decode ogg data: unsigned long PSS_OggStream::DecodeOggVorbis(OggVorbis_File *psOggVorbisFile, char *pDecodeBuffer, unsigned long ulBufferSize, unsigned long ulChannels) { int current_section; long lDecodeSize; unsigned long ulSamples; short *pSamples; unsigned long ulBytesDone = 0; while (true) { #ifdef WIN32 lDecodeSize = ov_read(psOggVorbisFile,

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 guys, I'm working doing the 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

Hi! I solved the problem using ov_read_float instead ov_read. Still do not know why ov_read returned garbage, but ov_read_float works fine! Thanks! El 17 de julio de 2011 10:41, Juan Miguel Mart?n Mu?oz <jmcubo at gmail.com>escribi?: > Hi, thanks for your replies! > > ogg.k, I'm sure MACOSX is defined. When I'm debugging line by line the > program runs into ov_read.

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying

Here's a patch to vorbisfile.c in libvorbis that splits the float to integer pcm packing out of ov_read into it's own function. The good stuff: - ov_pack_pcm can be used by folks who decode to float pcm with ov_read_float to do various sound manipulations (eg, preamp, fades, replaygain). No more need to roll your own, which will really begin to pay off when 24 bit output gets

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

OK, I've been developing a small class that I can use in virtually any application to load and decode OGG files. Everything works fine until it reaches the line with the call to ov_open, then the application freezes and has to be killed. This is a single-threaded Win32 app. Below is both the structure that gets passed around, and my entire OGG class. Maybe one of you can figure this out.

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 have been working on a game for a while now and noticed that using your library to stream music created a graphical problem while the screen would scroll. (certain tiles would flicker to be more specific). I found that if I don't play music this problem doesn't occur. Another developer suggested that if I can lower the priority (thread priority) of the music this could fix the problem.

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