Re: MIDIPacketList behaviour problem
Re: MIDIPacketList behaviour problem
- Subject: Re: MIDIPacketList behaviour problem
- From: Michael Harbour <email@hidden>
- Date: Tue, 20 Jan 2004 23:41:27 +0000
Thanks for replying Pete.
On 20 Jan 2004, at 22:28, Pete Gontier wrote:
I'm not familiar with the Java MIDI client, and I'm reluctant to
compile and
run code I don't understand, but...
An admirable position in general, old chap, you never know how badly it
could shag up your system.
A shame in this particular case, its such a noddy example. Never mind.
I understand the Java API is only a very thin layer over the C API
(unfortunately). I wonder if this behaviour, if not a result of my
programette, is inside the C code from apple, and whether anyone else
would be interested in what is going on here.
I do the MIDISPORT driver,
ahhhhh. great stuff. is there much left to do to it development wise
now or is it just maintainence when layers above and below change?
and a loopback cable works just fine. In fact, I
use that as one of the first quick tests of a new driver revision. If
I can
send a message around the loop, I know I haven't broken anything big
and I
move on to see if I've broken anything small. Sending one message
definitely
doesn't result in receiving 127, so there must be something wrong
above the
driver level.
righto. so that would suggest the behaviour is in the coreaudio code?
You might want to use some other application to do the
sending.
I've seen the same behaviour just now when I squirt a midi message into
the MIDISport from my Kenton Control Freak at the same time I'm sending
out messages to it - the incoming message arrives 127 times when
something is going out, but only once when output is quiet.
I think there is a simple PlayNotes sample app rattling around
somewhere. It's written in C.
Oh, I'm reluctant to compile and run code i dont...etc :-)
And by the way, the hardware worries about baud. You might want to
throttle
your output to avoid choking the receiver,
Sorry, you've lost me there, could you expand on this - it sounds like
it's relevant. If this means something like threading, my original code
had a secondary java thread that just collected incoming
MIDIPacketLists from the MIDIServer thread and dispatched the
collection in its own time to some listening objects
but there's no need to think in
terms of bit signaling.
ok.
Many thanks
Mike
--
Pete Gontier
http://www.m-audio.com/
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.