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.

AudioVeek Piano Roll MIDI sequencer AU

11112141617

Comments

  • It would be pretty neat if you could do polyrhythmic automation. Meaning you could decouple the length of each automated parameter and have it be whatever length you wanted for each.

  • The user and all related content has been deleted.
  • NOW NOW NOW

  • I’ve been following this thread since the first post, and this app started as an AU Piano roll MIDI sequencer (something that doesn’t yet exist in iOS and most users have been claiming for a long time) and it’s been rapidly turning into some kind of weird generative-random-mutil-poly-parameter lock-chop-slice-free tempo-pitch probability-automation curves-live transpose-loop triggering-scene launcher-arp generator-whatever you can imagine and it has to be intuitive, easy, light, cheap and beat Ableton on the desktop.
    You @blueveek have proven to be an incredible developer, but I’m afraid this is boldly going “where no man has gone before” very quickly, and it could take years for a one man operation to deliver a polished app like that.
    I humbly suggest that you deliver an AU Piano roll as originally planned, with the additions you already managed to implement that are working smoothly. You can then get some feedback from actual use (and some $$$ revenue you well deserve) and later decide what direction to follow or what other features are worth implementing.
    There are different groups of well defined users with very different needs. Just a few examples could be: traditional musicians that need a standard piano roll to be used with a real keyboard, Beatmakers that need to chop, slice, loop, etc with a multipad controller as instrument, Ableton users that want to generate patterns, invert, modify, automate, and write music just with a mouse, modular synth guys that mostly use step sequencers with parameter locks, etc, etc etc and all of them are suggesting awesome features based on their needs, which is really great, but I’m not sure absolutely everything can be condensed in just one AU piano roll app. Maybe you could develop several smaller apps targeted for the different users categories, and as AU plugins they could be used alone or combined according to user needs.
    But maybe I’m wrong and you are developing such a game changer app that nothing will be the same again. That would be awesome too.
    Just an opinion, of course.
    (Please roll it NOW 🙏🏻 😂😂😂)

  • @Rodolfo

    I agree, much better making a piano roll editor, which is good a being just that. There are already lots of other AU's which handle generative stuff, chords and those things.

  • edited March 2019

    Mission creep. That shit is real.

    Great post @Rodolfo - I've had several lengthy chats with @blueveek over the last few months and I can assure you he's very good at being able to clearly separate core, desirable and niche into their relevant places on his features roadmap.

    I expect he is even more eager to release this than any of you.. so I'm confident he will 'roll' as soon as its ready.

    Developers have the unenviable task of walking a tightrope between sometimes listening to users; whilst other times completely (but respectfully) ignoring them. I'm glad I don't have to deal with that dilemma - I have enough trouble arguing my inner-monologue!!

  • edited March 2019

    I'm humbled by all the responses here, as well as how eager everyone is to get their hands on this plugin. All of this excitement is encouraging indeed.

    There's a lot of new features that were added thanks to the feedback in this thread. From step input to elastic quantise, from instance colors and negative bpm and so on... And I'm happy to report you'll get your slicing at launch too :smile:

    Proper automation implementation seems to be taking longer than I was expecting. Different people in this thread seem to want different kinds of things. I went through a bunch of iterations, some well suited for certain kinds of tasks, some for others, but I haven't figured out a "grand unified automation theory yet". I want to get this part right, all while acknowledging the fact all of you are patiently waiting for a release.

    It looks like the vast majority of the folks here would still prefer to use this AU even without automation at launch. So here's the plan. I'll submit this for review next week. Arbitrary parameter automation will be part of a free update.

    Cheers! And see you on the other side :sunglasses:

  • Next week??? AWWWWWSSSUUUMMM!!!!
    Thanks mate! I waited so long for a piano roll plug!
    Thank you @blueveek
    So glad to support this as an instant buy and see where you will take us all 👍🏼😎

  • +1
    Great work @blueveek ! Highly appreciate! 👍

  • @blueveek said:
    I'm humbled by all the responses here, as well as how eager everyone is to get their hands on this plugin. All of this excitement is encouraging indeed.

    There's a lot of new features that were added thanks to the feedback in this thread. From step input to elastic quantise, from instance colors and negative bpm and so on... And I'm happy to report you'll get your slicing at launch too :smile:

    Proper automation implementation seems to be taking longer than I was expecting. Different people in this thread seem to want different kinds of things. I went through a bunch of iterations, some well suited for certain kinds of tasks, some for others, but I haven't figured out a "grand unified automation theory yet". I want to get this part right, all while acknowledging the fact all of you are patiently waiting for a release.

    It looks like the vast majority of the folks here would still prefer to use this AU even without automation at launch. So here's the plan. I'll submit this for review next week. Arbitrary parameter automation will be part of a free update.

    Cheers! And see you on the other side :sunglasses:

    Thanks! This is great news. Even without the automation editor, will it be able to record incoming CC?

  • @soundshaper said:

    @blueveek said:
    I'm humbled by all the responses here, as well as how eager everyone is to get their hands on this plugin. All of this excitement is encouraging indeed.

    There's a lot of new features that were added thanks to the feedback in this thread. From step input to elastic quantise, from instance colors and negative bpm and so on... And I'm happy to report you'll get your slicing at launch too :smile:

    Proper automation implementation seems to be taking longer than I was expecting. Different people in this thread seem to want different kinds of things. I went through a bunch of iterations, some well suited for certain kinds of tasks, some for others, but I haven't figured out a "grand unified automation theory yet". I want to get this part right, all while acknowledging the fact all of you are patiently waiting for a release.

    It looks like the vast majority of the folks here would still prefer to use this AU even without automation at launch. So here's the plan. I'll submit this for review next week. Arbitrary parameter automation will be part of a free update.

    Cheers! And see you on the other side :sunglasses:

    Thanks! This is great news. Even without the automation editor, will it be able to record incoming CC?

    I'll be disabling CC recording for this release, because not being able to visualise or remove CC messages is going to be painful. I'll turn it back on in the automation update.

  • edited March 2019

    Very happy with this great news too!! Thanks 🙏

    About automation, being able to make rhythmic automation based on notes position is very useful, as being able to copy paste notes and automation at the same time. I suppose a good way to do it should be to being able to see automation in background transparency with notes on foreground, and vice versa. A separate plugin for automation doesn’t make sense IMO, and will give a slower workflow.

  • @blueveek said:

    I'll be disabling CC recording for this release, because not being able to visualise or remove CC messages is going to be painful. I'll turn it back on in the automation update.

    Understandable, but it will still be possible to edit the note-velocities right?
    Hopefully the velocity editing will also respect the selection making easier to do velocity ramping on a selection.
    (usable for snare-rolls or when using velocity to control other sound parameters).

    My AUv3 'step-sequencers' of choice for now are ties between StepPoly Arp Unit and Fugue Machine and Rozeta Suite and well Photon...

    Considering what you've got cooking it can pretty easily replace all of the above for AUv3 sequencing ;)

  • @Samu said:

    @blueveek said:

    I'll be disabling CC recording for this release, because not being able to visualise or remove CC messages is going to be painful. I'll turn it back on in the automation update.

    Understandable, but it will still be possible to edit the note-velocities right?
    Hopefully the velocity editing will also respect the selection making easier to do velocity ramping on a selection.
    (usable for snare-rolls or when using velocity to control other sound parameters).

    Velocity is editable. This is a much simpler beast than other automation workflows.

  • @blueveek said:

    Velocity is editable. This is a much simpler beast than other automation workflows.

    There is also a big difference between editing recorded CC's and generating CC's automation.
    I think that's something that is easily forgotten...

  • @Samu said:

    @blueveek said:

    Velocity is editable. This is a much simpler beast than other automation workflows.

    There is also a big difference between editing recorded CC's and generating CC's automation.
    I think that's something that is easily forgotten...

    Agreed. To be clearer, velocity is both recordable and editable.

  • Just made my weekend. Whoo!

  • edited March 2019

    Great.. now let’s head over to that AUM thread...

    😆😆😆

    Thanks.. looking forward to next week..

  • @RajahP said:

    Great.. now let’s head over to that AUM thread...

    😆😆😆

    Thanks.. looking forward to next week..

    😂

  • edited March 2019

    Nice post @Rodolfo. You’re a gentleman and a scholar @blueveek. Looking forward to this.

  • Instabuy! 💯 So excited we are getting close to a release. Everyone is on their toes. @blueveek

  • @blueveek .. any price set in mind yet?

  • @blueveek said:

    @Samu said:

    @blueveek said:

    Velocity is editable. This is a much simpler beast than other automation workflows.

    There is also a big difference between editing recorded CC's and generating CC's automation.
    I think that's something that is easily forgotten...

    Agreed. To be clearer, velocity is both recordable and editable.

    Please don’t let CC64 recording out of the game... keyboard players (main users of a piano roll app) would get really frustrated as it happened with NS2... 🙏🏻

  • @White said:
    @Rodolfo

    I agree, much better making a piano roll editor, which is good a being just that. There are already lots of other AU's which handle generative stuff, chords and those things.

    Agreed.

  • @Rodolfo said:

    @blueveek said:

    @Samu said:

    @blueveek said:

    Velocity is editable. This is a much simpler beast than other automation workflows.

    There is also a big difference between editing recorded CC's and generating CC's automation.
    I think that's something that is easily forgotten...

    Agreed. To be clearer, velocity is both recordable and editable.

    Please don’t let CC64 recording out of the game... keyboard players (main users of a piano roll app) would get really frustrated as it happened with NS2... 🙏🏻

    And CC1. Got be able to record the mod wheel, at least eventually. And actually one of the main things I’d like to do with the app is sequence live electronic drums which uses CC4 for the hi hat pedal control.

  • wimwim
    edited March 2019

    I’d love to see arbitrary per note cc values in addition to full-on automation. They would be edited just like velocity, but send cc’s. I’m picturing a plus button, then a selector to add the cc. Once the cc is added you’d edit it just like velocity. The display could switch between velocity and added cc’s for editing. I don’t think it would necessarily need to be recordable.

    I’m not sure if this is the same as what I’ve heard called “Parameter Locks”, but I would use I’ll the time if it were there.

    This in addition to full automation editing, in a separate interface would be extremely powerful.

  • @wim said:
    I’d love to see arbitrary per note cc values in addition to full-on automation. They would be edited just like velocity, but send cc’s. I’m picturing a plus button, then a selector to add the cc. Once the cc is added you’d edit it just like velocity. The display could switch between velocity and added cc’s for editing. I don’t think it would necessarily need to be recordable.

    I’m not sure if this is the same as what I’ve heard called “Parameter Locks”, but I would use I’ll the time if it were there.

    This in addition to full automation editing, in a separate interface would be extremely powerful.

    Interesting, +1 on that!

  • edited March 2019

    @Rodolfo @soundshaper @wim All of the CC stuff is going to come in a free update after release, as they're dependent on the automation bits.

    "P Locks" is something I've been investigating a bit lately, and should be easy to reuse the velocity controls just for that (as this isn't the same thing as arbitrary automation that's decoupled from notes).

  • @Halftone said:
    @blueveek .. any price set in mind yet?

    He had an incredible and unbelievable intro sale on his midi tools... I am absolutely sure there will be the most fair price tag 👍🏼😁

  • Nice that consensus was reached quickly. I also think rolling out early is the best bet (especially since you’ll get feedback from a broader crowd). We’ve been clamouring for this kind of plugin for so long that you can’t (and probably shouldn’t to) fulfill all of our wishes.

Sign In or Register to comment.