• 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: virtual sources and destinations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: virtual sources and destinations


  • Subject: Re: virtual sources and destinations
  • From: Kurt Revis <email@hidden>
  • Date: Wed, 25 Sep 2002 11:10:14 -0700

On Wednesday, September 25, 2002, at 06:53 AM, nicolas berloquin wrote:

- create a client
- create a source (set its scheduletime to >0 in order to have the
midiserver manage things nicely)
- MIDIReceived() data to the source as you go along

At the moment, there's no point in setting an advance schedule time on a virtual source. CoreMIDI doesn't do any scheduling of events for virtual sources. When you call MIDIReceived(), the data is sent immediately, regardless of its timestamp.

Output is scheduled when it's sent to a virtual destination, though.

-> will creating a destination on the same client as the source add
any benefit with the above setup ?

It will let other apps send MIDI to your client. If you don't need that, don't use it.

- reason never appears as an existing destination/source/device, is
this a reason bug, or normal ?

Reason doesn't provide any virtual sources or destinations for me, either. I don't think it's supposed to. If you want this feature, ask the Propellerheads.

- can someone confirm me that once the midiserver has crashed, new
launches get buggy and a real restart is recommended ? (I'm also having problem with an USB keyboard that's sometimes not recognized...).

A USB computer keyboard (like the one I'm typing on) or musical keyboard? Are you using it through a hub? If so, what happens if you remove the hub?

Anyway, I haven't had such bad luck after MIDIServer crashes. It may depend on particular MIDI hardware or drivers that you are using. Exactly what "buggy" behavior are you seeing? Keep in mind that after the MIDIServer crashes, you will need to quit any apps that are using MIDI and launch them again.

Also, as one method of voodoo debugging, you may want to delete the MIDI preferences files (~/Library/Preferences/ByHost/com.apple.*.plist and ~/Library/Audio/MIDI Configurations/*) and start over. Might help, might not.

Also, if the MIDIServer crashes, you might a) file a bug or b) post the backtrace here. It should (of course) not crash normally. A crash might be Apple's fault, or a driver author's fault.

--
Kurt Revis
email@hidden
_______________________________________________
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: 
 >virtual sources and destinations (From: nicolas berloquin <email@hidden>)

  • Prev by Date: localized driver strings
  • Next by Date: AU2 - Reset
  • Previous by thread: virtual sources and destinations
  • Next by thread: Re: virtual sources and destinations
  • Index(es):
    • Date
    • Thread