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.

Issues with programming Morningstar MC6 for Loopy

Hey guys - I think it’s an old topic but just wanna make sure I’ve got the latest troubleshooting tips on programming Morningstar MC6 MIDI foot switch to work with Loopy. My setup:

  • loopy on IPad Pro
  • USB C - to USB port on MC6
  • MC6 updated to latest firmware 3.12.1
  • Successful programming of “Presets” through Morningstar Editor on Mac
  • Then when I put Loopy in MIDI learning mode it sends signals to MC6 and teaches it different actions, but every few clicks the MC6 goes blank on me and skips banks to like blank 29

Ive read that it might be related to the USB cable and someone suggested using USB to MIDI cable but that creates need for separate AC/DC adapter power supply etc. I’d prefer to run it from the USB HUB connected to IPad. Any suggestions?

Comments

  • @tsiwiec said:
    Hey guys - I think it’s an old topic but just wanna make sure I’ve got the latest troubleshooting tips on programming Morningstar MC6 MIDI foot switch to work with Loopy. My setup:

    • loopy on IPad Pro
    • USB C - to USB port on MC6
    • MC6 updated to latest firmware 3.12.1
    • Successful programming of “Presets” through Morningstar Editor on Mac
    • Then when I put Loopy in MIDI learning mode it sends signals to MC6 and teaches it different actions, but every few clicks the MC6 goes blank on me and skips banks to like blank 29

    Ive read that it might be related to the USB cable and someone suggested using USB to MIDI cable but that creates need for separate AC/DC adapter power supply etc. I’d prefer to run it from the USB HUB connected to IPad. Any suggestions?

    The first thing to do is to turn off feedback to the MC6 in Loopy Pro’s Control
    Settings.

    By default loopy sends feedback to controllers because many controllers will update their displays to reflect the status. But some controllers interpret that feedback as MIDI commands and it causes problems.

    If turning feedback off doesn’t solve the problem there may be other settings in the MC6 that need configuring.

  • Sweet - thanks Spiegel, I think that fixed it. At first I went in and turned off feedback without the MC connected and then it was still acting up but after I pulled the Control Settings with the MIDI unit connected there were actually 3 or 4 more new options referencing my unit and they all had Feedback Turn On toggle, which I disabled and now the switch seems to be learning the messages without blanking out and skipping banks, Thanks for your quick and professional help!

  • wimwim
    edited December 2023

    You may also need to disable Network Midi in Loopy Pro settings. It has been known to interfere with the MorningStar pedals.

    [edit] at least I think it was MorningStar. The discussion on the Beta Slack has been archived. Anyway, it can't hurt unless you're actually using Network Midi session.

  • Awesome thank you guys. Now that I got to use it properly without glitches and crashes it just dawned on me that every time I program it to my desired footswitch layout after I close loopy without saving the project session the settings disappear from Morningstar memory. Is that common? I figured once I program it, it would sit in its memory until I change the settings. If that’s normal, then it appears that I need to save the midi settings in every project that I work on to have it for future. How do you guys handle that?

  • @tsiwiec said:
    Awesome thank you guys. Now that I got to use it properly without glitches and crashes it just dawned on me that every time I program it to my desired footswitch layout after I close loopy without saving the project session the settings disappear from Morningstar memory. Is that common? I figured once I program it, it would sit in its memory until I change the settings. If that’s normal, then it appears that I need to save the midi settings in every project that I work on to have it for future. How do you guys handle that?

    What settings disappear from
    Morningstar memory?

    The mapping of midi events to Loopy actions are stored in Loopy’s projects or Loopy Global Profiles. By default loopy saves them into projects. So, if you aren’t saving the project , the bindings aren’t saved.

    If you want the midi mapping shared between projects, save them into the global
    profile… note that global profiles are a little fragile if you are trying to used them with different layouts.

  • You might find it worthwhile to watch the John Paul video tutorial about midi in Loopy.

  • @espiegel123 thank you!!!! Been going crazy trying to figure this out. This old post saved my sanity.

Sign In or Register to comment.