debug flag left on in MIDIMan OSX driver
debug flag left on in MIDIMan OSX driver
- Subject: debug flag left on in MIDIMan OSX driver
- From: Jeff Evans <email@hidden>
- Date: Wed, 14 Aug 2002 14:31:20 -0700
On May 22 Pete Gontier wrote as below concerning a debug flag accidentally
left in the posted version of the MIDIMan OSX drivers - I find that the
version currently posted at MIDIMan remains the February 2.01b1 that
includes the debug flag. Pete seems to be on vacation and MIDIMan hasn't
answered my inquiry about this - does anyone know about the status of a
release MIDIMan driver for OSX? The beta is really not usable; perhaps
someone on the list has access to the correct version?
Thanks, Jeff Evans
-----------
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.
_______________________________________________
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.