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

tahiche

@xglax said:

@mjm1138 said:
I feel like the answer is probably somewhere in this thread but I can’t find it: for some reason, in clip properties, I don’t see the option to assign a midi cc to trigger the clip. I see it mentioned in the manual and have even seen screenshots of the UI, but that setting does not appear for me, whether I have LK running standalone or as an AU. I’m sure I’m missing something obvious, but I’m stumped!

To use cc for clip midi triggering you must press the "Midi Learn" button on the top bar of the Matrix module. When pressing this the clips and buttons will have a purplish overlay meaning that you're in the midi learn mode. Then, you just need to press the clips you want to trigger (they will have a white outline when this is done), one by one, and send the midi cc information to LK. The clips will have a little label indicating which cc and channel are assign to them. Exit the midi learn mode when you're done and you're good to go

I don’t like it when “midi learn” is the only way to assign CC’s. It’s fine for hardware controllers I guess but there’s many cases where you’d just like to input the value manually. To me that should always be an option. You might want to set the CC beforehand and map the control later.

Janosax

@tahiche said:

@xglax said:

@mjm1138 said:
I feel like the answer is probably somewhere in this thread but I can’t find it: for some reason, in clip properties, I don’t see the option to assign a midi cc to trigger the clip. I see it mentioned in the manual and have even seen screenshots of the UI, but that setting does not appear for me, whether I have LK running standalone or as an AU. I’m sure I’m missing something obvious, but I’m stumped!

To use cc for clip midi triggering you must press the "Midi Learn" button on the top bar of the Matrix module. When pressing this the clips and buttons will have a purplish overlay meaning that you're in the midi learn mode. Then, you just need to press the clips you want to trigger (they will have a white outline when this is done), one by one, and send the midi cc information to LK. The clips will have a little label indicating which cc and channel are assign to them. Exit the midi learn mode when you're done and you're good to go

I don’t like it when “midi learn” is the only way to assign CC’s. It’s fine for hardware controllers I guess but there’s many cases where you’d just like to input the value manually. To me that should always be an option. You might want to set the CC beforehand and map the control later.

Yeah it’s better especially when there is midi traffic like several midi messages sent by a single button. Manual value setting makes life a lot easier.

uncledave

@Janosax said:

@tahiche said:

@xglax said:

@mjm1138 said:
I feel like the answer is probably somewhere in this thread but I can’t find it: for some reason, in clip properties, I don’t see the option to assign a midi cc to trigger the clip. I see it mentioned in the manual and have even seen screenshots of the UI, but that setting does not appear for me, whether I have LK running standalone or as an AU. I’m sure I’m missing something obvious, but I’m stumped!

To use cc for clip midi triggering you must press the "Midi Learn" button on the top bar of the Matrix module. When pressing this the clips and buttons will have a purplish overlay meaning that you're in the midi learn mode. Then, you just need to press the clips you want to trigger (they will have a white outline when this is done), one by one, and send the midi cc information to LK. The clips will have a little label indicating which cc and channel are assign to them. Exit the midi learn mode when you're done and you're good to go

I don’t like it when “midi learn” is the only way to assign CC’s. It’s fine for hardware controllers I guess but there’s many cases where you’d just like to input the value manually. To me that should always be an option. You might want to set the CC beforehand and map the control later.

Yeah it’s better especially when there is midi traffic like several midi messages sent by a single button. Manual value setting makes life a lot easier.

Exactly. In Drambo's MIDI learn, you tap the item once for automatic learn, then tap again to receive a full edit popup. This seems like a slick solution.

Janosax

Please could you consider implement record button in AUM instead of knob @sinosoidal that could be super useful:

sinosoidal

@uncledave said:

@Janosax said:

@tahiche said:

@xglax said:

@mjm1138 said:
I feel like the answer is probably somewhere in this thread but I can’t find it: for some reason, in clip properties, I don’t see the option to assign a midi cc to trigger the clip. I see it mentioned in the manual and have even seen screenshots of the UI, but that setting does not appear for me, whether I have LK running standalone or as an AU. I’m sure I’m missing something obvious, but I’m stumped!

To use cc for clip midi triggering you must press the "Midi Learn" button on the top bar of the Matrix module. When pressing this the clips and buttons will have a purplish overlay meaning that you're in the midi learn mode. Then, you just need to press the clips you want to trigger (they will have a white outline when this is done), one by one, and send the midi cc information to LK. The clips will have a little label indicating which cc and channel are assign to them. Exit the midi learn mode when you're done and you're good to go

