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
@jimpavloff if poss can you make the SHIFT button on/off bit difficult chopping slices holding the shift key
@jimpavloff maybe as an option in SETTINGS
You can change the pitch, volume (velocity), and duration of the slices in the slice edit window, as well as adding time shift and strokes.
Edit: and set chance.
@pfrf ok cheers for the tip
You have to tap edit then slice. If you tap slice then edit you end up in seq mode.
cheers
Here’s something I did 100% in GR-16 with only stock sounds, no imports. It’s going up as my WeeklyBeats posting for this week. Not my typical fare, but I had fun.
@wim could completely hear Steve Winwood singing over some of this
He wanted to, but we didn’t have a decent mic handy.
+20 for this!
This. Maybe via long pressing the SHIFT button?
And make it BIGGER please..
good suggestion
i agree 100%
@jimpavloff and anyone in the know - I'am in slice EDIT STEP page trying to affect different velocity for each slice but all the slices seem to be all globally affected not seperately?
ok iam sort of working out the step editing now - bit confusing but will meet the challenge
update out now. The copy/paste works again. I can now resume making FAT LAYERS
If you could midi map everything - transport, knobs, even buttons (I have an mpd232) this would basically be an app I would make sweet sweet love to every night
When inputing notes via the pads in step edit mode- how do you change the octave range of the keypad without having to leave edit mode- change it then return to edit mode again?
I believe holding shift changes octaves.
Edit: never mind that’s for pure step editing not pads. The hell are you doing in edit mode anyway?
No, you're right. Holding shift changes and touching 1 or 4 moves up or down an octave respectively. Shift-2 or 3 selects octave 2 or 3 respectively.
I think that changed along the way with an update because I don't remember having to hold shift before.
Still gotta know how to shift octaves even when recording rather than editing notes.
Shit I was right. When you record in keys, chords, or slice mode you just hit those buttons no shift required for octaves. Jump and sequence is bars by default. Trigger, mute, erase don’t do anything with those buttons.
When you're in Keys, Chords or Slice mode, bar buttons will always change the octave.
When you're in any Edit mode, bar buttons will always change current bar being edited.
If you're in Edit + Keys/Chords/Slice mode and want to change the octave, not the bar, then hold SHIFT + press bar buttons.
Has this thread set a record yet with number of posts? Apparently I gave up 786 ago, but do love the app!
The beat maker3 release thread was twice as long! We haven’t even reached a ridiculous level yet
If you weed out the 80% or so posts from the BM3 thread that deal with bugs then this one is way ahead. If @jimpavloff really wants to really pull ahead he's going to have to screw up way more often.
Ahhh ... thanks for the clarification. That one threw me off. I'm kind of like "when in doubt press shift" mode, so just got around without a whole lot of thought.
@wim i agree - I'am loosing confidence in BM3 the new 3.0.9 has bugs already - UNDO functions etc - also it took some people 7 hours for it to install - for a progrom in the high price bracket I'am not one bit impressed
To be fair it's pretty harsh to compare BM3 to GR16 in terms of difficulty for the devs to make it solid. The concept for gr16 has been almost entirely stolen from something already proven to (mostly) work (electribe). And the feature set has been limited to a level that really shouldn't have any issues (no AU/external considerations, limited cpu taxing down to sample size, polyphony, fx limits, all samples added to cache etc).
You can potentially do a million times more in one BM3 bank than in the whole of GR16. No way to test every scenario and it must be a nightmare for devs there to get a grip on it all as well as bug fix the more obvious stuff
Not really comparable apps in terms of depth/complication. Hence the appeal of GR16 for a different workflow.
Bm3 has some quite unique/risk taking workflow concepts that are taking some time to smooth out overall. And I guess that's slowing down the more obvious bug fixing too ('undo' like you mention). The intricacies of options in BM3 and subsequent dev maintenance are pretty much endless.. Different level of app/task entirely