• 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: MIDIReceive and SysEx event
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIDIReceive and SysEx event


  • Subject: Re: MIDIReceive and SysEx event
  • From: Nigel Redmon <email@hidden>
  • Date: Thu, 21 Jun 2007 13:50:06 -0700

BTW, the "1" after the f0 in my example ("f0 1 2 3 4 f7") is simply a manufacturer's ID code (Sequential Circuits, which started MIDI, so of course they got #1)--I haven't checked MIDI Monitor to see what it says when it comes across a manufacturer's ID code it doesn't know, but the point is there is nothing magical; coremidi should have no problem passing on any legal sysex message (and plenty of illegal ones too, I'm sure--it's not a traffic cop). What the receiver does is up to the receiver.


On Jun 21, 2007, at 7:18 AM, Jasmin Lapalme wrote:
I try the exact same SysEx event and it worked! I think that the 1 after the f0 is very important.

_______________________________________________ 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
References: 
 >MIDIReceive and SysEx event (From: Jasmin Lapalme <email@hidden>)
 >Re: MIDIReceive and SysEx event (From: Nigel Redmon <email@hidden>)
 >Re: MIDIReceive and SysEx event (From: Jasmin Lapalme <email@hidden>)

  • Prev by Date: Re: MIDIReceive and SysEx event
  • Next by Date: auval 1channel test
  • Previous by thread: Re: MIDIReceive and SysEx event
  • Next by thread: Re: 答复: 答复: S/PDIF audio output
  • Index(es):
    • Date
    • Thread