I don’t like it when “midi learn” is the only way to assign CC’s. It’s fine for hardware controllers I guess but there’s many cases where you’d just like to input the value manually. To me that should always be an option. You might want to set the CC beforehand and map the control later.

Yeah it’s better especially when there is midi traffic like several midi messages sent by a single button. Manual value setting makes life a lot easier.

Exactly. In Drambo's MIDI learn, you tap the item once for automatic learn, then tap again to receive a full edit popup. This seems like a slick solution.

@Janosax said:

@sinosoidal said:

@Janosax said:

@sinosoidal said:
Since the beggining of the week that we have been trying to reproduce th> @onerez said:

@sinosoidal said:

@onerez said:
@sinosoidal I am running new M1 ipad on iOS 15.2. I have AUM set pretty much default but buffer at 1024 see screen shots…. Here is the interesting thing. I have used LK for a LONG time and I have never had this happen, until I added Loopy Pro into the mix…. I am not saying that Loopy is causing it or it could be I am sending midi to 2 different synths on same channel.. but as soon as I added loopy and started to record loops this is when it happens. The other issue it that sometimes I can go through a session and it does not go blank. Does LK dump any logs locally that I could send????

How often does this happen? Does this happen sistematically? Can you easily reproduce it? How? Or is it completely random?

@sinosoidal …. I tried for 30 mins to get it to do it and it would not do it again. Sorry.

Since the beggining of the week that we have been trying to reproduce this problem. It is a rare and random ocurrence. We are definetely able to reproduce it but it can take 3, 5 or 8 minutes tests and sometimes it doesn't happen.

We have uploaded a new build that had an update to the underlying framework we use for our apps. We have been trying to reproduce the problem with this new build without success. We are now looking for others feedback about it.

@gregsmith the issue with UI disappearing on Loopy Pro happens if background audio on Loopy Pro is not enabled (which is not by default). For now, an easy workaround is to enable background audio on Loopy Pro.

Which build is it? I don’t see this in version notes. Last one for me is 1.11.8 272.

I encountered some issues too, like full crashes with LK AUM node asking for reload, and also LK UI freezed (aka LK still sending midi but all graphics freezed and touch unresponsive). I can’t see how to reproduce steps. It’s on iPad M1. Let’s see if this build helps with that too.

That's precisely the build (1.11.8 - 272). We didn't mention I'm mentioned here because it is too vague. However, if we can confirm the issues are gone with it, then we will mention on the update notes.

The issues you describe are exactly what exactly what we are trying to find a solution for. Those are indeed not easily reproducible but as far as we can tell, its more prone to happen on M1 devices. Please give it a go and let me know if it makes any difference. Thanks!

Just spent 30 mn with it and not a single issue. Let’s hope it’s fixed, I will test it more in days to come

Good news!

sinosoidal

@uncledave said:

@Janosax said:

@tahiche said:

@xglax said:

@mjm1138 said:
I feel like the answer is probably somewhere in this thread but I can’t find it: for some reason, in clip properties, I don’t see the option to assign a midi cc to trigger the clip. I see it mentioned in the manual and have even seen screenshots of the UI, but that setting does not appear for me, whether I have LK running standalone or as an AU. I’m sure I’m missing something obvious, but I’m stumped!

To use cc for clip midi triggering you must press the "Midi Learn" button on the top bar of the Matrix module. When pressing this the clips and buttons will have a purplish overlay meaning that you're in the midi learn mode. Then, you just need to press the clips you want to trigger (they will have a white outline when this is done), one by one, and send the midi cc information to LK. The clips will have a little label indicating which cc and channel are assign to them. Exit the midi learn mode when you're done and you're good to go

I don’t like it when “midi learn” is the only way to assign CC’s. It’s fine for hardware controllers I guess but there’s many cases where you’d just like to input the value manually. To me that should always be an option. You might want to set the CC beforehand and map the control later.

Yeah it’s better especially when there is midi traffic like several midi messages sent by a single button. Manual value setting makes life a lot easier.

Exactly. In Drambo's MIDI learn, you tap the item once for automatic learn, then tap again to receive a full edit popup. This seems like a slick solution.

We will try to figure out a solution for this. Thanks for your feedback.

Janosax

Still testing the crash fix @sinosoidal

Before I had a crash every two sessions so 50% of the time.

Since latest beta I made perhaps more than a dozen of sessions on three/four hours and I had only one crash.

