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
@lostress I'am not comparing but I will say what I already said - bm3 unresponsive screen prob How the heck am
I meant to make a beat - now there are UNDO probs - then bug bug bug bug - no thanks thats wack - especially when everytime they advertise a new update with all the "cool" new features - be nice to be able to use them - at least in GR16 even if it has it limitations my workflow flows - and like I said I paid for the software - a few bugs here and there ok but there's way too many in bm3 for me to be able to get a "pro" production completed.
Weird, I never really had issues with unresponsive screen in BM3? Can easily believe it though. Definitely rough around the edges still. I think it'll be a year or so before it all gets worked out. Huge app. Small team. Sadly it's the only app on ios that vaguely does what I want from my main daw/sampler environment so I suffer onwards in the meantime
@lostress To add - I'am frustrated with bm3 because I actually think it has excellent features - just a shame that as it's laden with bugs it's hard to use it - the bug at the moment is a very fundamental one - try to UNDO" after duplicating patterns the app crashes - whoever is doing the "testing" has got to be on another planet. And I'am not talking about the beta tester but the actual developers at INTUA.
Just tested this with a 'pattern duplicate > undo' frenzy. No crashes? Must be some other logistic also involved in the issue? Can't replicate it here..
yeh dude they fixed the screen bug but now added some new features in 3.0.9 which are excellent additions but if the app crashes for simple functions it's naturally off putting - the sample edit screen i shaky a - i mean come on its a sampler - all my other apps dont have the after touch jumpy issue - GR neat and tidy and I have way more confidence in the fundamental workflow and it's new - A few things here and there like extra effects as a paid upgrade / multi output routing /Inter App Sampling/ Direct Line In Sampling and GR will be a seriou contender - I don't want to be a nerd I want to make beats.
Are you on 3.0.9 Goto the forum - its Duplicate twice then UNDO - anyway its on the beatmaker forum .All iam saying is for the price it is the amount of bugs aint fair - if it were half the price then fair enough - Auria/Cubase etc which fall in the same price bracket not half as many issues
Haha
I know what you're saying. BM3's all about templates for me. Nerd out for a couple of day making templates and then it's waaaay fast/simple to do whatever you want it to in most cases. Simple or complex. You can define your own set of limitations, lay out what you want in a template and kill some of the general workflow ballache 
FWIW I never noticed the 'shaky' thing you mention? Either way would definitely rather load/edit samples in BM3 browser/editor than the tiny GR16 one 
@lostress cool
@lostress I'am back on my s950 using it with GR
Yep I'm on 3.09. Only post I see on BM3 forum says it happened once to one user and never again after rebooting after update? You made it sound like it was happening to you and every time you did it
Auria and cubasis have been around a lot longer than BM3 to sort themselves out and slowly add features and bug fix. And very different daws to bm3. Much simpler... Intua have taken risk/shown a bagfull of ambition. I'm fully behind them for not playing it safe. Just wish it didn't require me being this patient
@lostress I hear ya -I'am only being like this because I think Bm3 is excellent in many ways - anyway there is a prob with 3.0.9 which is why 3.0.10 is on it's way - right lets get bk on topic - GR the future - Peace
All good, both are great apps
for sure I agree -
Got it - thanks. It means you can pick a part of the sequence and play about with the notes/ octaves till you find one you like- before moving on.
It’s in the manual- though it’s in the chord mode setting- which I don’t use.
If app copies (or is inspired by) some elements from other app or hw - this is not argument for anything, developers simply use other developers ideas and build news stuff upon them..
That's normal thing and it doesn't affects how app will be stable in any way .. I work as coder, and maybe it will sound hard, but number of bugs in app is simply direct measure of how good is coder .
Some coder have more bugs, some less ... Bugless SW doesn't exists, but the number of bugs in BM3 from it's first release was really enormous ..
Plus, last thing - i would not use "stolen" related to GR16, it sounds too offensive - GR16 is unofficial clone of Electribe, that's very clear and nobody is trying say that no. Not even Jim .. Talking about stealing is a little bit over the border ..
IF we should talk about stealing, then BM3 copied of lot app elements including basic app layout, menus, etc. from iMaschine 2. So BM3 is bettter candidate for this term
(althought i think it is not correct to use it even in this case)
Lol. Of course it makes a difference?? An original concept is far harder to design and test than mimicking something that is mostly copied and already tested by another company/General public and known to be a solid workflow. Ask Behringer
If you're genuinely saying that GR16 is as original and as complicated and hard to code and keep bugs out as BM3 is, then fine, but to me that's just nonsense. And if that's not what you're saying then you're just arguing for the sake of it.
The banks system of BM3 is unlike any other daw I ever used. Not to mention making that work alongside all the more traditional daw stuff and scenes and current/future ios stuff like rozetta and AU in general. GR16 is basically a software electribe with couple bells and whistles. In fact I'm sure you said that yourself about a hundred times in this thread
Saying all this, I never used imaschine so can't say how similar BM3 and imaschine are. But yeah obviously almost everything advances from what went before it to some extent. That's a given...
And I wasn't saying there's anything wrong with GR16, just that it is what it is...the concept/workflow is almost entirely taken/stolen/lifted whatever word doesn't offend you. I didn't mean to upset you or jim... So I take it back, you're right, it's nothing at all like an electribe workflow and feature set
Lol...
“There is no such thing as a new idea. It is impossible. We simply take a lot of old ideas and put them into a sort of mental kaleidoscope. We give them a turn and they make new and curious combinations. We keep on turning and making new combinations indefinitely; but they are the same old pieces of colored glass that have been in use through all the ages.”
― Mark Twain
Yeah everyone knows there are no totally new ideas. But even more so with something that is modelled almost entirely on something else. And less R&D, feature refinement, unforseen uses/bugs, risk for something like that.
Not sure what we're arguing about really? Seems Dendy wants it both ways... I ask for new features and I'm greeted with 'but it's just an electribe clone for performance!'. So then I call it an electribe clone and it's 'Oh, well everything is a little bit of something else...'. Nonsense argument.. Not down for taking part
Man. Again. U don't know anything about coding. I code last 25 years. I'm deeply experienced senior developer, it's my dayjob.
The thing is. It doesn't matter if app is inspired, or even copies VISUAL design of other app or HW have NOTHING to do with fact if it is more or less buggy .. At the end it's developer who have to write every single line of code and quality of that code isn't affected in any way by the fact, if he "steal" UI/UX concept or develop something own, completely new unseen ..
How app looks doesn't affect in ANY WAY how it is stable and how buggy (or bugfree) is coded.
Number of features CAN affect it, using third party APIs (IAA, AB, AUv3, ...) definitely can affect it (and in many cases it's out of control of develooper of app which uses third party APIs, for sure for lot of crashes is not resposible host app put specific IAA / AU plugin)
If we are talking about BM3 - in my opinion biggest problem in this case was poor beta testing. Maybe beta testers didn't their job propertly and deeply enough, i don't know. I worked on lot project last 25 years (as single dev but also as a part of smaller or larget team) - and i must say i never experienced in any project soo much bugs after release - even with project more complex than BM3 and GR16 together ..
Yeah, that's ok, that's just because you know nothing about coding
Don't take it wrong .. it's not mentioned to be offensive please ! I'm just trying explain to you something where you obviously have no knowledge. Believe me, i really deeply know what i'm talking about.
Whole BM3 is copied iMaschine 2 / Maschine HW concept, specailly in case of iMaschinge down to the level of menu layout and other UI/UX stuff ..of course added some new things, but basically it looks like iMachine 4 :-)
Check some screenshots of iMaschine, Maschine desktop SW and Maschine HW controller and you will see.. there is completely nothing groundgreaking new in BM3 .. Just taken existing pieces and gluing them together and adding some more stuff ..
Which is NOT BAD thing ! Just saying it is far away from groundbreaking new concept
Lets just spare the thread on this one and agree to entirely disagree.
Deny has it right about coding in my opinion. I have been a programmer for a similar amount of time. With 18+ of those years getting paid for it as my main source of income.
If two painters paint an apple, they both will have a different end result. Different shades of red, different techniques used to apply the paint, different starting canvas, etc... Coding is very similar.
It's this I often get mad of on this forum!
I have three iPads (Air2, 12.9" gen1, 12.9" gen2) - AND no one crash when Undo:ing things...
I have tried several patterns, banks, projects etc.etc... No problem...
@stormbeats - don't BS when it's not a big problem...
Quick someone new post some Grooverider music
My point was that it's going to be much less problematic to paint an apple if you have seen an apple before and you have one in front of you. Than if you haven't and you don't
And also that GR16 is like painting an apple on a white background. BM3 is a bowl of fruit in front of moving scenary.
Thats probably enough with the fruit talk
Basically I just said it was unfair to be harsh on BM3 for having bugs and not having squashed them all yet whilst using GR16 as a comparison to measure against. Intua are clearly still working out parts of the workflow concept out via feedback and there's a lot more moving parts and workflow refinements to be done in bm3 than with GR16 and it's not only bugs that BM3 have been focusing their time on (implementing midi AU and a TON of other tweaks and additions). Personally I'd rather have access to it now as it is than have to wait til it's more bug free.
No big deal though. Didn't mean for it to become a big derail!
But man, how are you going to pound a dev for feature requests, and then be this disrespectful in describing their work?
I'm not going to.. GR16 is what it is. I'm over my initial optimism for development
FWIW my saying the concept is mostly stolen isn't disrespectful at all imho. He already said or implied concept was mostly taken from electribe. You take something without asking or paying, thats kind of the definition of stealing
It happens tho. In software, hardware, music, film, whatever... I wasn't saying it in the sense he commited some kind of crime... I'd have thought my meaning was pretty obvious? But instead people seem to zone in on whatever is the easiest thing to twist and turn in to an argument.
Being an owner of the Electribe 2 I'd say GR-16 has already passed it when it comes ease of use especially when it comes to editing and automation. The area where the Electribe 2 still shines is more varied factory content when it comes to sounds/samples but that can be remedied with user samples when needed...
I trust that Jim didn’t make this without knowing his bases were covered in some way. Also it’s powered by an original sound engine, 202 or whatever. So that leaves nothing but the skin. Feature list wise it already surpasses its inspiration according to some. And these features can be found in countless iterations anyway.
But the bottom line is this: I have it and I love it.
Yeesh, you are a winky-faced handful.