• 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: MIDI TimeCode generator
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIDI TimeCode generator


  • Subject: Re: MIDI TimeCode generator
  • From: Peter Krajcik <email@hidden>
  • Date: Sun, 18 Aug 2002 23:47:38 +0200

Now, I'm a little bit disoriented:

- Virtual destination in my app seems to be a "port" where other application
can send data - it is a MIDI in of my app.

- Virtual source in my app seems to be a "port" from where other application
can recieve data - it is a MIDI output of my app.

If this is a true, why I need to use MIDIReceived() if I need to send out
data to my "virtual output port" -> my Virtual source ?

I think I just need to call MIDISend(port, myVirtualSource, packetlist);

Did you mean that recieving application needs to call MIDIRecieved() from my
VirtualSource and in that case it takes everythink from MIDIServer's buffer
ignoring the time stamps ?

If that's what you meant, how to make an accurate timing of MIDI data via
virtual source ? (What is logic in that: destination uses TimeStamps and
source doesn't. Should be symmetrical Ithink.)

Thank you.

- peter

on 18.08.2002 23:20, Kurt Revis at email@hidden wrote:

> On Sunday, August 18, 2002, at 01:49 PM, Herbie Robinson wrote:
>
>> I believe that right now, virtual endpoints will get packets that don't
>> happen until some future date.
>
> This isn't quite the case. If an application uses MIDISend() to send to
> a virtual destination, the MIDIServer will use the timestamps and
> schedule the events in the same way as it does for actual MIDI devices.
>
> (Schedule-ahead values for virtual destinations were ignored in 10.1,
> but supposedly 10.2 honors them.)
>
> However: If your application creates a virtual *source*, it needs to use
> MIDIReceived() to give the source's events to the MIDIServer. But
> MIDIReceived() does not do any scheduling, so all events are sent
> through the pipeline immediately, regardless of their timestamps. This
> may be what you are thinking of.
>
> --
> 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.

  • Follow-Ups:
    • Re: MIDI TimeCode generator
      • From: Kurt Revis <email@hidden>
References: 
 >Re: MIDI TimeCode generator (From: Kurt Revis <email@hidden>)

  • Prev by Date: Re: MIDI TimeCode generator
  • Next by Date: Re: MIDI TimeCode generator
  • Previous by thread: Re: MIDI TimeCode generator
  • Next by thread: Re: MIDI TimeCode generator
  • Index(es):
    • Date
    • Thread