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.

LK - for Ableton Live & Midi by Imaginando - AUv3 Clip Launcher Finally Available in AUM!!

15758606263130

Comments

  • @sinosoidal said:
    We are adding keyboard layouts to 1.9.5:

    For the next build we have Ruismaker and Ruismaker FM. For more layouts we will need your help.

    We don't have all the apps you have, so it is important that you help us populate the data. We use JSON format to describe the layouts:

    "Ruismaker": {
    "49": "Kick",
    "51": "Snare",
    "54": "Clap",
    "56": "Tom 1",
    "58": "Tom 2",
    "61": "Tom 3",
    "63": "Hit Hat",
    "66": "Open Hit Hat"
    }

    Which keyboard layouts would you like to have available here?

    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:

    • General Midi Drum Map. Obvious fallback, it’s called general for a reason.
    • I believe it’d be really handy to have a simple “generic” incremental layout. (GM above does that?) . So kick 36, snare 37, clap 38, hh 39, open hh 40... and so on. That’d be easy to map from anywhere without having to check any docs (renaming the note header would be a plus).
      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

  • @tahiche said:

    @sinosoidal said:
    We are adding keyboard layouts to 1.9.5:

    For the next build we have Ruismaker and Ruismaker FM. For more layouts we will need your help.

    We don't have all the apps you have, so it is important that you help us populate the data. We use JSON format to describe the layouts:

    "Ruismaker": {
    "49": "Kick",
    "51": "Snare",
    "54": "Clap",
    "56": "Tom 1",
    "58": "Tom 2",
    "61": "Tom 3",
    "63": "Hit Hat",
    "66": "Open Hit Hat"
    }

    Which keyboard layouts would you like to have available here?

    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:

    • General Midi Drum Map. Obvious fallback, it’s called general for a reason.
    • I believe it’d be really handy to have a simple “generic” incremental layout. (GM above does that?) . So kick 36, snare 37, clap 38, hh 39, open hh 40... and so on. That’d be easy to map from anywhere without having to check any docs (renaming the note header would be a plus).
      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!

    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! ;)

  • @sinosoidal said:

    @auwerk said:
    Hello, @sinosoidal !
    Can we have an option to send midi message (note-on will be good I think) when clip is triggered? This can be used to trigger AUM FilePlayer nodes or whatever else. Note message can be sent from piano roll currently, but it’s bound to track’s midi channel. If we could specify channel for triggers globally in LK settings (“send clip triggers on channel X”) and use notes assigned with midi learn for clips, that could be neat.

    Why don't you clip parameter automation for this purpose?

    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?

  • edited January 2021

    @MisplacedDevelopment said:
    @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"
    }

    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.

  • edited January 2021

    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"
    }

  • @branis said:
    Here is the GM map from the link above:

    "General MIDI": {
    "35": "Acoustic Bass Drum",...

    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!. 🙃

    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! ;)

    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.

  • _ki_ki
    edited January 2021

    As promised: Here are the mappings that i personaly checked

    {
      "Axon 2" : {
        "36": "Sound 00",
        "37": "Sound 01",
        "38": "Sound 02",
        "39": "Sound 03",
        "40": "Sound 04",
        "41": "Sound 05",
        "42": "Sound 06"
      },
    
      "Elastic Drums" : {
        "36": "Drum 1",
        "37": "Drum 2",
        "38": "Drum 3",
        "39": "Drum 4",
        "40": "Drum 5",
        "41": "Drum 6"    
      },
    
      "Fractal Bits" : {
        "48": "Pad 3-1",
        "49": "Pad 3-2",
        "50": "Pad 3-3",
        "51": "Pad 3-4",
        "52": "Pad 2-1",
        "53": "Pad 2-2",
        "54": "Pad 2-3",
        "55": "Pad 2-4",
        "56": "Pad 1-1",
        "57": "Pad 1-2",
        "58": "Pad 1-3",
        "59": "Pad 1-4"
      },
    
      "MV08" : {
        "60": "BD",
        "61": "SN",
        "62": "CLP",
        "63": "LT",
        "64": "MT",
        "65": "HT",
        "66": "RS",
        "67": "CB",
        "68": "CYM",
        "69": "OH",
        "70": "CH",
        "71": "LC",
        "72": "MC",
        "73": "HC",
        "74": "CLV",
        "75": "MRC"
      },
    
      "Ruismaker GM": {
        "36": "Kick",
        "38": "Snare",
        "39": "Clap",
        "45": "Tom 1",
        "48": "Tom 2",
        "50": "Tom 3",
        "42": "Hit Hat",
        "46": "Open Hi-Hat"
      },
    
      "Ruismaker Noir" : {
        "0":  "N 0",
        "12": "N 12",
        "24": "N 24 ",
        "36": "N 36",
        "48": "N 48",
        "60": "N 60",
        "72": "N 72",
        "84": "N 84",
        "96": "N 96",
        "108": "N 108",
        "120": "N 120"
      },
    
      "Patterning 2" : {
        "60": "Ring 1  Kick",
        "62": "Ring 2  Snare",
        "64": "Ring 3  Closed Hi-Hat",
        "65": "Ring 4  Open Hi-Hat",
        "67": "Ring 5  Perc A",
        "69": "Ring 6  Perc B",
        "71": "Ring 7  Perc C",
        "72": "Ring 8  Perc D"    
      },
    
      "Vatanator AU" : {
        "48": "Pad 1  Kick",
        "51": "Pad 2  Snare",
        "54": "Pad 3  Closed Hi-Hat",
        "57": "Pad 4  Open Hi-Hat",
        "60": "Pad 5",
        "63": "Pad 6",
        "66": "Pad 7",
        "69": "Pad 8  Crash"
      }
    }
    
  • _ki_ki
    edited January 2021

    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:

    {
      "Boom 808" : {
        "36": "BD",
        "37": "SD",
        "42": "CP",
        "50": "LT",
        "51": "MT",
        "52": "HT",
        "58": "CH",
        "57": "OH"    
      },  
    
      "Boom 909" : {
        "36": "BD",
        "37": "SD",
        "42": "CP",
        "50": "LT",
        "51": "MT",
        "52": "HT",
        "67": "CH",
        "68": "OH"    
      },
    
      "Circuit" : {
        "60": "BD",
        "62": "SD",
        "64": "CP",
        "65": "LT",
        "67": "MT",
        "69": "HT",
        "71": "CH",
        "82": "OH"    
      },
    
      "DM1 / DM2" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "37": "LT",
        "56": "MT",
        "43": "HT",
        "42": "CH",
        "46": "OH"    
      },
    
      "DrumBrute" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "47": "LT",
        "45": "MT",
        "40": "HT",
        "42": "CH",
        "43": "OH"    
      },  
    
      "Elliot Garage Drums" : {
        "36": "BD",
        "38": "SD",
        "50": "CP",
        "43": "LT",
        "47": "MT",
        "49": "HT",
        "42": "CH",
        "46": "OH"    
      },  
    
      "Funkbox" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "43": "LT",
        "48": "MT",
        "37": "HT",
        "42": "CH",
        "46": "OH"    
      },  
    
      "Gadget Abu/Tokyo/Ams" : {
        "36": "BD",
        "37": "SD",
        "38": "CP",
        "39": "LT",
        "40": "MT",
        "41": "HT",
        "42": "CH",
        "43": "OH"    
      },
    
    
      "Gadget Bilbao" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "48": "LT",
        "46": "MT",
        "44": "HT",
        "40": "CH",
        "41": "OH"    
      },
    
      "Gadget Gladstone" : {
        "36": "BD",
        "38": "SD",
        "37": "CP",
        "43": "LT",
        "42": "MT",
        "41": "HT",
        "39": "CH",
        "40": "OH"    
      },
    
      "Gadget London" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "42": "LT",
        "43": "MT",
        "37": "HT",
        "40": "CH",
        "41": "OH"    
      },
    
      "Gadget Receife" : {
        "36": "BD",
        "37": "SD",
        "41": "CP",
        "45": "LT",
        "46": "MT",
        "47": "HT",
        "38": "CH",
        "39": "OH"    
      },  
    
      "General Midi" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "43": "LT",
        "47": "MT",
        "50": "HT",
        "42": "CH",
        "46": "OH"    
      },
    
      "iElectribe" : {
        "36": "BD",
        "38": "SD",
        "40": "CP",
        "41": "LT",
        "39": "MT",
        "49": "HT",
        "42": "CH",
        "46": "OH"    
      },  
    
      "iSpark" : {
        "60": "BD",
        "61": "SD",
        "62": "CH",
        "63": "OH",
        "64": "HT",
        "65": "MT",
        "66": "LT",
        "68": "CP"
      },
    
      "SeekBeats" : {
        "48": "BD",
        "49": "SD",
        "50": "CP",
        "51": "LT",
        "52": "MT",
        "53": "HT",
        "54": "CH",
        "55": "OH"    
      },
    
      "TR-8 / 08 / 09" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "43": "LT",
        "47": "MT",
        "50": "HT",
        "42": "CH",
        "46": "OH"    
      },
    
      "Volca Beats" : {
        "36": "BD",
        "38": "SD",
        "39": "CP",
        "43": "LT",
        "50": "MT",
        "75": "HT",
        "42": "CH",
        "46": "OH"    
      }
    }
    
  • @_ki said:
    And these 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 😊

  • @White said:
    That was quick 😊

    I will just include some of the mapping @_ki sent and make another build

  • _ki_ki
    edited January 2021

    I made/tested two more mappings of plugins:

    {
      "DrumComputer (default)“ : {
        "44": "Pad 1  Kick",
        "32": "Pad 2  Snare",
        "83": "Pad 3  Closed Hi-Hat",
        "24": "Pad 4  Perc",
        "36": "Pad 5",
        "47": "Pad 6  Open Hi-Hat",
        "65": "Pad 7  FX",
        "55": "Pad 8  Perc"    
      },
    
      "DigiStix" : {
        "48": "Bass Drum",
        "49": "Snare",
        "50": "Closed Hat",
        "51": "Open Hat",
        "52": "Alt Kick",
        "53": "Clap",
        "54": "Rimshot",
        "55": "Misc. Perc",
        "56": "Hi Tom",
        "57": "Mid Tom",
        "58": "Low Tom",
        "59": "Floor Tom",
        "60": "Crash",
        "61": "Shaker",
        "62": "Ride",
        "63": "Tambourine"
      }
    }
    

    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 :)

  • @sinosoidal said:

    @Optahealth said:

    @Punct said:
    Drum computer, patterning

    PATTERNING +1

    Is this available as Audio Unit Extension? I have Patterning 1 but couldn't find the AUv3 on the list on my AUM.

    Patterning is IIA, no AUV3. Would be nice if it was.

  • edited January 2021

    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.

    @kveis said:
    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?

    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?

  • @Samu said:
    @_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 :)

    Totally missed that. It's almost like a new app now. Thanks! :)

  • edited January 2021

    @auxmux said:
    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?

    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!

  • @gregsmith said:

    @auxmux said:
    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?

    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.

  • @Pxlhg said:

    @Stuntman_mike said:
    New Atom supports Launchpad Mini MK3, when will LK?

    Is it released finally after 7months, can't find it?

    😂 Atom update isn’t released yet, but there is a video showing it out in the wild now (blurred) in AUM and it looks amazing! BTW LK midi learn is great!

  • edited January 2021

    Deleted

  • edited January 2021

    @sinosoidal beta 195 (197): Drum maps are a brilliantly useful addition, no double notes happening (from a Launchpad X in my case) and record quantisation back sounding like I can play in time, great work, thank you.

  • edited January 2021

    @steve99 said:
    @sinosoidal beta 195 (197): Drum maps are a brilliantly useful addition, no double notes happening (from a Launchpad X in my case) and record quantisation back sounding like I can play in time, great work, thank you.

    Thanks for your feedback. Version 1.9.5 is already on the store. :blush:

  • edited January 2021

    due to latest updates suggest add option generate drum events and melodies limited by keyboard and fold notes layouts

  • @Pxlhg said:

    @gregsmith said:

    @auxmux said:
    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?

    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.

    MV08 works as it is for for GR-16 too. I’ll try and find one that does just the bottom 8 pads on GR-16 as that’s where the drums are by default.

    Anyone know how to do Pure Acid’s drums? It just plays the 303 sound.

    @sinosoidal awesome work on the drum maps - mini gamechanger for me!
    I’ve been working on trying to complete a song just using LK in AUM and it’s coming together. Are there plans to improve automation? It’s great that it’s there, but very fiddly at the moment. Would be good if you could make the automation bit full height and have some ‘node tools’ that work on automation nodes to easily move them around and do curves etc. One of the most difficult things I find is to put a node at the very start of a clip. Not impossible but fiddly.

  • @gregsmith said:
    Anyone know how to do Pure Acid’s drums? It just plays the 303 sound.

    Pure Acid drums are on midi channel 10

  • Automation curves for midi cc would be epic for smoother modulation. With the AUM's new midi mapping update, this is already making a huge difference in how I do things.

Sign In or Register to comment.