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

1…8586889091…130

Comments

  • soundtemplesoundtemple

    @sinosoidal With Follow actions if I have two clips
    1. Clip action: Next Notes action: Generate Melody
    2. Clip action: Previous Notes action: Generate Melody

    The clips keep playing one after the other which is perfect but it seems the generate melody never happens.
    If I turn the clip action off then the melody generation returns.

    Is it one or the other for follow actions or should I be able to have both going on?

    My intention is to have a regular, unchanging loop (say 3 bars) play and then jump to the next clip for 1 bar that re-generates melody each time it is triggered and then returns to the previous 3 bar loop.

  • sinosoidalsinosoidal

    @baccharis said:
    @sinosoidal thanks for the info! Really enjoying using Controller with Drambo...both as AUv3 or stand-alone

    Thanks for your feedback! :blush:

  • sinosoidalsinosoidal

    @soundtemple said:
    @sinosoidal With Follow actions if I have two clips
    1. Clip action: Next Notes action: Generate Melody
    2. Clip action: Previous Notes action: Generate Melody

    The clips keep playing one after the other which is perfect but it seems the generate melody never happens.
    If I turn the clip action off then the melody generation returns.

    Is it one or the other for follow actions or should I be able to have both going on?

    My intention is to have a regular, unchanging loop (say 3 bars) play and then jump to the next clip for 1 bar that re-generates melody each time it is triggered and then returns to the previous 3 bar loop.

    We need to investigate what is going on.

  • soundtemplesoundtemple

    I can select a clip without playing it using shift but is there a way to select a scene without playing all clips?

    With LK as an AUV3, when I stop the host I want to set the active scene to play back to the first scene.
    It seems to me that the only way to do this is:
    -Stop host
    -Trigger first scene in LK
    -Press stop in LK

    Is there a better way?
    Is there a way to disable LK transport and rely only on Host transport?

  • branisbranis

    @soundtemple said:
    I can select a clip without playing it using shift but is there a way to select a scene without playing all clips?

    With LK as an AUV3, when I stop the host I want to set the active scene to play back to the first scene.
    It seems to me that the only way to do this is:
    -Stop host
    -Trigger first scene in LK
    -Press stop in LK

    Is there a better way?
    Is there a way to disable LK transport and rely only on Host transport?

    Yes, just lock the clock source to host:

  • soundtemplesoundtemple

    @branis ah thanks. I never knew that little white infinity sign could turn gold!!!

    So much better!!!
    Yay!

  • tahichetahiche

    @branis said:

    @soundtemple said:
    I can select a clip without playing it using shift but is there a way to select a scene without playing all clips?

    With LK as an AUV3, when I stop the host I want to set the active scene to play back to the first scene.
    It seems to me that the only way to do this is:
    -Stop host
    -Trigger first scene in LK
    -Press stop in LK

    Is there a better way?
    Is there a way to disable LK transport and rely only on Host transport?

    Yes, just lock the clock source to host:

    Gold it is!

  • [Deleted User][Deleted User]

    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)
    • The layouts for GR-16 and sEGments have only 15 keys, both have Pad 2 missing
    • DM1/DM2 are missing 1 pad
    • Bilbao and Recife from Gadget have 16 pads, but only 8 in LK. Also, Gladstone has 10, not 8
    • The list is not properly sorted

    Hope this helps make LK better :) I'm gonna continue playing with it, really enjoy it. I must say I'm really surprised how well it works on the smaller screen of my iPhone SE. Great job

  • sinosoidalsinosoidal

    @yug said:
    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)

    This sounds like a bug. We will fix it for 1.10.9

    • The layouts for GR-16 and sEGments have only 15 keys, both have Pad 2 missing
    • DM1/DM2 are missing 1 pad
    • Bilbao and Recife from Gadget have 16 pads, but only 8 in LK. Also, Gladstone has 10, not 8
    • The list is not properly sorted

    Most of these keyboards layouts were provided by community and we didn't personally check all of them because sometimes we don't even have the app.

    We might need your help to validate and fix.

    Hope this helps make LK better :) I'm gonna continue playing with it, really enjoy it. I must say I'm really surprised how well it works on the smaller screen of my iPhone SE. Great job

    Wanne join TestFlight? Please send me pvt message! :blush:

  • [Deleted User][Deleted User]

    @sinosoidal said:

    @yug said:
    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)

    This sounds like a bug. We will fix it for 1.10.9

    More on this: it actually gets updated but only after I touch one of the keys

    @sinosoidal said:
    Wanne join TestFlight? Please send me pvt message! :blush:

    Ok, please check your inbox

  • xglaxxglax

    @yug said:
    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)
    • The layouts for GR-16 and sEGments have only 15 keys, both have Pad 2 missing
    • DM1/DM2 are missing 1 pad
    • Bilbao and Recife from Gadget have 16 pads, but only 8 in LK. Also, Gladstone has 10, not 8
    • The list is not properly sorted

    Hope this helps make LK better :) I'm gonna continue playing with it, really enjoy it. I must say I'm really surprised how well it works on the smaller screen of my iPhone SE. Great job

    Can someone please help me fix the layouts that were reported by @yug ?

    This is what we have in LK:

    DM1/DM2 (missing one pad):
    "36": "BD",
    "38": "SD",
    "39": "CP",
    "37": "LT",
    "56": "MT",
    "43": "HT",
    "42": "CH",
    "46": "OH"

    Gadget Bilbao (missing 8 pads):
    "36": "BD",
    "38": "SD",
    "39": "CP",
    "48": "LT",
    "46": "MT",
    "44": "HT",
    "40": "CH",
    "41": "OH"

    Gadget Recife (missing 8 pads)
    "36": "BD",
    "37": "SD",
    "41": "CP",
    "45": "LT",
    "46": "MT",
    "47": "HT",
    "38": "CH",
    "39": "OH"

    Gadget Gladstone (missing 2 pads)
    "36": "BD",
    "38": "SD",
    "37": "CP",
    "43": "LT",
    "42": "MT",
    "41": "HT",
    "39": "CH",
    "40": "OH"

    Thanks in advance =)

  • [Deleted User][Deleted User]
    edited June 2021

    @xglax said:

    @yug said:
    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)
    • The layouts for GR-16 and sEGments have only 15 keys, both have Pad 2 missing
    • DM1/DM2 are missing 1 pad
    • Bilbao and Recife from Gadget have 16 pads, but only 8 in LK. Also, Gladstone has 10, not 8
    • The list is not properly sorted

    Hope this helps make LK better :) I'm gonna continue playing with it, really enjoy it. I must say I'm really surprised how well it works on the smaller screen of my iPhone SE. Great job

    Can someone please help me fix the layouts that were reported by @yug ?

    I'm working on it

  • [Deleted User][Deleted User]

    @yug said:

    @xglax said:

    @yug said:
    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)
    • The layouts for GR-16 and sEGments have only 15 keys, both have Pad 2 missing
    • DM1/DM2 are missing 1 pad
    • Bilbao and Recife from Gadget have 16 pads, but only 8 in LK. Also, Gladstone has 10, not 8
    • The list is not properly sorted

    Hope this helps make LK better :) I'm gonna continue playing with it, really enjoy it. I must say I'm really surprised how well it works on the smaller screen of my iPhone SE. Great job

    Can someone please help me fix the layouts that were reported by @yug ?

    I'm working on it

    Ok, this is for Gadget:

    Gadget London
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8"

