Re: Runaway clock?
Re: Runaway clock?
- Subject: Re: Runaway clock?
- From: William Stewart <email@hidden>
- Date: Mon, 16 Jun 2008 12:12:57 -0700
If you open the transport window in AULab, do you see the same
problem? All we are doing there is calling the Stop call when the user
hits the stop button, and that seems to work ok for me. We do a little
bit of extra stuff to manage whether the clock is running or not for
the AU Host callbacks, but I don't see any additional code here to
deal with the clock "not stopping"
Bill
On Jun 13, 2008, at 9:42 PM, Todd Blanchard wrote:
A kind soul pointed me to CAClock and I'm trying to use it to
provide metronome and countoff. I can create the clock, set the
tempo, start it playing. I run a timer in the UI thread the reads
the current measure/beat/fraction and puts it into a text field
regularly. Works great. It shows 1.1.000 initially until I hit
start. If I up the tempo it counts faster, down it and it slows
down. Lovely.
Except for stop. CAClockStop returns noErr, but the numbers keep
going up in the display just the same. Is there another way to stop
the clock short of hitting it with a hammer?
This is 10.4 BTW.
-Todd Blanchard
_______________________________________________
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
_______________________________________________
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