• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: debug flag left on in MIDIMan OSX driver
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debug flag left on in MIDIMan OSX driver


  • Subject: Re: debug flag left on in MIDIMan OSX driver
  • From: Pete Gontier <email@hidden>
  • Date: Wed, 14 Aug 2002 15:09:36 -0700

I'm not on vacation; I'm just stalling until I can give a better answer. :-)

I don't know why the non-debug driver has not been posted on the web after
all this time. All I can say is that it should have been. Meanwhile, I've
been rewriting the driver from scratch, and it's pretty close to done. I
can't predict when it will be posted, but it ought to be Real Soon Now.

Releases are (obviously) not my prerogative, so I will not be able to oblige
requests for the present (internal) build.

circa 8/14/02 2:31 PM, Jeff Evans <email@hidden> wrote:

> 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?

>> 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.

--

Pete Gontier -- pete at m-audio dot com -- <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.

References: 
 >debug flag left on in MIDIMan OSX driver (From: Jeff Evans <email@hidden>)

  • Prev by Date: debug flag left on in MIDIMan OSX driver
  • Next by Date: Disabling a IOAudioLevelControl
  • Previous by thread: debug flag left on in MIDIMan OSX driver
  • Next by thread: Disabling a IOAudioLevelControl
  • Index(es):
    • Date
    • Thread