Gadget Tokyo/Amsterdam
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4"

Gadget Gladstone
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8",
"44": "Pad 9",
"45": "Pad 10"

Gadget Bilbao/Recife/Abu Dhabi
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8",
"44": "Pad 9",
"45": "Pad 10",
"46": "Pad 11",
"47": "Pad 12",
"48": "Pad 13",
"49": "Pad 14",
"50": "Pad 15",
"51": "Pad 16"
  • xglaxxglax

    @yug said:

    @yug said:

    @xglax said:

    @yug said:
    Hi @sinosoidal

    I'm currently evaluating LK Matrix, trying to find out whether it works for me before buying the unlock. I must say I really like it so far, but in the process of making it control some of the drum apps I own I've found a couple bugs and inconsistencies

    • When switching between 2 keyboard layouts with the same amount of keys, the piano roll keys are not updated. For example, when switching from iElectribe to iSpark, it redraws the piano roll but not the piano keys on the left side. This does not happen when switching from 8 to 16 keys (i.e. iSpark to sEGments)
    • The layouts for GR-16 and sEGments have only 15 keys, both have Pad 2 missing
    • DM1/DM2 are missing 1 pad
    • Bilbao and Recife from Gadget have 16 pads, but only 8 in LK. Also, Gladstone has 10, not 8
    • The list is not properly sorted

    Hope this helps make LK better :) I'm gonna continue playing with it, really enjoy it. I must say I'm really surprised how well it works on the smaller screen of my iPhone SE. Great job

    Can someone please help me fix the layouts that were reported by @yug ?

    I'm working on it

    Ok, this is for Gadget:

    Gadget London
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8"

