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

17778808283130

Comments

  • @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @Harro said:

    @Thacapos said:

    @sinosoidal said:

    @Harro said:
    @sinosoidal : I noticed a (small) bug in LK: the FOLLOW ACTIONS for clips are not saved... (not in AUM-sessions, (state-saving), and not in LK-presets. I hope very much you can solve this.

    Is anyone else having this problem?

    Because I've a session with scene follow actions saved and I've tested with it before releasing.

    Just tried, not having this problem

    I meant the CLIP folow actions (not the scene follow actions) that are NOT saved.

    That's even more strange because part of the code does not change for a long time and a lot of people here is using the clip follow actions.

    Can anyone else confirm this is a problem?

    I just made a quick test and clip actions were saved both from AU to Standalone and vice versa. They are also state-saved with my AUM sessions.

    Thank you @branis!

    @Harro can you make a video showing your problem? Maybe it will help us understand it better.

    I narrowed this 'not (state-)saving' down to the Clip-Follow Action -> NOTES: whatever action I choose, it's not saved. I hope you'll try this yourself. Also: when I choose Generate Chords or Generate Melody (in Clip-Follow Action->NOTES, the Range-rule in the clip-property Generate is not respected; I wish it would, because now it tends to generate very high notes/chords!

  • @sinosoidal just got the chance to have a proper go with the new scene follow actions. So much easier than my previous setup with midi note triggers.

    Only problem I did see was that the stop follow action doesn’t seem to work. I only use it at the end of the song so can just set it not to loop instead, but thought it was worth mentioning 👍

  • @gregsmith said:
    @sinosoidal just got the chance to have a proper go with the new scene follow actions. So much easier than my previous setup with midi note triggers.

    Only problem I did see was that the stop follow action doesn’t seem to work. I only use it at the end of the song so can just set it not to loop instead, but thought it was worth mentioning 👍

    Confirmed. @gregsmith Does LK also crash for you if you set the scene follow action to stop? I'm getting a couple of loops, like if there was no follow action and then LK crashes (AU inside AUM).

  • @branis said:

    @gregsmith said:
    @sinosoidal just got the chance to have a proper go with the new scene follow actions. So much easier than my previous setup with midi note triggers.

    Only problem I did see was that the stop follow action doesn’t seem to work. I only use it at the end of the song so can just set it not to loop instead, but thought it was worth mentioning 👍

    Confirmed. @gregsmith Does LK also crash for you if you set the scene follow action to stop? I'm getting a couple of loops, like if there was no follow action and then LK crashes (AU inside AUM).

    Hmm it didn’t crash for me but maybe I didn’t do it enough times.

  • @auxmux said:
    @sinosoidal Yup exactly, as @AlmostAnonymous and @White are showing their screenshot and gif. With slideover, it's easy to drag and drop files. With EG Pulse, it's possible to drag and drop wav files onto the audio unit in AUM.

    Does anyone knows EG developer? Is he around in the forum? I would like ask him some questions about the drop implementation.

  • @sinosoidal said:

    Does anyone knows EG developer? Is he around in the forum? I would like ask him some questions about the drop implementation.

    @ElliottGarage Is around here at the forums...
    ...PM/DM should work.

  • @Samu said:

    @sinosoidal said:

    Does anyone knows EG developer? Is he around in the forum? I would like ask him some questions about the drop implementation.

    @ElliottGarage Is around here at the forums...
    ...PM/DM should work.

    Thank you @Samu ! :blush:

  • edited March 2021
    The user and all related content has been deleted.
  • @d4d0ug said:
    Hey @sinosoidal

    Re importing midi.....

    one thing that I hit yesterday, and a change could be beneficial is.....naming clips with the name of the imported midi file name.

    Currently need to import, then go in and edit the name via the inspector.

    Yeah, sure! :blush:

  • @sinosoidal said:

    @Samu said:

    @sinosoidal said:

    Does anyone knows EG developer? Is he around in the forum? I would like ask him some questions about the drop implementation.

    @ElliottGarage Is around here at the forums...
    ...PM/DM should work.

    Thank you @Samu ! :blush:

    @sinosoidal @blueveek also recently added drag and drop to Atom, so could be another resource.

  • @auxmux said:

    @sinosoidal said:

    @Samu said:

    @sinosoidal said:

    Does anyone knows EG developer? Is he around in the forum? I would like ask him some questions about the drop implementation.

    @ElliottGarage Is around here at the forums...
    ...PM/DM should work.

    Thank you @Samu ! :blush:

    @sinosoidal @blueveek also recently added drag and drop to Atom, so could be another resource.

    Thanks! I've dropped him a message.

  • The user and all related content has been deleted.
  • Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

  • @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Are you able to upload or send me crash report?

  • @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

  • @sinosoidal said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Are you able to upload or send me crash report?

    The feedback you provided via TestFlight does not contain crash report! :disappointed:

  • @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

  • @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

  • @sinosoidal said:

    @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

    I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?

  • @White said:

    @sinosoidal said:

    @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

    I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?

    https://support.apple.com/en-us/HT202100

    After enabling it, please reproduce the crash a couple of times.

  • @sinosoidal said:

    @White said:

    @sinosoidal said:

    @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

    I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?

    https://support.apple.com/en-us/HT202100

    After enabling it, please reproduce the crash a couple of times.

    Or, you could also send me the AUM project to see if I cant replicate.

  • @sinosoidal said:

    @White said:

    @sinosoidal said:

    @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

    I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?

    https://support.apple.com/en-us/HT202100

    After enabling it, please reproduce the crash a couple of times.

    That's really strange, because I have everything enabled under "analytics and enhancments". Are the crash reports stored somewhere on the iPad so I can send them to you?

  • @White said:

    @sinosoidal said:

    @White said:

    @sinosoidal said:

    @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

    I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?

    https://support.apple.com/en-us/HT202100

    After enabling it, please reproduce the crash a couple of times.

    That's really strange, because I have everything enabled under "analytics and enhancments". Are the crash reports stored somewhere on the iPad so I can send them to you?

    Send me a AUM project that is causing the crash.

  • @sinosoidal said:

    @White said:

    @sinosoidal said:

    @White said:

    @sinosoidal said:

    @sinosoidal said:

    @White said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Yes I have the same problem.

    Standalone and AUv3 or just AUv3?

    Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.

    I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?

    https://support.apple.com/en-us/HT202100

    After enabling it, please reproduce the crash a couple of times.

    That's really strange, because I have everything enabled under "analytics and enhancments". Are the crash reports stored somewhere on the iPad so I can send them to you?

    Send me a AUM project that is causing the crash.

    When I had the crashes earlier today, LK also crashed when I tried to create a new AUM project and then add LK as a Midi processor. I sent a mail to you earlier today about it, but it was beta version 217 and I have just installed version 218, so I will try and see if I can get it to crash too.

  • @sinosoidal said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Are you able to upload or send me crash report?

    I switched on sharing analytics with app developers and sent feedback again. Did you get my crash report this time?

  • @sinosoidal

    I found 2 reports in analytics and enhancements/data named LK and date and time, I have sendt them to you.

  • @branis said:

    @sinosoidal said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Are you able to upload or send me crash report?

    I switched on sharing analytics with app developers and sent feedback again. Did you get my crash report this time?

    Don't have nothing yet. Weird!

    @white has shared crash reports with me. Maybe he can tell how to retrieve them.

  • @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Are you able to upload or send me crash report?

    I switched on sharing analytics with app developers and sent feedback again. Did you get my crash report this time?

    Don't have nothing yet. Weird!

    @white has shared crash reports with me. Maybe he can tell how to retrieve them.

    My crash logs are located here. The screenshot is in danish, sorry:

    Open a log and then you can share it.

  • @White said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @branis said:
    Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them

    Are you able to upload or send me crash report?

    I switched on sharing analytics with app developers and sent feedback again. Did you get my crash report this time?

    Don't have nothing yet. Weird!

    @white has shared crash reports with me. Maybe he can tell how to retrieve them.

    My crash logs are located here. The screenshot is in danish, sorry:

    Open a log and then you can share it.

    thanks!

  • I've just published build 224. Based on some beta testers feedback, the crash at startup is solved by deleting and installing the app again. If LK crashes at startup, please delete the app and install it again from TestFlight and please let me know if it still crashes.

    Attention: Before deleting LK, ensure that you backup .json files inside LK/Imaginando/LK if you rely on project manager instead of host state saving

    This build has all the changes that are supposed to be on 1.10.4:

    • Send midi when editing midi automation
    • Enable grid context menu in Live mode
    • On save as, confirm overwrite if user choose name of existing project
    • Mark project as changed when automation is modified
    • Add background clip feature to Live mode
    • Add midi file name to clip when importing
    • Add drop support of midi files to AUv3 (without import dialog)
    • Fix background clip notes when its notes changes
    • Fix scene follow action stop
    • Fix selected track/scene/clip when opening properties context menu option
    • Fix composer visibility when clip is audio (Live Mode)
    • Fix composer automations editor visibility bug
    • Fix Ableton Live Set export button
    • Fix automation recording with/without overdub
    • Fix stuck notes when saving or changing project
    • Fix midi export to include automations
Sign In or Register to comment.