• 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: core midi time stamping
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: core midi time stamping


  • Subject: Re: core midi time stamping
  • From: Peter <email@hidden>
  • Date: Fri, 15 Jul 2005 11:14:02 +1000


On 15/07/2005, at 2:33 AM, Doug Wyatt wrote:


On Jul 13, 2005, at 21:46, david tay wrote:

How is core midi time stamping done? Product marketing thinks that some special code is required.

Would special drivers for MIDI interfaces be required to for midi time stamping to work?

<snip>

On output, when possible, your app should schedule outgoing packets in advance. As little as 5 ms in advance may make a noticeable improvement. Scheduling more than 100 ms in advance is probably not a good idea, unless you make further calls to flush previously-scheduled events when you stop etc.


As an aside, could you tell us how far ahead the built in MusicPlayer schedules packets? Reason why I ask is that I have recently changed parts of my app and am now getting a short pause when performing some actions. This never happened before.



Peter

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >core midi time stamping (From: david tay <email@hidden>)
 >Re: core midi time stamping (From: Doug Wyatt <email@hidden>)

  • Prev by Date: AUGraph & kAudioUnitSubType_GenericOutput
  • Next by Date: Creating a varispeed converter
  • Previous by thread: Re: core midi time stamping
  • Next by thread: Re: core midi time stamping
  • Index(es):
    • Date
    • Thread