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

espiegel123

@sinosoidal said:

@RajahP said:

@sinosoidal said:

@RajahP said:
Well, Ableton 11 (Beta) turned the piano roll into a ‘midi tool’.. and, probability is not just an enhancements, but a performance feature that can dynamically change a clip/project..

I think LK’s piano roll should be a separate module from the launcher.. with both getting their own TLC.... working with each other...

I think it would be even more cumbersome to switch between modules just to edit notes. What is TLC?

Tender Loving Care (TLC)... You do have a point...How about a floating Paino Roll. My 2 cents... Thanks for the response..

It would be possible to have multiple floating windows for each clip. Those windows, would be inside the the LK AUv3 though. Would that be better? I'm not sure yet. Specially on phone.

Even on a 9.7” iPad in full screen, I don’t think there is enough space to deal with multiple piano roll windows. One (non-trivial but elegant solution) would be multiple layers in the piano roll with each layer’s notes displayed in a different color and edit actions target at the “active” layer.

espiegel123

@sinosoidal said:

@nnbveh said:

P.S. Oh, and what's the deal with transport when using it inside hosts like AUM and ApeMatrix? I can still start and stop it separately, and this is really confusing, THREE sets of transport controls, all operating independently, it's quite a mess

This question has been raised already. We allow LK to work without being tied to it's AUv3. This can be good and a bad thing depending on the user. Some users have already suggested a button which would lock it to the host. We might implement that feature. Right now, if you want to sync them together you just need to pause and set the host transport controls to the beggining and play again.

Let me know if you would like to test the forthcomming version and provide feedback for your use cases. Thank you!

Since clock source is always host in the AU, you could use that space at top of window for Transport popup with options host or LK. I find the current setup difficult (particularly for those projects where I would like to start by recording MIDI whose length is not predetermined) as there isn’t a way to record the first clip with a count off or click so that you can start on one. The workaround of starting play back in the plugin and stopping the host transport is kind of cumbersome (and as far as I can tell doesn’t allow for a first clip without a pre-determined length to be recorded).

p.s. it would be great if LK let you choose a input controller protocol so that even if you don’t have a launchpad (or other controller LK has mappings for) that you could send the same MIDI such a controller would. This would allow one to use Mozaic or MIDIDesigner to remote control LK without the laborious process of setting up the triggers for each clip manually.

RajahP

@sinosoidal said:

@dobbs said:
Maybe on phones/ipad minis shift+click could just open the piano roll in "fullscreen" mode

That's basically what the draggable split viewport does. What's the gain? 5 mm of extra height?

I'm trying to figure out the cons and pros for approaching this with another angle than the draggable slit viewport.

@dobbs said:
ok I've only just discovered you don't have to drag it but can also just tap on the bar to open it fullscreen... forget what I said before

The ‘tap’ works well.. ✌️ Maybe all we need are some ‘cosmetic’ colorations to highlight the piano roll borders.. I was using long press on the clip and selecting properties... Tap helped a lot...😉.. Thanks...

dobbs

One (non-trivial but elegant solution) would be multiple layers in the piano roll with each layer’s notes displayed in a different color and edit actions target at the “active” layer.

That would be awesome! I think i've seen that in another app, atom maybe?

nnbveh

@sinosoidal
PM'ed you.

Model10000

Maybe a bit of an out there idea, but I’ve got a lot of midi files generated over time. Would be cool if you could preview midi sounds (with drum/synth etc LK is output to) in files app before importing them to LK.

nnbveh

I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

branis

@nnbveh said:
I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

I have both, but I never really used Modstep. A big advantage that LK has over Modstep is that it can be used as an AUv3 inside other hosts such as AUM or Audiobus.

Modstep is interesting, but it hasn’t been updated in a while even though it is buggy and crashy (at least for me). On the other hand LK is very actively developed and at this moment you can help shape it with your ideas which is great.

espiegel123

@nnbveh said:
I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

Because LK can be loaded as an AUv3 inside a host such as AUM. In those cases, it can be a nice workflow to have your clip launcher in the host you prefer working with. It doesn’t obviate the need for ModStep for people making full use of Modstep.

nnbveh

@branis said:

