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.

Different Drummer on sale!

12357

Comments

  • Ok thanks that makes sense. Shame though, it sounded much better out of sync!

  • Understand completely. I think I will make it so if you hit snapshot it will store more params regarding the play points of all the waves. And then if you hit play, I'll restore those points which makes sense for "capture" but if you save while stopped it will save the zero points. I might need to add a reset/rewind type of button too...getting some ideas. See, it's a collaboration! Music and precision are the goals.

  • edited May 2015

    I have a performance coming up that uses a saved preset and every time I load it it sounds exactly the same as when I saved it. And then in the performance I change the beat value and mix on different voices so it's all under my control. So not sure what tweaks you made or at what point you save your presets, Flo, and also you've never been able to tell me what exactly changed (phase, CPM, beatvalue, wave partial, rest wave, tie wave, etc...any clue?) which makes it hard to address or fix. If it exists and I can find it, such a bug should be easy to fix.

  • Idea:
    What if you make the app have a Noob or Amateur type of level and a Pro User type level. So in the Amateur level many of the more advanced options would not be available. So to help the new users first learn to get the hang of what the app can do. The as they outgrow the Amateur level, they can go to the Pro user level and have every option available.
    I think this would greatly help newbies wanting to get the app but get intimidated by how deep it is. Just an idea.

  • There is also a persisting problem with performance, (Air-1, 8.3)
    I get glitching after 30 seconds of playing...and on 1 track/channel only...

    To reproduce: solo 1 channel, and hit random button a few times. It plays OK for few seconds, (less than 1 minute) and then it glitches, distorts...Stop, restart. Glitching? here yes.

    In last update, techne fixed the problem of clock lagging.

    I really like this app, but in my opinion it is too complex for its own good, to the point that it can't even "run"? and it keeps getting more and more complex..
    I haven't got one app that glitches this bad:(

  • Thank for the feedback. I try my best and in my last release I would run 8 tracks on my old iPad 2 for 15 minutes without glitching. I would not release it if it glitches after 30 secs but I wasn't hitting random that much. @soundklinik did you have any other audio apps running at the time? Maybe email me a glitching preset. I'm sure there are bugs in there so I hope I can knock em out...if I can find em.

  • @technemedia One thing I've noticed is that the time marker in the top window is smooth when starting the app but when switching back and forth between other apps soon becomes laggy very quicky, sounds still ok but the update is slow. Stopping and starting the timeline then doesn't help. This isn't a cpu issue because at this time the cpu usage is very low. Also occasionally one of the tracks in a preset will stop playing it's sample and I'll have to change sample or restart the app.

    It would be great if the top visualisation could be set to a more traditional view of the midi notes to help see what's going on, I know the third visualisation option is nearly that but it just becomes an abstract pattern.
    Perhaps when you highlight one of the tracks this view scales up so you can see the midi notes properly along a grid/piano roll.

  • @techne, I will upload the track through DD for you to test.
    Thanks

  • That definitely was glitching for me so will be interesting to figure out. Thanks for uploading @soundklinik

  • @technemedia said:
    That definitely was glitching for me so will be interesting to figure out. Thanks for uploading soundklinik

    You're very welcome, hope you get it fixed.
    Thanks for caring;-)

  • edited May 2015

    I found one real PIG in the poke...the saw wave has (HAD) a really terrible old algorithm in it that worked harder and harder as time went by and I found a couple others too like that but now both your examples now run flawlessly for as long as I've run them. The individual track reverbs also use up some CPU but they do it consistently, not increasingly. For now avoid the saw wave....sorry about that! Grid Mode is also safe.

  • edited May 2015

    Keep Calm! Strength in numbers. All is well.. :-)

  • Try as I might, just can't keep those pigs outta my pokes! Don't mind me...just thought that funny coming from a NJ guy and me being a southern boy. ;-)

  • @technemedia Really like the Progression composer :) is there a way to export the progression as a midi file? Or to create a sequence from the progression in the sequence manager?

    At the moment it doesn't seem to be possible. Would be an awesome update, unless there's a way I'm missing?

  • My pig is in the poke. Grid Mode is safe. All is well.

  • Interesting idea...will think about that....Progression to Sequence. Theoretically if you have a progression applied it should export it to MIDI already when calculating the MIDI notes. If not then it's a bug.

  • Thanks, maybe it's already working but I'm not doing it right, I'm a little confused by the sequence manager process. Will have a look....

  • Yeah It definitely exports the progression so my mistake, although being able to see it as a progression sequence in the sequence manager would be cool :)

    Another thing I'm finding (apologies for all the queries!) I'm trying to sync to a DAW (multitrackstudio) and I'm finding that when I send the clock from MTS with DD set to sync "in" the tempo is too fast. It would be great to be able to choose a clock source from DD then I think I could fix this with midiflow....

  • @Carnbot - if you have MidiBus, you might want to try that, as DD will take clock from there. Not sure if MTS will, but if so, that might solve the problem.

  • @funjunkie27 said:
    Carnbot - if you have MidiBus, you might want to try that, as DD will take clock from there. Not sure if MTS will, but if so, that might solve the problem.

    Thanks, I don't have Midibus right now to test that. I think the problem is also that MTS won't sync from an external clock or if it can I've not been able to do it yet ...

  • I'm not seeing a way to get MTS to accept an ext clock either.

  • Just submitted v. 3.3.2 with a lot of fixes. Thanks everyone. Always more to do!

  • You are the update king Peter!!

  • @technemedia said:
    Just submitted v. 3.3.2 with a lot of fixes. Thanks everyone. Always more to do!

    Good news!

  • Great news, thanks for all your hard work. Seems like is does sync with MTS after all (I'm only just getting used that app which is by the way also excellent)

  • Another DD Delight from the Flowster! Thanks for sharing.

  • Nice groove Flo...should we start calling you Flow?

    @Carnbot - how did you get MTS to sync?

  • @funjunkie27 In MTS devices setting, "Midi clock to apps" choose different drummer.

    This syncs with DD but you always have to rewind to the start of an MTS track to get the sync . I do find DD quite prone to crashing when syncing too.

  • Wow...I missed that setting entirely. I haven't seen any crash issues yet though. I wonder what we might be doing differently. In any case, thanks for the enlightenment @Carnbot.

  • @Carnbot Next version I'll look at possible bugs in this code...I didn't spend too much time on that so far. Probably some sort of divide by zero bug.

Sign In or Register to comment.