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

sinosoidal

@krassmann said:
Hi, I try to sync LK and Cubasis. I used LK standalone and turned sync to Midi clock on. I set Midi In to Cubasis 3 and ensured Cubasis generates Midi clock. LK started to receive the Midi clock and adjusted the tempo. So far so good.

LK did not react to start/stop of Cubasis. Both apps were totally not on the beat. Looks like they were not synced on a bar. Totally unusable.

I tried to throw AudioBus into mix. The experience was better. AB being the Midi clock slave and LK loaded as AU in AB and host sync on. Basically works but there is a significant delay which is changing during playback - impossible to compensate. Also not usable.

Any ideas?

Are you loading LK as an audio unit extension into Cubasis?

krassmann

@sinosoidal said:

@krassmann said:
Hi, I try to sync LK and Cubasis. I used LK standalone and turned sync to Midi clock on. I set Midi In to Cubasis 3 and ensured Cubasis generates Midi clock. LK started to receive the Midi clock and adjusted the tempo. So far so good.

LK did not react to start/stop of Cubasis. Both apps were totally not on the beat. Looks like they were not synced on a bar. Totally unusable.

I tried to throw AudioBus into mix. The experience was better. AB being the Midi clock slave and LK loaded as AU in AB and host sync on. Basically works but there is a significant delay which is changing during playback - impossible to compensate. Also not usable.

Any ideas?

Are you loading LK as an audio unit extension into Cubasis?

I tried that as well but it’s also not usable. The problem is that the Midi out of Cubasis tracks can not output the events with their original Midi channel. So the Midi events that LK generates are then all of the same Midi channel and that is the channel that is set at the Midi out routing of the track. This makes it impossible to send the right notes to the instruments. If you set the Midi output to “All” then all notes generated by LK are sent on all 16 channels. I tried to work around with Midi Bus but it’s all not working.

That’s why I try to sync a standalone LK but that’s probably also not really working well. Midi clock on the iPad internally never really worked well for me. For hardware is okay, though. If Cubasis would just implement Ableton link or add a flexible Midi routing like AUM….

soundtemple

@krassmann Without knowing exactly what you are trying to achieve, It sounds to me like you are trying to solve the same problem that many of us are looking to solve here and that is DAW like features with AUM flexible routing. If so, then in my experience i can say that routing midi outside of one environment is a path to frustration and misery. It might seem likes it's theoretically possible but in reality (in my experience) it doesn't work, at least not reliably.

My conclusion, is compromise by keeping everything in one domain and work from there in finding the (compromised) solution that works best for you. ie: Adding DAW like features to AUM with things like LK or dealing with sub-standard routing inside Cubasis3. With recent advances to midi devices like LK, Atom and Helium I'm on the AUM side. Not being a Cubasis3 user I cant argue for advantages of using it. Why Cubasis3 and why not LK with AUM?

krassmann

@soundtemple, I actually do like the workflow in Cubasis 3. Since the sidechaining and better Midi routing in 3.3. I started my last project with Cubasis and the experience is great. I moved my whole sample library into the Cubasis directory and now using audio files became a breeze. Easy browsing and previewing the samples and loops. Just dragging samples on an audio track to try things out. Easy loading of samples into mini sampler directly out of the preview browser. It's just nice. The only I'm missing is the smooth transition from jamming with song sections to a linear arrangement. Moreover I just plugin my nanoKontrol 2 Midi mixer and it just works - no Midi learning session. When I re-arrange track order it is automatically reflected on the controller. All these things are very painful in the LK + AUM setup. So, I'm back being a linear guy.

baccharis

Is there any way to save LK Controller mapping assignments as presets in the stand-alone? Matrix seems to save everything but have not been able to save a Controller preset.

sinosoidal

@baccharis said:
Is there any way to save LK Controller mapping assignments as presets in the stand-alone?

Sorry, but no.

Matrix seems to save everything but have not been able to save a Controller preset.

If you are using the standalone, the controller settings will be saved automatic on a bank basis

If you are using the AUv3, it should be saved with your state.

sinosoidal

We have made available a new beta version of LK (1.10.9 - Build 241) with the following changes:

• Add undo/redo support to automations editor
• Fix clip color when importing
• Fix notes being wrongly create at the end of clip while recording with quantization
• Fix APC 25 clip launching bug

baccharis

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

soundtemple

@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.

sinosoidal

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

Thanks for your feedback!

sinosoidal

@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.

soundtemple

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?

branis

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

soundtemple

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

So much better!!!
Yay!

tahiche

@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]

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

sinosoidal

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

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

Ok, please check your inbox

xglax

@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]

@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]

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

xglax

@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]

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]

@xglax said:
Thanks

You are welcome

[Deleted User]

And two more 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"

sinosoidal

@yug said:
And two more 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.

White

@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]

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

soundtemple

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?

sinosoidal

@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.