Re: Idle processing
Re: Idle processing
- Subject: Re: Idle processing
- From: Marc Poirier <email@hidden>
- Date: Tue, 25 Feb 2003 14:49:05 +0100 (CET)
>
To implement such a thing, two elements are required:
>
>
1) A way to convey information from the model layer to the view layer
>
2) A way to schedule the low priority task so it doesn't interfere
>
with the higher priority task of audio processing.
>
>
Number one can be accomplished by the plugin with a variety of
>
mechanisms including message queues and property queries (triggering
>
a GUI update from the audio thread would be a bad thing indeed!).
Right, just to reiterate (or maybe I was clear the first and you're just
restating this): the parameter notifications are safe from the audio
thread, they just get queued and immediately return.
>
Number two however, requires the supervision of the host. Only the host
>
knows how busy it is, and therefore whether low priority tasks should
>
be scheduled or not. The result is that low-priority tasks will be run
>
less frequently when cpu load is heavy.
Well, like Ralph said, the OS knows better than the host about how busy
the system is, and I would add that, in addition to Ralph's proposed
method, the parameter listeneter / property combo method that I proposed
also will defer to the audio thread and occur less frequently at high CPU
loads while audio will continue smoothly (I just tested that out).
Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.