Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Audiokit Pro AR909 - Midi learn “Start/Stop”

13»

Comments

  • Ok guys, very many thanks for all your help with this. To be honest, MY issue with regard this is now solved, even though I can’t get MG2 to communicate with Synth One totally within AB3.

    My primary issue, now that I have my BlueBoard pedal, is to sort out how I’m going to get it to scroll through App/AU presets.

    I did start another thread on this subject, so, to avoid muddying the subject of this thread I’ll take up the story over there.

    Thanks again, as I said, your knowledge help and patience have really helped to give me confidence and interest in this whole arena!

  • @espiegel123 said:
    Have you experimented with launch order?

    As an experiment, try turning off 'velocity-sensitive MIDI'. And using different launch order than you have been using.

    @espiegel123 thanks for this, I'll make it my very last attempt with this issue before I move on to StreamByter scripts.

    My only question is " how do I affect the Launch Order?" As far as I can see the Apps and AUs etc are all loaded automatically when I load the relevant AB3 preset.

  • @MikeFloutier said:

    @espiegel123 said:
    Have you experimented with launch order?

    As an experiment, try turning off 'velocity-sensitive MIDI'. And using different launch order than you have been using.

    @espiegel123 thanks for this, I'll make it my very last attempt with this issue before I move on to StreamByter scripts.

    My only question is " how do I affect the Launch Order?" As far as I can see the Apps and AUs etc are all loaded automatically when I load the relevant AB3 preset.

    I mean see if it matter whether you launch synth one by hand rather than having audiobus load it. IAA apps often work best if launched by hand.

  • edited February 2022

    @espiegel123 said:
    I mean see if it matter whether you launch synth one by hand rather than >having audiobus load it. IAA apps often work best if launched by hand.

    >

    @espiegel123 , sorry, it’s all questions with me...by “launching by hand” did you mean launching Synth One as a Stand-alone App (outside AB3) or some non-automated way of launching it within AB3 (not sure how to do this)?

  • @MikeFloutier said:

    @espiegel123 said:
    I mean see if it matter whether you launch synth one by hand rather than >having audiobus load it. IAA apps often work best if launched by hand.

    >

    @espiegel123 , sorry, it’s all questions with me...by “launching by hand” did you mean launching Synth One as a Stand-alone App (outside AB3) or some non-automated way of launching it within AB3 (not sure how to do this)?

    Yes, launching by hand outside of Audiobus. IAA apps are standalone and communicate with the host but always exist outside of it. For some reasons, some IAA apps do better if launched by hand rather than the host.

  • @espiegel123 said:

    @MikeFloutier said:

    @espiegel123 said:
    I mean see if it matter whether you launch synth one by hand rather than >having audiobus load it. IAA apps often work best if launched by hand.

    >

    @espiegel123 , sorry, it’s all questions with me...by “launching by hand” did you mean launching Synth One as a Stand-alone App (outside AB3) or some non-automated way of launching it within AB3 (not sure how to do this)?

    Yes, launching by hand outside of Audiobus. IAA apps are standalone and communicate with the host but always exist outside of it. For some reasons, some IAA apps do better if launched by hand rather than the host.

    Ok, I am getting confused now, this seems to be where I came in 😂.

    If I launch Synth One outside AB3 it works fine, ie. it receives Midi from MG2, it always has done. The only reason for trying to launch either MG2 or Synth One inside AB3 was to improve their functionality; although, in practice I don’t really need any more functionality than I already get without AB3.

    Hence, my sole need for AB3 is as a host for the AR-909 drum machine to give me access to the ability to Start/Stop and scripted preset scrolling that doesn’t seem to be available in the standalone iOS version.

    Hope this makes sense.

  • @MikeFloutier said:

    @espiegel123 said:

    @MikeFloutier said:

    @espiegel123 said:
    I mean see if it matter whether you launch synth one by hand rather than >having audiobus load it. IAA apps often work best if launched by hand.

    >

    @espiegel123 , sorry, it’s all questions with me...by “launching by hand” did you mean launching Synth One as a Stand-alone App (outside AB3) or some non-automated way of launching it within AB3 (not sure how to do this)?

    Yes, launching by hand outside of Audiobus. IAA apps are standalone and communicate with the host but always exist outside of it. For some reasons, some IAA apps do better if launched by hand rather than the host.

    Ok, I am getting confused now, this seems to be where I came in 😂.

    If I launch Synth One outside AB3 it works fine, ie. it receives Midi from MG2, it always has done. The only reason for trying to launch either MG2 or Synth One inside AB3 was to improve their functionality; although, in practice I don’t really need any more functionality than I already get without AB3.

    Hence, my sole need for AB3 is as a host for the AR-909 drum machine to give me access to the ability to Start/Stop and scripted preset scrolling that doesn’t seem to be available in the standalone iOS version.

    Hope this makes sense.

    The idea is that you launch the app stand-alone, then "open" it in Audiobus, just as if you were starting it from Audiobus. This can avoid problems if Audiobus is unable to start the app gracefully. So you could try starting the app, then accessing it from Audiobus, to see if that works better.

    However, as I mentioned previously, I was able to launch SynthOne smoothly from Audiobus, and send MIDI to it. And AR-909 is AUv3, so no problem running it in Audiobus.

    Just one li'l question, however. Do both Audiobus and SynthOne have Local Network permission? Check in the Settings app. This is required for IAA communication. You might have denied it when first starting the apps.

  • @uncledave said:

    The idea is that you launch the app stand-alone, then "open" it in Audiobus, just as if you were starting it from Audiobus. This can avoid problems if Audiobus is unable to start the app gracefully. So you could try starting the app, then accessing it from Audiobus, to see if that works better.

    However, as I mentioned previously, I was able to launch SynthOne smoothly from Audiobus, and send MIDI to it. And AR-909 is AUv3, so no problem running it in Audiobus.

    Just one li'l question, however. Do both Audiobus and SynthOne have Local Network permission? Check in the Settings app. This is required for IAA communication. You might have denied it when first starting the apps.

    Thanks for these tips @uncledave , will try your external launching suggestion.

    In the meantime, a couple of other things to report:

    1. Both AB3 & Synth One have local network permission enabled. I take it that it’s not needed for Midi Guitar 2?
    2. Also, for some reason, I tried setting up a mirror test on my iPad mini, as opposed to the iPhone 7 (on iOS 14.1, which is refusing to allow Midi to pass between MG2 and Synth One). It worked fine on the iPad (running iOS 12.5.5)
  • @MikeFloutier said:

    @uncledave said:

    The idea is that you launch the app stand-alone, then "open" it in Audiobus, just as if you were starting it from Audiobus. This can avoid problems if Audiobus is unable to start the app gracefully. So you could try starting the app, then accessing it from Audiobus, to see if that works better.

    However, as I mentioned previously, I was able to launch SynthOne smoothly from Audiobus, and send MIDI to it. And AR-909 is AUv3, so no problem running it in Audiobus.

    Just one li'l question, however. Do both Audiobus and SynthOne have Local Network permission? Check in the Settings app. This is required for IAA communication. You might have denied it when first starting the apps.

    Thanks for these tips @uncledave , will try your external launching suggestion.

    In the meantime, a couple of other things to report:

    1. Both AB3 & Synth One have local network permission enabled. I take it that it’s not needed for Midi Guitar 2?
    2. Also, for some reason, I tried setting up a mirror test on my iPad mini, as opposed to the iPhone 7 (on iOS 14.1, which is refusing to allow Midi to pass between MG2 and Synth One). It worked fine on the iPad (running iOS 12.5.5)

    FWIW, the early iOS 14 versions were a bit buggy . You might want to upgrade the OS.

  • @MikeFloutier said:

    @uncledave said:

    The idea is that you launch the app stand-alone, then "open" it in Audiobus, just as if you were starting it from Audiobus. This can avoid problems if Audiobus is unable to start the app gracefully. So you could try starting the app, then accessing it from Audiobus, to see if that works better.

    However, as I mentioned previously, I was able to launch SynthOne smoothly from Audiobus, and send MIDI to it. And AR-909 is AUv3, so no problem running it in Audiobus.

    Just one li'l question, however. Do both Audiobus and SynthOne have Local Network permission? Check in the Settings app. This is required for IAA communication. You might have denied it when first starting the apps.

    Thanks for these tips @uncledave , will try your external launching suggestion.

    In the meantime, a couple of other things to report:

    1. Both AB3 & Synth One have local network permission enabled. I take it that it’s not needed for Midi Guitar 2?
    2. Also, for some reason, I tried setting up a mirror test on my iPad mini, as opposed to the iPhone 7 (on iOS 14.1, which is refusing to allow Midi to pass between MG2 and Synth One). It worked fine on the iPad (running iOS 12.5.5)

    This is great. At least you know that you're configuring it correctly, and that it does work as intended. As Ed said, the early iOS 14 had some bugs; it was the first implementation of a new MIDI queueing system, supposedly preparing for MIDI 2.0. I guess your iPad mini is a "classic" model, like my iPad Air, which is frozen at iOS 12.5.5.

  • Thanks guys, I’ll try updating the iPhone.

    In the meantime I noticed that, for the mirror presets I created on iPhone and iPad, there was one difference I could see.

    The attached pics show that the thumbnail copy of MG2 loaded in the iPad’s midi page contains the legend “: MIDI OUT” whereas the iPhone’s does NOT!

    Don’t know if that’s significant.

  • @MikeFloutier said:
    Thanks guys, I’ll try updating the iPhone.

    In the meantime I noticed that, for the mirror presets I created on iPhone and iPad, there was one difference I could see.

    The attached pics show that the thumbnail copy of MG2 loaded in the iPad’s midi page contains the legend “: MIDI OUT” whereas the iPhone’s does NOT!

    Don’t know if that’s significant.

    I think that probably is a cosmetic difference.

    i think i figured out your problem. Don't send the midi to the app. choose the Audiokit Synth One virtual midi port instead. On the midi page, when you tap on the + sign to set the midi destination, tap on the system tab and choose the Audiokit Synth One port there. I just tested. That works. Choosing the app from the apps tab does not work for me.

  • Choose this destination not the app

  • Many thanks @espiegel123 , will try this out in the morning.

    I did update my iPhone to iOS 15.3.1 which took me hours of failing before I tried a forced re-start. Didn’t make any difference though 😂

  • @espiegel123 said:
    i think i figured out your problem. Don't send the midi to the app. choose the Audiokit Synth One virtual midi port instead. On the midi page, when you tap on the + sign to set the midi destination, tap on the system tab and choose the Audiokit Synth One port there. I just tested. That works. Choosing the app from the apps tab does not work for me.

    Many thanks @espiegel123 , that works perfectly; inspired thinking!

  • @MikeFloutier said:

    @espiegel123 said:
    i think i figured out your problem. Don't send the midi to the app. choose the Audiokit Synth One virtual midi port instead. On the midi page, when you tap on the + sign to set the midi destination, tap on the system tab and choose the Audiokit Synth One port there. I just tested. That works. Choosing the app from the apps tab does not work for me.

    Many thanks @espiegel123 , that works perfectly; inspired thinking!

    Glad to hear that you are now set.

  • Thanks also to @uncledave , for all your help with this!

Sign In or Register to comment.