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.
Comments
Awesome. Looking forward to it. I'm brushing up on my skills this week, haha.
I have posted my current version of the software (which is for the Launchkey Mini Mark 2) here
https://patchstorage.com/launchkey-helper/
It works well for me. I didn't have time to put together notes about how to set things up. I'll try to get that done in the next day or two -- but maybe it will be helpful anyway.
Use the shift key to switch between settings pages. When you hold a pad down on the settings pages, use the knobs on the layout to set the associated setting for the pad being held down.
Hello @espiegel123 unfortunately it doesn't work on MK3.
Mainly the Mini MK3 no longer has an inControl mode but uses the "LaunchKey Midi MK3 DAW Port" midi port for the input of NoteON and NoteOFF messages and Velocity to change the colors of the pads and the "LaunchKey Midi MK3 MIDI Port" port for use it as a controller.
To change the colors of the pads just send the following messages to the DAW port:
Would it be possible for you to modify your script to work with MK3 too?
Thanks a lot
I don't have a Mark 3. I can look at the code and suggest where to make changes. Btw, what you describe is not very different from how mark 2 works. Both use separate ports for communicating regular MIDI and "host midi"
It sounds like the main difference is not having the ability to turn off in-control mode and the note numbers for the pads.i'll take a look later today.
Thanks that would be great!
I have uploaded an update that uses constants (variables) for the pad numbers to make it easier to update for a Mark 3. Just change the two constants related to the pad rows found in the OnLoad section.
Look for
padTopFirst
padBottomFirst
There are also notes at the top about what to look at to change the color handling. I think you can probably just adjust the knob handling so that the knob can assign a range from 0 to 127 rather than 0 to 15 and then bypass the translation of the index to a raw color. You can just store and assign the number you receive from the knob.
Sorry but it's too much for me, I tried to edit the script but I can't get it to work.
The notes of the pads are not consecutive and are organized like this.
Top row - 40, 41, 42, 43, 48, 49, 50, 51.
Bottom row - 36, 37, 38, 39, 44, 45, 46, 47
But I changed padTopFirst and padBottomFirst to see if the rest of the parameters were changed and I only get that one pad block is fixed on orange color and the others are off.
Any parameter modified on the Mozaic interface (button status, group, etc.) is not reflected on the Launchkey
@wim on another thread wrote me another script that works fine but I have to manually change the variable values and doesn’t have the other features of your script.
If it can help it is this:
Thanks again and sorry if I wasted your time
Maybe you can find someone with a mark 3 willing to collaborate on building something of the mark 2 code I provided. The pads not being sequential will make things a bit messier. But not terribly so. On the mark 2, the pads are broken into two sequential groups (96 to 103 and 112 to 119)
From what you describe the Mark 3 has the pads broken into 4 groups of consecutive pads. There are only a few lines of code that need to be changed to accommodate that. Maybe someone can work with you or do it for you.
Thanks, I hope someone can help me
You may want to post a request in the Mozaic request thread.
I've already written something like this there and I also created a guess Mozaic interface but I didn't get help at the moment.
https://forum.audiob.us/discussion/comment/881909/#Comment_881909
@wim might be a good candidate to do this, he wrote the piece of code I'm using right now, but he's currently busy with other projects.
I honestly think that if you spent an hour or two (maybe less) with the Mozaic manual, you would be able to understand enough to modify the code I posted with a few hints -- which I'd be happy to provide.
Short version: there are a couple of places in the code that check to see if the incoming message is from one of the pads. In my case I check to see if it is within the range of the upper and lower rows. For the mark 3, you make a change to the line of code that checks that range to by checking the against the boundaries of 4 groups rather than 2 groups.
Thanks @espiegel123 Been away for a bit but thanks for the reply. Will look into it.
I thought I'd have my usage notes ready -- but haven't had time. Short version. The shift key advances through the settings pages. On the settings pages, while you hold a pad down in Mozaic, the knobs will become labeled with settings they change. So, hold a pad and dial in the settings. On the groups page, you are setting the properties for the group that a pad is in. (All pads in a group share the same color scheme -- which you can set). On that page, the pads in Mozaic represent groups (there can be up to 8 groups). On the other settings pages, the settings are for the pad on the Launchkey.
Thanks to the help of @wim on another thread, that made all the code, on Patchstorage there is a script for Mozaic to configure color behavior for Launchkey Mini MK3 pads (DRUM MODE ONLY).
With it you can do things on iOS that you can't even do on a mac/pc with Novation Componets!
Enjoy it
https://patchstorage.com/launchkey-mk3-utility/
Thanks @Tatobx ! Just now seeing this. Have been off of Audiobus for a long while. Just want to let you know I appreciate your post.
Wow man, you just blew my mind! I don’t have mosaic and I’ve ignored all the buzz because I suffer from codophobia but this looks super useful. The only thing I miss on my mk 2 is to be able to see if I’m in mute mode or not and I’m currently blind and have to bring Drambo to the foreground to verify it.
One consideration though. Do you find power issues when having all those leds lit? I’m guessing you’re using a usb c iPad? I have several controllers already hooked up to my pro 11 so I doubt it will tollerate a light show like that
I have an iPad 6 with CCK. I don't have any issues wth the LEDs
But it is the only controller you have connected right?
I agree, switching midi channels is super useful. I’m thinking about switching the nanokey studio for this.
Pros
Cons?
How does the Launchkey mini mk3 compare to the launchkey 25 mk3 ?. Link
Same number of keys but a lot bigger and heavier, it does have a scale mode and a little display... wonder if the little display is helpful with scales and such, as I commented before that’s sort of hard to do in nanokey studio.
Let’s continue the convo over on the thread about the Mark II and this script:
https://forum.audiob.us/discussion/43223/launchkey-mini-mk-2-helper-script
Got a bit sidetracked for the past few weeks...apologies. Didnt get the chance to test the script. I've set some time this weekend to go over the script. Thanks again for the video on the script. Just saw the other thread.
So the Launchkey Mini mk3 has a scale mode for pads but only when using the components software that needs a desktop to run... right?. Basically means no scale mode on iPad. So you’re stuck with a “c minor” or whatever and no possibility to change from the device?. Would it be possible to change scales via Mozaic as a workaround?.