Audiobus: Use your music apps together.
What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.Download on the App Store
Audiobus is the app that makes the rest of your setup better.
About Atom, Audioveek, where we are and what's next
How have you been?
It's a while now since I've been active on the forum. I'm not glad about that either. Been working on some demanding things over at Mozilla, and since I'm pretty bad when it comes to context switching, I can only focus on one thing at a time. But hey, you folks are helping me get better at it!
My lovechild Audioveek is being taken care of. I still have all the post-its with all your feature requests. And I still enjoy making music and working on Atom.
I'm looking at that top-right messages icon on this forum, and the red badge scares me. But I'll do right by you and make sure I reply to all of your messages. There's a few recurring themes that I've also been answering on the Audioveek support website, so by now I've got some answers ready!
Here's some technical context for the delays: After the last release, Apple screwed me over a bit (though I suppose it's maybe equally my fault). I've been using (abusing) Swift, the programming language in which Atom's UI is written, in various ways which weren't publicly supported. For science! And of course, speed and efficiency. But with the recent versions of Xcode and Swift, I'm unable to build and submit Atom to the App Store, since the latest Xcode literally cannot compile my code. I've noticed this issue around late May, and tried to work around it for a few weeks after that. However, moving forward, I'm uneasy with this situation and using too old versions of Xcode, so I've decided to rewrite Atom from scratch.
That... that is going to take a bit of time to finish. But I've already started. And I'm pretty far along.
If there's one thing that impresses me in all of this, is your patience. I'm putting a lot of love into Audioveek and Atom, and I see the fruits of that reflected on this forum.
 For devs: this isn't about using undocumented APIs. This is about using function initialization via lazy vars, combined with partial key paths for makeshift reflection on Swift classes. Doing those things helped me implement something like React props propagation (top-down single store application state) on CA layers, which gave me debouncing and caching for "free". This meant that the UI never updated when it didn't have to.
 The compiler crashes while compiling. Yes Apple knows about it. Yes Apple isn't prioritising fixing it because it's always been a hack and a technically unsupported aspect of the syntax.