@nnbveh said:
I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

I have both, but I never really used Modstep. A big advantage that LK has over Modstep is that it can be used as an AUv3 inside other hosts such as AUM or Audiobus.

Modstep is interesting, but it hasn’t been updated in a while even though it is buggy and crashy (at least for me). On the other hand LK is very actively developed and at this moment you can help shape it with your ideas which is great.

My plan was/is to use it to control other things like hardware/software instruments on the laptop mostly, not the ipad apps, although i've bought Segments and apeMatrix as well while it was all on sale))

nnbveh

@espiegel123 said:

@nnbveh said:
I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

Because LK can be loaded as an AUv3 inside a host such as AUM. In those cases, it can be a nice workflow to have your clip launcher in the host you prefer working with. It doesn’t obviate The need for ModStep for people making full use of Modstep.

I wanted to use LK with external software/hardware, not the ipad apps, but after trying it the clock issues are just too big for now. Tried Drambo as a midi sequencer and it seem to be more stable.

nnbveh

@nnbveh said:

@espiegel123 said:

@nnbveh said:
I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

Because LK can be loaded as an AUv3 inside a host such as AUM. In those cases, it can be a nice workflow to have your clip launcher in the host you prefer working with. It doesn’t obviate The need for ModStep for people making full use of Modstep.

I wanted to use LK with external software/hardware, not the ipad apps, but after trying it the clock issues are just too big for now. Tried Drambo as a midi sequencer and it seem to be more stable.

Figured out that sync problem was mostly about the other piece of software, tested latest beta, clock seem to be quite tight!

sinosoidal

@nnbveh said:
Figured out that sync problem was mostly about the other piece of software, tested latest beta, clock seem to be quite tight!

Awesome! Thanks for your feedback.

sinosoidal

If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

tahiche

@branis said:

@nnbveh said:
I'm kind of new to the whole ipad sequencing thing and when i've read about LK it sounded like it's the first ableton-style midi clip launcher that's why i bought it. Apparently there's a Modstep app which looks very mature and does all that and maybe more. Why people choose LK over it(except Ableton integration)? Is there someone who use both?

I have both, but I never really used Modstep. A big advantage that LK has over Modstep is that it can be used as an AUv3 inside other hosts such as AUM or Audiobus.

Modstep is interesting, but it hasn’t been updated in a while even though it is buggy and crashy (at least for me). On the other hand LK is very actively developed and at this moment you can help shape it with your ideas which is great.

Modstep is great and probably ahead of its time, but the UI and workflow I found really confusing. I would struggle and figure out where something was, come back a few days later and felt lost again. It didn’t make sense to me, which is a pity cos feature wise it’s a killer app.
I do think LK’s UI could be improved, making some things more obvious or easily accessible, but unlike Modstep, LK is VERY actively maintained and getting better at a staggering rate. I highly recommend it.

PeteSasqwax

Launchcontrol XL seems like the most powerful in relation to LK's feature set (full disclosure: yes, I do have one 😉)

Aletheia

@sinosoidal said:
If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

Launchpad Pro Mk3 because if you already have its smaller brothers it should be really easy to add this. It would make the workflow even faster.

skrat

@sinosoidal said:
If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

As I mentioned, I'd really be happy if you provide generic way to support controllers. But my love goes to AKAI APC40 (MK2) - it's the 'all-in-one' controller for live playing. I believe it should be simple to add as you already support AKAI APC series, maybe not even extra effort. I am on TestFlight so feel free to approach me to test it if needed.

Tatobx

@sinosoidal said:
If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

LaunchKey Mini MK3 which, by the way, is already compatible with Ableton and has specific functions for it that you could emulate

kveis

@sinosoidal said:
If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

Another vote for Launchpad Pro MK3 here.

branis

Of course, everybody is going to vote for a controller they own, I'm no different
My vote goes to Launchpad MK2

@sinosoidal If there is any chance of assisting you remotely with adding controller support I'd be more than happy to help

skrat

