• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
MIDI device source/destination visiblity
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MIDI device source/destination visiblity


  • Subject: MIDI device source/destination visiblity
  • From: Alex Sheh <email@hidden>
  • Date: Mon, 28 Apr 2008 11:23:47 -0700
  • Acceptlanguage: en-US
  • Thread-topic: MIDI device source/destination visiblity

Hi all,
I work on a MIIDDriver.plugin that presents a virtual MIDI Device with sources/destinations to 3rd party applications.  Blocks of 4 source/destination pairs are configured for a single 3rd party application at a time.  If source/destinations 1-4 are "owned" by application A, is there any way for me to make source/destinations 1-4 visible ONLY to application A, and hide them when application B (or any othe application) inspects the virtual MIDI Device?  If that is not possible, is there a way for me to determine the identity of the process whose input/output ports are connected to source/destinations 1-4, so that I can ignore all MIDI data to/from all applications other than application A?
 
Thanks for your help.
 
- Alex
 _______________________________________________
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

  • Prev by Date: AudioUnitSetParameter vs AUParameterSet
  • Next by Date: AudioFormat::FileDataIsThisFormat
  • Previous by thread: AudioUnitSetParameter vs AUParameterSet
  • Next by thread: AudioFormat::FileDataIsThisFormat
  • Index(es):
    • Date
    • Thread