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.
Drambo by BeepStreet released
This discussion has been closed.
Comments
Well, I did a hard reboot, updated AUM, and it still didn't show as an AU MIDI processor. So then I completely deleted Drambo and did a fresh download (not an update). That did the trick. That's the second time that has happened to me--where an update didn't actually update but deleting the app and starting with a fresh download worked. Hmph.
That's strange. Were/are you subscribed to a Drambo beta? That could affect updating.
Nope, not involved in beta at all.
Well I do use the Graphic envelope, it's just kind of inefficient.
Can you chain Env flex units to build an ADSR? If I could work out how to do that I'd stop complaining, I promise...
The only little missing things in the Graphic Env are:
I've had this kind of very strange behavior a few times with different apps since iOS 11.
Actually the big thing that's missing is parametric curves. I fake curves using lines (and the interface for this is excellent), but I would love to be able to create a curve and bend it.
You can easily draw curves but you can't draw functionality. Approximating curves by a few line segments works very well in practice.
I wanted to see how Drambo behaves inside a BM3 bank, and whether BM3 macros could be configured for some Drambo targets. Sadly, Drambo doesn't expose any AU parameters in BM3, AUM etc. Has this been discussed before? Could there be some generic AU parameters available (similar to how Mozaic does it), and what about e.g. the scene morph slider?
Drambo will host AudioUnits soon.
eeeh.. Drambo is modular... it depends on what you build in it, there are no "global" parameters
I would disagree. If you know the exact shape then it's reasonably easy to get it right. If you like to play with the curve (something I do a lot, as it makes a huge difference to the sound) it's kind of a pain.
The envelopes in Nanostudio are very good.
No AU params but full MIDI control, including scene pads and morph slider. Use these instead.
@cian I agree that curve shapes are nice to have but not as important as ENV retrigger and sustain+release phases.
Ok, full MIDI control is good (haven't studied it yet). Not quite sure whether a BM3 macro could be assigned, though. I guess I would need a midi app in-between, one which also exposes some AU parameters.
@noob I guess one could allow for a small set of global parameters to act as exposed AU parameters (if the developer wishes so). Mozaic also depends on what you build and script, but there you have "Knob 1", "Knob 2", "Pad 1" etc. available as AU parameters (even if you don't use pad 1 in your script).
Woohoo 🙌
Fair enough
Whoa great! I thought that we were still in proof-of-concept territory
I feel as a corrective to my moaning above that @giku_beepstreet is constantly improving the app, I use it all the time and I understand there are only so many hours in the day. I just want it to be better...
🤤
Is there a way for Drambo to share the AUM/AudioShare folder?
You mean via its WebDAV interface?
I mean directly from the sampler. Just select a file from any folder on the device instead of importing.
Ok... Thanks..
Sure, that's exactly what "Import" does.
So, if you “import” a file or folder, you are just creating a link to the file or folder and not actually copying everything into the Drambo folder?
No duplicate files all over the device?
OK, now I get your point. Only @giku_beepstreet can answer that.
You may be mistaken on this point from the point of view of the operating system. The iOS file system doesn't usually make a physical copy of a file unless it's changed from the original. Instead it "links" to the file. Even though to the app it seems like an individual copy, it's just a pointer to the original.
(In fact, it's even better than that: if a file is copied, then one is changed, there's still only one copy, only the changes between the two are stored - again, transparently.)