Gadget Tokyo/Amsterdam
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4"

Gadget Gladstone
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8",
"44": "Pad 9",
"45": "Pad 10"

Gadget Bilbao/Recife/Abu Dhabi
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8",
"44": "Pad 9",
"45": "Pad 10",
"46": "Pad 11",
"47": "Pad 12",
"48": "Pad 13",
"49": "Pad 14",
"50": "Pad 15",
"51": "Pad 16"

    Thanks =)

  • [Deleted User][Deleted User]
    edited June 2021

    Now, more. I've renamed some pads so that they have same names in LK and in the corresponding app. Also, I've added mappings for Hammerhead.
    You know what.. you can actually remove the (GM) keymaps for Ruismaker's, they are not really needed

    Groove Rider GR-16
(From the manual:
Play midi notes to GR-16 from your midi controller. In this mode, every two octaves (24 notes) on midi keyboard are mapped to Pads (1-16) with 8 unused notes left in each second octave. So, Pad 1 is mapped to midi notes C1, C3, C5 etc., Pad 2 is mapped to midi notes C#1, C#3, C#5 etc.)
"24": "Pad 1",
"25": "Pad 2",
"26": "Pad 3",
"27": "Pad 4",
"28": "Pad 5",
"29": "Pad 6",
"30": "Pad 7",
"31": "Pad 8",
"32": "Pad 9",
"33": "Pad 10",
"34": "Pad 11",
"35": "Pad 12",
"36": "Pad 13",
"37": "Pad 14",
"38": "Pad 15",
"39": "Pad 16"

sEGments
"60": "Pad 1",
"61": "Pad 2",
"62": "Pad 3",
"63": "Pad 4",
"64": "Pad 5",
"65": "Pad 6",
"66": "Pad 7",
"67": "Pad 8",
"68": "Pad 9",
"69": "Pad 10",
"70": "Pad 11",
"71": "Pad 12",
"72": "Pad 13",
"73": "Pad 14",
"74": "Pad 15",
"75": "Pad 16"

DM1/DM2/DrumLab
"36": "Kick",
"37": "Rimshot",
"38": "Snare",
"39": "Clap",
"42": "HH closed",
"43": "Tom",
"46": "HH open",
"49": "Cymbal",
"56": "Cowbell"

Ruismaker
"49": "BD",
"51": "SD",
"54": "CP",
"56": "LT",
"58": "MT",
"61": "HT",
"63": "CH",
"66": "OH"

Ruismaker (GM)
"36": "BD",
"38": "SD",
"39": "CP",
"42": "CH",
"45": "LT",
"46": "OH",
"48": "MT",
"50": "HT"

Ruismaker FM
"49": "1",
"51": "2",
"54": "3",
"56": "4",
"58": "5",
"61": "6"

Ruismaker FM (GM)
"36": "1",
"38": "2",
"39": "3",
"45": "4",
"48": "5",
"50": "6"

Hammerhead
"49": "Ch 1",
"51": "Ch 2",
"54": "Ch 3",
"56": "Ch 4",
"58": "Ch 5",
"61": "Ch 6",
"63": "Ch 7",
"66": "Ch 8"

Hammerhead (Patterns)
"24": "P1",
"25": "P2",
"26": "P3",
"27": "P4",
"28": "P5",
"29": "P6",
"30": "P7",
"31": "P8"

    EDIT: Changed "DM1/DM2" to "DM1/DM2/DrumLab"

  • [Deleted User][Deleted User]

    @xglax said:
    Thanks =)

    You are welcome :)

  • [Deleted User][Deleted User]

    And two more :D That's it for now. Everything else is either correct or I just don't have that app

    iElectribe
"36": "Synth 1",
"38": "Synth 2",
"39": "CL/SD",
"40": "Synth 3",
"41": "Synth 4",
"42": "HC",
"46": "HO",
"49": "CY"

iSpark
"60": "Pad 1",
"61": "Pad 2",
"62": "Pad 3",
"63": "Pad 4",
"64": "Pad 5",
"65": "Pad 6",
"66": "Pad 7",
"67": "Pad 8",
"68": "Pad 9",
"69": "Pad 10",
"70": "Pad 11",
"71": "Pad 12",
"72": "Pad 13",
"73": "Pad 14",
"74": "Pad 15",
"75": "Pad 16"
  • sinosoidalsinosoidal

    @yug said:
    And two more :D That's it for now. Everything else is either correct or I just don't have that app

    iElectribe