It was after clearing a big AUM session with tons of AUV3 (no LK), then opening directly my LK template and starting recording, happened after 2 mn. This was already a condition which seems to be there with crashs I’ve seen before with LK. Perhaps something in memory, even if it’s a 8 Go M1?

After this one, I always closed/reopen AUM before using LK and not a single crash!!!!!! I’m super happy, really!!! Thanks for that fix. LK multichannel input multi recording and abletonesque capabilities are really cool for midi live looping and fast production 😎

sinosoidal

@Janosax said:
Still testing the crash fix @sinosoidal

Before I had a crash every two sessions so 50% of the time.

Since latest beta I made perhaps more than a dozen of sessions on three/four hours and I had only one crash.

It was after clearing a big AUM session with tons of AUV3 (no LK), then opening directly my LK template and starting recording, happened after 2 mn. This was already a condition which seems to be there with crashs I’ve seen before with LK. Perhaps something in memory, even if it’s a 8 Go M1?

After this one, I always closed/reopen AUM before using LK and not a single crash!!!!!! I’m super happy, really!!! Thanks for that fix. LK multichannel input multi recording and abletonesque capabilities are really cool for midi live looping and fast production 😎

This is good news. Really glad to hear it. During the weekend we have released this version to App Store. Let's see what more data tell us.

In the mean time, we are working in version 1.12.0 and making a significant revolution in the midi composer. We should be able to post a new beta really soon to have your early feedback about the changes.

In summary, we are merging the automations editor with the notes editor using a toggle button. This will allow to end with the second drag bar, saving more space and at the same time giving more space for automations editing.

We are also introducing curves to automations lines. By simply dragging a line up and down we can control the curvature.

Another change is to have the tools under the properties inspector layed out in tabs to avoid toggling panels and scrolling up and down.

I'm really looking forward to share this with you.

audiblevideo

Another change is to have the tools under the properties inspector layed out in tabs to avoid toggling panels and scrolling up and down.

I like this

Janosax

Sounds amazing, can’t wait to test @sinosoidal

Janosax

One LK blank screen crash yesterday, 30 mn new session, without closing AUM with a 15 mn session using Wireless Audio AUV3 just before. Fortunately session has been saved only after LK crash and all LK midi data was restored properly with session re opening. It was mixing on iPad internal speakers.

sinosoidal

@Janosax said:
One LK blank screen crash yesterday, 30 mn new session, without closing AUM with a 15 mn session using Wireless Audio AUV3. Fortunately session has been saved only after LK crash and all LK midi data was restored properly with session re opening. It was mixing on iPad internal speakers.

This probably means the issue is still around but is happening less frequently. This is not an easy one.

paikan777

Hi all , testing the last beta in settings , what is " responds to midi start/stop messages" please ? best regards

sinosoidal

@paikan777 said:
Hi all , testing the last beta in settings , what is " responds to midi start/stop messages" please ? best regards

This means that LK with respond to midi realtime messages when enabled. Let's suppose you have a foot pedal that sends a start message when pressed, and a stop message when pressed again, LK transport will react to those message and start/stop transport.

paikan777

Thank you . Ah ok , this is to have a master device play and stop ( and transports ) control LK from its own transports . ( this is globaly the idea I mean and I believe it was asked for AUM ) Got it thx

sinosoidal

@paikan777 said:
Thank you . Ah ok , this is to have a master device play and stop ( and transports ) control LK from its own transports . ( this is globaly the idea I mean and I believe it was asked for AUM ) Got it thx

This was a request from a user who had a foot pedal and wanted to control LK transport with it.

Jeezs

@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.
Another request is triplet quantize it works at record time but there’s no way to quantize at a later time.
At least it’s impossible to create note with length inferior to 1/32 so it’s impossible to create snare flame and other fast note effect.

Thanks

sinosoidal

@Jeezs said:
@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.

This is also we have been requested several times. We need to investigate.

Can you explain better which mouse events and actions lead to erratic note deletion?

Another request is triplet quantize it works at record time but there’s no way to quantize at a later time.

We need to investigate. Thanks for reporting.

At least it’s impossible to create note with length inferior to 1/32 so it’s impossible to create snare flame and other fast note effect.

Opening issue for this. Thanks for reporting.

There is a new LK beta available. (1.12.0 - Build 273). We are testing a composer overhaul. This is what is changing:

• Removed inner drag bar which would allow to see the velocity, probability and automations
• Added a toggle button to switch between notes view and automations editing
• Added a setting to song settings to allow LK transport respond to midi realtime start/stop messages
• Added the ability to change matrix midi assignments using a dialog - @tahiche
• Automations lines can now become curves when dragging up/down on top of them

