Matthias Fischaleck
2004-Apr-05 16:29 UTC
[vorbis-dev] Massive Problems on Windows XP pro with Libvorbis[Vorbisfile]1.0.1
Hey there I'm using CodeWarrior8 for development on the windows platform and have been trying for some time now to add .ogg support to my engine project. First i had the problem quite a lot had out there with a crashing/freezing call to ov_open which i solved by recompiling those libs against the single-threaded variant of the core libs using VC++ 6 But now i have another problem. now every call to ov_open or ov_test or whatever returns OV_EREAD, no matter which file i use. I am perfectly positive on thos .ogg files beeing correct as several tools can load and play them back alright. Since the given explanation string "A read from media returned an error" isn't really self-explanatory i was hoping that somebody out there could help me out. The only thing differing from standard samples using ov_open is that i use it in a OggFile-class that is derived 2 levels from the class that handles the fopen but has perfect access to the Handle... ths Fiesch --- >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.
Matthias Fischaleck
2004-Apr-05 16:31 UTC
[vorbis-dev] Massive Problems on Windows XP pro with Libvorbis[Vorbisfile]1.0.1
Hey there I'm using CodeWarrior8 for development on the windows platform and have been trying for some time now to add .ogg support to my engine project. First i had the problem quite a lot had out there with a crashing/freezing call to ov_open which i solved by recompiling those libs against the single-threaded variant of the core libs using VC++ 6 But now i have another problem. now every call to ov_open or ov_test or whatever returns OV_EREAD, no matter which file i use. I am perfectly positive on thos .ogg files beeing correct as several tools can load and play them back alright. Since the given explanation string "A read from media returned an error" isn't really self-explanatory i was hoping that somebody out there could help me out. The only thing differing from standard samples using ov_open is that i use it in a OggFile-class that is derived 2 levels from the class that handles the fopen but has perfect access to the Handle... ths Fiesch <p>--- >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.
Ralph Giles
2004-Apr-05 16:58 UTC
[vorbis-dev] Massive Problems on Windows XP pro with Libvorbis[Vorbisfile]1.0.1
On Tue, Apr 06, 2004 at 01:31:53AM +0200, Matthias Fischaleck wrote:> But now i have another problem. > now every call to ov_open or ov_test or whatever returns OV_EREAD, > no matter which file i use. > [...] > > The only thing differing from standard samples using ov_open is that i > use it > in a OggFile-class that is derived 2 levels from the class that handles > the fopen > but has perfect access to the Handle...Didn't follow this last part, but OV_EREAD is returned whenever there's a problem getting data from the next level down, so it's either another build issue (possibly with libogg) or an ioerror. Have you tried just compiling the ogg and vorbis source as part of your project in CW? This seems to be the path of least resistance on win32. Another common error is messing with the FILE* after you hand it to ov_open(). Make sure you're not doing that; the library owns it after that point and will take care of closing it. FWIW, -r --- >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.