• 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
Fat custom AU issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fat custom AU issue


  • Subject: Fat custom AU issue
  • From: Evan Olcott <email@hidden>
  • Date: Wed, 8 Jun 2005 23:35:02 -0700

Hey guys - good to meet you (some of you) at the lab yesterday!

In compiling my custom audio unit as a fat binary, I believe I've done everything right, but something's gone awry.

The new AU I've compiled, when put into my app, now generates this error message in the log:

===
NOTE: ignoring this component:
Discovered 0 component = 0x7c013d type = aumx subt = MIXR manu = Ado\304 flags = 0
===


...and the graph is unable to connect to the node; it seems like it wasn't created properly at all. (error -2005's all over)
It's the same AU code, I didn't change a thing from the original, but I recompiled it as a universal. Ironically (or not), this new compile of the AU seems to work on the test machines here @ the compatibility labs, but comes up with this error on the PPC.


What am I neglecting to do in my AU project (or in my app) to make this work?

Ev
Technical Knowledge Officer
Head Programmer/Designer
Audiofile Engineering

http://www.audiofile-engineering.com/


_______________________________________________ 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
  • Prev by Date: Re: Fat Binaries for AUs?
  • Next by Date: Reading supported sample rate in a device
  • Previous by thread: Re: Audio Units user interface
  • Next by thread: Re: Fat custom AU issue
  • Index(es):
    • Date
    • Thread