• 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
Midisport and sysex
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Midisport and sysex


  • Subject: Midisport and sysex
  • From: "Peter Karlsson" <email@hidden>
  • Date: Mon, 20 Dec 2004 13:35:13 +0100

Dear list!

I'm having trouble with my MIDISport 4x4 and sysex.

I have just found out that if I send a dump request message from my app:

- Kurt Revis MIDI Monitor says that 6 bytes has been sent to port A, and
it's the complete request message.

- MIDISPORT 4x4 is not receiving sysex (no red lamp is blinking) and my
synthesizer is not responding.

This happens only after my app is just started. If I send the same sysex
request again, everything works and willl continue working. Until the next
time I start my app.

I made a change in my app so it now sends out some controller messages
after startup, this seems to solve the problem (not 100% sure). So it seems
that the MIDISport driver is having trouble with some sysex status flag or
something. Can this be a driver problem in the MIDISport 4x4? The driver
version I'm using is 3.1 with latest OS X panther version.

Peter

 _______________________________________________
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

  • Follow-Ups:
    • Re: Midisport and sysex
      • From: Herbie Robinson <email@hidden>
  • Prev by Date: Re: Midi sysex request in new thread
  • Next by Date: CoreAudio driver's buffer management
  • Previous by thread: Re: auval could be more helpful
  • Next by thread: Re: Midisport and sysex
  • Index(es):
    • Date
    • Thread