"36": "Synth 1",
"38": "Synth 2",
"39": "CL/SD",
"40": "Synth 3",
"41": "Synth 4",
"42": "HC",
"46": "HO",
"49": "CY"

iSpark
"60": "Pad 1",
"61": "Pad 2",
"62": "Pad 3",
"63": "Pad 4",
"64": "Pad 5",
"65": "Pad 6",
"66": "Pad 7",
"67": "Pad 8",
"68": "Pad 9",
"69": "Pad 10",
"70": "Pad 11",
"71": "Pad 12",
"72": "Pad 13",
"73": "Pad 14",
"74": "Pad 15",
"75": "Pad 16"

    We published a new beta but this last two haven't been updated.

  • WhiteWhite

    @sinosoidal

    Here are some more keyboard layouts:

    "DigiStix" : {
    "48": "Pad 1",
    "49": "Pad 2",
    "50": "Pad 3",
    "51": "Pad 4",
    "52": "Pad 5",
    "53": "Pad 6",
    "54": "Pad 7",
    "55": "Pad 8",
    "56": "Pad 9",
    "57": "Pad 10",
    "58": "Pad 11",
    "59": "Pad 12",
    "60": "Pad 13",
    "61": "Pad 14",
    "62": "Pad 15",
    "63": "Pad 16"
    }

    "Drum Session" : {
    "26": "Cymb stop",
    "27": "Woodblock low",
    "28": "Woodblock low dbl",
    "29": "Woodblock hi",
    "30": "Woodblock hi dbl",
    "31": "Tamb tap",
    "32": "Tamb shake",
    "33": "Clap solo",
    "34": "Clap multi",
    "35": "Stick hit",
    "36": "Kick damp",
    "37": "Snare side",
    "38": "Snare center",
    "39": "Snare rim",
    "40": "Snare half",
    "41": "Tom 4 center",
    "42": "Cl hihat tip",
    "43": "Tom 3 center",
    "44": "Cl hihat pedal",
    "45": "Tom 2 center",
    "46": "Open hihat cntrl",
    "47": "Tom 1 center",
    "48": "Hi crash tip",
    "49": "Hi crash edge",
    "50": "Hi crash bell",
    "51": "Ride tip",
    "52": "Ride edge",
    "53": "Ride bell",
    "54": "Low crash tip",
    "55": "Low crash edge",
    "56": "Low crash bell",
    "57": "China edge",
    "58": "China tip",
    "59": "Splash edge",
    "60": "Kick open",
    "61": "Snare rim only",
    "62": "Snare flam",
    "63": "Snare roll",
    "64": "Snare off",
    "65": "Tom 4 rim",
    "66": "Cl hihat tt",
    "67": "Tom 3 rim",
    "68": "Cl hihat shank",
    "69": "Tom 2 rim",
    "70": "Open hihat pedal",
    "71": "Tom 1 rim",
    "72": "Tom 4 rim only",
    "73": "Tom 3 rim only",
    "74": "Tom 2 rim only",
    "75": "Tom 1 rim only",
    "76": "Open hihat qtr",
    "77": "Open hihat hif",
    "78": "Open hihat 3qtr",
    "79": "Open hihat loose",
    "80": "Open hihat full",
    "81": "Snare ctr lft",
    "83": "Snare ctr right",
    "84": "Snare half lft",
    "85": "Cl hihat tt lft",
    "86": "Snare half right",
    "87": "Cl hihat tt right",
    "88": "Tom 4 ctr lft",
    "89": "Tom 4 ctr right",
    "90": "Cl hihat tip lft",
    "91": "Tom 3 ctr lft",
    "92": "Cl hihat tip right",
    "93": "Tom 3 ctr rt",
    "94": "Cl hihat shank lft",
    "95": "Tom 2 ctr lft",
    "96": "Tom 2 ctr rt",
    "97": "Cl hihat shank rt",
    "98": "Tom 1 ctr lft",
    "99": "Cymb stop",
    "100": "Tom 1 ctr right"
    }

    "FAC Drumkit" : {
    "36": "Pad 1",
    "37": "Pad 2",
    "38": "Pad 3",
    "39": "Pad 4",
    "40": "Pad 5",
    "41": "Pad 6",
    "42": "Pad 7",
    "43": "Pad 8",
    "44": "Pad 9",
    "45": "Pad 10",
    "46": "Pad 11",
    "47": "Pad 12",
    "48": "Pad 13",
    "49": "Pad 14",
    "50": "Pad 15",
    "51": "Pad 16"
    }

  • [Deleted User][Deleted User]

    @sinosoidal said:
    We published a new beta but this last two haven't been updated.

    I've tested the updated layouts in the new beta and all but GR-16 worked fine. I made a mistake with GR-16 because they've used a different octave naming convention in the manual.

    Also, I have an idea. I think the keyboard layout setting should be per-track, not per-clip. It's a very tedious process to set it for every new clip. There are 2 ways this can be implemented:
    1. Make it per-track only, no ability to change it for a single clip
    2. Add it to track properties and make every new clip on that track inherit that setting by default. The user will be able to go to clip properties and change it there if needed
    Just some food for thought.

    Anyway, here's correct mappings for GR-16:

    GR-16
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8",
"44": "Pad 9",
"45": "Pad 10",
"46": "Pad 11",
"47": "Pad 12",
"48": "Pad 13",
"49": "Pad 14",
"50": "Pad 15",
"51": "Pad 16"
  • soundtemplesoundtemple

    Is it possible to save midi learn assignments with an LK project?
    ie: not with an AUM session ... but with the LK project. So, opening an LK project in an AUV3 instance opens project midi learn assignments?

  • sinosoidalsinosoidal

    @yug said:

    @sinosoidal said:
    We published a new beta but this last two haven't been updated.

    I've tested the updated layouts in the new beta and all but GR-16 worked fine. I made a mistake with GR-16 because they've used a different octave naming convention in the manual.

    Also, I have an idea. I think the keyboard layout setting should be per-track, not per-clip. It's a very tedious process to set it for every new clip. There are 2 ways this can be implemented:
    1. Make it per-track only, no ability to change it for a single clip
    2. Add it to track properties and make every new clip on that track inherit that setting by default. The user will be able to go to clip properties and change it there if needed
    Just some food for thought.

    Anyway, here's correct mappings for GR-16:

    GR-16
