Re: CallHostTransportState and Logic Pro
Re: CallHostTransportState and Logic Pro
- Subject: Re: CallHostTransportState and Logic Pro
- From: Howard Moon <email@hidden>
- Date: Wed, 9 Dec 2009 07:59:16 -0800
I've files a bug report on this: id = 7456584
I'm getting odd behavior in Logic Pro (i.e., 9) when calling the
host CallHostTransportState callback. Sometimes, when calling this
from Render (once per call), the first parameter (isPlaying) returns
FALSE, even though the transport is clearly still running. I'm not
running in a loop, and no other plug-ins besides mine are running.
It's just chugging along, and suddenly my plug-in thinks the
transport has stopped, and so it changes states and does some
housekeeping. Meanwhile, the transport keeps on chugging along,
processing audio in the normal fashion.
This is happening in Logic Pro under OS X 10.5. I don't (yet) know
if this happens in other Logic versions or other OS versions. It
does not always happen, but when it does happen, it is in specific
locations in time, (although I don't see any particular significance
in the times I've observed).
Has anyone else observed this behavior?
For earlier hosts, where this callback does not exist, we checked
whether the time value passed to Render had changed or not between
calls. But, assuming we get reliable information from the callback,
this method is better. However, if we cannot rely on the callback,
then what good does it do to use it?
Is this perhaps a Logic bug? Or is there some reason why the host
might tell us that the transport is stopped, even though time has
clearly advanced (and continues to advance with each subsequent call)?
_______________________________________________
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