You didn't ask for it But here's my suggestion for generic support for any controller. I think it's not so complex changes, given how much progress you did just in last months, and you'd cover needs for any possible controller in the future. What I see that needs to be done is:
1. Ability to change clip MIDI trigger properties also on empty slot (Actually exactly like it's currently done for scenes), so you won't need to map everything over and over when creating a new project and you'll be able to create empty preset projects for your controller.
2. Ability to choose MIDI SEND trigger message, for controlling LEDs color when the clip is pressed and played (distinguish between clip pending to be triggered and actually playing - for the "blinking" state of a pad / button)
3. For controlling specific LED color, at least on APC40, note velocity is used and I believe this is the case for most of the controllers. Also don't forget to allow for channel selection, which is pretty important too as (again at least APC40) controls LED blinking state based on the MIDI channel on which the note is sent.
4. That said, you should also allow for separate MIDI out for these controller messages, so they won't mix up with the actual notes playing from matrix clips. E.g. Fugue machine have separate MIDI out as AUv3.
5. Then when LK loads, it'll send all these MIDI SEND trigger messages to the controller to initialize the LEDs state. If this could be triggered manually (e.g. when you connect controller after the load), that'd be nice.

Nice to have improvements:

• "Scrolling", or basically navigating, in the matrix from the controller - to set the currently visible area on your controller to not be restricted only on the number of pads on your controller. For that you'd need:

  • Ability to set the matrix size of your controller - number of tracks and scenes.
  • Be able to MIDI map arrows to navigate scene up / down and select next / previous track.
  • If navigating up / down, LK will send all the mapped MIDI sends of all the clips that fit into it's matrix size to the controller, so you'll see the same thing on the controller as in LK.
  • Since you can have LK open a window of any size as AUv3, it would be nice to indicate, which part is currently displayed on the controller, or you'd get easily lost. Ableton Live uses red rectangle around the clips that are currently displayed on the controller.

• Custom mapping of color palette to note velocity per controller somewhere in the settings to indicate that e.g. color red is lit up when note is send with velocity 124.

Still, I am getting to the conclusion, it'd be the best to be able to load some controller setting file in LK preferences. People (or even you) would be able to create those files even without owning the controller, just based on their manual and send to people with less technical skills to test. Such file would contain: 1. List of note/cc numbers with option to set: number, type (note/cc/pc), channel, scene coordinate and track coordinate and velocity. This way you can also detect the size of the matrix. 2. To have flexibility over how various controllers handle blinking state, the same list would go for mapping blinking state and you e.g. just change MIDI channel there (or velocity or so). Then besides these notes list, there would be color mapping to either velocity or other parameter (if you know about other system some controllers use for displaying specific color), something like 'red' : 124 or 'red': { 'velocity': 123 }

There is endless amount of controllers out there that currently support some kind of pads and on light up them on received MIDI messages. Opening the option for people to create their own mapping will save you a lot of time and requests. Not to mention you won't have to add anything new in the UI (maybe except a button to open the mapping file). I'd happily create such mapping for less skilled users and their controllers and I believe here in the community many people would do so. Please, at least give it a try

cozido

@branis said:
Of course, everybody is going to vote for a controller they own, I'm no different
My vote goes to Launchpad MK2

+1 another vote for the Launchpad MK2.

Freddy_Valeur

Ableton Push 😎

Svetlovska

@sinusoidal - another vote here for LaunchControl XL as a controller template. It’s custom made for a tight AUM/LK workflow.

bleep

Also a vote for L-XL here. And a +1 on what @skrat said (the better option for us geeks and nerds, but I understand you want a wider reach with plug and play support for popular controllers).

Liquidmantis

@kveis said:

@sinosoidal said:
If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

Another vote for Launchpad Pro MK3 here.

And here!

(maybe a poll would be better...)

sinosoidal

@Liquidmantis said:
(maybe a poll would be better...)

Deffo! Is there any way of doing a pool on a existing thread?

Thacapos

@sinosoidal said:
If you could choose the next dedicated controller support for LK, which one would be? We want to invest in one more controller to add support. We will choose the one with more votes. Thank you for your feedback!

Launchpad mk3 pro

Liquidmantis

@sinosoidal said:

@Liquidmantis said:
(maybe a poll would be better...)

Deffo! Is there any way of doing a pool on a existing thread?

I think you'll need to start a new thread and just link to it here, unfortunately.