• 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: Audio Unit ioConfigs (Resolved)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio Unit ioConfigs (Resolved)


  • Subject: Re: Audio Unit ioConfigs (Resolved)
  • From: Brian Willoughby <email@hidden>
  • Date: Mon, 14 Dec 2009 18:01:40 -0800

Chris,

You can avoid this situation by changing the version number of your AU whenever you change it's interface to AU hosts.  For public releases, a version number change is absolutely necessary.  For development purposes on your private machine, you can use version 0.0.0 to force compliant AU hosts to rescan your AU every time it launches.  Just remember to set a non-zero version before release, and also remember to make sure that each different release has a different version number.

i.e. Logic and AULab are doing a proper re-scan and re-validation, you just happened to be breaking the rules!

Brian Willoughby
Sound Consulting


On Dec 14, 2009, at 11:31, Chris Santoro wrote:
Issue Resolved.

Had to manually clear the audiounits cache at

user/Library/Caches/com.audiounits.cache

Apparently Logic/AULab do not do a proper re-scan/re-validation of a plugin once it is removed/replaced in the system. If you have a rebuild of a plugin that you change the channel capability of, you'll have to clear the cache to get the system to see it properly.

Hope this helps someone else out there!

Thanks,
Chris

On Mon, Dec 14, 2009 at 10:24 AM, Chris Santoro <email@hidden> wrote:
I'm trying to implement an audio unit (type aufx) with the ability for mono->stereo and stereo->stereo, but NOT mono->mono.
[...]
However, both AULab and Logic 8 show a mono->mono option, even though it isn't there.

Is this a bug in Logic or am I doing something wrong? Has anyone else experienced problems with this? I've also tried every combination of removing/restarting/rebuilding I could think of, in case the component manager might be caching out-of-date information.
 _______________________________________________
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: Audio Unit ioConfigs (Resolved)
      • From: Paul Davis <email@hidden>
References: 
 >Re: Audio Unit ioConfigs (Resolved) (From: Chris Santoro <email@hidden>)

  • Prev by Date: Enable matrix mixer inputs without ramping
  • Next by Date: Re: Audio Unit ioConfigs (Resolved)
  • Previous by thread: Re: Audio Unit ioConfigs (Resolved)
  • Next by thread: Re: Audio Unit ioConfigs (Resolved)
  • Index(es):
    • Date
    • Thread