does the AudioConverter implementation differ between tiger and leopard?
does the AudioConverter implementation differ between tiger and leopard?
- Subject: does the AudioConverter implementation differ between tiger and leopard?
- From: "Saad Nader" <email@hidden>
- Date: Tue, 24 Feb 2009 16:38:31 -0800
- Delivered-to: email@hidden
- Delivered-to: email@hidden
- Thread-index: AcmW4WHmT/+zbvNxRIWRopQ0ojcPnQ==
- Thread-topic: does the AudioConverter implementation differ between tiger and leopard?
I’ve been trying to debug a problem with my conversion code that works on tiger, but completely fails on leopard. My problem is that when I’m using tiger, the outOutputData has the correct mDataByteSize. When using almost the exact same code on leopard (given the changes need to get rid of obsolete functions), it fills it in with a smaller value that doesn’t reflect the value from AudioStreamBasicDescription. Am I missing something here? I’ve debugged with everything in mind and this is where the problem narrows down to. I’m going to continue to debug but if anyone has ran into this issue when writing code for AudioDevices
Thanks,
------------------
Saad
Nader
Middlware
Engineer
Powered
By Gamespy
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden