search for: o3gam

Displaying 5 results from an estimated 5 matches for "o3gam".

Did you mean: 03am
2001 Oct 16
4
Possible channel coupling bug in encoder
I'm not sure that this is not my fault, but here it goes: I'm trying to encode a 22 kHz Mono stream. I started with the encoder example and made it take dynamic channels etc. This is how I init it: vorbis_info_init(&VorbisInfo); vorbis_encode_init(&VorbisInfo, 1, 22050, -1, 128000, -1); then I get a crash in: _vp_quantize_couple(vorbis_look_psy * 0x01e6a6ec,
2001 Nov 22
14
Small vorbis files with vorbisfile
I think I have bumped into the small file error, or I''m doing something stupid. The files are short audio effects for a game (embedded in our own data format). Sample info: Vorbis packets: 1 (4 kb) Samples: 28672 Samplerate: 22 kHz Channels: 2 This is what I''m doing when I want to get a number of bytes from the stream: The problem is that ov_pcm_tell always returns 0. And so
2002 Jan 13
1
Vorbis memory consumption
I have been researching using vorbis for streaming (music and sound effects) in our xbox game. As it turns out every stream takes about 300 kb when decoding from it. This is pretty ok, if I only had to deal with one stream. Unfortunately I have to be able to handle more streams simultaneously, and 400 kb would be ideal for all stream to take as a maximum. Is it possible to share some of the
2001 Oct 16
7
Performance tests
I did some testing of vorbis codec (Winamp plugin) on a Pentium 166 MMX, and found that the performance is pretty good. I got 3 % cpu utisization if I turned dithering off, and 5 % otherwise. This was with a 138 kbit song. It's pretty long to mp3 performance that was 0 to 1 % on that machine for a 128 kbit song. Also vorbis seems to have a larger working set, because if I play two songs at
2001 Oct 10
5
#include scheme in vorbis project
I'm trying to implement vorbis into our game engine as a substitute to mp3 and wma encoding. And I have some questions/suggestions in how #includes are done in vorbis. Right now ogg and vorbis stuff relies on ogg and vorbis include paths being in global (or local) include path environment. This could easily be avoided by using relative includes in vorbis: #include