Re: Midi console printing solved but not resolved
Re: Midi console printing solved but not resolved
- Subject: Re: Midi console printing solved but not resolved
- From: Pete Gontier <email@hidden>
- Date: Wed, 22 May 2002 13:13:36 -0700
It's not a new standard; it's just a bug. The debug flag got set in a build
without my realizing it. I've since sent a non-debug build in to the folks
who maintain the web site. If you can't download it as you read this, let me
know and I will notify the appropriate people.
circa 5/22/02 1:04 PM, Joshua Strickon <email@hidden> wrote:
>
I downloaded the old beta version of the midi sport driver and it does not
>
print to the console. It appears that this is a new feature of the supposed
>
release version. I can9t imagine all drivers doing this. If anyone knows
>
whether or not this is standard for all drivers now, it would be nice to
>
know. It is as if they forgot to turn off debugging when they built their
>
latest driver.
circa 5/22/02 11:12 AM, Joshua Strickon <email@hidden> wrote:
>
Is there any way to prevent printing of midi input messages to the console.
>
Aside from the performance overhead of printing to the console every time a
>
midi packet is received, I would like to use it for more important messages.
>
>
You can experience this by using the MIDIMonitor tool.
>
>
Here is an example of what it is printing
>
>
MIDIReceived because we have 1 packets; intf->mSources[prevInputPort] is
>
0x0981000A
>
inputPort 0 bytesInPacket 1: FE 00 00 01
>
new status FE, remainingBytesInMsg = 0
>
>
I am doing some stuff with jni and the console and standard out are 1 and
>
the same.
--
Pete Gontier -- pete at midiman dot net -- <
http://www.midiman.net/>
_______________________________________________
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.