Re: MIDI Development
- From: "Bruce Varley" <bxvarley@xxxxxxxxxxxxxxx>
- Date: Fri, 4 Jan 2008 21:34:01 +0900
<c.melchiorri@xxxxxxxxx> wrote in message
news:52e29032-59f3-4f46-abd5-176d3f6f15c6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I don't know if is this a right place to ask something about
development, but I didn't find some specific newsgroup..
so, I am using for the first time MIDI protocol to using a Yamaha
Mixer remotly, and I'm sending commands by System Exclusive, but
during debuging sometime software must be stopped before it had
destroyed the Handles that lock the midi-in channels, so when I try to
reconnect an exception told me the the port is already in use...
I'm looking for a command or procedur to unlock this port, beacouse in
the new session I can't have the old handle to destroy it.
Anybody knows how can I do this?
Some Sugestions?
Thanx in advance
A bit more information on your development/debugging environment, and also
how your program accesses the MIDI ports, would help.
IME with C++, when a debugging session is terminated all handles go out of
existence, so the problem doesn't arise. That suggests there's some aspect
to your setup that you aren't describing fully.
There are standard kludge techniques for this sort of situation that you're
probably aware of, like running the application outside the debugger and
using trace techniques like cprintf() to a DOS window. That way you can get
your information on the fly, and also allow the program to close out
whatever objects that are causing the problem. For real time I tend to debug
this way more than by using debuggers.
MIDI-Ox and MIDI-Yoke are good allies with this sort of work BTW.
.
- References:
- MIDI Development
- From: c . melchiorri
- MIDI Development
- Prev by Date: MIDI Development
- Next by Date: Re: MIDI Development
- Previous by thread: MIDI Development
- Next by thread: Re: MIDI Development
- Index(es):
Relevant Pages
|
Loading
