Re: plugin looses sync with transport
Re: plugin looses sync with transport
- Subject: Re: plugin looses sync with transport
- From: William Stewart <email@hidden>
- Date: Tue, 12 Oct 2010 18:01:14 -0700
You can only call the host callbacks from within the context of the AudioUnitRender call.
If you are calling this from within AudioUnitReset, you should be getting an error back from the host telling you you "can't do this in this context"
On Oct 10, 2010, at 11:31 AM, Artemiy Pavlov wrote:
> Hi all!
>
> I have a gate sequencer plugin which is synchronized to the transport.
>
> As an example, I place it on an instrument track which has two regions, about 30 seconds apart:
> http://www.artemiypavlov.com/tmp/regions.png
>
> If I sync to the current transport location with each Process() call, all is well. The sequencer is in sync with the transport in both regions.
>
> However, if I only sync with the transport when Reset() is called, the sequencer is in sync only on the first region, and is out of sync in the second region.
>
> Debugging shows that the plugin is hibernated between the regions, which is expected, but before the second region it is being woken up without calling Reset().
>
> The question is, should I revert to synchronizing on each Process() cycle? If not, how do I detect when my plugin is being woken up like I described? Nothing in CallHostTransportState changes either, so I can't trace this moment.
>
>
> Thanks and best wishes,
>
> Artemiy.
>
>
> _______________________________________________
> 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