Re: HAL user-land audio driver
Re: HAL user-land audio driver
- Subject: Re: HAL user-land audio driver
- From: "Mikael Hakman" <email@hidden>
- Date: Fri, 28 Mar 2008 13:59:46 +0100
- Organization: Datakonsulten AB
On March 26, 2008 7:39 PM, Jeff Moore wrote:
On Mar 26, 2008, at 5:25 AM, Mikael Hakman wrote:
Are the basic (and laborious) shared memory and/or IPC and/or dividing
the plug-in into multiple clients/shared server architecture the only
alternatives?
You are definitely going to be using shared memory and/or IPC, but
whether you use a client/server or peer-to-peer styled protocol depends
totally on what you are trying to accomplish.
I got global state and global property change notifications working now. I'm
using POSIX named shared memory for global state, POSIX named semaphore for
serializing access to this shared memory, and Core Foundation Distributed
Notifications for notifying all plug-in instances of the changes. For
example, when using my plug-in driver as default audio output and having
both Sound Preferences and AMS panels open, and also volume control visible
on the menu bar, I can see volume changes in all 3 of them when moving
anyone of the 3 sliders. Many thanks for your help so far, Jeff.
My next question is as follows. Is there any way to add to, or extend AMS
panel with an additional user interface elements? I have one custom property
on device, global scope, master element that I would like to display to the
user as a dropdown select list.
TIA
_______________________________________________
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