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.

M-Vave Wireless MIDI Controller

123578

Comments

  • I'm curious what "CW" is under Knob Type.

  • @wim said:
    I'm curious what "CW" is under Knob Type.

    Good question. @jamietopol : how does the knob behave if you choose CW?

  • @espiegel123 said:

    @wim said:
    I'm curious what "CW" is under Knob Type.

    Good question. @jamietopol : how does the knob behave if you choose CW?

    That is available in the cubesuite app. I think it looks like cubesuite has all the features of the app Jamie shared screenshots of btw. I checked this now - CW makes the knob toggle between one value and another. By default that is 0 when you twist left and 127 when you twist right, but you can change those values using the app.

  • @Gavinski said:

    @espiegel123 said:

    @wim said:
    I'm curious what "CW" is under Knob Type.

    Good question. @jamietopol : how does the knob behave if you choose CW?

    That is available in the cubesuite app. I think it looks like cubesuite has all the features of the app Jamie shared screenshots of btw. I checked this now - CW makes the knob toggle between one value and another. By default that is 0 when you twist left and 127 when you twist right, but you can change those values using the app.

    That sounds like relative cc’s.

  • @espiegel123 said:

    @Gavinski said:

    @espiegel123 said:

    @wim said:
    I'm curious what "CW" is under Knob Type.

    Good question. @jamietopol : how does the knob behave if you choose CW?

    That is available in the cubesuite app. I think it looks like cubesuite has all the features of the app Jamie shared screenshots of btw. I checked this now - CW makes the knob toggle between one value and another. By default that is 0 when you twist left and 127 when you twist right, but you can change those values using the app.

    That sounds like relative cc’s.

    Thanks, I was about to ask, could this then solve things? To recap, it can't make any difference for aum, but means these could work in loopy pro and drambo as endless encoders, correct?

  • @Gavinski said:

    @espiegel123 said:

    @Gavinski said:

    @espiegel123 said:

    @wim said:
    I'm curious what "CW" is under Knob Type.

    Good question. @jamietopol : how does the knob behave if you choose CW?

    That is available in the cubesuite app. I think it looks like cubesuite has all the features of the app Jamie shared screenshots of btw. I checked this now - CW makes the knob toggle between one value and another. By default that is 0 when you twist left and 127 when you twist right, but you can change those values using the app.

    That sounds like relative cc’s.

    Thanks, I was about to ask, could this then solve things? To recap, it can't make any difference for aum, but means these could work in loopy pro and drambo as endless encoders, correct?

    I’m going to take a look at the Loopy manual, I’m not familiar with the app. I don’t see relative mode here but will see if I can find in the manual how to implement it. If someone knows and can tell me here how to do it though, that would be handy.

  • edited January 2




    Found it, but I can’t get it working. This is my current setup, but now when I tweak the knob on the controller, nothing is happening. Before I turned on relative mode, Loopy Pro was toggling the value between 1 and 127 as expected. Must be something wrong with my current setup, please enlighten me

  • wimwim
    edited January 2

    @Gavinski said:
    I’m going to take a look at the Loopy manual, I’m not familiar with the app. I don’t see relative mode here but will see if I can find in the manual how to implement it. If someone knows and can tell me here how to do it though, that would be handy.

    Tap where it says Action Adjust Continuously > and Flip on the "Relative" switch.

    [edit] cross-posted. Sorry, I don't know how to help with it not working with that setting.

  • @wim said:

    @Gavinski said:
    I’m going to take a look at the Loopy manual, I’m not familiar with the app. I don’t see relative mode here but will see if I can find in the manual how to implement it. If someone knows and can tell me here how to do it though, that would be handy.

    Tap where it says Action Adjust Continuously > and Flip on the "Relative" switch.

    See my newer post above Wim, thnx

  • @Gavinski said:

    @wim said:

    @Gavinski said:
    I’m going to take a look at the Loopy manual, I’m not familiar with the app. I don’t see relative mode here but will see if I can find in the manual how to implement it. If someone knows and can tell me here how to do it though, that would be handy.

    Tap where it says Action Adjust Continuously > and Flip on the "Relative" switch.

    See my newer post above Wim, thnx

    Yeh. Cross posted.
    Maybe turn off Pick Up Mode?

  • @wim said:

    @Gavinski said:
    I’m going to take a look at the Loopy manual, I’m not familiar with the app. I don’t see relative mode here but will see if I can find in the manual how to implement it. If someone knows and can tell me here how to do it though, that would be handy.

    Tap where it says Action Adjust Continuously > and Flip on the "Relative" switch.

    [edit] cross-posted. Sorry, I don't know how to help with it not working with that setting.

    Ok!

  • @wim said:

    @Gavinski said:

    @wim said:

    @Gavinski said:
    I’m going to take a look at the Loopy manual, I’m not familiar with the app. I don’t see relative mode here but will see if I can find in the manual how to implement it. If someone knows and can tell me here how to do it though, that would be handy.

    Tap where it says Action Adjust Continuously > and Flip on the "Relative" switch.

    See my newer post above Wim, thnx

    Yeh. Cross posted.
    Maybe turn off Pick Up Mode?

    Thanks, that didn’t fix it.

    Btw, for the benefit of anyone else unfamiliar with loopy, you access the panel for toggling relative mode by tapping on the place shown in the attached screenshot

  • @Gavinski - I just saw on Slack that @espiegel123 was having the same issue. It appears a reboot fixed it for him.

  • I think Loopy accelerates changes the farther away from 64 the left and right values are. You might have to adjust the left and right ranges to something closer to 64.

  • @wim said:
    I think Loopy accelerates changes the farther away from 64 the left and right values are. You might have to adjust the left and right ranges to something closer to 64.

    @Gavinski : the left number should be 127 and the right number 1.

    That might result in an adjustment that is too fine.... in which case try 123 and 5.

    Check in a midi monitor and see of the values sent out vary with the speed. The best relative encoders are sensitive to speed.

  • @wim rebooted and tried changing values to 63 and 65, neither made any difference. This is on the latest test flight build of Loopy Pro, btw

  • There are a few relative MIDI conventions. One is that 127 is the smallest decrement and 1 the smallest increment and the coarseness increases as the values approach 64 (or is it 63?)

  • @espiegel123 said:

    @wim said:
    I think Loopy accelerates changes the farther away from 64 the left and right values are. You might have to adjust the left and right ranges to something closer to 64.

    @Gavinski : the left number should be 127 and the right number 1.

    That might result in an adjustment that is too fine.... in which case try 123 and 5.

    Check in a midi monitor and see of the values sent out vary with the speed. The best relative encoders are sensitive to speed.

    Thanks Ed - I tried both those suggestions but the slider in Loopy Pro is not moving at all when I twist the knob. Maybe you can double check if there is sth wrong in my set up, cheers

    Current setup:


  • I confirmed with a MIDI monitor that the knobs are functioning the way we want. Now I have to figure out if Keystage can support a relative control mode that will take advantage of this.

  • wimwim
    edited January 2

    I'm finding that relative is working fine for knob widgets, but I can't get it to work properly for color volume faders in Loopy Pro.

  • @Gavinski : let me out together a test project for you to run.

  • @espiegel123 said:
    @Gavinski : let me out together a test project for you to run.

    Sweet

  • @Gavinski said:

    @espiegel123 said:
    @Gavinski : let me out together a test project for you to run.

    Sweet

    I'm pretty sure relative mode isn't working for mixer faders. It works for widgets though, and widgets can be used to change the mixer faders.

  • @Gavinski : here is a test project.

    Add MIDI and add your controller. make streambyter a destination. if you are using cc30 sending 127 for left and 1 for right, it should behave the same as swipe left/right on the buttons.

    while putting this together, i may have seen a bug where relative midi was working to control a widget that controls a parameter but not the parameter directly which i will report to @michael

  • edited January 2

    @espiegel123 said:
    @Gavinski : here is a test project.

    Add MIDI and add your controller. make streambyter a destination. if you are using cc30 sending 127 for left and 1 for right, it should behave the same as swipe left/right on the buttons.

    while putting this together, i may have seen a bug where relative midi was working to control a widget that controls a parameter but not the parameter directly which i will report to @michael

    (Edited to remove confusion Re pickup mode)

    Thanks Ed. Just before this I tested it with a widget and it worked. Your session also works, so it seems that yes, this controller does indeed work endlessly in hosts that support relative mode. @j_liljedahl could we get a relative mode for endless encoders in AUM, do you think?

  • wimwim
    edited January 2

    @Gavinski said:

    @espiegel123 said:
    @Gavinski : here is a test project.

    Add MIDI and add your controller. make streambyter a destination. if you are using cc30 sending 127 for left and 1 for right, it should behave the same as swipe left/right on the buttons.

    while putting this together, i may have seen a bug where relative midi was working to control a widget that controls a parameter but not the parameter directly which i will report to @michael

    Thanks Ed. Just before this I tested it with a widget and it worked but @Michael, not only is it currently not possible to use relative mode with mixer faders, it also seems that when I turn on pickup mode the controller is no longer working in relative mode.

    Ed - I have extremely limited knowledge of Loopy Pro, btw, but this is what I did: I turned on midi learn and assigned my controller , set as CW with 127 for left value and 1 for right value to the clip volume fader, and it worked. As mentioned above, I had to make sure pickup mode was off in Loopy Pro to get it to work. With pickup mode on, widgets are completely non-responsive to my controller. I will be out for a few hours btw, so unable to check things, but can do so later if anyone has further suggestions.

    Pickup mode doesn't make sense in the context of relative controllers, so it should definitely be off for relative encoders (shouldn't even be an option in the GUI).

    If you're referring to absolute controls not being responsive in pickup mode, are you sure you have the latest Loopy Pro installed? There was a bug with pickup mode, but it's fixed now.

  • @wim said:

    @Gavinski said:

    @espiegel123 said:
    @Gavinski : here is a test project.

    Add MIDI and add your controller. make streambyter a destination. if you are using cc30 sending 127 for left and 1 for right, it should behave the same as swipe left/right on the buttons.

    while putting this together, i may have seen a bug where relative midi was working to control a widget that controls a parameter but not the parameter directly which i will report to @michael

    Thanks Ed. Just before this I tested it with a widget and it worked but @Michael, not only is it currently not possible to use relative mode with mixer faders, it also seems that when I turn on pickup mode the controller is no longer working in relative mode.

    Ed - I have extremely limited knowledge of Loopy Pro, btw, but this is what I did: I turned on midi learn and assigned my controller , set as CW with 127 for left value and 1 for right value to the clip volume fader, and it worked. As mentioned above, I had to make sure pickup mode was off in Loopy Pro to get it to work. With pickup mode on, widgets are completely non-responsive to my controller. I will be out for a few hours btw, so unable to check things, but can do so later if anyone has further suggestions.

    Pickup mode doesn't make sense in the context of relative controllers, so it should definitely be off for relative encoders (shouldn't even be an option in the GUI).

    If you're referring to absolute controls not being responsive in pickup mode, are you sure you have the latest Loopy Pro installed? There was a bug with pickup mode, but it's fixed now.

    Ah, I was referring to relative mode, and yes, thinking now, I understand why that doesn't make sense, cheers

  • I don't know whether to feel happy or sad that the encoders on this controller can now work as encoders. I was just feeling good about not having yielded to the temptation. Now it's back on the table. 😂

    Just what I need ... yet another controller I'll convince myself I "need" ... that will get tossed in the drawer with all the rest of 'em.

  • @wim said:
    I don't know whether to feel happy or sad that the encoders on this controller can now work as encoders. I was just feeling good about not having yielded to the temptation. Now it's back on the table. 😂

    Just what I need ... yet another controller I'll convince myself I "need" ... that will get tossed in the drawer with all the rest of 'em.

    I don't know whether to feel happy or sad that I will perhaps now finally have to learn loopy pro if I want to use these encoders as endless ones lol. Happy I think, I've been wanting to get round to that for a while, but I'm honestly a bit tired of learning apps at the moment 🤷‍♂️

  • If any of you are Keystage users, Ali is writing a script that will translate 0 and 127 to "decrease by 1" and "increase by 1" commands for parameters. I'll post more info once I have and test the script. In my opinion, this is a game-changer!

Sign In or Register to comment.