• 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
Re: MIDI driver monitoring -- bad destination?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIDI driver monitoring -- bad destination?


  • Subject: Re: MIDI driver monitoring -- bad destination?
  • From: Kurt Revis <email@hidden>
  • Date: Sat, 9 Mar 2002 23:49:48 -0800

Answering my own question...

On Thursday, March 7, 2002, at 11:22 PM, Kurt Revis wrote:

Has anyone tried using the monitoring function in a CoreMIDI driver (that is, implemented a Monitor() function on their driver)?

I am finding that the MIDIEndpointRef passed in as a destination is not a real MIDIEndpointRef that I can use in other CoreMIDI calls.

I figured out that the Monitor() function is being given a *pointer* to the MIDIEndpointRef instead of a real MIDIEndpointRef, in violation of the function's declaration. Casting the given value to a (MIDIEndpointRef *) and dereferencing it gives me the real MIDIEndpointRef.

Filed as bug #2877457.

--
Kurt Revis
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: MIDI driver monitoring -- bad destination?
      • From: Doug Wyatt <email@hidden>
References: 
 >MIDI driver monitoring -- bad destination? (From: Kurt Revis <email@hidden>)

  • Prev by Date: waveform drawing ?
  • Next by Date: Objective-C wrapper on AudioUnits
  • Previous by thread: MIDI driver monitoring -- bad destination?
  • Next by thread: Re: MIDI driver monitoring -- bad destination?
  • Index(es):
    • Date
    • Thread