• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How is an AU supposed to close its files when it closes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Brian Willoughby <email@hidden>
  • Date: Sat, 16 Aug 2008 02:38:53 -0700

Jeremy,

Perhaps I have misunderstood your use of the terminology, but an AudioUnit is not an executable. 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.

However, in the rare case that your AU starts a separate task, you will want to stop that task when your AU is uninitialized, but remember that this is rare.

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? 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. Virtual memory handles quite a bit for you.

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


  • Follow-Ups:
    • Re: How is an AU supposed to close its files when it closes
      • From: Jeremy Sagan <email@hidden>
References: 
 >How is an AU supposed to close its files when it closes (From: Jeremy Sagan <email@hidden>)

  • Prev by Date: How is an AU supposed to close its files when it closes
  • Next by Date: Re: How is an AU supposed to close its files when it closes
  • Previous by thread: How is an AU supposed to close its files when it closes
  • Next by thread: Re: How is an AU supposed to close its files when it closes
  • Index(es):
    • Date
    • Thread