In some ways this problem is similar to the problem of writing custom settings from within a Sounds control panel extension. In a previous post on that problem, I said this //www.freelists.org/archives/wdmaudiodev/10-2006/msg00066.html, //www.freelists.org/archives/wdmaudiodev/10-2006/msg00067.html. For your problem, your hot-key handler can write a setting to your audio driver as suggested in these links above. Using a similar mechanism, your SYSFX APO can monitor KS events for changes on those settings and adjust their DSP. For these settings, the audio driver acts as little more than a conduit and storage for these settings since the SYSFX APO actually implements the DSP for them. Frank Yerrace Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. -----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] Sent: Monday, November 06, 2006 4:41 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Hotkey implementation for APOs? Hi everyone, We have an OEM that is going to be bundling one of our APOs on their system. They already have a keyboard designed with a hotkey that can toggle a property in our APO. (The key toggles through four states for the APO.) The question is: How do we inform any running APOs when the hotkey is pressed? Their hotkey signals their own application, which is supposed to inform any APOs that the property has changed. However, they cannot use the property store, since applications do not have write access to it. We thought of writing to a registry key in HKLM, but the app does not have write access to that either. (HKCU is out, since the hotkey app and the APO are running under different accounts.) We are also considering using shared memory and a named event to set the value and trigger the event, but that seems problematic when multiple APOs are running. (Or we'd have to maintain a list of events in shared memory that need to be signaled when the hotkey was pressed.) Overall, it seems like a lot of effort for what you would think should be a simple solution. Any advice? Thanks, Jeff ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/ ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/