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 Store

Audiobus is the app that makes the rest of your setup better.

Koala - the ultimate pocket-sized sampler

16264666768

Comments

  • @Janosax said:
    @elf_audio

    I’ve got a small issue with 4 bars sequence not starting on first bar (but on second bar) after playing a one bar sequence, look at this GIF:

    This is with Ableton Link enabled or disabled, so that don’t seem to be related.

    I’m having this same issue but within two-bar loops: if I play a two bar loop then play a one-bar loop twice, returning to the two-bar loop lands it in the loop middle (the second bar) instead of at the start.

    Regardless I just can’t say enough great things about Koala.

    FX Wet amount (not per effect but one that adjusts all) and HP / LP filters per pad and I think we’d be at the plateau.

  • Does Koala expose its MIDI port? If I load Koala into AUM, I can direct MIDI to Koala. But if I have Koala running without loading it directly into AUM, I see a virtual MIDI port called "MIDI Monitor" which seems to only exist when Koala is running, but when I send MIDI to that destination, Koala doesn't respond (at least not when midi mapping)

  • @elf_audio : is there a way to remotely (i.e. via MIDI) to delete a pad or record over it without user interaction? I implemented a sort of "endless looper"/take recorder in Mozaic that I use with Loopy and I'd like to adapt the script to Koala. What it does is endlessly (until you press stop) cycle between a number of buffers/loops/pads recording into them. This lets you keep a record of just last 'x bars' of your playing. It is super handy.

    Anyway, in Loopy there is a way via MIDI to clear a track (or record over it) without user intervention. Those commands (like clear/delete) that normally need user intervention treat a second triggering as confirmation.

    I can issue the Delete command but it requires the user to tap. What if a second issuing of the delete midi (in close proximity) acts as confirmation?

    The other issue for this scenario is that I'd like to be able to erase one pad while another one is still recording OR be able to record over an existing pad.

    Here are a couple of demos of what the script does with Loopy. I'd love to write one for Koala since Koala allows editing of the results.

  • FX Wet amount (not per effect but one that adjusts all) and HP / LP filters per pad and I think we’d be at the plateau.

    Self-edit: just found the ‘Tone’ slider per pad - holy sh_t @elf_audio - Koala really is a masterpiece.

  • @elf_audio : after experimenting, i just discovered that I think that I can do what is needed. While pad two is playing, I can send the delete MIDI note event on and send the midi note for another track which deletes the other track without interrupting the recording. At least that is what it looks like... I need t9 test, but if that works, I am very psyched.

  • edited February 26

    @espiegel123 said:
    @elf_audio : after experimenting, i just discovered that I think that I can do what is needed. While pad two is playing, I can send the delete MIDI note event on and send the midi note for another track which deletes the other track without interrupting the recording. At least that is what it looks like... I need t9 test, but if that works, I am very psyched.

    OOPS! Something odd is going on. After more testing, the behavior I described seems not to always happen. It might even be that when I got the behavior I was looking for that I had gotten Koala into a weird state...as I can’t do it at will.

    Sometimes sending the MIDI note I mapped to delete works as described above, sometimes it brings up a confirm dialog, and sometimes it does nothing.

  • @espiegel123 said:

    @espiegel123 said:
    @elf_audio : after experimenting, i just discovered that I think that I can do what is needed. While pad two is playing, I can send the delete MIDI note event on and send the midi note for another track which deletes the other track without interrupting the recording. At least that is what it looks like... I need t9 test, but if that works, I am very psyched.

    OOPS! Something odd is going on. After more testing, the behavior I described seems not to always happen. It might even be that when I got the behavior I was looking for that I had gotten Koala into a weird state...as I can’t do it at will.

    Sometimes sending the MIDI note I mapped to delete works as described above, sometimes it brings up a confirm dialog, and sometimes it does nothing.

    I think I have this figured out now. I just noticed that sending 127 turns the Delete button on and 0 turns it off. Knowing that I things are acting predictably.

  • Ah yes, I guess there's no convention for how to handle button presses with midi CC's so I chose one - if the number is higher than 63, it's a press, if it's below, it's a release. Different buttons have different behaviours on their press and release - e.g. the play button might start transport on a press, the delete button might delete on release - the point of that is so if you change your mind about deleting whilst your finger is down, you can slide your finger off the button

  • @elf_audio said:
    Ah yes, I guess there's no convention for how to handle button presses with midi CC's so I chose one - if the number is higher than 63, it's a press, if it's below, it's a release. Different buttons have different behaviours on their press and release - e.g. the play button might start transport on a press, the delete button might delete on release - the point of that is so if you change your mind about deleting whilst your finger is down, you can slide your finger off the button

    Something that I am running into is that sometimes Koala seems to be reverting to an old MIDI Mapping. A few days ago, I mapped the first page of pads to notes sent on MIDI Channel 12 -- but yesterday I remapped those pads to channel 1. What seems to be happening is that periodically, Koala reverts to thinking that everything is mapped to channel 12.

    I have not found a trigger for this happening. Note that this happens in a session in which I never opened the MIDI Map dialog. It is possible that it is happening after Koala crashes.But I am not certain. If it is then it seems to suggest that the midi mapping isn't being permanently saved when you press stop mapping -- and so if you crash and re-open you may lose the most recent mapping.

  • @espiegel123 said:

    @elf_audio said:
    Ah yes, I guess there's no convention for how to handle button presses with midi CC's so I chose one - if the number is higher than 63, it's a press, if it's below, it's a release. Different buttons have different behaviours on their press and release - e.g. the play button might start transport on a press, the delete button might delete on release - the point of that is so if you change your mind about deleting whilst your finger is down, you can slide your finger off the button

    Something that I am running into is that sometimes Koala seems to be reverting to an old MIDI Mapping. A few days ago, I mapped the first page of pads to notes sent on MIDI Channel 12 -- but yesterday I remapped those pads to channel 1. What seems to be happening is that periodically, Koala reverts to thinking that everything is mapped to channel 12.

    I have not found a trigger for this happening. Note that this happens in a session in which I never opened the MIDI Map dialog. It is possible that it is happening after Koala crashes.But I am not certain. If it is then it seems to suggest that the midi mapping isn't being permanently saved when you press stop mapping -- and so if you crash and re-open you may lose the most recent mapping.

    It just happened again. After remapping everything to channel 1, I saved the session explicitly. About 2 minutes later Koala crashed and when I reopened, it was using the MIDI mapping with channel 12.

    There is puzzling thing happening with the delete command. Sometimes, it is asking for confirmation when sending the MIDI command but sometimes it is behaving as i had hoped and deleting without the confirmation (when using MIDI CC). I have no idea if there is a pattern. To when it asks for confirmation and when it doesn't.

  • Is anyone else seeing CPU spikes (that result in audio glitches in all audio apps not just koala) when you end recording into a pad? This is on an iPad 6 with iOS 13.7 and happens even with 1024 buffers and nothing much going on (baseline CPU % in AUM reads 10-20% in this session and spikes to over 130% momentarily at which time there is a short burst of noise.

  • I've got my "Endless" script working in Koala.

    You can set any number of pads (up to 16) to be endlessly recycled as you record going from pad to pad. The pads can be set to record from 1 to 64.

  • @elf_audio any chance of adding cycle markers/loop points in piano roll?

  • I don’t really understand what the endless script is doing... it it automatically changing to the next pad after a certain length?

  • I haven't read the whole thread, but is choosing line input one of the features in the future?
    I would really like to record from one of my audio interface.

  • @jaijai said:
    I haven't read the whole thread, but is choosing line input one of the features in the future?
    I would really like to record from one of my audio interface.

    I don’t understand. IOS only allows one audio interface at a time so what would you select?

    Or did you mean selecting from one output of a multi/channel interface?

  • I have a Griffin studio connect and a focusrite itrack dock. When my iPhone/iPad is docked in one of those devices, Koala does not record from the input. Koala always records from the mic. It would be awesome if I could record from the line inputs.
    Same applies to the MacBook version, it can not record from the line in of an audio interface.

  • @reasOne said:
    I don’t really understand what the endless script is doing... it it automatically changing to the next pad after a certain length?

    It records into pads and endlessly cycles around them till you stop. You set how long the pad recordings are. There are many applications. Record so that each pad is a take, giving you a chance to play till you get it right or you could sit down and and just noodle and if inspiration strikes, press stop. It can be a retrospective/look ahead looper or flight recorder style recorder (kind of) or take recorder.

    There is more background in this thread about the Loopy-based version:
    https://forum.audiob.us/discussion/43651/loopy-endless-mozaic-script-lookahead-flight-recorder-style-looper

    The advantage of Koala is there isn’t a need for a separate audio editor for stitching or editing takes.

  • @jaijai said:
    I have a Griffin studio connect and a focusrite itrack dock. When my iPhone/iPad is docked in one of those devices, Koala does not record from the input. Koala always records from the mic. It would be awesome if I could record from the line inputs.
    Same applies to the MacBook version, it can not record from the line in of an audio interface.

    You could use AudioBus or AUM to pipe audio into Koala.

  • @espiegel123 said:

    @jaijai said:
    I have a Griffin studio connect and a focusrite itrack dock. When my iPhone/iPad is docked in one of those devices, Koala does not record from the input. Koala always records from the mic. It would be awesome if I could record from the line inputs.
    Same applies to the MacBook version, it can not record from the line in of an audio interface.

    You could use AudioBus or AUM to pipe audio into Koala.

    Awesome thank you, that was the last clue I needed. Using AUM everything works.
    Now Koala has rendered half of my gear obsolete :smile:

  • As with any instrument,,, practice helps. I finally hit "Record Song" after making my own drum kit and chopping up some @LinearLineman Rhodes ("Glisten" track on SoundCloud).
    This is a open doors to new ideas I missed over the last 30 years:

  • @espiegel123 said:
    I've got my "Endless" script working in Koala.
    You can set any number of pads (up to 16) to be endlessly recycled as you record going from pad to pad. The pads can be set to record from 1 to 64.

    Very cool indeed! :)

  • Hello dearies. I have a problem that I don't know if it comes from my Keystep Pro or Koala sampler. What do you think?
    I program 3 midi notes with the same gate in this video but you will see that between KSP and Koala they decide to play the same notes differently. Do you recognize the same problem?
    It's like Koala a lot of times does not want to play the notes I send, I have not figured it out yet. If I fill up all 16 steps it will the launching vill vary. Koala is supposed to retrigger clips, it's not in one shot. Can it be something with that Playhead moving in Sequence mode competing with my KSP? I have nothing programmed in Koala. Have a nice day now,

  • Anyone getting this to sync properly in Cubasis 3 on a 2020 regular ipad yet? Or do we have to wait for the AUv3 treatment?

  • @elf_audio and anyone - Iam trying to work out a way to add pad mutes & solos to the Koala pads Can this be done via Xequence2 etc? Thanks in advance

  • @stormbeats said:
    @elf_audio and anyone - Iam trying to work out a way to add pad mutes & solos to the Koala pads Can this be done via Xequence2 etc? Thanks in advance

    Koala doesn’t have mutes and solos.

  • Since Koala switches patterns instantly one can always create a pattern variation and delete the pad that needs to be muted...

    Lots of people enjoying Koala flipping stuff :)

  • @espiegel123 said:

    @stormbeats said:
    @elf_audio and anyone - Iam trying to work out a way to add pad mutes & solos to the Koala pads Can this be done via Xequence2 etc? Thanks in advance

    Koala doesn’t have mutes and solos.

    @espiegel123 I know but was thinking just maybe there was a way. Much needed

  • @Samu said:
    Since Koala switches patterns instantly one can always create a pattern variation and delete the pad that needs to be muted...

    Lots of people enjoying Koala flipping stuff :)

    @Samu True but its more for when exporting . It’s sometimes needed to mute loads of chops from a sequence to export. Yes can be done deleting stuff in piano roll but longer process. Also quicker for resampling slices. Some to mute some to solo. Hopefully this will arrive soon

  • @stormbeats said:

    @Samu said:
    Since Koala switches patterns instantly one can always create a pattern variation and delete the pad that needs to be muted...

    Lots of people enjoying Koala flipping stuff :)

    @Samu True but its more for when exporting . It’s sometimes needed to mute loads of chops from a sequence to export. Yes can be done deleting stuff in piano roll but longer process. Also quicker for resampling slices. Some to mute some to solo. Hopefully this will arrive soon

    Export stems and delete the files that are not needed.
    Mr. @elf_audio may need some time to 'recharge' :)

    BM3 just got updated as well so...

Sign In or Register to comment.