On a mac, will core audio always be item 1, and what is the PC equivalent?

    Mar 13 2013 | 11:11 am
    Hello all, just putting the finishing touches to an app I've been making for OSX. I want to preset the audio driver/in/out to [core audio] [Built-in input] and [Built-in output] and was wondering if, in the following example, will these settings be menu item number one on all mac systems?
    I have only ever used a mac, but I want to make the app for PC as well, so just another quick question - what would be the PC equivalent of [core audio] [Built-in input] and [Built-in output]? I need to avoid using any built in microphones as standard to avoid feedback loops.
    Many thanks.

    • Mar 13 2013 | 3:55 pm
      Perhaps I'm being dense, but parsing your request . . . I can't for the life of me figure out what it is you actually want to do?
    • Mar 13 2013 | 4:07 pm
      Sorry, I probably wasn't too clear. I've built an app, when the user turns it on I want it to default to core audio as the driver, built-in input as the input device, built-in output as the output device. I want to make sure that regardless of what mac you open the app on, and regardless of what other audio drivers you may have installed, that the application defaults to that driver, that input and that output. Thats why I need to know if those settings are always going to be item 1 within the umenu that is generated by [adstatus] in the example code I gave.
      I also want to find out what the windows equivalent of core audio is.
      Thanks :)
    • Mar 13 2013 | 4:30 pm
      I got that far - it's the seeming contradiction between autoselecting the built-in inputs while somehow managing to avoid using the built-in input (mic) that's throwing me.
      There isn't really an equivalent to Core Audio on Windows anyway, so you're SOL there. If I'm not mistaken, the first entry in any menu on Win will be "Primary Sound Driver" - and this could be anything from from the crappy Microsoft DirectX stuff to the marginally less crappy WASAPI stuff.
      It'll end in tears! ^_^
      Best bet? Allow . . . in fact positively encourage the user to select vendor-supplied ASIO drivers (or obtain ASIO4ALL if they're using the onboard codec).
    • Mar 13 2013 | 6:10 pm
      Why not just set them based upon the symbol? It has the drawbacks of not working in other languages, but should be reliable with differing setups in a given language.
    • Mar 13 2013 | 8:28 pm
      Hi, and thank you both for the input. The problem with using the built in microphone on my macbook pro is the feedback. Mac, in their eternal wisdom, have placed the microphone right under the left hand speaker which results in howling feedback the second the app is opened. This is why I have to auto select the jack in and out ports on the computer as standard.
      So if you wanted to select the standard audio jack input/output on a PC what would you select? The trouble here is that I am building this app for anyone to use with the presumption that they will be useless with technology. With the demographic we're talking about the very mention of an audio driver would make them sweat! The app needs to be turned on - and work with the minimum of fuss. I have that pretty much sorted on the mac now (thanks Chris) it's just the PC version I need help with...
      Thanks again for your input and help guys! :)
    • Mar 13 2013 | 8:58 pm
      No worries - not that I've been much help!
      This is an odd one for anyone doing pro audio on Windows precisely because one wouldn't dream of using anything except ASIO, since Microsoft's efforts on this front have (over the years), ranged from the laughable to the barely adequate.
      Is latency likely to be an issue at all?
      To add to what I already said re: Primary Sound Driver - this can also be ASIO . . . because it's just whatever one assigns to be the default audio driver for the system in Control Panel > Sounds.