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 StoreAudiobus is the app that makes the rest of your setup better.
Comments
I look forward to this new direction Bram. That I will buy in is purely a given.
As long as they keep midi events list in an AUv3 render call I'm happy - but not sure if Apple are supporting midi effects AUs, so might have to swap to audio effects....
I think I must have some Dutch ancestry. 😅
That’s even supported in Garageband, so that should count as ‘supported’
The language does seem quite accessible so far, for the likely user base. Seems like a good design decision.
It already looks like something I could learn to use and I hate scripting (even though I have to use it in various other mediums like animation/design etc). Anything with actual logical english helps so much. (for english speakers)
I've put them back in. You can now have up to 1000 global 'meta' variables/arrays shared across all instances. I'll put a big warning in the user manual about the risks involved in using these (nothing destructive, but you will have a hard time debugging your script when another script is messing up your global variables in the background )
We should be in luck as @brambos loves writing documentation and the Dutch are famed for their direct communication style.
I look forward to the tsunami of scripts people far smarter than me will be sharing.
That looks real cool Bram!
This is what it looks like when Bram has had it with all of our feature requests.
Immediate impression (and partially hope): Streambyter is to Perl as Mosiac is to Python. (Or maybe Javascript :: jQuery?)
Both Perl and Python are powerful AF but one is considerably more pleasant to spend an afternoon (or year) with. Particularly when it comes to understanding other people's code (or coming back to your own code 6 months later)... perl can inspire you to consider hurting puppies.
Perhaps (some day) custom events would fit the syntax model a little better than custom functions?
Yes, indeed! But not for 1.0
Two questions that came to mind:
I think I need to move to Holland. How's your asylum laws? I'm a musical refugee!
I have a feeling this tread is going to end up blowing the Drambo one out of the water for size/growth if The Bram Bros don't pop this baby out soon!
I just recently stumbled upon this big news, it's a combo that promises incredibly exciting future: Brambos - one of the heroes of iOS music app scene, endless flexibility with real programming and Audio units standard.
Only I was a little sad about your attitude towards GUI controls. Yes, you can route the signal to any MIDI AU or app, but it's not really the same (not to mention, many MIDI AUs don't receive MIDI, only send). Here you'd have the ability to e.g. put labels on knobs (programatically). This is not possible via raw MIDI. I can also imagine much more creative options, e.g. control RGB of pads. You could program a step sequencer with position indicator if you have a row of e.g. 16 buttons and control over RGB. But with only 4 buttons, I don't see much use. Honestly, I don't see much use of only 4 pads at all...
I would even pay for extra IAP (or maybe a separate apps?) to have only knobs, only pads and maybe also only XY. This way you can be more modular, in AUM you can resize the window and hide as much controls as you need for a specific instance.
The other option would be to show more rows of the same GUI (4 x pads, knobs and XY) while having AU window maximised. Also we would need a button to hide the code editor and that would reveal maybe two more rows of the same controls. This is only according to your screenshot, which is in portrait mode. In landscape, there is only option of having them in multiple columns (and maybe 2 rows? So 2x2?) I am not sure where the code editor would be on landscape, but if it would be on left/right, this is a viable design.
Nevertheless, I am super-excited about this, even if you'll stay opinionated. Crossing fingers it'll be a smooth ride a we'll get this in our hands as soon as possible!
Point taken, and taken on board. Many things are still in consideration.
However, what I'm hoping with Mozaic is that instead of worrying about things that may not be possible (yes, limitations will always exist - with every usable product) we can also wonder about all the things that are now suddenly possible.
Every other app released since 2016 has a UI with boring 4x4 pad controls. Perhaps we don't need more plugins with a vanilla MPC layout, but stuff that is a bit more left-field You can use those 4 pads in conjunction with the XY controller to create something a little bit more original perhaps, something that does not yet exist? Limitations breed creativity.. and I will show examples with the factory scripts
Perhaps I will still decide to offer a limited set of different control layouts, if I can think of an elegant way to integrate it. If anything, I want to stay far-far-away from WYSIWYG layout editors
I can see the advantage of offering a modular ui, add 3 sets of xy pads instead of dials etc, etc. But in case that won't happen, in theory it would be possible to use a hardware controller however you wanted? i think I can see me using it more this way. Or as much anyway
I have decided there will be a limited set of different layouts, which can be selected programmatically through the script...
Great news
Just one word: drooling.
That was the sneakiest of peaks!
Yes, but the beginnings of much more. Now implementing a boring 16-pad layout
Awesome!
[peeks]
I think this is most excellent!
Nice. And don't forget pad and knob labels