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.

Using two M-Vave chocolate plus controllers in Loopy Pro

I have been using two Chocolate plus footswitches controllers with great success for quite awhile.
Today I experienced some perplexing behavior. I use them with an iPad Pro wirelessly.
Some functions were not working today.

Through trouble shooting I found that in the control profiles they two controllers had become switched with each other. It happened twice today. In other words in the control profiles they cc #s for one controller were designated for the other controller.

I have wondered how LP tells them apart. In the device list they both are named FootCtrlPlus. In the control settings they are named FootCtrlPlus Bluetooth and FootCtrlPlus Bluetooth 2.
Somehow cc messages that are in Bluetooth 2 ended up assigned to the first Bluetooth controller in the control settings. This happened twice today.

I thought perhaps it mattered which controller was turned on first but I have not been able to make it happen again. Anyone else run into a problem like this?

Comments

  • I have some issues with 2 M-VAVE Chocolates. One is a plus one is regular. I was having issues using them both wired. Loopy Pro would see them separate, sinco 1 and sinco 2 but on a restart, the mappings would be doubled or messed up. And it would not matter what order you turned them on.

    I did have a slight issues using Bluetooth as far as a microsecond latency, which is why I wanted to be wired. I have later switched to one wired, the plus, which is for record or other tasks where the most accurate timing is required. And the other one is Bluetooth for other controls. This has worked out well for me on my pedal board.

  • @TheAudioDabbler said:
    I have some issues with 2 M-VAVE Chocolates. One is a plus one is regular. I was having issues using them both wired. Loopy Pro would see them separate, sinco 1 and sinco 2 but on a restart, the mappings would be doubled or messed up. And it would not matter what order you turned them on.

    I did have a slight issues using Bluetooth as far as a microsecond latency, which is why I wanted to be wired. I have later switched to one wired, the plus, which is for record or other tasks where the most accurate timing is required. And the other one is Bluetooth for other controls. This has worked out well for me on my pedal board.

    For USB, the OS assigns IDs of identical-looking devices based on connection order. For reliable operation, you need to plug them in after the device has booted and always in the same order.

  • Thank you both for your input. I have also found best results with my motu interface is to turn it on last.

  • @espiegel123 so plug in verses turn on? I tired to just turn on in the same order and it didn't work. It was like loopy pro was receiving double messages.

  • @TheAudioDabbler said:
    @espiegel123 so plug in verses turn on? I tired to just turn on in the same order and it didn't work. It was like loopy pro was receiving double messages.

    Sorry, let me re-phrase, the OS assigns IDs in the order that the OS first sees them in a boot cycle.

    Btw, strangely, a wired plus has much higher latency than a wired non-plus.

Sign In or Register to comment.