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
@sinusoidal I own a Launchpad X. Do you think it would possible for LK to change the notes layout on the pad controller depending on the keyboard that has been chosen (synth vs drum mapping)?
EGDR606 Midi note mapping:
BassDrum = MIDI note 36
SnareDrum = MIDI note 38
LowTom = MIDI note 43
HiTom = MIDI note 47
Cymbal = MIDI note 50
Open HiHat = MIDI note 37
Closed HiHat = MIDI note 39
EGDR808 Midi note mapping:
BassDrum = MIDI note 36
SnareDrum = MIDI note 38
LowTom = MIDI note 43
MidTom = MIDI note 47
HiTom = MIDI note 50
RimShot = MIDI note 37
ClaP = MIDI note 39
CowBell = MIDI note 56
CYmbal = MIDI note 49
OpenHat = MIDI note 46
ClosedHat = MIDI note 42
EGDR909 Midi note mapping:
BassDrum = MIDI note 36
SnareDrum = MIDI note 38
LowTom = MIDI note 43
MidTom = MIDI note 47
HiTom = MIDI note 50
RimShot = MIDI note 37
ClaP = MIDI note 39
OpenHat = MIDI note 56
ClosedHat = MIDI note 49
Crash = MIDI note 46
Ride = MIDI note 42
EGLM1 Midi note mapping:
CONGA = MIDI note 48
CONGA2 = MIDI note 49
TOM = MIDI note 50
TOM2 = MIDI note 51
snare = MIDI note 52
SNARE = MIDI note 53
bass = MIDI note 54
BASS = MIDI note 55
hihat = MIDI note 56
HIHAT = MIDI note 57
CRASH = MIDI note 58
RIDE = MIDI note 59
CLAPS = MIDI note 60
CLAVE = MIDI note 61
STICK = MIDI note 62
TAMB = MIDI note 63
CABASA = MIDI note 64
COWBELL = MIDI note 65
@sinosoidal
Here are the GM mappings that DrumDrops use for their Mapex kit. Feel free to abbreviate the drum names if necessary. Cheers.
"DrumDropsMapexGM": {
"36": "KickEmad",
"35": "KickEQ2",
"38": "SnareCentre",
"82": "SnareEdge",
"40": "SnareRim",
"37": "SnareSide",
"28": "Flam",
"49": "Crash19",
"42": "HiCentreFullClose",
"68": "HiCentreClosed",
"71": "HiCentreOpenQ",
"72": "HiCentreOpenH",
"73": "HiCentreOpen3Q",
"46": "HiCentreOpenFull",
"55": "Crash18",
"57": "Crash20",
"85": "EdgeFullyClosed",
"87": "EdgeClosed",
"90": "EdgeQuarter",
"92": "EdgeOpenH",
"94": "EdgeOpen3Q",
"97": "EdgeOpenFull",
"44": "PedalShut",
"99": "PedalOpen",
"52": "CrashChina",
"43": "FloorTom",
"45": "LoRackTom",
"47": "HiRackTom",
"51": "RideCentre",
"59": "RideEdge",
"53": "RideBell"
}
Maybe in the future. Not immediatelly.
This controllers have two modes: DAW and Programmer.
Eventually we will need to go into programmer mode one day because only in that mode we can define the color of the pads correcrtly.
Let's see how it goes!
Briliant! Thanks Mr. @White
Thanks!
DrumDrops is what? A plugin for computer?
@sinosoidal
DrumDrops sell multi-velocity drum sample packs along with exs format files which let you import them directly into the AudioLayer AU as an instrument. You can then trigger the different parts of the drumkit by sending the correct note to AudioLayer.
@sinosoidal
MV08 Midi note mapping:
BD = midi note 60
SD = midi note 61
CLP = midi note 62
LT = midi note 63
MT = midi note 64
HT = midi note 65
RS = midi note 66
CB = midi note 67
CYM = midi note 68
OH = midi note 69
CH = midi note 70
LC = midi note 71
MC = midi note 72
HC = midi note 73
CLV = midi note 74
MRC = midi note 75
I love this feature!. I can’t stand doing drums on a piano roll. This might be one but doesn’t feel like it.
Here’s my proposition:
Extra freaky points... if it’s as simple as a json like the above. It’d be really cool if you could add your own layouts, which you could then share. It’d probably save you a lot of time!.
Cheers!
@sinosoidal
VADrumSM midi mapping:
Bass Drum = midi note 36
Rim Shot / Claves = midi note 37
Snare Drum = midi note 38
Hand Clap / Maracas = midi note 39
Bass Drum 2 = midi note 40
Low Tom 2 = midi note 41
Closed HiHat = midi note 42
Tom 2 = midi note 43
High Tom 2 = midi note 44
Tom / Low Conga = midi note 45
Open HiHat = midi note 46
Tom / Mid Conga = midi note 47
Tom / High Conga = midi note 48
Cymbal = midi note 49
Cowbell = midi note 50
Snare Drum 2 = midi note 51
You are a programmer. You know that adding the ability to the user customize something via user interface is a tediuous task for the programmer. But we will eventually find a smart solution that anyone can use with the least effort!
The problem with using clip parameter automation is that sometimes you need to send the data before the first beat of the bar. For example the Digitakt will receive a program change then change the pattern at the next pattern boundary. The way to get around this in ableton is trigger dummy clips in gate mode with loop off so the clip is launched immediately rather than waiting for the start of the next bar. Is it easy enough to add a gate mode in the clip properties?
I think that GM map is a bit specific to the DrumDrops app. Here is the standard one
It is specific to DrumDrops, yeah. They have a few different mappings for different host software, e.g. Addictive, BFD, iMap, Slate but I thought I would choose the one labelled GM for inclusion here. I don’t quite know why they called it GM as it isn’t a straight GM map.
Here is the GM map from the link above:
"General MIDI": {
"35": "Acoustic Bass Drum",
"36": "Bass Drum 1",
"37": "Side Stick",
"38": "Acoustic Snare",
"39": "Hand Clap",
"40": "Electric Snare",
"41": "Low Floor Tom",
"42": "Closed Hi Hat",
"43": "High Floor Tom",
"44": "Pedal Hi-Hat",
"45": "Low Tom",
"46": "Open Hi-Hat",
"47": "Low-Mid Tom",
"48": "Hi Mid Tom",
"49": "Crash Cymbal 1",
"50": "High Tom",
"51": "Ride Cymbal 1",
"52": "Chinese Cymbal",
"53": "Ride Bell",
"54": "Tambourine",
"55": "Splash Cymbal",
"56": "Cowbell",
"57": "Crash Cymbal 2",
"58": "Vibraslap",
"59": "Ride Cymbal 2",
"60": "Hi Bongo",
"61": "Low Bongo",
"62": "Mute Hi Conga",
"63": "Open Hi Conga",
"64": "Low Conga",
"65": "High Timbale",
"66": "Low Timbale",
"67": "High Agogo",
"68": "Low Agogo",
"69": "Cabasa",
"70": "Maracas",
"71": "Short Whistle",
"72": "Long Whistle",
"73": "Short Guiro",
"74": "Long Guiro",
"75": "Claves",
"76": "Hi Wood Block",
"77": "Low Wood Block",
"78": "Mute Cuica",
"79": "Open Cuica",
"80": "Mute Triangle",
"81": "Open Triangle"
}
The problem with the GM map is that it’s super long, IMO it wouldn’t feel good to work with. You’d loose the really cool aspects of big note areas, it’d look more like a piano roll. I’d skip everything starting with Vibraslap. Sorry to all the vibraslap lovers!. “Cuica” heavy users will also hate me for proposing this, and they’re legion!. 🙃
In case I wasn’t clear, I meant loading a json file into LK describing a mapping, not being able to produce or edit a JSON file. Like @branis could just save the json he posted above and share it. Sort of like Mozaic patches that you can share and load, just plain json.
As promised: Here are the mappings that i personaly checked
And this is the list of mappings that were supplied by others to be included in my Mozaic script - The script remapped from the XoX source, so not all sounds of the destinations may be captured. But the list may serve as a base to enhance for additional sounds and better naming:
Thank you very much for sharing those! If you want to join the beta testing send me a pvt message with your email. Thx!
@_ki Regarding Fractalbits...
It uses the whole keyboard range to map out the sounds in different octaves.
Try it, some of the sounds take a totally different character in the other octaves.
Also if you go into the settings '...' of the app and set it to 'Keyboard Height:3' you can access 3 octaves at once
That was quick 😊
I will just include some of the mapping @_ki sent and make another build
I made/tested two more mappings of plugins:
Probably i didn’t have these plugins when i last updated my re-mapping script - i‘ll add them in a minor update.
@Samu I noticed that Fractal Bits maps the whole range, but choose the 12 pads that give a visual feedback. I didn‘t know about the 3 octave settings. That seems very convenient - thanks a lot for the info
Patterning is IIA, no AUV3. Would be nice if it was.
Would be great to have EG Pulse, GR-16 and beathawk.
I’ll see if I can figure out the note codes when I get some time.
Thanks for posting this. I posted the same question a few pages ago but haven’t used ableton so didn’t know there was a ‘best practice’ workaround.
Dunno about gate mode in LK, but sounds like a good addition if it isn’t there already.
For EG Pulse, can use Elliot Garage Drums mapping for first 8 pads.
Loving this new update with the drum maps, and note folding. Haven't used LK in a bit, but will be using more.
I may have missed this, but is there a way to do step recording for the piano roll, so each note is recorded incrementally without transport running?
Totally missed that. It's almost like a new app now. Thanks!
Thanks, for the EG Pulse tip. Agreed, the drum maps are genius. So simple but so useful. I was sequencing using the build in sequencer in EG Pulse or whatever and recording that midi into LK then sorting it out to the right notes... bit of a workflow killer but not any more!
I just tried the MV08 map and pitched it through mfxPitch first and got it to detect all 16 pads on EGpulse. I have the \MPC pad layout\ setting on in EG.