Re: Problems aith M-Audio Audioohile Firewire
Re: Problems aith M-Audio Audioohile Firewire
- Subject: Re: Problems aith M-Audio Audioohile Firewire
- From: Jeff Moore <email@hidden>
- Date: Tue, 23 Feb 2010 12:21:54 -0800
On Feb 23, 2010, at 12:09 PM, Paul Sanders wrote:
> Can someone please tell me if there is any functional difference between the AudioObject API's and the older, now deprecated API's like AudioDeviceGetProperty?
The AudioDevice property methods are implemented under the hood in terms of the AudioObject property methods. Mostly, the differences between the two styles of APIs are that the AudioObject APIs allow for more possibilities for addressing and add the qualifier argument.
> We have some strange behaviour in the field with the M-Audio Audiophile firewire device and I'm wondering if the fact that we're still using the older API's might be responsible.
I'm not saying that it can't happen, but I've never heard of a problem that could be traced to a difference in API usage.
> I don't have a device here to test with, unfortunately, but MTCoreAudio's AudioMonitor app displays exactly the same problems as ours, so I don't think it's a bug in my own code. The machine in question is a PowerMac G5 running (I believe) Leopard, if that makes any difference.
It's hard to diagnose a problem with what you've provided so far.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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