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…4142444647…130

Comments

  • sinosoidalsinosoidal

    I've created a pool for the controller -> https://forms.gle/LuTptp2QUBh6m9Kj7

  • cozidocozido
    edited December 2020

    @sinosoidal said:
    Launchpad MK2 is very similar to Launchpad X, what's the difference?

    They might be similar but the MK2 doesn’t seem to work, it’s recognized by LK in standalone mode, but doesn’t respond to anything. And it’s not even recognized in AU mode.

  • skratskrat

    @sinosoidal said:

    @skrat said:
    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 ;)

    Thanks for your incredible feedback. I've made a post at the bottom of the thread on why I don't want to choose this path right now.

    I see your point, of course some big refactoring does not make sense. But I believe some of the points like having extra MIDI out to be routed in AU host and ability to send specific notes out for each clip trigger / play would help a lot and does not require some fundamental changes. Of course, I get the feature creep issue which always can cause instability and I am totally with you rather having limited but stable app, than an app that does a lot of things, but is unreliable, which is basically useless for people relying on it for live performances.

    Nevertheless, I have an idea of an hack to go around this limitation in my setup. Let's see how it goes, I'll keep you informed :smile:

  • ghost_forestsghost_forests

    Still using my Tascam 424 mk iii here!

    @McD said:

    @espiegel123 said:
    I'd say Sonic Foundry's Acid (later Sony Acid Pro) got the ball rolling on. It was PC only and until the first version of Live came around several years later, people on the Mac were begging for Acid on the Mac because realtime pitch-shifting/time-stretching of loops wasn't really available -- I think GarageBand's AppleLoops weren't around till a few years after Live hit.

    Wow. That's around the time I stopped following Music Making on a PC. When Sony bought
    Acid.

    I later got a Mac and bought Reason but never really dug into it. It was already into a hardware device simulation that I just didn't get and still need to catch up on. I was and
    still am stuck in the Multi-track Tape system with out-board FX. I bought a couple of the
    Korg Digital Recording systems and made some projects there using keyboards, guitars, and mics.

  • ghost_forestsghost_forests

    Like Riffer!

    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.

  • ghost_forestsghost_forests

    Big +1 for this

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

  • branisbranis

    @sinosoidal said:

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

    Launchpad MK2 is very similar to Launchpad X, what's the difference?

    The biggest difference are the custom modes making the Launchpad X more useful as a you can easily configure it to work with other software/hardware than just Ableton Live. Also, the pads are velocity sensitive.

    I think there's not much change in integration with Live if any at all, but I'm not sure about that because I don't use Live. I got my Launchpad MK2 to use it with the Launchpad app where the integration is perfect.

    I tried to connect my Launchpad MK2 to LK, but it's not recognized, so for me that's the biggest difference :p

  • ghost_forestsghost_forests

    Yeah I got the LCXL and Mini 2 to use with the Launchpad app and it’s a ton of fun. Really need to actually start investigating LK as I don’t think I really grasped quite what it was on release!

  • sinosoidalsinosoidal

    LK 1.9.0 has been finally released and features some important improvements:

    • Sample accurate midi events (playback & recording)
    • Clip drag and copy (with shift)
    • Notes drag and copy (with shift)
    • Fixes playback jitter
    • Fixes sample rate (AUv3)
    • Adds the ability to sync with host when hosted (status bar link icon)
    • Send MIDI clock start/stop events only when enabled
    • General bug fixes and improvements

    Thank you to all the beta testers that helped us fine tuning this release.

    A special thanks to @j_liljedahl for the help he has kindly provided to me, understanding how to schedule midi events in sample time. AUM is one of the most complex, beautiful and carefully crafted applications I've seen in the mobile iOS world and I just can't get tired of saying this.

    We hope you enjoy this release! :blush:

  • ThacaposThacapos

    Just updated and now the midi contoller doesnt work properly. I can play some notes but then it gets stuck on a note (holds it) and doesn‘t recognise any new input

    Ios 13.7 ipad 6 gen

  • sinosoidalsinosoidal

    @Thacapos said:
    Just updated and now the midi contoller doesnt work properly. I can play some notes but then it gets stuck on a note (holds it) and doesn‘t recognise any new input

    Ios 13.7 ipad 6 gen

    Sorry to hear about that. What's your controller? How are you setting it up? Can you send me a video? Thx!

  • ThacaposThacapos

    I tried with two different, launchpad mk3 pro and arturia minilab mk 2
    With launchpad i doesnt always respond to every not im playing and gets stuck after some notes (video is on the way), with mk2 it responds to every key but gets stuck after some time

  • sinosoidalsinosoidal

    @Thacapos said:
    I tried with two different, launchpad mk3 pro and arturia minilab mk 2
    With launchpad i doesnt always respond to every not im playing and gets stuck after some notes (video is on the way), with mk2 it responds to every key but gets stuck after some time

    We have tested all the controllers we have and they are working just fine:

    • APC Key 25
    • Arturia KeyStep
    • Launchpad X

    I've been playing for more than one hour yesterday with APC Key 25 and didn't have a single stuck note with the controller.

    Thanks for making a video. It will help us understand the problem.

    Regards,

    Nuno

  • RajahPRajahP

    @sinosoidal said:
    LK 1.9.0 has been finally released and features some important improvements:

    • Sample accurate midi events (playback & recording)
    • Clip drag and copy (with shift)
    • Notes drag and copy (with shift)
    • Fixes playback jitter
    • Fixes sample rate (AUv3)
    • Adds the ability to sync with host when hosted (status bar link icon)
    • Send MIDI clock start/stop events only when enabled
    • General bug fixes and improvements

    Thank you to all the beta testers that helped us fine tuning this release.

    A special thanks to @j_liljedahl for the help he has kindly provided to me, understanding how to schedule midi events in sample time. AUM is one of the most complex, beautiful and carefully crafted applications I've seen in the mobile iOS world and I just can't get tired of saying this.

    We hope you enjoy this release! :blush:

    Thanks... will give it a shot now..

  • ThacaposThacapos

    Maybe ill have to update to ios 14, but i dont dare since i still read about problems with au

  • sinosoidalsinosoidal

    @Thacapos said:
    Maybe ill have to update to ios 14, but i dont dare since i still read about problems with au

    We only have one device on iOS 14. All the other are on iOS 13

  • sambosambo

    @sinosoidal: does LK presently operate in slide over/split screen mode? The reason I ask is I'd like to use LK in a performative context triggering a Drambo set - and while I can obviously run them both side by side in AUM, I would lose Drambo's new ability to run AU's internally (Drambo wont host AU's when running in AMU).

  • espiegel123espiegel123

    @Thacapos said:
    Maybe ill have to update to ios 14, but i dont dare since i still read about problems with au

    Don't upgrade to iOS 14. There are some serious issues. Apparently 14.3 beta is better but still unknown if it solves them all.

  • espiegel123espiegel123

    @sinosoidal : what is the trick to record into an empty clip when the transport is linked to the host. I have set LK to record mode (both LK and my track). I deleted the clip on the track so that I can record without a pre-set clip length and nothing I do seems to result in LK recording into the clip when AUM’s transport hits 1.1.0.

    It seems to work fine if the clip is not empty.

  • branisbranis

    @espiegel123 said:
    @sinosoidal : what is the trick to record into an empty clip when the transport is linked to the host. I have set LK to record mode (both LK and my track). I deleted the clip on the track so that I can record without a pre-set clip length and nothing I do seems to result in LK recording into the clip when AUM’s transport hits 1.1.0.

    It seems to work fine if the clip is not empty.

    did you tap the empty clip itself?

  • espiegel123espiegel123

    @branis said:

    @espiegel123 said:
    @sinosoidal : what is the trick to record into an empty clip when the transport is linked to the host. I have set LK to record mode (both LK and my track). I deleted the clip on the track so that I can record without a pre-set clip length and nothing I do seems to result in LK recording into the clip when AUM’s transport hits 1.1.0.

    It seems to work fine if the clip is not empty.

    did you tap the empty clip itself?

    Yup. It works for me if the clip is not an empty clip.

    Does it work for you?

  • branisbranis

    Yes, It’s working. I’m on the latest beta, but it should be the same as the latest update from the App Store

  • espiegel123espiegel123

    @branis said:
    Yes, It’s working. I’m on the latest beta, but it should be the same as the latest update from the App Store

    So you can set transport locking on, create a new project , delete the first clip so that the first clip is empty , arm recording, and recording starts when the host transport hits 1?

  • espiegel123espiegel123

    @espiegel123 said:

    @branis said:
    Yes, It’s working. I’m on the latest beta, but it should be the same as the latest update from the App Store

    So you can set transport locking on, create a new project , delete the first clip so that the first clip is empty , arm recording, and recording starts when the host transport hits 1?

    Note that the clip needs to be truly empty not just a clip with no notes

  • branisbranis

    Just to be sure we are talking about the same thing, here is a video of what I do: https://1drv.ms/v/s!AjeElcrX4ad7q4JWmbECO2v547Y26Q

  • espiegel123espiegel123

    @branis said:
    Yes, It’s working. I’m on the latest beta, but it should be the same as the latest update from the App Store

    Now that I try again, it looks like I can't record into an empty clip at all even if not locked to the host.

    In the previous couple of versions, you could record into a slot that had no clip to create a new clip without pre-setting a clip length. This is not working for me in the new version at all. Note that I have only tried when there are no other clips.

    Try this with and without host transport linked.

    • Start with a new project.
    • Delete the first clip (tap and hold on the first clip and delete
    • Put LK into record mode
    • Put the track into record mode
    • Tap play in LK's transport controls
    • Make sure the AUM transport is rewound
    • Press play in AUM (I have tried with and without count off). If not linked to host, press play in LK transport
    • Start playing on your keyboard

    @sinosoidal : i am finding that recording a first clip is not working well in the new version -- linked to transport or not. I can never get it working in a truly empty clip (whether it is the first clip or not) -- and recording into the first clip even if not empty is not working often either.

    One thing that I notice -- even with the default 1 bar clip -- is that i need to open the clip itself and tap in the clip's play button when the piano roll is visible for recording to work. Even with host transport not linked.

    Question: Is there no 'new project' command anywhere?

  • RajahPRajahP
    edited December 2020

    I’m having a hard time just trying to record an ATOM 1 seq. Into LK..

    Edit.. should be an easy task.. by just hitting ‘rec/play’ in LK or, AUM...

  • espiegel123espiegel123

    @RajahP said:
    I’m having a hard time just trying to record an ATOM 1 seq. Into LK..

    Edit.. should be an easy task.. by just hitting ‘rec/play’ in LK or, AUM...

    I think you are running into the issues that I am running into in this new release.

  • branisbranis

    @espiegel123 said:

    @branis said:
    Yes, It’s working. I’m on the latest beta, but it should be the same as the latest update from the App Store

    Now that I try again, it looks like I can't record into an empty clip at all even if not locked to the host.

    In the previous couple of versions, you could record into a slot that had no clip to create a new clip without pre-setting a clip length. This is not working for me in the new version at all. Note that I have only tried when there are no other clips.

    Try this with and without host transport linked.

    • Start with a new project.
    • Delete the first clip (tap and hold on the first clip and delete
    • Put LK into record mode
    • Put the track into record mode
    • Tap play in LK's transport controls
    • Make sure the AUM transport is rewound
    • Press play in AUM (I have tried with and without count off). If not linked to host, press play in LK transport
    • Start playing on your keyboard

    @sinosoidal : i am finding that recording a first clip is not working well in the new version -- linked to transport or not. I can never get it working in a truly empty clip (whether it is the first clip or not) -- and recording into the first clip even if not empty is not working often either.

    One thing that I notice -- even with the default 1 bar clip -- is that i need to open the clip itself and tap in the clip's play button when the piano roll is visible for recording to work. Even with host transport not linked.

    Question: Is there no 'new project' command anywhere?

    You skipped tapping the empty clip after “Press play in AUM”

  • espiegel123espiegel123

    @branis said:

    @espiegel123 said:

    @branis said:
    Yes, It’s working. I’m on the latest beta, but it should be the same as the latest update from the App Store

    Now that I try again, it looks like I can't record into an empty clip at all even if not locked to the host.

    In the previous couple of versions, you could record into a slot that had no clip to create a new clip without pre-setting a clip length. This is not working for me in the new version at all. Note that I have only tried when there are no other clips.

    Try this with and without host transport linked.

    • Start with a new project.
    • Delete the first clip (tap and hold on the first clip and delete
    • Put LK into record mode
    • Put the track into record mode
    • Tap play in LK's transport controls
    • Make sure the AUM transport is rewound
    • Press play in AUM (I have tried with and without count off). If not linked to host, press play in LK transport
    • Start playing on your keyboard

    @sinosoidal : i am finding that recording a first clip is not working well in the new version -- linked to transport or not. I can never get it working in a truly empty clip (whether it is the first clip or not) -- and recording into the first clip even if not empty is not working often either.

    One thing that I notice -- even with the default 1 bar clip -- is that i need to open the clip itself and tap in the clip's play button when the piano roll is visible for recording to work. Even with host transport not linked.

    Question: Is there no 'new project' command anywhere?

    You skipped tapping the empty clip after “Press play in AUM”

    Forgot to list it. But I am doing that. It doesn't work here. In fact, with a non empty clip, I have to actually open the piano roll editor and tap play while in the clip for recording to work.

Sign In or Register to comment.