I've just started looking into using Ogg Vorbis for our streaming audio
needs. We're doing games for MacOS, OS X and Win32.
So far, after wading through the docs and sample code, I think I have a
reasonably solid idea of how it all works. Now some questions:
- currently my code is architected with a separate audio thread
responsible for decoding chunks of compressed audio on demand
("Demand"
== notification from the audio layer that it will need new data fairly
soon, e.g. using notification handles in DirectSound). Does this seem
reasonable?
- The prepackaged Win32 libs are compiled with "multithreaded DLLs"
instead of static libs. Is it fairly trivial to get the latest tarball
and recompile for static linkage of the CRT DLLs?
- Have people had much success getting Ogg Vorbis to compile and run
cleanly on MacOS 8/9 and MacOS X?
Thanks,
Brian
--- >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
'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
On 9/25/2001 at 12:46 PM Brian Hook wrote:>I've just started looking into using Ogg Vorbis for our streaming audio >needs. We're doing games for MacOS, OS X and Win32. > >So far, after wading through the docs and sample code, I think I have a >reasonably solid idea of how it all works. Now some questions: > >- currently my code is architected with a separate audio thread >responsible for decoding chunks of compressed audio on demand ("Demand" >== notification from the audio layer that it will need new data fairly >soon, e.g. using notification handles in DirectSound). Does this seem >reasonable?That's pretty much what I've seen done.> >- The prepackaged Win32 libs are compiled with "multithreaded DLLs" >instead of static libs. Is it fairly trivial to get the latest tarball >and recompile for static linkage of the CRT DLLs?You can try it, but I've found that the debug version of that code will crash, unless that code is compiled for, and linked with, the DLL version of the runtime. Also it appears that certain routines are missing from the static debug runtime, for example "strchr". This was with MSVC, v6 sp5 The release versions of those static libaraies are configured for static linking of the runtime and appear to work. --- >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 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2001-09-25 at 21:46:00 Brian Hook wrote: BH> - The prepackaged Win32 libs are compiled with "multithreaded DLLs" BH> instead of static libs. Is it fairly trivial to get the latest tarball BH> and recompile for static linkage of the CRT DLLs? Should be no problem, just select the appropriate option in the Code Generation dialog of VC (I'm assuming that you're using that), and rebuild. You can use both the single- and multithreading static CRT. BH> - Have people had much success getting Ogg Vorbis to compile and run BH> cleanly on MacOS 8/9 and MacOS X? I've got a decoder compiled and running successfully on MacOS 9, using CodeWarrior 6. However, I"m still having some noise artefact problems: the Ogg files don't seem to decompress "cleanly" on MacOS. Still investigating... I don't have MacOS 8 around, but I don't think there will be much problems getting it compiled on that version. I haven't tried MacOS X yet, but since CW6 runs almost exactly the same on MacOS X, and the Vorbis libraries themselves don't really use any OS-specific stuff, it shouldn't give much problems. Cheers, - -- Dimitry Andric <dim@xs4all.nl> PGP Key: http://www.xs4all.nl/~dim/dim.asc Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3 Lbh ner abj va ivbyngvba bs gur QZPN -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBO7DZv7BeowouIJajEQK+sQCfSiVRGPq0L7VoL+zqfZJclzZ+kqAAoPUe YN9SszMGKH+4VGFySeCoXEC8 =2kJv -----END PGP SIGNATURE----- --- >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 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
At 12:46 PM 9/25/01 -0700, you wrote:>I've just started looking into using Ogg Vorbis for our streaming audio >needs. We're doing games for MacOS, OS X and Win32. > >So far, after wading through the docs and sample code, I think I have a >reasonably solid idea of how it all works. Now some questions: > >- currently my code is architected with a separate audio thread >responsible for decoding chunks of compressed audio on demand ("Demand" >== notification from the audio layer that it will need new data fairly >soon, e.g. using notification handles in DirectSound). Does this seem >reasonable?Yes. In terms of how and when you feed data to the vorbis library and get decoded audio back, the API is pretty flexible. Shouldn't be a problem.> >- The prepackaged Win32 libs are compiled with "multithreaded DLLs" >instead of static libs. Is it fairly trivial to get the latest tarball >and recompile for static linkage of the CRT DLLs?Chris Wolf has improved the win32 build stuff recently, so this should be even easier now. Shouldn't be a problem - I always used to use full static linking where possible.> >- Have people had much success getting Ogg Vorbis to compile and run >cleanly on MacOS 8/9 and MacOS X?I don't personally use them, but I know people regularly compile everything on these platforms. Some of the examples may be a bit harder, but the core libraries don't have any problems at all. Michael --- >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 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.