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
Yooo. Yeah before I released I didn't even know exposing the parameters was an option! At least I know how people are having those little dials next to their apps in AUM now. Next update will have all the things exposed hopefully. Not sure how I'm going to handle the bit board buttons at the moment though.
Regarding the performance page, not sure I follow what your suggestion is?
All the controls fit on one default sized screen - how would you change it ?
Ahhh, that makes sense!
Preach brother! 🤜🏻
Glad you like the app btw! I made another thread about it so forgot to update with a link in here.
Nice! Whats WOW btw?
Sugarbytes WOW filter. It has just been updated to AU3. It's a crazy thing that can be modulated in all kinds of wild ways.
Ahh nice! Yes I've heard of it. I have Turnado which I was impressed with.
Bought. Will be useful on stuff and when I specialise in auv3 drums. Volca drum has bit crush per step with adsr per step ( I think )
Its a good effect for it to have then - its limitations.
Going to see what scatter is like on a set of drum audio.
>
A couple of thoughts about the bit board buttons. One of these maybe:
I can see some cool rhythmic remote changing of the various bit states as being ultra cool.
Originally I was thinking cc per button as you say, but actually I like your midi note idea much more. Its not like they're being used for anything else. Maybe it would be better though to map the invert buttons to the sharps.
So like:
that way it looks a little bit more the way the bit board as represented inside Bit Maestro.
What do you think? Would it get confusing having the Es and Bs skipped? I guess I can just try it out and see what works best, but think midi notes is the better idea atm.
If you wanted to get really crazy you could also map reordering the bits... by having like C5-C6 to choose which bit you want to move, and then send the velocity 1-8 to decide which position you want to substitute it for or velocity 11-18 if you want to insert it and shift over the bits.... but honestly I can just imagine that being more of a nuance with people doing it accidentally more than anything.
Feel free, it's your app !!
Interesting. The white keys/black keys idea seems pretty easy to remember. I like it.
@JamMaestro
Season to taste this is JUST an example of what I was thinking
Could work all on white keys with alternate octaves as the invert too?
@JamMaestro The reason I suggested apeMatrix previously is because it is an AUv3 host designed around the idea of automation (and interconnection - but not yet automated interconnections, hmm).
If you want to automate a bunch of parameters, apeMatrix makes it really easy. I suggest you add it to your arsenal of hosts and write it off as a business expense.
@audiblevideo dudeeee..... 100 points for effort! I'm really impressed, you got the font right and everything! I understand what you mean now, try and keep all the main controls on one screen and have anything performance related on another screen. I see what you're saying and I understand the merits, not quite sure that it would be necessary on bit maestro (I try to design it to be pretty playable as it is), but I will definitely bare it in mind when making future apps. The reason I made the 'full screen' version of bit maestro that I have is I wanted something that would work better on a portrait iPhone, which is why I have laid it out how it is.
@Krupa yeah that was @espiegel123 's original idea. Pretty good too, only thing is there are 8 buttons and 7 white keys, so would it go C3-C4 and C5-C6? or D4-D5 ?
@mojozart cheers for the tip. Maybe I will check it out, or at least see if the owner would be open to trading promo codes 🤷🏻♂️
@JamMaestro doh, yeah, i can’t count up to G 🤣
@JamMaestro @espiegel123 I was wondering about two-note chords or sequence for bit position. As a chord One octave of white notes for the position and another for the bit. Or a two-note from-to sequence in the same octave range. A5 C5 could mean move the 5th bit to the 0th position.
There are no guarantees in what order midi messages are delivered, so you want to avoid a system where you have to enter 2 notes and have bit maestro waiting on the other end to receive notes. Say you wanted to automate it in a sequencer for example, chances are its going to be sending out both those midi messages at almost exactly the same time. IF you were going to do a way of updating bit order via midi you'd want to contain the complete instructons in on message.
@mojozart good news! ApeMatrix dev was kind enough to swap some promo codes with me
Makes sense. I was thinking about performing rather than precise sequencing.
Oh I see. True, but I think if you're performing at wanting to do that its going to be much better for you to just use the GUI to do it in Bit Maestro. Would get pretty damn confusing otherwise I think.
I think your white key/black key proposal will work well for sequencing or perform and one could easily enough write Mozaic or Streambyter scripts to create their own mappings.
@JamMaestro I hope you are planning on explicitly exposing the AUv3 parameters for AUV3 hosts like AUM so we can create our own MIDI assignments rather than just being limited to a fixed MIDI map.
@InfoCheck Don't worry - theres another entire Bit Maestro thread on here that is mostly just people asking for that same thing
... I'd be scared not to at this point!
Thank you for your consideration, I’ve really been enjoying the app.
Love this plugin!!!! is there any documentation? I guess is there a way to control the gate threshold??
Hey, I love this too! Is the manual for the oto biscuit (semi clone>)? gonna be usable or where is the documentation or manual, like iLLaFentT asked. I just want to know why im getting good results and what inverting does on each step etc. Thanks what beast. I actually don't know at al what is going on im watching sound test room, but still I get nasty and sick tones so all is well.
Is your question, what is the underlying principle of this app? It has a good explanation when you press the question mark icon next to the bits. also an easily overlooked feature: you can swap bits by pressing and holding on a number.
Thanks, I DID miss that and want to know if this is a semi biscuit OTTO type clone inspiration? That would help but I will look for the elusive ? mark! Thanks and wapping bits even doesn't make sense to me, I am an effects madman but know little of this kind of bit crushing. I mean I know I like 8 bit or 4 bit with a horrid sample rate for low fi and I like a gate, so I don't ruin the mix with unholy fuzzy madness.
If you haven't, you might want to read the thread from the beginning. This was inspired by the Biscuit
I also find it pretty hard to wrap my head around what bit swapping will do. I mean, sure I understand the principle, the app reduces the signal to 8bit and you swap/invert/"disable" one of the bits. but what will it actually do to the sound?
For disabling/inverting,mI assume the result is this: You will get varying amounts of "jumps" while the signal goes through a full period. If you disable the lowest bit, you basically reduced the signal to 7 bit. if you invert the lowest bit you will have a discontinuity/jump up to 128 times per half period. if you invert the highest bit, that will only introduce a jump once per half period. So basically, with those jumps you add additional square waves to your signal. inversion vs disabling a bit will lead to square waves of twice the amplitude. the frequencies of those square waves depend on 1)which bit 2)the frequency of the source signal 3) the amplitude of the source signal.
Did I get that right?
Thanks about the biscuit clarity! Last post: your a cool mad scientist so im gonna go ahead and say your more correct than I.
@dobbs @oceansinspace yeah it can be pretty confusing imagining what all this bit manipulation does to the waveform. Originally I made that visual waveform in the center of the app just for testing purposes so I could understand what effect the different algorithms I was trying was having on the sound, but I found it so useful in architecting your sound and understanding the effect of the different bits that I left it as a permanent feature.
Your explanation was good @dobbs. Basically the difference between this 'biscuit' style crushing @oceansinspace is that normal crushing will add the steps into the waveform at equal intervals (so it looks like steps), where as with this you can carve out more specific rules to it. In terms of what bit swapping does, basically imagine you put the '16' bit in place of the '1' bit. Now every time it would fire the '1' bit (so every other number, eg 1,3,5,7,9....109 etc) it will now add 16 to the value instead of 1 (so counting up from 1: 16, 2, 18, 4, 20, 6). As you can imagine this can have a pretty harsh effect on the waveform (where as before it was just going in a straight linear line up, now its going up, down up, down, up down in a zig zag).... but can also create some interesting sounds with it too. I made the undo button there to helpfully undo something that isn't so pleasant 😂
No docs 😂 but you can click the (?) button to the right of the bit board... by gate do you mean the limiter?