• 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: AU resources (plist problem)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU resources (plist problem)


  • Subject: Re: AU resources (plist problem)
  • From: Bill Stewart <email@hidden>
  • Date: Tue, 17 Dec 2002 10:46:33 -0800

At this point I don't think that it is Core Audio that is throwing the exception - but I'd like to see the back trace that you're getting when its crashing... (off list is fine)

Please don't flame me for this suggestion:) - have you tried using Project Builder? We haven't had any of these kinds of problems when using that. Maybe someone has already got a PB version of the VST2AU project they could send you if you're interested in trying this route?

Bill

On Tuesday, December 17, 2002, at 09:07 AM, Howard Moon wrote:

Hi..

following suggestions about making my resources visible in my AU (which is a vst port using VST2AU), I added the following to the VST2AUplist.plc file:
...
key "CFBundleIdentifier" value string "com.Antares.AutoTune"
...

(This is inside the "dictionary" node along with the other key/values pairs.)

Sometimes, CodeWarrior fails to write out the plist file into the contents of the component (bundle). In those cases, my call to CFBundleGetBundleWithIdentifier returns null (since it can't find the key I'm looking for), and then my plug-in won't be created. Then, the host continues to launch but without my plug-in being available.

Sometimes, the plist file IS created. (I have yet to know when/why this difference.) In THOSE cases, the CoreAudio code throws an Access Fault Exception even before any of my code is executed. (Which of course makes it impossible to debug!) I am totally confused as to what to do about this problem. I've been stuck for weeks unable to get my vst plug ported to AU using this VST Porting SDK.

One other note: even though I renamed the bundle to AutoTune.component, CodeWarrior still creates a folder hierarchy called Plugin.component (although it has no content, just folders). Could this be related somehow to the plist generation problem? Is there something not mentioned in the readme.h or porting doc that I missed regarding the target?

Anyone have any idea what is going on here??? Why would the presence of Info.plist cause CoreAudio to throw an exception? And why would the plist only be written *sometimes*? Can somebody shed some light on this?

Thanks for any advice...

Howard
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.


-- mailto:email@hidden
tel: +1 408 974 4056

________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
  • Follow-Ups:
    • Re: AU resources (plist problem)
      • From: Howard Moon <email@hidden>
References: 
 >AU resources (plist problem) (From: Howard Moon <email@hidden>)

  • Prev by Date: Re: Disappearing AU
  • Next by Date: Re: Any documentation yet?
  • Previous by thread: AU resources (plist problem)
  • Next by thread: Re: AU resources (plist problem)
  • Index(es):
    • Date
    • Thread