We are looking for early feedback specially for the new automations editor approach as many of you have request some of this features and changes in the past.

Thank you!

crushed

Thank you for these improvements!
The clip properties panel icons are very clear, and the automations editor is much more convenient.

For those who can’t find this toggle notes/automation: tap on the NOTES label on just above the piano roll

https://forum.audiob.us/uploads/editor/9c/wf0fxlmh70yh.jpeg

gregsmith

@sinosoidal said:

@Jeezs said:
@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.

This is also we have been requested several times. We need to investigate.

Can you explain better which mouse events and actions lead to erratic note deletion?

Another request is triplet quantize it works at record time but there’s no way to quantize at a later time.

We need to investigate. Thanks for reporting.

At least it’s impossible to create note with length inferior to 1/32 so it’s impossible to create snare flame and other fast note effect.

Opening issue for this. Thanks for reporting.

There is a new LK beta available. (1.12.0 - Build 273). We are testing a composer overhaul. This is what is changing:

• Removed inner drag bar which would allow to see the velocity, probability and automations
• Added a toggle button to switch between notes view and automations editing
• Added a setting to song settings to allow LK transport respond to midi realtime start/stop messages
• Added the ability to change matrix midi assignments using a dialog - @tahiche
• Automations lines can now become curves when dragging up/down on top of them

We are looking for early feedback specially for the new automations editor approach as many of you have request some of this features and changes in the past.

Thank you!

You can edit the names of automation lanes now!! That’s a big one for me!! 🙌

It’d be good if the automation lane names were persistent across clips in the same column over different scenes, otherwise you have to name them every time you make a new clip.

The notes/automation as a toggle is fine but it wasn’t particularly obvious it was clickable. It’s better than the drag bar was. Nice to have the extra real estate, especially on iphone.

I couldn’t get the new curve thing to work, but I’m probably not doing it right.

Also feels like a good opportunity to make the automation pencil, eraser etc icons slightly bigger on iphone. I know things are always gonna be fiddly on a small screen but my god they’re tiny! also, what are the little icons to the right of the eraser? Like 2 squares on top of each other?

If you tap and drag from the black bar at the bottom during automation, you get what looks like a marquee selection. Not sure if this is supposed to happen?

Awesome improvements though 👍👍👍

Jeezs

@sinosoidal said:

@Jeezs said:
@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.

This is also we have been requested several times. We need to investigate.

Can you explain better which mouse events and actions lead to erratic note deletion?

Yes with the Magic Mouse 2 a t least if you click on a note to delete it sometimes it delete it sometimes it don’t.

sinosoidal

@crushed said:
Thank you for these improvements!
The clip properties panel icons are very clear, and the automations editor is much more convenient.

For those who can’t find this toggle notes/automation: tap on the NOTES label on just above the piano roll

https://forum.audiob.us/uploads/editor/9c/wf0fxlmh70yh.jpeg

This is provisory location. I think the best location for this button will be the toolbar with a proper icon but we haven't fully decided yet.

sinosoidal

@gregsmith said:

@sinosoidal said:

@Jeezs said:
@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.

This is also we have been requested several times. We need to investigate.

Can you explain better which mouse events and actions lead to erratic note deletion?

Another request is triplet quantize it works at record time but there’s no way to quantize at a later time.

We need to investigate. Thanks for reporting.

At least it’s impossible to create note with length inferior to 1/32 so it’s impossible to create snare flame and other fast note effect.

Opening issue for this. Thanks for reporting.

There is a new LK beta available. (1.12.0 - Build 273). We are testing a composer overhaul. This is what is changing:

• Removed inner drag bar which would allow to see the velocity, probability and automations
• Added a toggle button to switch between notes view and automations editing
• Added a setting to song settings to allow LK transport respond to midi realtime start/stop messages
• Added the ability to change matrix midi assignments using a dialog - @tahiche
• Automations lines can now become curves when dragging up/down on top of them

We are looking for early feedback specially for the new automations editor approach as many of you have request some of this features and changes in the past.

Thank you!

You can edit the names of automation lanes now!! That’s a big one for me!! 🙌

It’d be good if the automation lane names were persistent across clips in the same column over different scenes, otherwise you have to name them every time you make a new clip.

This is a setting per clip, as other clips might not have the same label for the same cc, right? Making it available per tracks might not seem very logical because if you paste a clip from a another track, it would get the new lanes names.

