> Two things: first, just a quick check that you never intend for your > application to work on any other platform. Be warned that using Apple's > objects like AUGraph will render your code 100% useless on other platforms.
I appreciate the heads up, but I'm so far in the hole there, it makes no difference. I'd be amazed if even 5% of my code would make any sense on a different platform. Most of the work is actually on AppKit stuff. The audio side of things is harder work, but so far less time consuming. Even if I wanted to port it to iOS, it would be a massive pain. > Obviously, if you're really 100% attached to OS X/iOS, then using the > stuff Apple provides makes sense. > I'm ok to keep it OS X only, unless Tim Cook announces iOS for Mac, and end-of-life for OS X. I think you should spend more on other mailing lists. This list is actually > one of the least helpful, generally silent technical mailing lists I've > ever been on. A few of us do try to help out people with certains kinds of > questions, but in general, I find it much easier to get information via > google than this list. I guess I've been lucky so far. Google and SO are great for a lot of things, but don't work as well if there's a question where one "doesn't know what one doesn't know." I've only dabbled in a few areas of CoreAudio so far, and been lucky, I guess, to get some good advice here. I also like knowing that the Apple teams who wrote the code are on these lists... well, probably the people who wrote the parts of CoreAudio I use now are long gone, but you never know!
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
