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.

Support Discussion: LK - for Ableton Live & Midi by Imaginando

2»

Comments

  • @FordTimeLord said:
    I get that you’re disappointed about the feature you’re after being missing but bloody hell, read the room dude.

    Seriously, “bro”

  • @espiegel123 said:
    You don’t know that…you may also be (wrongly) assuming that these devs make a lot more money from these apps than they do. Any time they spend implementing some feature is taken away from working on other things that may be more important to more users.

    Like I said, it's an essential feature for an Ableton controller. The way LK is advertised their Ableton control screams APC40 or Launchpad, and these have this feature since day 1. It's a catch 22, without this feature no Ableton user will try to replace their midi controller with it. Include this feature and they might come.

  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • edited December 2022

    @ik2000 said:

    @Rob_Timeless said:

    @tja said:
    This is very helpful for this thread.

    It is. I wanted LK to be usable as a midi controller replacement and not having macro support is not only a dealbraker but a workflow breaker for me. And I know that things don't change without some public pressure. It's not so much work for a dev to fix this.

    How many iOS music apps have you developed yourself? Do you know how much effort goes into building these apps, and at a very low cost to us users as well. The development lifecycle, testing and time taken to debug isn’t something that I would call simple. Go easy on the developers and next time use official channels (clue: this is not one of them) to raise any suggestions.

    It's an external script that needs to communicate with their internal midi messages. There some hobby coders who create scripts for unsupported devices, they don't earn anything.

    This script is added manually to an Ableton folder or by a desktop installer. Every controller with rack macro support has a script included. I even send Imaginando a link to the Github repo with decompiled scripts which they can use as templates. https://structure-void.com/ableton-live-midi-remote-scripts/

    Following the link you can see a long list of supported devices, the main task is to pick one that's topologically similar to LK and customize it, then sync the messages with the internal ones in LK.

    Like I said the main problem seems to be the unwareness of the usefulness of the feature. They were/are unaware that it's something Ableton users just expect from these type of controllers.

  • edited December 2022

    @tja said:
    Including the link to more specific details at https://www.imaginando.pt/products/lk/help

    What exactly is NOT as written?

    Tight integration is what's misleading. Every Ableton user understands "rack macro control/auto mapping" as tight integration. Push has tight integration, APCs have tight integration, Faderfoxes and Midi Fighters have tight integration. Change a device and the knobs/endless encoders on your controller are mapped automatically. That's why there are 8 knobs on those controllers, there were 8 macros in the past (upped to 16 in Ableton 11).

  • LK isn't a low cost equivalent of AppBC's TouchAble. It's a totally different app that imho shines with great usability at the cost of not supporting all kinds of deep Ableton Live features that are more likely to be supported in TouchAble.

    I prefer LK by far because of its clean UI and the fact that I'm one of the seasoned Ableton users who find LK's feature set a great and usable compromise between functionality and complexity. So I'm not "every Ableton user" for sure.

  • @FordTimeLord said:
    Or maybe it was that there was much more demand for iOS centric features. This thread has been going on for two years now and is full of feature requests from users that the devs implemented. I get that you’re disappointed about the feature you’re after being missing but bloody hell, read the room dude.

    What's there to read? Most of you, Imaginando included don't even seem to know what rack macro auto mapping is. Why should I back down when I'm surrounded by people who would be on my side if they'd be Ableton users. I've registered here to solve problems I have with apps and my workflow.

  • @Rob_Timeless said:

    @FordTimeLord said:
    Or maybe it was that there was much more demand for iOS centric features. This thread has been going on for two years now and is full of feature requests from users that the devs implemented. I get that you’re disappointed about the feature you’re after being missing but bloody hell, read the room dude.

    What's there to read?

    120 pages of primarily iOS specific feature requests?

  • @Rob_Timeless said:

    @espiegel123 said:
    You were rude to people that tried to point you to the developer’s support channels.

    No I wasn't. If yes then show the post where I was rude. I even thanked one user for the help. And in regards of sales channels it must be one of the main ones for the product if it's 122 pages in this forum.

    Since you asked for a post where you were rude to someone pointing you to the developer’s web site how about this. You wrote:

    “Sorry dude, being a small team isn't an excuse to not monitor the main thread in the only relevant mobile audio forum at least once a day.”

    @symianbeatz said:…If your patience is wearing thin you could always email the Devs via their website or from the link in the app store, they're pretty busy guys and small team..

    You wrote: “I'm busy too, sorry bro but monitoring your main plugin sales channels is absolute standard behavior….Damn I sound like a dickhead but it is what it is.”

    Sure sounds rude to me.

  • @rs2000 said:
    LK isn't a low cost equivalent of AppBC's TouchAble. It's a totally different app that imho shines with great usability at the cost of not supporting all kinds of deep Ableton Live features that are more likely to be supported in TouchAble.

    I prefer LK by far because of its clean UI and the fact that I'm one of the seasoned Ableton users who find LK's feature set a great and usable compromise between functionality and complexity. So I'm not "every Ableton user" for sure.

    Touchable looks like a hot and complex mess in comparison, and the devs don't even react to posts on their forum, they go afk for year. Maybe that's another reason for my intitial reaction, I get upset when I see such wasted potential.

  • The user and all related content has been deleted.
  • @tja said:
    And can we now let this thread sleep some time, for all to calm down?
    😉

    👍

  • ok its all is not so important

    lk will get or no addirional fuunctions, macros, scripts

    who knows?

    but it is not a reason to be too serious and lost humour sense

    great that macro-tight subject occurred and maybe lk will get this, or no, thats all is … life

  • edited December 2022

    @Rob_Timeless said:

    @FordTimeLord said:
    Or maybe it was that there was much more demand for iOS centric features. This thread has been going on for two years now and is full of feature requests from users that the devs implemented. I get that you’re disappointed about the feature you’re after being missing but bloody hell, read the room dude.

    What's there to read? Most of you, Imaginando included don't even seem to know what rack macro auto mapping is. Why should I back down when I'm surrounded by people who would be on my side if they'd be Ableton users. I've registered here to solve problems I have with apps and my workflow.

    To be fair fella people would probably be on your side if you were a bit more respectful of the Devs and the community, even people that disagree and ruffle feathers round here are treated well, myself included, if they don't let things get personal or snarky and make a reasoned argument.
    My own personal stance on any software or hardware product is you should buy it based on what it is not what you want it to be, anything that's comes after by way of updates is a bonus and for the most part free and nothing to be grumbles about, if a product doesn't meet my needs I don't buy, that may sound over simplified but it negates disappointing purchase's

    For the record I'm an avid Ableton and push user too .

  • I really like LK and I like Imaginando. Especially their synth, DRC which sounds great.

    They make some nice products that are regularly maintained and improved. @sinosoidal and the rest of the team seem to check in very regularly on this forum, and often engage in long conversations with people about very specific user needs. They are also quite transparent about what is possible and what isn’t.

    All this is great. People are mostly polite, helpful and appreciative of each other in here, and I’ve learned a ton from helpful devs and users. It’s great to have you join the forum, @Rob_Timeless, and I hope that you will stay around and be part of this atmosphere and culture.

  • @espiegel123 said:

    @Rob_Timeless said:

    @espiegel123 said:
    You were rude to people that tried to point you to the developer’s support channels.

    No I wasn't. If yes then show the post where I was rude. I even thanked one user for the help. And in regards of sales channels it must be one of the main ones for the product if it's 122 pages in this forum.

    Since you asked for a post where you were rude to someone pointing you to the developer’s web site how about this. You wrote:

    “Sorry dude, being a small team isn't an excuse to not monitor the main thread in the only relevant mobile audio forum at least once a day.”

    @symianbeatz said:…If your patience is wearing thin you could always email the Devs via their website or from the link in the app store, they're pretty busy guys and small team..

    You wrote: “I'm busy too, sorry bro but monitoring your main plugin sales channels is absolute standard behavior….Damn I sound like a dickhead but it is what it is.”

    Sure sounds rude to me.

    This how I speak with homies, thought that somebody with a "beatz" in his name would be somebody from the same tribe basically. I can write "nerd english", but I don't prefer it.

  • Hope a thread turn like this promotes some well deserved rating updates for the Imaginando apps... spread a little holiday cheer for devs who've been generous with updates.

  • @symianbeatz said:
    To be fair fella people would probably be on your side if you were a bit more respectful of the Devs and the community, even people that disagree and ruffle feathers round here are treated well, myself included, if they don't let things get personal or snarky and make a reasoned argument.

    My own personal stance on any software or hardware product is you should buy it based on what it is not what you want it to be, anything that's comes after by way of updates is a bonus and for the most part free and nothing to be grumbles about, if a product doesn't meet my needs I don't buy, that may sound over simplified but it negates disappointing purchase's

    For the record I'm an avid Ableton and push user too .

    Just don't call it tight integration then, you should know how tight integration feels with Push or similar controllers. Everything else about LK looks cool. Maybe even too good leading me to assume they're more professional than they are in the end.

This discussion has been closed.