• 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
CAClock and MIDI Clock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CAClock and MIDI Clock


  • Subject: CAClock and MIDI Clock
  • From: Evan Olcott <email@hidden>
  • Date: Thu, 9 Oct 2008 21:58:14 -0500

I'm not sure I understand what's going on with the sending of MIDI clocks via the CAClock. (I haven't even tapped into the MTC stuff yet, but I will once I understand this). There is no M in RTFM in this case, so I came here:

I want to send MIDI clocks to a given MIDI endpoint by using CAClock. So far so good.

A few issues I can't seem to resolve:

1) The clock seems to ALWAYS run regardless of CAClockStart or CAClockStop. I assume this is because these methods start and stop the *media timeline* and not the timebase. This also makes me assume that the MIDI clocks are based on the timebase alone, and so if the MIDI endpoint exists, the clocks will be sent as long as the CAClock exists. The only way to stop it being sent to a particular MIDI endpoint is if it's not on the list for CAClock in the first place. Is this a correct assumption?

2) It also seems as though tempo changes have no effect on the MIDI clock. I can't even yet confirm that tempo changes are happening, since I am really only using the CAClock for the MIDI clock/MTC, and I won't really be using the media timeline (I don't think). The clocks run at a nice, steady 120bpm. How does one change the tempo that the MIDI clocks get sent?

I had been sending MIDI clocks through my own method with an NSTimer and checking against the host time, etc. It was fairly clever, but not really robust. If CAClock is doing what I hope it's doing, it looks like a great solution for a lot of issues I'd have to address eventually with syncing with other devices, etc. However, it seems to be lacking in some flexibility (I think), but CERTAINLY is lacking in any documentation or explanation of how to use it properly.

Thanks in advance for any help or pointers - CAClock looks great, but I'm not sure I know what's going on!

Ev
Technical Knowledge Officer
Head Programmer/Designer
Audiofile Engineering

http://www.audiofile-engineering.com/






_______________________________________________ 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
  • Follow-Ups:
    • Re: CAClock and MIDI Clock
      • From: Doug Wyatt <email@hidden>
  • Prev by Date: Re: raw data extraction
  • Next by Date: Re: How to perform fast forward/rewind with AudioQueue
  • Previous by thread: Re: Can AU plug-ins ask the host to change the transport?
  • Next by thread: Re: CAClock and MIDI Clock
  • Index(es):
    • Date
    • Thread