Re: Re(2): MIDI send problems.
Re: Re(2): MIDI send problems.
- Subject: Re: Re(2): MIDI send problems.
- From: Doug Wyatt <email@hidden>
- Date: Tue, 7 Aug 2001 21:41:28 -0700
On Tuesday, August 7, 2001, at 02:25 PM, Jason Bagley wrote:
email@hidden writes:
Below is a small command-line tool that creates a virtual destination
and then calls MIDISend to send to it. I can't reproduce any problems
with it ... can you? If not, then it's something for the author of the
driver to investigate.
Thank you. Yes, that proves that using MIDISend with some larger packets
crashes the MIDISPORT driver. I've sent a message to MIDIMAN tech
support.
However, the only reason I'm trying to send larger packets through
MIDISend is because MIDISendSysex is apparently not working. Modifying
your tool to send through MIDISendSysex shows that no data is being
transmitted to the virtual destination (VirtualReadProc never is
called),
yet my sysex completion procedure is called. I suppose the point is moot
since both functions would call the same callback in the driver though.
Correct?
Yes.
We have a bug here too; 10.0.x's MIDISendSysex sometimes decides to
schedule packets for delivery at a random time in the future, which
unfortunately means "never" in many cases. Should be fixed in the next
release.
A side note: if you set the completion procedure to NULL in the send
request, you'll get a bus error. The header docs don't say that you have
to set the completion proc.
This too is a known problem and should be fixed in the next release.
sorry,
Doug
--
Doug Wyatt
work: email@hidden
personal: email@hidden
http://www.sonosphere.com
Synchronicity, 16 Jan 2001:
"Example is more important than precept."
-- fortune cookie
"Religion is the life we lead, not the creed we profess."
-- sign on Unitarian church passed 5 minutes later