Re: Problems aith M-Audio Audioohile Firewire
Re: Problems aith M-Audio Audioohile Firewire
- Subject: Re: Problems aith M-Audio Audioohile Firewire
- From: "Paul Sanders" <email@hidden>
- Date: Tue, 23 Feb 2010 21:15:47 -0000
Thanks Jeff. As you say, there's not a lot to go
on. I may just let it ride, in fact. The customer affected can route
through Sound Flower so that will provide a workaround for him and anyone else
affected. We haven't heard of any other audio problems so I'm hoping that
it's just this one, mutant device.
Just for info, the strange behaviour reported
is:
1. Calling (I think) AudioStreamSetProperty
(... AudioStreamSetPropertyAudioStreamSetProperty ...) seems to upset it.
Up to that point, MTCoreAudio plays correctly through the device. After
that, nothing plays (i.e. there is no audio output).
2. When the device is (again, I think) started (by
us or by MTCoreAudio) , iTunes stops playing through it (and reverts to the
internal speakers). When the device is stopped, iTunes resumes playing
through the Audiophile.
But don't read too much into this. There's some
guesswork going on here and I'm only writing it up in case any else
recognises the symptoms and has also been scratching their head.
Ciao!
Paul Sanders
----- Original Message -----
Sent: Tuesday, February 23, 2010 8:21 PM
Subject: Re: Problems aith M-Audio Audioohile
Firewire
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