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.
iRig BlueBoard MIDI feedback
The thing I like best about the BlueBoard is that it supports MIDI feedback, so the state of the foot switches matches the state of the buttons I have them bound to, even if something other than the BlueBoard toggles them. However, on my BlueBoard at least, this is unreliable. It seems to frequently miss messages so the state of a button will temporarily fall out of sync, and sometimes it stops responding to state changes entirely. It continues to send midi just fine, but messages sent back get ignored until I reconnect. Enabling/disabling midi timestamps and adjusting latency compensation in Loopy Pro don't seem to have an impact.
Questions:
Does this happen with all BlueBoards? I have the previous rev with the USB port in the battery compartment. Is there any reason to think a new one would behave differently?
Any suggestions for a fix or workaround when it gets stuck? The BlueBoard doesn't auto connect to bluetooth so I can't even toggle the power when it stats to act up. I need to open Bluetooth Devices on my phone and reconnect from there.
What other floor controllers support MIDI feedback in some fashion, so the foot switch indicators can be toggled externally? Most/all pad controllers seem to support this, but the only floorboards that I'm aware of are the BlueBoard and the KMI/Muse Kinetics pedals. Are there others?
Edit: I'm running the BlueBoard in "C" mode, where presses send CC messages, but I see the same thing in "B"/note mode.
Comments
Are you using the blueboard in notes or cc mode? CC mode is more reliable for midi feedback in my experience with Loopy Pro.
I've tried it both ways, but at the moment it's in CC mode. I'd guess that 1 in 10 button presses don't toggle the LEDs properly, and it stops responding to incoming messages entirely after 50 - 100 presses.
Can you provide details about the precise feedback that isn’t working? What are the bindings?
I have 4 buttons with "First Action" state feedback enabled, that all have "Press" actions to scroll 2 position stepped dials. The stepped dials do things like recall plugin presets, send midi, and mute/unmute channels.
The buttons have "Press" action midi bindings to CCs 20 - 24 on the blueboard. The blueboard is set as "Generic Device" and has feedback enabled in Loopy Pro's Control Settings screen.
When things are working properly, pressing either a footswitch on the BlueBoard or the bound button on my screen will toggle both the button and the indicator light on the blueboard. However the indicator changes on the blueboard are unreliable, and sometimes stop working entirely.
Can you create a simple project that demonstrates the issue and zip and upload it here. I can check with my blueboard.
Thank you @espiegel123. I really appreciate it.
Assuming the midi mappings exported as expected, the attached project should have 4 buttons that are linked to the state of the blueboard's buttons. You can toggle all 4 from the blueboard or on the screen, and the state of the buttons should match both places.
To have a somewhat repeatable test, after connecting I toggled both the C and D buttons on the blueboard at the same time and started to count, pressing them 2 or 3 times a second. Within 20 presses I'll usually see something go out of sync, at least temporarily. The on screen buttons always toggle as they should, but occasionally the blueboard doesn't light or dim. Eventually the blueboard will stop responding entirely, and stay stuck with whatever buttons happened to be lit at the time. It continues to send messages just fine, and the on screen buttons continue toggling as they should. In my testing this happened within 200 presses, and usually within 100.
Do you see the same thing?
I just did a couple of hundred presses with my bluebird and they haven't gone out of sync. I included mostly fast presses. If yours goes out of synch, does pressing the onscreen control put it back in sync?
What device are you using?
Yes, pressing either the on screen control or the foot switch will usually sync things up again. It seems to be missing or ignoring a message, but usually responds properly to the next one, until things get "stuck", and all buttons stop responding to incoming messages until it reconnects.
I'm using an iPhone 16 Pro, but I saw this on previous phones as well. Years ago I ran MIDI Messenger hosted in AUM to control the BlueBoard LEDs on a 12 pro or a XS and I had the same problem. I guess it could be my device? That's not what I expected, but I can reproduce this easily. I'll have to try to get my hands on another BlueBoard.
If you had the problem with other configurations not involving loopy pro, that sounds like a hardware issue.
A simple test is to open a project with no bindings and create one button with a press/release action to send a cc from 20-23 and keep pressing the button fast the led should always be off after a release.