Re: How is an AU supposed to close its files when it closes
Re: How is an AU supposed to close its files when it closes
- Subject: Re: How is an AU supposed to close its files when it closes
- From: Jeremy Sagan <email@hidden>
- Date: Sat, 16 Aug 2008 11:01:17 -0400
On Aug 16, 2008, at 5:38 AM, Brian Willoughby wrote:
Jeremy,
Perhaps I have misunderstood your use of the terminology, but an
AudioUnit is not an executable.
You are incorrect. An AudioUnit is a component, which executes and
therefore contains an executable. I did not post this question to
argue semantics with you.
The only executable is the host itself. Each and every AU is
running as part of the main host executable. Thus, the host is
responsible for closing anything that it opens. An AU cannot close
itself.
Again I am not looking for a basic teaching of how plug-ins work. A
plug-in must execute to work.
How is it that you are determining whether a component is open or
closed, and what do you mean by an executable being open or closed?
If you had read the original post below you could easily answer your
own question, I am determining whether a component (file) is open or
closed using Activity Monitor. A Component's executable is opened with
the 'OpenComponent' call and I thought should be closed with
'CloseComponent'.
Note that when you terminate a task (i.e. when you quit the host)
all files opened by that task/host will automatically be closed.
This is not a problem when the task terminates, this is a problem that
last only for the duration of the host session.
I don't think you needed to respond to this post at all.
Virtual memory handles quite a bit for you.
Well this statement is the only one in your post that is relevant.
Does VM close the component when it exits a cache or something?
Brian Willoughby
Sound Consulting
On Aug 15, 2008, at 22:59, Jeremy Sagan wrote:
I have been doing some coding help on an audiounit plugin and I have
noticed that it and virtually all Music Device AudioUnits leave
their executable open after the component has been closed. The one
notable exception appears to be the DLS MusicDevice. Which leads to
my question. What is a Music Device (or other AU) plug-in supposed
to do to ensure that it's executable file is closed in the host
after the component is closed?
Here is an example of a path to a fictional plugin's file left open:
/Library/Audio/Plug-Ins/Components/pluginnamehere.component/Contents/
MacOS/pluginnamehere
Note that I have been checking the files left open using Activity
Monitor's 'open files and ports' tab and I have tried this test with
AULab, my host, Metro, and AudioUnitHosting. I am running OS X
10.5.3 (in case it is OS related).
As I side not it would be great if AUVal posted nasty warnings if
files were left open.
Thanks,
Jeremy
_______________________________________________
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