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.

Loopy Pro | Midi Controller Compatibility / Auto Mapping

13»

Comments

  • @jazzmess said:
    I can confirm launchpad mini mk3 automaps (session view) : tested with ipad air 4 - cck didnt try on ipad pro m1 but it should work !

    Can someone report a mark on launchpad pros mk 1 and 2 and other launchpad mini versions?

  • What I would love to see is an advanced midi fighter twister mapping : you have knobs you can press to launchclips but also take of advantage of the color ring around the knobs.

  • @espiegel123 said:
    Can someone report a mark on launchpad pros mk 1 and 2 and other launchpad mini versions?

    mini mk2 - negative. no automap. doesn't surprised me as you program them differently than a mk3

    @jazzmess said:
    What I would love to see is an advanced midi fighter twister mapping : you have knobs you can press to launchclips but also take of advantage of the color ring around the knobs.

    AFAIK theres no way to program the twister on the fly (sending commands to it to change LED colors, note values, etc), but I could be wrong. Maybe @soundtemple might be able to shed some light on this?

  • @AlmostAnonymous said:

    @espiegel123 said:
    Can someone report a mark on launchpad pros mk 1 and 2 and other launchpad mini versions?

    mini mk2 - negative. no automap. doesn't surprised me as you program them differently than a mk3

    @jazzmess said:
    What I would love to see is an advanced midi fighter twister mapping : you have knobs you can press to launchclips but also take of advantage of the color ring around the knobs.

    AFAIK theres no way to program the twister on the fly (sending commands to it to change LED colors, note values, etc), but I could be wrong. Maybe @soundtemple might be able to shed some light on this?

    It can be programmed in bitwig, so I guess its doable, but I clearly dont have the skills !!

  • @DeadPhish said:
    Just got my APC40 MK2. Going to have some fun playing around tonight.

    Wow the APC40 is HUGE in terms of size…

  • @jazzmess said:
    I can confirm launchpad mini mk3 automaps (session view) : tested with ipad air 4 - cck didnt try on ipad pro m1 but it should work !

    My gear exactly, so thanks a lot for the confirmation! 🙏

  • Yoire welcome mate !

  • @jazzmess said:
    What I would love to see is an advanced midi fighter twister mapping : you have knobs you can press to launchclips but also take of advantage of the color ring around the knobs.

    AFAIK theres no way to program the twister on the fly (sending commands to it to change LED colors, note values, etc), but I could be wrong. Maybe @soundtemple might be able to shed some light on this?

    It can be programmed in bitwig, so I guess its doable, but I clearly dont have the skills !!

    This may not be "on the fly", but I t hink this video demonstrate exactly how to set up midi fighter twister.

  • If there ever is a list of "supported" devices from @Michael I would be extremely interested in that as having whatever I buy work with Loopy Pro is one of my main requirements.

    See: https://wiki.audiob.us/doku.php?id=loopy_pro

    there may be some other launchpad variants that work but haven't been tested

    Thanks for pointing me to this list since I'm brand new to all this. Much appreciated!

    It seems to me there is a difference between the "Auto-Mapped Devices" in this list and what will work with the midi learn functionality in Loopy Pro., which is what I was hoping to learn. I was reading some of the Amazon comments for the APCKey25 and there are comments like "all the pads works as midi notes, so you can't assign CC commands to the side buttons for example." and simply "you can't reprogram it." I'm cautious since I know nothing about midi instruments, but from a tech background my first inclination is to think most of this is user error or they are not dealing with something as advanced as Loopy Pro, but I have no idea.

    So, to ask a more specific question, until Michael adds this as an auto-mapped device, would I be able to midi-learn at least some of the basic functionality of Loopy Pro on the buttons and knobs on this device like record clips (press button corresponding with position of clip on Loopy Pro), play/stop entire color/track (button at bottom of column), start/stop an entire group of clips/track (button at end of row), use the knobs to control the volume of an entire color/track, etc. It seems like I should be able to set that up and then replicate that as a kind of template with those mappings intact. Right? Or is there a limitation of the APCKey25 that would prevent it from being midi mapped?

    Sorry for asking such newbie questions, but it just seems like this super-affordable device is at least a good entry-level purchase that covers a lot of the functionality you would want to control Loopy Pro with a keyboard input to boot.

  • edited February 3

    I bought an AKAI APC 40 second hand and Michael recently improved the APC support significantly because DubFX uses this combo for his performances. Here is a small summary what we have discovered so far.

    • Now the top row knobs work as expected: you can switch their target between pan, sends and a user defined assignment. The different sends A,B,C, etc. can be selected with the track selector buttons.
    • The device section is also improved a lot. You can navigate the devices and their banks of knob mappings with the respective arrow left and right buttons. Each device can have multiple banks. With SHIFT + bank button the bank can be selected directly. Now the Midi learn has a concept of device and bank for the device knobs so you can create a huge amount of mappings.
    • The „Bank Select“ navigation arrows lets you scroll around the clips. Scrolling affects only the launch buttons but not the mixer controls.

    This makes the APC quite a versatile controller for Loopy. A drawback is that you easily can get lost which device is currently controlled by the device knobs if you have several devices mapped. There is no visual feedback for this. In Ableton the APC follows the device that is focused in Ableton. Something similar would great to have in LP, too.

  • @StateOfTate said:

    If there ever is a list of "supported" devices from @Michael I would be extremely interested in that as having whatever I buy work with Loopy Pro is one of my main requirements.

    See: https://wiki.audiob.us/doku.php?id=loopy_pro

    there may be some other launchpad variants that work but haven't been tested

    Thanks for pointing me to this list since I'm brand new to all this. Much appreciated!

    It seems to me there is a difference between the "Auto-Mapped Devices" in this list and what will work with the midi learn functionality in Loopy Pro., which is what I was hoping to learn. I was reading some of the Amazon comments for the APCKey25 and there are comments like "all the pads works as midi notes, so you can't assign CC commands to the side buttons for example." and simply "you can't reprogram it." I'm cautious since I know nothing about midi instruments, but from a tech background my first inclination is to think most of this is user error or they are not dealing with something as advanced as Loopy Pro, but I have no idea.

    So, to ask a more specific question, until Michael adds this as an auto-mapped device, would I be able to midi-learn at least some of the basic functionality of Loopy Pro on the buttons and knobs on this device like record clips (press button corresponding with position of clip on Loopy Pro), play/stop entire color/track (button at bottom of column), start/stop an entire group of clips/track (button at end of row), use the knobs to control the volume of an entire color/track, etc. It seems like I should be able to set that up and then replicate that as a kind of template with those mappings intact. Right? Or is there a limitation of the APCKey25 that would prevent it from being midi mapped?

    Sorry for asking such newbie questions, but it just seems like this super-affordable device is at least a good entry-level purchase that covers a lot of the functionality you would want to control Loopy Pro with a keyboard input to boot.

    You can midi map anything in loopy pro so that LP responds. You will not get feedback back from Loopy pro to light buttons and whatnot, but it will respond.

  • edited February 3

    @krassmann said:
    I bought an AKAI APC 40 second hand and Michael recently improved the APC support significantly because DubFX uses this combo for his performances. Here is a small summary what we have discovered so far.

    • Now the top row knobs work as expected: you can switch their target between pan, sends and a user defined assignment. The different sends A,B,C, etc. can be selected with the track selector buttons.
    • The device section is also improved a lot. You can navigate the devices and their banks of knob mappings with the respective arrow left and right buttons. Each device can have multiple banks. With SHIFT + bank button the bank can be selected directly. Now the Midi learn has a concept of device and bank for the device knobs so you can create a huge amount of mappings.
    • The „Bank Select“ navigation arrows lets you scroll around the clips. Scrolling affects only the launch buttons but not the mixer controls.

    This makes the APC quite a versatile controller for Loopy. A drawback is that you easily can get lost which device is currently controlled by the device knobs if you have several devices mapped. There is no visual feedback for this. In Ableton the APC follows the device that is focused in Ableton. Something similar would great to have in LP, too.

    @krassmann

    Maybe @Michael can get Jürgen Moßgraber who does all the DAW mapping for AKAI, PUSH and Novation to help out with the controllers out there.

  • @espiegel123 said:

    @StateOfTate said:

    If there ever is a list of "supported" devices from @Michael I would be extremely interested in that as having whatever I buy work with Loopy Pro is one of my main requirements.

    See: https://wiki.audiob.us/doku.php?id=loopy_pro

    there may be some other launchpad variants that work but haven't been tested

    Thanks for pointing me to this list since I'm brand new to all this. Much appreciated!

    It seems to me there is a difference between the "Auto-Mapped Devices" in this list and what will work with the midi learn functionality in Loopy Pro., which is what I was hoping to learn. I was reading some of the Amazon comments for the APCKey25 and there are comments like "all the pads works as midi notes, so you can't assign CC commands to the side buttons for example." and simply "you can't reprogram it." I'm cautious since I know nothing about midi instruments, but from a tech background my first inclination is to think most of this is user error or they are not dealing with something as advanced as Loopy Pro, but I have no idea.

    So, to ask a more specific question, until Michael adds this as an auto-mapped device, would I be able to midi-learn at least some of the basic functionality of Loopy Pro on the buttons and knobs on this device like record clips (press button corresponding with position of clip on Loopy Pro), play/stop entire color/track (button at bottom of column), start/stop an entire group of clips/track (button at end of row), use the knobs to control the volume of an entire color/track, etc. It seems like I should be able to set that up and then replicate that as a kind of template with those mappings intact. Right? Or is there a limitation of the APCKey25 that would prevent it from being midi mapped?

    Sorry for asking such newbie questions, but it just seems like this super-affordable device is at least a good entry-level purchase that covers a lot of the functionality you would want to control Loopy Pro with a keyboard input to boot.

    You can midi map anything in loopy pro so that LP responds. You will not get feedback back from Loopy pro to light buttons and whatnot, but it will respond.

    Actually, Loopy Pro will send feedback to any device – it won’t send colours, but it will turn lights on or off if supported by the device.

  • @Michael said:

    @espiegel123 said:

    @StateOfTate said:

    If there ever is a list of "supported" devices from @Michael I would be extremely interested in that as having whatever I buy work with Loopy Pro is one of my main requirements.

    See: https://wiki.audiob.us/doku.php?id=loopy_pro

    there may be some other launchpad variants that work but haven't been tested

    Thanks for pointing me to this list since I'm brand new to all this. Much appreciated!

    It seems to me there is a difference between the "Auto-Mapped Devices" in this list and what will work with the midi learn functionality in Loopy Pro., which is what I was hoping to learn. I was reading some of the Amazon comments for the APCKey25 and there are comments like "all the pads works as midi notes, so you can't assign CC commands to the side buttons for example." and simply "you can't reprogram it." I'm cautious since I know nothing about midi instruments, but from a tech background my first inclination is to think most of this is user error or they are not dealing with something as advanced as Loopy Pro, but I have no idea.

    So, to ask a more specific question, until Michael adds this as an auto-mapped device, would I be able to midi-learn at least some of the basic functionality of Loopy Pro on the buttons and knobs on this device like record clips (press button corresponding with position of clip on Loopy Pro), play/stop entire color/track (button at bottom of column), start/stop an entire group of clips/track (button at end of row), use the knobs to control the volume of an entire color/track, etc. It seems like I should be able to set that up and then replicate that as a kind of template with those mappings intact. Right? Or is there a limitation of the APCKey25 that would prevent it from being midi mapped?

    Sorry for asking such newbie questions, but it just seems like this super-affordable device is at least a good entry-level purchase that covers a lot of the functionality you would want to control Loopy Pro with a keyboard input to boot.

    You can midi map anything in loopy pro so that LP responds. You will not get feedback back from Loopy pro to light buttons and whatnot, but it will respond.

    Actually, Loopy Pro will send feedback to any device – it won’t send colours, but it will turn lights on or off if supported by the device.

    Is there a list of such devices? On a few devices people have mentioned problems caused by midi sent back for feedback.

  • edited February 3

    @espiegel123 said:

    @Michael said:

    @espiegel123 said:

    @StateOfTate said:

    If there ever is a list of "supported" devices from @Michael I would be extremely interested in that as having whatever I buy work with Loopy Pro is one of my main requirements.

    See: https://wiki.audiob.us/doku.php?id=loopy_pro

    there may be some other launchpad variants that work but haven't been tested

    Thanks for pointing me to this list since I'm brand new to all this. Much appreciated!

    It seems to me there is a difference between the "Auto-Mapped Devices" in this list and what will work with the midi learn functionality in Loopy Pro., which is what I was hoping to learn. I was reading some of the Amazon comments for the APCKey25 and there are comments like "all the pads works as midi notes, so you can't assign CC commands to the side buttons for example." and simply "you can't reprogram it." I'm cautious since I know nothing about midi instruments, but from a tech background my first inclination is to think most of this is user error or they are not dealing with something as advanced as Loopy Pro, but I have no idea.

    So, to ask a more specific question, until Michael adds this as an auto-mapped device, would I be able to midi-learn at least some of the basic functionality of Loopy Pro on the buttons and knobs on this device like record clips (press button corresponding with position of clip on Loopy Pro), play/stop entire color/track (button at bottom of column), start/stop an entire group of clips/track (button at end of row), use the knobs to control the volume of an entire color/track, etc. It seems like I should be able to set that up and then replicate that as a kind of template with those mappings intact. Right? Or is there a limitation of the APCKey25 that would prevent it from being midi mapped?

    Sorry for asking such newbie questions, but it just seems like this super-affordable device is at least a good entry-level purchase that covers a lot of the functionality you would want to control Loopy Pro with a keyboard input to boot.

    You can midi map anything in loopy pro so that LP responds. You will not get feedback back from Loopy pro to light buttons and whatnot, but it will respond.

    Actually, Loopy Pro will send feedback to any device – it won’t send colours, but it will turn lights on or off if supported by the device.

    Is there a list of such devices? On a few devices people have mentioned problems caused by midi sent back for feedback.

    It’s all devices – I’m shortly going to be adding a setting for every device where you can turn off feedback if necessary - and I’ll be adding more advanced configuration, for adding your own specialised support for devices.

  • @Michael said:

    @espiegel123 said:

    @Michael said:

    @espiegel123 said:

    @StateOfTate said:

    If there ever is a list of "supported" devices from @Michael I would be extremely interested in that as having whatever I buy work with Loopy Pro is one of my main requirements.

    See: https://wiki.audiob.us/doku.php?id=loopy_pro

    there may be some other launchpad variants that work but haven't been tested

    Thanks for pointing me to this list since I'm brand new to all this. Much appreciated!

    It seems to me there is a difference between the "Auto-Mapped Devices" in this list and what will work with the midi learn functionality in Loopy Pro., which is what I was hoping to learn. I was reading some of the Amazon comments for the APCKey25 and there are comments like "all the pads works as midi notes, so you can't assign CC commands to the side buttons for example." and simply "you can't reprogram it." I'm cautious since I know nothing about midi instruments, but from a tech background my first inclination is to think most of this is user error or they are not dealing with something as advanced as Loopy Pro, but I have no idea.

    So, to ask a more specific question, until Michael adds this as an auto-mapped device, would I be able to midi-learn at least some of the basic functionality of Loopy Pro on the buttons and knobs on this device like record clips (press button corresponding with position of clip on Loopy Pro), play/stop entire color/track (button at bottom of column), start/stop an entire group of clips/track (button at end of row), use the knobs to control the volume of an entire color/track, etc. It seems like I should be able to set that up and then replicate that as a kind of template with those mappings intact. Right? Or is there a limitation of the APCKey25 that would prevent it from being midi mapped?

    Sorry for asking such newbie questions, but it just seems like this super-affordable device is at least a good entry-level purchase that covers a lot of the functionality you would want to control Loopy Pro with a keyboard input to boot.

    You can midi map anything in loopy pro so that LP responds. You will not get feedback back from Loopy pro to light buttons and whatnot, but it will respond.

    Actually, Loopy Pro will send feedback to any device – it won’t send colours, but it will turn lights on or off if supported by the device.

    Is there a list of such devices? On a few devices people have mentioned problems caused by midi sent back for feedback.

    It’s all devices – I’m shortly going to be adding a setting for every device where you can turn off feedback if necessary - and I’ll be adding more advanced configuration, for adding your own specialised support for devices.

    Great

  • edited February 3

    @Jumpercollins absolutely true. Moßgraber‘s extension „Driven by Moss“ for Bitwig is phenomenal. I have a Bitwig 8 Track installed. Well, I‘m also on some kind of quest for my preferred desktop DAW. Since I have the APC I wanted to try it with desktop software. I‘ve used it only a few hours and I’m also still learning Bitwig, but I‘m really blown away. It goes far beyond Bitwig‘s factory support. Same for the Launchpads. It turns them into a powerful control surface instead of simple clip launcher. Jürgen Moßgraber did all his stuff in the open and put it on github: https://github.com/git-moss/DrivenByMoss

  • @AlmostAnonymous said:

    @espiegel123 said:
    Can someone report a mark on launchpad pros mk 1 and 2 and other launchpad mini versions?

    mini mk2 - negative. no automap. doesn't surprised me as you program them differently than a mk3

    @jazzmess said:
    What I would love to see is an advanced midi fighter twister mapping : you have knobs you can press to launchclips but also take of advantage of the color ring around the knobs.

    AFAIK theres no way to program the twister on the fly (sending commands to it to change LED colors, note values, etc), but I could be wrong. Maybe @soundtemple might be able to shed some light on this?

    You can send a cc message back to an encoder to update its state. It's the same cc# it outputs and the value comes from the host.
    The LED's are a little different as you select the colours in the utility, but pretty sure you can send a message with a 0 or 127 value to back to the Twister to change the on/off colour displayed.

  • edited February 4

    @soundtemple
    Well, there def is a way......unless these are just programmed in the utility to match

  • edited February 4

    @AlmostAnonymous There you go. Neat little setup there with MFTW and the iPhone display!

    From the manual....

    It is also possible to override the color of the RGB segment by sending a MIDI message (Note or CC) of
    the same MIDI number, > on channel 1. Sending a message of value 0 will force it to
    its inactive color state, while sending a message of value 127 will force it to it's active color
    state. Any value between 0 and 127 will set it to a color as shown in the scale below.

    So values BETWEEN 0 & 127 will show different LED segment colours

  • As expected, Loopy Pro automaps beautifully to my Launchpad X, but as soon as I add an instance of LK or Atom 2, the buttons are hijacked and only highlight to show the LK or Atom instances. I understand how this could be valuable in certain circumstances to launch the midi driven clips, but in general I want to use the Launchpad for standard circle clip launching, and direct LK or Atom by hand to where I want them to be recorded. Is there any way to turn off LK or Atom 2 taking over? (Neither seem to show up in the Midi Control section in the settings…)

  • @Tovokas said:
    As expected, Loopy Pro automaps beautifully to my Launchpad X, but as soon as I add an instance of LK or Atom 2, the buttons are hijacked and only highlight to show the LK or Atom instances. I understand how this could be valuable in certain circumstances to launch the midi driven clips, but in general I want to use the Launchpad for standard circle clip launching, and direct LK or Atom by hand to where I want them to be recorded. Is there any way to turn off LK or Atom 2 taking over? (Neither seem to show up in the Midi Control section in the settings…)

    Loopy can’t prevent atom or LK from taking over, but you can. Each has a setting to turn off their Launchpad control.

  • @espiegel123 said:

    Loopy can’t prevent atom or LK from taking over, but you can. Each has a setting to turn off their Launchpad control.

    Thanks! It seemed to require a few restarts of LP to keep LK from shutting off all auto mapping when I disabled it inside the instrument, but I think I’m there. :)

  • edited June 23

    @Michael said:
    I’m shortly going to be adding a setting for every device where you can turn off feedback if necessary - and I’ll be adding more advanced configuration, for adding your own specialised support for devices.

    I have just bought a Behringer X Touch Compact which I hope will soon be usable with similar dynamic fader/ knob bank switching implementation to the APC 40 mk2 , given its similar* features & feedback functionality .

    Rather than expecting @Michael to add many different hardware implementations , could I request in the first instance you provide a dummy template mode of existing APC40 functions , which a user can activate & set up their particular hardware to replicate the parameter assignments of the APC on their device as best they can make fit .
    Am I right thinking at the moment it seems there is no way to tell LoopyPro to go into APC40 mode without connecting an APC ? , even if I sent the same assigned notes/CCs from a different device .

    *I would be using Launchpad X for Clip** triggering (** I hate the D-word , I’m a serious musician Godammit!) ,
    so the XTouch Compact’s 40 obvious buttons + 16 push button function of encoders should get me most of APC Mixer aspect functionality I’m hoping .

Sign In or Register to comment.