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.
Midi Controllers - Midi Feedback - Novation SL MK3
Hi fellow Loopy lovers!
I have some midi questions I am hoping to get sorted out. Especially after seeing the DubFX interview. Any input would be greatly appreciated and if it’s already been discussed please point me to the applicable posts.
-I know it shows as a selectable midi device in the options already and seems to be popular with Loopy Pro users, so does the APC40 MKII get feedback to control its lights and indicators?
-Has anyone been able to map a Novation SL MK3 to work in “InControl” mode and get the proper midi feedback to work as it would in Ableton? It uses MMC midi btw.
-Is anyone interfacing with devices that require sysex? If so please share how you are going about it.
I love what this app can do and would really love to have it be the center of my setup.
Thank you,
Alex
Comments
See responses in line.
The devices listed in the Special Hardware Support section of the manual get more sophisticated feedback and coordination than generic devices. For example, LED and pad colors are co-ordinated and automated pre-configured bindings are available.
The feedback available to generic devices is explained in the manual:
https://loopypro.com/manual/#midi-state-feedback
How midi feedback is handled is described in the link above.
Some people have used combinations of follow actions, midi scripting (using streambyter ot Mozaic) and widgets to set up integration with other devices akin to Loopy’s special hardware support.
Loopy doesn’t directly support MMC but it is fairly straightforward to use something like streambyter, MIDIFire or Mozaic to convert MMC messages to ccs messages that Loopy can bind to.
Loopy can send sysex with the send midi messsage action. Some people use streambyter or mozaic to integrate sysex.
Hi espiegel123, thank you for the fast and detailed reply!
This information is very helpful and at least I know those controllers on the list should be a sure bet.
I had a feeling this would lead back to Streambyter and Mosaic lol. Even before I started using Loopy I tried to make my own scripts or repurpose existing ones but could never get any of them to work. Since no one else had already come up with them (last I checked) I wasn’t even sure if it could be done or if it was just me. So this is at least good to hear.
I’m pretty tech savvy with a background in mechanical engineering and medicine before I became disabled but coding just hasn’t clicked with me after trying on and off for years. I will see if I can make some more progress on this though!
Do you know of any downloadable Loopy templates I could dissect that are already using Streambyter or Mosaic to do something similar?
MMC is only for transport control. The SL MKIII uses standard note or CC messages to control LEDs. No sysex needed thankfully, though you can use sysex if you like. Sysex is needed to customize the screen properties though.
https://fael-downloads-prod.focusrite.com/customer/prod/s3fs-public/downloads/SLMkIII_Programmer's_Guide.pdf
Hi wim, thank you for the follow up! I think you are right about the MMC and I was confusing things from when I was last trying to do this with my hacked MPC. I have done all the standard CC templates on the SL for different synths and hardware before no problem.
However I tried to understand that guide you shared before to get the incontrol mode to work, but no success. I see it mentioning CCs but it all seems to be talking about is sending hexadecimal and decimal messages. Even just for the pad color and lighting status is showing multiple hex messages that need to be sent to the SL from the host, unless I am completely missing something.
I’d love to be able to use all the InControl functions ideally, but at the least launch/stop/rec/arm loops and rows along with channel vol/solo/mute. I think standard instrument templates only give you the pads as scale notes or are used for the internal sequencer and internal clip launching.
Are you using InControl with Loopy?
No, I'm not using InControl with Loopy. I don't have the MKIII controller. But I know quite a bit about midi.
Those hexadecimal numbers are just Midi CC messages and Midi Note messages. You'll need to do some reading up on midi message structure. Midi messages consist of three numbers, which are often expressed in hexadecimal. However, really only the first number (byte) is easier to express in hex.
The first byte of a midi message gives its type + midi channel. A cc message starts with hexadecimal
Bfollowed by the channel number. So, when you see 0xBF, for the first byte, you are seeing0xto indicate it's a hexidecimal number,B= CC message type + F ( F = 15 = midi channel 16).It may be easier to look at the decimal representation for the other two bytes, as we're more familiar with those. The second number is the CC number and the third is the CC value.
Confused? Yeh. I'm not going to be able to do a better job of explaining it than you'll be able to find with some searching on the web. Or, better yet, maybe take a look at the Mozaic manual. Chapter 3 has one of the best explanation of midi message structuring I've seen.
I'm not gonna lie. Setting things up to do what you want is likely to end up being a big load of eye-crossing grunt work.
You actually did a pretty great job explaining it and I appreciate your time! I’ve learned some of this stuff then have to take a break from it for months for medical reason and forget so much in that time. I think I even read the entire Mosaic and Loopy manuals multiple times before but then it fades away unless I could keep it up. I can still program my Ensoniq Mirage using hex though! …just not build an editor to run it and send samples from the computer using sysex lol.
I agree though I am not sure the juice(torture) will be worth the squeeze with the SL. I need to use my time wisely and should probably be making music instead.
A lot of the gear I have was from before my condition progressed and income tanked so that’s why I was hoping to see if I could work with what I already have. The APC will probably be the best bet and I like the idea of using the crossfader with macros like an Octatrack/Drambo vibe.
Thanks again!
Ahhh ... man. I'm sorry to hear about your medical and income struggles. I hope everything gets better.
I appreciate the kind words and really hope so too! I’m staying optimistic and since the medical system here in the US is failing me I am going to try to at least take my journey on my own terms and find the joy in what I love.
I’m sure we’ll be crossing paths some more and hopefully I’ll have some cool loopy stuff to share soon. I have a laundry list of other questions that will be popping up if they haven’t already been asked and answered somewhere lol.