"36": "Pad 1",
"37": "Pad 2",
"38": "Pad 3",
"39": "Pad 4",
"40": "Pad 5",
"41": "Pad 6",
"42": "Pad 7",
"43": "Pad 8",
"44": "Pad 9",
"45": "Pad 10",
"46": "Pad 11",
"47": "Pad 12",
"48": "Pad 13",
"49": "Pad 14",
"50": "Pad 15",
"51": "Pad 16"

    You can also copy a clip with a certain keyboard layout and paste it. No need to set it up again.

  • onerezonerez

    Hey folks. Help with Midi Trigger. I have looked until my eyes have bleed, but please is there a way to do this? I can’t get midi learn to do anything. I just want one clip to trigger other clips. I want one clip to rule them all!!!! 😁🙏

  • Model10000Model10000

    If I’m understanding it right, map the scene?

  • onerezonerez

    @Model10000 I have clip one as sort of my song template for AUM. It’s like 65 bars long and I can trigger various items . I want to be able to use clips with in clips of LK to trigger them. I don’t care if I need to use another instance.. I am just trying to avoid using atom2.

  • branisbranis
    edited June 2021

    I found a way to do it. In this example the first track is the master track containing the master clip that launches all other clips.

    First set LK as a midi input for LK and set it to receive only from channel 1:

    set the master channel to send to midi channel 1 but receive no midi, set others to receive from 1, but send to other than 1:

    then midi learn a note for each clip:

    Enter the selected notes in the master clip:

  • onerezonerez

    @branis

    Dang every time I try this I get N/A on all mappable items……. 😢. Anything you can think of that I don’t have set right?

  • onerezonerez

    OK….. making progress, but I can’t get the midi trigger to be other then channel 0?? And it triggers the whole scene and not just the one clip.

  • onerezonerez

    Never mind now. I believe I have it all sorted with starts and stops.

    Thanks @branis

  • branisbranis

    @sinosoidal It looks like there is a small bug in LK - only in clips CH: 0 actually means MIDI channel 1. If I send a note from my controller to LK on channel 2, LK registers CH: 1. This doesn't happen in other MIDI learn destinations.

    @onerez In your screenshot I see that you mapped a trigger to the scene, maybe you have that note in the master clip so it triggers the scene

Sign In or Register to comment.

© Vanilla Keystone Theme 2024