Re: Changing Default Device and Sample Rate via Objective C
Re: Changing Default Device and Sample Rate via Objective C
- Subject: Re: Changing Default Device and Sample Rate via Objective C
- From: Paul Davis <email@hidden>
- Date: Mon, 01 Oct 2012 11:44:52 -0400
On Mon, Oct 1, 2012 at 11:42 AM, "René J.V. Bertin"
<email@hidden> wrote:
On Oct 01, 2012, at 17:25, Paul Davis wrote:
> ObjC is definitely easier to learn than C++, it's got a much more restricted (and readable) vocabulary, and is much more an extension on top of C than C++ is.
>
> sure, until you start to run into namespace collisions ....
Which probably only happens in very specific cases (and isn't impossible in C++ either, is it?)
in a world full of plugins (i.e. audio software) it happens remarkably often. and no, it cannot happen in C++ unless someone tries to make it happen.
> But sure, it's a bit problematic that OS X doesn't provide mechanisms like those on MS Windows that allow apps to 'lock' an output device through WASAPI
>
> it does. its called "hog mode". no other client can use the device when hog mode is in effect. obviously, its intended for use only by very specific classes of applications.
And apparently rather 'confidential'. Windows at least offers an option to (dis)allow exclusive access mode to a given output device, I can't recall having seen anything like that on OS X.
complaints about the documentation for CoreAudio are nothing new. there's very little you can't do, but finding out how to do it is normally the hard part.
R.
_______________________________________________
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
_______________________________________________
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