Since the new AV stuff just wraps CoreAudio, I'll probably start with Swift, and if the performance is unacceptable, rewrite the portions I need to in C. I think you get access to underlying data structures, so hopefully I can mix and match.
I should perhaps just heed the multiple warnings in this thread, but the new API looks simple enough that I think it will only be a few wasted days if I scrap it.
> If I was writing a sound editor (chortle - inside joke) and it was focused only on OS X
Well, I see on Wikipedia that you have reason to sound confident :)
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