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.

EG Nodes

1…78101213…42

Comments

  • LuxthorLuxthor

    @gregsmith said:

    @Luxthor said:

    @ElliottGarage said:
    @5k3105 I like when users send me requests or suggestions...it means they like the app and want to use it! That's why I will publish the board with the roadmap... I'd just like that requests will come after they tried the app and check its workflow and if they really miss that feature. Unfortunately it's not easy to make a trial period for an app into iOS.

    @Luxthor everything is a tradeoff between performance, creativity and workflow...limitations are mandatory if you have your design for an app. EG Nodes for me is not a transparent tool as a DAW where you will work and you already know that piano roll works in this way, there you have this tool, there is this and there is that... my apps should have their approach and their way to make things, I need to be creative and have fun while developing...like it or not :)

    I know a lot about limitations, format, and discipline in art, don’t get me wrong. I already stated that Nodes is a fantastic new app. Just that people who work with more bars are not some flux in the matrix, they are real people too, haha. ;)

    I totally get that limitations are a good thing. It’s a big reason why I choose the iOS platform.

    16 bars would still be a limitation. Christ, if you really want to be limited and be forced to make interesting creative decisions, just never set it past 1 bar. I happen to enjoy making the music I make, just always looking for more efficient workflows, and nodes looks like the one for midi in loopy pro.

    Anyway, I’m repeating myself. Looking forward to trying this in loopy pro and voting for 16 bars and midi export the second the dashboard is published 😉

    Oh, I will buy this app too, of course, it’s probably not for me, but I want that experience, and who knows, maybe @ElliottGarage will unlock some different ways of thinking for me. 🫣

  • ElliottGarageElliottGarage

    Changing to 16 bars is literally 1 seconds for me (I just have to change a constant), since that was just a design decision.
    But the question is, will the app workflow fit expectations of users that needs 16 or more bars...
    Anyway that just a first version of the app.

  • iansainsburyiansainsbury

    @ElliottGarage said:
    Changing to 16 bars is literally 1 seconds for me (I just have to change a constant), since that was just a design decision.
    But the question is, will the app workflow fit expectations of users that needs 16 or more bars...
    Anyway that just a first version of the app.

    If it's that easy, I'll join in with those requesting it. It might not get used in every session, but it would be great to have the option of a longer, evolving synth part. Especially if I could select an odd number of bars (11, 17), so that it constantly shifts over a longer piece. I've pre-ordered either way, because it looks great.

  • lazyasslazyass
    • with longer bar loops you got more space for automation
  • mistercharliemistercharlie

    Literally none of the people asking for more than 4 bars have ever used the app, and yet somehow they already know better than than the developer, and the people who have been using and testing it for weeks or months.

  • jobeatsjobeats

    @mistercharlie said:
    Literally none of the people asking for more than 4 bars have ever used the app, and yet somehow they already know better than than the developer, and the people who have been using and testing it for weeks or months.

    I have watched plenty videos listed by the developer on his social media pages. Also a few videos on YouTube, and that kind of gave me an insight to how things work with this app. I don’t really need to use the app to know if I need the use of more bars.

  • [Deleted User][Deleted User]

    And sends like auxes would be great. If that’s 1 second, pls 64 bars.

  • gregsmithgregsmith
    edited January 4

    @mistercharlie said:
    Literally none of the people asking for more than 4 bars have ever used the app, and yet somehow they already know better than than the developer, and the people who have been using and testing it for weeks or months.

    Are you on the beta team? What kind of music are you making with it? Do you record in using a midi keyboard?

  • skiphuntskiphunt
    edited January 4

    The thing about the 4 bars… it’s never been an issue for me. Granted, I’m more of a soundscaping abstract experimenter.

    If I ever needed more than 4 bars, I’d just add another scene on the node.

    I also played/recorded notes using the Atom 2 app in a midi fx node. That worked well, but occasionally I’d find myself bumping Atom up to 5 bars.

    I suppose it depends on how you use the app. The flow is kinda different in Nodes.

    I’m sure there are some who’d actually use 16bars in the piano roll, but it doesn’t seem to fit with the elegant and efficient overall Nodes interface.

    Personally, if I ever needed more than 4 bars, I’d just add a midi fx node and use a full piano roll app like Atom 2 or one of the other dozens of piano roll apps out there.

    I think people should simply sit tight on the additional requests until they’ve actually used the app a few days and know for sure they feel something is lacking.

    This dev could cram everything but the kitchen sink into Nodes in an effort to appease every desire, but then he’d risk destroying the beautiful overall interface design… to the point that it’d no longer be such a joy to use.

  • 5k31055k3105

    @skiphunt said:
    The thing about the 4 bars… it’s never been an issue for me. Granted, I’m more of a soundscaping abstract experimenter.

    If I ever needed more than 4 bars, I’d just add another scene on the node.

    I also played/recorded notes using the Atom 2 app in a midi fx node. That worked well, but occasionally I’d find myself bumping Atom up to 5 bars.

    I suppose it depends on how you use the app. The flow is kinda different in Nodes.

    I’m sure there are some who’d actually use 16bars in the piano roll, but it doesn’t seem to fit with the elegant and efficient overall Nodes interface.

    Personally, if I ever needed more than 4 bars, I’d just add a midi fx node and use a full piano roll app like Atom 2 or one of the other dozens of piano roll apps out there.

    I think people should simply sit tight on the additional requests until they’ve actually used the app a few days and know for sure they feel something is lacking.

    This dev could cram everything but the kitchen sink into Nodes in an effort to appease every desire, but then he’d risk destroying the beautiful overall interface design… to the point that it’d no longer be such a joy to use.

    Its like… one feature request. Not a kitchen sink.

    How does adding additional options in a drop down affect interface design?

    An option to increase bar length is gonna destroy the app for you huh? No more joy? Wow lol

  • 5k31055k3105

    @wim said:
    I gotta get off the internet. It seems like all I'm doing is picking arguments over every post I read. 😂

    Get in here, the test team just came back!

  • skiphuntskiphunt

    @5k3105 said:

    @skiphunt said:
    The thing about the 4 bars… it’s never been an issue for me. Granted, I’m more of a soundscaping abstract experimenter.

    If I ever needed more than 4 bars, I’d just add another scene on the node.

    I also played/recorded notes using the Atom 2 app in a midi fx node. That worked well, but occasionally I’d find myself bumping Atom up to 5 bars.

    I suppose it depends on how you use the app. The flow is kinda different in Nodes.

    I’m sure there are some who’d actually use 16bars in the piano roll, but it doesn’t seem to fit with the elegant and efficient overall Nodes interface.

    Personally, if I ever needed more than 4 bars, I’d just add a midi fx node and use a full piano roll app like Atom 2 or one of the other dozens of piano roll apps out there.

    I think people should simply sit tight on the additional requests until they’ve actually used the app a few days and know for sure they feel something is lacking.

    This dev could cram everything but the kitchen sink into Nodes in an effort to appease every desire, but then he’d risk destroying the beautiful overall interface design… to the point that it’d no longer be such a joy to use.

    Its like… one feature request. Not a kitchen sink.

    How does adding additional options in a drop down affect interface design?

    An option to increase bar length is gonna destroy the app for you huh? No more joy? Wow lol

    Have a great day and a very happy new year. I wish you joy and great luck in the future. :)

  • 5k31055k3105

    @skiphunt said:

    @5k3105 said:

    @skiphunt said:
    The thing about the 4 bars… it’s never been an issue for me. Granted, I’m more of a soundscaping abstract experimenter.

    If I ever needed more than 4 bars, I’d just add another scene on the node.

    I also played/recorded notes using the Atom 2 app in a midi fx node. That worked well, but occasionally I’d find myself bumping Atom up to 5 bars.

    I suppose it depends on how you use the app. The flow is kinda different in Nodes.

    I’m sure there are some who’d actually use 16bars in the piano roll, but it doesn’t seem to fit with the elegant and efficient overall Nodes interface.

    Personally, if I ever needed more than 4 bars, I’d just add a midi fx node and use a full piano roll app like Atom 2 or one of the other dozens of piano roll apps out there.

    I think people should simply sit tight on the additional requests until they’ve actually used the app a few days and know for sure they feel something is lacking.

    This dev could cram everything but the kitchen sink into Nodes in an effort to appease every desire, but then he’d risk destroying the beautiful overall interface design… to the point that it’d no longer be such a joy to use.

    Its like… one feature request. Not a kitchen sink.

    How does adding additional options in a drop down affect interface design?

    An option to increase bar length is gonna destroy the app for you huh? No more joy? Wow lol

    Have a great day and a very happy new year. I wish you joy and great luck in the future. :)

    Nice try

  • michael_mmichael_m

    @wim said:
    I gotta get off the internet. It seems like all I'm doing is picking arguments over every post I read. 😂

  • Didi57850Didi57850

    :D

  • RajahPRajahP
    edited January 4

    Is there a reason why EG Node cannot be released for this weekend?

    Edit.. And hoping for midi import for the Rhythm Node.. Editing Midi Drums sequences is difficult in Drambo..

  • rs2000rs2000

    @ElliottGarage Does MIDI controller support include LED/parameter feedback, e.g. to program sequences on a pad controller?

  • ExAsperis99ExAsperis99

    This is so impressive, @ElliottGarage
    I, too, am in the FOUR BARS: IMPOSSIBLE! camp, but let's not lose sight of how inspiring this app looks, and how it seems to solve so many problems elegantly.

    Hope this is a huge success for you.

  • gregsmithgregsmith

    I’m on the beta now and can tell already that this is going to be a hit @ElliottGarage

    Super responsive dev as well. Preorder, you won’t be disappointed 👍

  • [Deleted User][Deleted User]

    @gregsmith said:
    I’m on the beta now and can tell already that this is going to be a hit @ElliottGarage

    Super responsive dev as well. Preorder, you won’t be disappointed 👍

    I would like to also be on beta…. Anyway thanks for the opinion!

  • JohnnyGoodyearJohnnyGoodyear

    If there are more of the bars of an extra type in whatever manner that might be possibly available I would be grateful to have my name applied to the approval cylinder in favor of etc thank you.

  • ShabuduaShabudua

    @JohnnyGoodyear said:
    If there are more of the bars of an extra type in whatever manner that might be possibly available I would be grateful to have my name applied to the approval cylinder in favor of etc thank you.

    +1😂 I mean, yeah… if they’re just sitting around somewhere, might as well put them in.🙂

  • HotStrangeHotStrange

    @5k3105 said:

    @skiphunt said:

    @5k3105 said:

    @skiphunt said:
    The thing about the 4 bars… it’s never been an issue for me. Granted, I’m more of a soundscaping abstract experimenter.

    If I ever needed more than 4 bars, I’d just add another scene on the node.

    I also played/recorded notes using the Atom 2 app in a midi fx node. That worked well, but occasionally I’d find myself bumping Atom up to 5 bars.

    I suppose it depends on how you use the app. The flow is kinda different in Nodes.

    I’m sure there are some who’d actually use 16bars in the piano roll, but it doesn’t seem to fit with the elegant and efficient overall Nodes interface.

    Personally, if I ever needed more than 4 bars, I’d just add a midi fx node and use a full piano roll app like Atom 2 or one of the other dozens of piano roll apps out there.

    I think people should simply sit tight on the additional requests until they’ve actually used the app a few days and know for sure they feel something is lacking.

    This dev could cram everything but the kitchen sink into Nodes in an effort to appease every desire, but then he’d risk destroying the beautiful overall interface design… to the point that it’d no longer be such a joy to use.

    Its like… one feature request. Not a kitchen sink.

    How does adding additional options in a drop down affect interface design?

    An option to increase bar length is gonna destroy the app for you huh? No more joy? Wow lol

    Have a great day and a very happy new year. I wish you joy and great luck in the future. :)

    Nice try

    Think you may need to clock out for the day lol

  • lukesleepwalkerlukesleepwalker

    @gregsmith said:
    I’m on the beta now and can tell already that this is going to be a hit @ElliottGarage

    Super responsive dev as well. Preorder, you won’t be disappointed 👍

    BUT WAIT, WHAT ABOUT THE FOUR BAR LIMIT! ;)

  • gregsmithgregsmith

    @lukesleepwalker said:

    @gregsmith said:
    I’m on the beta now and can tell already that this is going to be a hit @ElliottGarage

    Super responsive dev as well. Preorder, you won’t be disappointed 👍

    BUT WAIT, WHAT ABOUT THE FOUR BAR LIMIT! ;)

    in my most humble opinion, still needs 8 and 16 bar options 😉

  • lukesleepwalkerlukesleepwalker

    @gregsmith said:

    @lukesleepwalker said:

    @gregsmith said:
    I’m on the beta now and can tell already that this is going to be a hit @ElliottGarage

    Super responsive dev as well. Preorder, you won’t be disappointed 👍

    BUT WAIT, WHAT ABOUT THE FOUR BAR LIMIT! ;)

    in my most humble opinion, still needs 8 and 16 bar options 😉

    I'm glad that @ElliottGarage invited you to test!

  • CarnbotCarnbot

    Looks interesting, but I think I read that it doesn't support multi-core... that is now a dealbreaker for me in any new hosts. I don't think that multi-core will come to AUM anytime time in the near future and my ipad pro 2017 needs multi-core hosts to make the most of newer apps. So this will have similar performance as AUM/Drambo, great if you have M1/M2 etc but the older hardware is still good enough if multi-core becomes more standard.

    I'm finding that miRack is my most performance friendly modular AU host for now, hope the others catch up soon :)

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • espiegel123espiegel123

    @Carnbot said:
    Looks interesting, but I think I read that it doesn't support multi-core... that is now a dealbreaker for me in any new hosts. I don't think that multi-core will come to AUM anytime time in the near future and my ipad pro 2017 needs multi-core hosts to make the most of newer apps. So this will have similar performance as AUM/Drambo, great if you have M1/M2 etc but the older hardware is still good enough if multi-core becomes more standard.

    I'm finding that miRack is my most performance friendly modular AU host for now, hope the others catch up soon :)

    Keep in mind that some apps that do multi-core (I believe this is the case with Cubasis) crank up the latency when using multi-core.

  • CarnbotCarnbot

    @espiegel123 said:

    @Carnbot said:
    Looks interesting, but I think I read that it doesn't support multi-core... that is now a dealbreaker for me in any new hosts. I don't think that multi-core will come to AUM anytime time in the near future and my ipad pro 2017 needs multi-core hosts to make the most of newer apps. So this will have similar performance as AUM/Drambo, great if you have M1/M2 etc but the older hardware is still good enough if multi-core becomes more standard.

    I'm finding that miRack is my most performance friendly modular AU host for now, hope the others catch up soon :)

    Keep in mind that some apps that do multi-core (I believe this is the case with Cubasis) crank up the latency when using multi-core

    I don't use cubasis but the only other host app I use which supports multi-core is MultitrackStudio which also has great performance, I always prefer hosts which have user latency control and isn't automatic.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024