Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Audio Unit support in OS X

  • 27-08-2007 9:18am
    #1
    cornbb
    Registered Users, Registered Users 2 Posts: 6,790 ✭✭✭


    Hi guys, hope someone here can help me.

    I'm supporting an application that uses an Audio Unit plugin for sound synthesis. The plugin is added by our installer and there is no problem with it 99.9% of the time. However on one customer's machine the plugin is not being found. Is it possible that occasionally, AU plugins are not supported in OS X? If so, how can I find out why, and how can I fix it? Thanks all.


Comments

  • #2
    Oriel
    Banned (with Prison Access) Posts: 5,154 ✭✭✭Oriel


    Garageband supports AUs, if that helps.


  • #3
    cornbb
    Registered Users, Registered Users 2 Posts: 6,790 ✭✭✭cornbb


    Oriel wrote:
    Garageband supports AUs, if that helps.

    Not really, but thanks anyway.

    Just realised that my original post should have said "Is it possible that occasionally, AU plugins are not supported in OS X?" as opposed to "now supported"

    I guess thats the crux of what I'm asking. I had assumed AU support was universal across OS X installs, but does anyone know if there's an exception to the rule?


  • #4
    babypink
    Closed Accounts Posts: 1,250 ✭✭✭babypink


    i had assumed this too....


  • #5
    Oriel
    Banned (with Prison Access) Posts: 5,154 ✭✭✭Oriel


    cornbb wrote:
    Just realised that my original post should have said "Is it possible that occasionally, AU plugins are not supported in OS X?" as opposed to "now supported"
    Ah, that changes things with it being a completely different question and all! :)
    Sorry, that's my knowledge of OS X and Audio Units.
    440Hz should be able to help you out.


  • #6
    440Hz
    Registered Users, Registered Users 2 Posts: 6,424 ✭✭✭440Hz


    Ahhhh work wasn't supposed to start until 9:30! Guess my holiday ends here sigh. We'll have a look at this in the morning cornbb, was hoping that would have been solved by now :(

    Just on a general note for this question though, there is no reason why any installed AU should not be found by OS X providing the OS version and AU version are compatible. In general (and I know you have done most of this already but) a couple of obvious things for others which would be worth checking are the path for the AU, if it is being shared with another host application, version compatability (as mentioned) etc.

    I have a few ideas on the problem ,will look tomorrow and update this with any info (if any) for everyone else's benefit


  • Advertisement
  • #7
    ZENER
    Registered Users, Registered Users 2 Posts: 6,163 ✭✭✭ZENER


    Some apps that install AUs put them in the applications directory rather than the correct location in the Library/Audio/Plugins location. This means that other apps don't see them because these are looking in the normal location. Perhaps copying the plugins to the /Library/Audio/Plugins directory might help ? Also try putting them in the <username>/Library/Audio/Plugins.

    I had an issue with Peak a while back in that it wouldn't see all the plugins I knew I had on my system - the above solved the issue.

    ZEN


  • #8
    cornbb
    Registered Users, Registered Users 2 Posts: 6,790 ✭✭✭cornbb


    Hi ZENER, thanks for the response. We've already checked with the customer that the AU is correctly installed at /Library/Audio/Plugins and running the auval tool at the terminal indicates that the plugin is found and functioning properly.

    This seems to mean that the problem is with the host (our app) not the plugin.

    Argh :(

    /bangs head off wall


Advertisement