• 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: Sysex dump problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sysex dump problem


  • Subject: Re: Sysex dump problem
  • From: Doug Wyatt <email@hidden>
  • Date: Mon, 3 Jan 2005 10:17:15 -0800

Peter,

MIDIMonitor may be showing what's going on inside the MIDI server, not installing a readProc. (Kurt, if you're reading this, can you confirm?)

I'd like to check up on this and make sure there isn't a bug in the server->client data transfer. It might be a situation where memory is getting touched for the first time during the first dump and thus we're falling into an obscure case where the server has to do some secondary buffering.

Can you please summarize the calls you're making to CoreMIDI in this situation? Do you request the dump very shortly after app startup, or do you wait for the user to initiate the request?

Doug

On Dec 25, 2004, at 8:32, Peter Karlsson wrote:
Dear list!

If I request a sysex dump from my Ensoniq ESQM I often (not always) gets
problems with the last bytes of the dump. Maybe the last 1000 bytes or so.


Kurt Revis MIDI monitor always reports 8166 bytes from F0 to F7, and that
is correct. If I look at the bytes in the MIDI monitor every byte is
correct.


My app saves the dump to disc and when I look at it the last bytes of the
dumps is not correct. Often it's filled with zeros and garbage and the last
F7 is not there. But the number of bytes received (8166) seems to be
correct.


This happens only the very first time I request the dump from my
synthesizer after my app has started. I can request the dump again and
again and again after that and everything is always correct.

That leeds me to think that I have a problem with my MIDISport 4x4 or it's
driver. But I'm not sure. Can it be the MIDISPort USB data toggle problem?


How can the MIDI monitor be correct every time but not my app? I really
don't understand. Can someone please explain or give me a suggestion what
to do.


Best regards 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


_______________________________________________ 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: Re: induce the MIDI class driver to use a particular icon
  • Next by Date: Re: KMIDIPropertyIsEmbeddedEntity
  • Previous by thread: Re: KMIDIPropertyIsEmbeddedEntity
  • Next by thread: Re: AudioFileTools in CoreAudo SDK 1.3.3
  • Index(es):
    • Date
    • Thread