• 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
(no subject)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)


  • Subject: (no subject)
  • From: Doug Wyatt <email@hidden>
  • Date: Wed, 20 Jun 2001 11:10:22 -0700

From: email@hidden
To: email@hidden
Date: Fri, 15 Jun 2001 10:01:22 -0700
Subject: USB MIDI question...

Hi there...

I am just starting to port my OS9 usb midi driver to X. I have a couple
questions...thanks in advance...

1. On OS9 I have an OMS driver *and* a usb driver. I think that on X I only need
a single binary which is a plug-in to the midi server. Does this sound right?

Yes.

2. My device is based on the EZ-USB chip and needs a "download driver" as well
as the actual midi driver. On OS9 these were separate usb drivers. On X I am not
sure exactly how this works. Do I need 2 separate usb drivers like on OS9? Or
can I incorporate the download functionality into the midi driver itself?

Probably the latter, assuming you can use the USB user client to implement the download.

3. With OMS, I know exactly how and when it scans for new midi devices. On X,
when does the midi server re-scan the bus? Or, maybe it deosn't scan, it waits
for notifications instead?

In 10.0, it's when the server starts up or someone calls MIDISetupCreate. We're aware of the desirability of a better plug-and-play model.

Doug


  • Prev by Date: USB audio interface for MacOS X
  • Next by Date: Re: coreaudio-api digest, Vol 1 #27 - 6 msgs
  • Previous by thread: USB audio interface for MacOS X
  • Next by thread: Re: coreaudio-api digest, Vol 1 #27 - 6 msgs
  • Index(es):
    • Date
    • Thread