What if this gets along if the clip is copied/pasted?

The notes/automation as a toggle is fine but it wasn’t particularly obvious it was clickable. It’s better than the drag bar was. Nice to have the extra real estate, especially on iphone.

This is a really really raw beta. One of the main goals was to be on TestFlight for early feedback. We are looking to have a nice icon on the toolbar instead. But at this stage we are open to suggestions.

I couldn’t get the new curve thing to work, but I’m probably not doing it right.

Also feels like a good opportunity to make the automation pencil, eraser etc icons slightly bigger on iphone. I know things are always gonna be fiddly on a small screen but my god they’re tiny!

Sounds reasonable

also, what are the little icons to the right of the eraser? Like 2 squares on top of each other?

copy/paste of automations. You can have a selection of automations, copy it and then paste it on another clip.

We are ironing the interaction to allow selection without having to untoggle between notes and automations. Next beta should have that

If you tap and drag from the black bar at the bottom during automation, you get what looks like a marquee selection. Not sure if this is supposed to happen?

Probably a left over bug.

Awesome improvements though 👍👍👍

Thanks for your feedback!

sinosoidal

@Jeezs said:

@sinosoidal said:

@Jeezs said:
@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.

This is also we have been requested several times. We need to investigate.

Can you explain better which mouse events and actions lead to erratic note deletion?

Yes with the Magic Mouse 2 a t least if you click on a note to delete it sometimes it delete it sometimes it don’t.

Ok, thanks for your feeedback!

gregsmith

@sinosoidal said:

@gregsmith said:

@sinosoidal said:

@Jeezs said:
@sinosoidal
Is it possible to support mouse events, for now, scroll doesn’t work and note deletion work erratically.

This is also we have been requested several times. We need to investigate.

Can you explain better which mouse events and actions lead to erratic note deletion?

Another request is triplet quantize it works at record time but there’s no way to quantize at a later time.

We need to investigate. Thanks for reporting.

At least it’s impossible to create note with length inferior to 1/32 so it’s impossible to create snare flame and other fast note effect.

Opening issue for this. Thanks for reporting.

There is a new LK beta available. (1.12.0 - Build 273). We are testing a composer overhaul. This is what is changing:

• Removed inner drag bar which would allow to see the velocity, probability and automations
• Added a toggle button to switch between notes view and automations editing
• Added a setting to song settings to allow LK transport respond to midi realtime start/stop messages
• Added the ability to change matrix midi assignments using a dialog - @tahiche
• Automations lines can now become curves when dragging up/down on top of them

We are looking for early feedback specially for the new automations editor approach as many of you have request some of this features and changes in the past.

Thank you!

You can edit the names of automation lanes now!! That’s a big one for me!! 🙌

It’d be good if the automation lane names were persistent across clips in the same column over different scenes, otherwise you have to name them every time you make a new clip.

This is a setting per clip, as other clips might not have the same label for the same cc, right? Making it available per tracks might not seem very logical because if you paste a clip from a another track, it would get the new lanes names.

What if this gets along if the clip is copied/pasted?

Yeah that sounds reasonable! 👍

krassmann

I want to use LK and Loopy Pro together in AUM and use my Launchpad X with Loopy. I turn off the LPX in LK but when I load the AUM project again LK takes over the Launchpad again. Is there any way how to make the controller settings in LK permanent? It does not seem to store it in its AU state.

gregsmith

@krassmann said:
I want to use LK and Loopy Pro together in AUM and use my Launchpad X with Loopy. I turn off the LPX in LK but when I load the AUM project again LK takes over the Launchpad again. Is there any way how to make the controller settings in LK permanent? It does not seem to store it in its AU state.

Presumably it’s the same issue with LK hosted in loopy as well.

xglax

@gregsmith

To use the automation curves, you must have the shift button enabled. Then, just move the lines between automation nodes up and down, and they will curve accordingly.

xglax

@krassmann said:
I want to use LK and Loopy Pro together in AUM and use my Launchpad X with Loopy. I turn off the LPX in LK but when I load the AUM project again LK takes over the Launchpad again. Is there any way how to make the controller settings in LK permanent? It does not seem to store it in its AU state.

Do you turn off LPX under the MIDI tab, or under the Controllers tab?

gregsmith

@xglax said:
@gregsmith

To use the automation curves, you must have the shift button enabled. Then, just move the lines between automation nodes up and down, and they will curve accordingly.

Ah! Thank you. Forgot about the shift button