• 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: Chris Santoro <email@hidden>
  • Date: Tue, 15 Dec 2009 14:40:28 -0500

Hi Bill,

Rather than re-scanning when seeing this or that version number, why not simply re-scan a plug-in when the component file changes? That seems like the most logical behavior, and is what I would have expected behavior-wise from *any* host before Brain tipped me to the obscure version number detail.

My problem occurred because I compiled my project with the wrong channel config *once* in the past. When I corrected the channel configuration reporting, I would have expected Logic and AU Lab to see the change, but neither did, because the version number was held constant (and was not 0x0 or 0xFFFF...).

Trying to correct the issue, I had totally removed the plug-in, and confirmed that Logic and AU Lab no longer saw it. At that point I would have expected that component to be removed from the component manager in the system. Why keep it around? Perhaps that's a bug? Or is there a good reason for that?

Thanks,
Chris

On Mon, Dec 14, 2009 at 2:31 PM, Chris Santoro <email@hidden> 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.

My AU subclasses from AUMIDIEffectBase and properly overrides the SupportedNumChannels function.


If I run the AU Validation tool on it, it shows the proper channel handling capabilities.

//-------------------------------------------------------
Reported Channel Capabilities (explicit):
      [1, 2]  [2, 2] 

Input/Output Channel Handling:
1-1   1-2   1-4   1-5   1-6   1-7   1-8   2-2   2-4   2-5   2-6   2-7   2-8   4-4   4-5   5-5   6-6   7-7   8-8
      X                                   X          
//-------------------------------------------------------

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.

Best,
Chris



 _______________________________________________
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: Brian Willoughby <email@hidden>
References: 
 >Re: Audio Unit ioConfigs (Resolved) (From: Chris Santoro <email@hidden>)

  • Prev by Date: Re: Audio Unit ioConfigs
  • 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