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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Morningstar MC8 and count in issues
Hello. I'm having a bit of a frustrating issue with my foot controller. I feel like there are still probably some troubleshooting steps I could take but I wanted to start a thread possibly to help shape my thinking about troubleshooting going forward. Or hopefully to arrive at a solution.
My setup is iPad>anker powered hub>Morninstar MC8. I'm running BLEASS Multiband comp on the output bus of each project. I also have a Rhode Vocaster usb interface hanging off the same hub and I use that interface for audio output. In every project, I'm using dials to protect my count-in from accidental double-taps that would normally bypass the clips' count-ins. Each project is essentially six to ten clips arranged across six colors. Each clip plays one at a time. We have recently added a percussionist on certain shows and I created a separate set of projects for those gigs. In those projects, I have a click being generated by a pair of clips that run continuously throughout each song. One of those clips is a stick click on quarter notes and one is a bell on the downbeat of each measure.
The first symptom is that at completely random intervals, the MC8 drops off. I suddenly have no foot control over the dials that trigger the clips. Not the end of the world because i can reach down and trigger the dials by touch but also not great because I'm probably playing sax when this is happening. The solution thus far has been to unseat then reseat the usb going into the MC8.
The second symptom is a little more problematic. Starting this friday, after the MC8 drops off and I reseat the usb cable, tapping a footswitch bypasses the count in. Which should be impossible because the footswitches aren't triggering the clips directly but are triggering dials as outlined in this thread:
https://forum.loopypro.com/discussion/66560/second-trigger-bypasses-count-in#latest
Also the next footswitch trigger after the one with no count-in appears to fire the second clip with a count in that behaves as if the first, non-count-in clip was fired with a count in. So say that first clip fires one bar and one beat early because there's no count in, the second trigger will fire a clip one bar and one beat late. Hopefully this makes sense. Basically the first, non-count in clip is off grid but the second one is back on.
This happened last night on a show with the percussionist and the first, no-count-in clip launched completely out-of-sync with the click he was hearing.
Anyway, this second issue is a little bit of a show-stopper. I've tried shutting down all background apps except for the mixer app for our Soundcraft UI12. Whenever I start building my ipad and pedalboard setup, I always let the MC8 boot up before connecting it to the hub. And I try connect the MC8 to the hub before connecting the hub to the ipad (though this weekend's show were both a little hectic during setup so I may have gotten things out of order).
As ludicrous as this may sound, I don't recall exactly which songs I had the issue with last night. One would think that would have made an impression. It was definitely one of these three:
Any thoughts about this issue would be very welcome. Thank you.
Comments
@Superaction80 : sounds very frustrating. It also has me scratching my heard.
Make sure that the MIDI Feedback to the MC8 is off -- and that no MIDI is being sent to it. It has a lot of internal MIDI mappings that can be triggered if MIDI is sent to it.
If something is being triggered when the MC8 powers up, there must be some sort of binding that was being triggered. I've not heard of clips being triggered when there was a binding involved.
Make sure both that the MC8 is not set to send clock and that in Loopy Pro's synchronization settings that external clock is off for all possible sources.
To troubleshoot, you might want to connect a MIDI monitor running as a standalone app and plug and unplug the MC8 to see if anything unexpected shows up.
You might want to try a different order of plugging things in. While different set ups seem to different, I find that if things aren't working right, it works for me to unplug everything. Power-cycle the iPad. After it is booted, plug in the hub then plug in the devices.
The next time you lose connection with the hub, launch ShowMIDI as a standalone app and see if it sees the MC8. If it doesn't there may be a hardware glitch.
Thank you!
Turns out I was sending and receiving MIDI clock from the mc8 to LP. And apparently I needed to run a fw update. And in doing that I saw the current fw has an iteration that prevents iOS from seeing the mc8 as a qwerty keyboard. Which makes me wonder if the mc8 being recognized as a qwerty keyboard is the issue.
Thanks for the update. Fingers-crossed that it solves your problems.
I feel like there has been at least one science fiction movie about time travel wherein, near the climax of the story, one character is about to go through the time portal and that person pauses and says to another character "if you never see me again, you know this worked."
Of course I'll try to stop back and update if I never have the drop out/count in issues again, but, if you never hear from me again, you know this worked