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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Thanks, @Samu. It was the last step to tap the icon after tapping record that tripped me up. Working now!
Goodie!
For most 'IAA-Instruments' the midi gets auto-routed (ie. you can use the BM3 keyboard to play the hosted app).
For 'IAA-Generators' the midi-output has to be manually set. (Either set the IAA-Generator to 'listen' to BM3 or send midi to the iAA-Generator, this varies between apps).
Over all the Plug-In sampler works quite smoothly.
Hoping to see that implemented for 'sampler pads' too for easier re-sampling
During the beta I tried to feed enough ideas to make the plug-in sampler a somewhat smooth process as it is one area in BM3 I use a LOT.
There are some areas that can still be polished for those who like to create multi-samples. (In addition to 'move to next pad' a 'move to next key'). With the 'move to next pad' disabled the sample gets added to a new layer on the selected pad. Others would be to 'auto-map' the sample to the key that was used to play the attached plug-in.
But there are many other areas in BM3 that need more attention...
Yes! Quite! Here here! I often host BM3 in Audioshare for hands on manipulation recording but it would be so much nicer in app straight to pads like it is for plugins. Would save time not having to automate and playback/record all the time.
Thanks @Samu > @AudioGus said:
Count me in on this one. This seems like a no brainer (design wise). At its heart, BM3 is mainly just a big old fancy sampler. Sampling itself makes a lot of sense. I like your idea of separate "sample pads" @Samu . I still find the concept of a pad either holding a sample or hosting a plugin or both to be confusing. And it actually can cause problems in workflow if you don't understand what's going on. If you sample into a pad that's hosting a plugin and then "play" that pad, you'll hear the plugin and the sample. That doesn't seem like a very musically useful use case, and having to unload the plugin to make the pad "just a pad" isn't a very smooth flow IMO.
Maybe "sample pads" could be connected to audio tracks??
I know, I got 'voted down' on the idea of keeping things separated...
Ie. it would make more sense (to me) if a pad could have a 'dedicated mode'(ie. Pure Midi, Sample or Plug-In).
This would work nicely if the time-line also had a 'bank explode' feature where each pad had a dedicated pattern on the time line. (current all pad patterns are 'locked' into the bank-pattern).
At some point 'extra tracks' will come, meaning you can just like in BM2 attach additional patterns pointing to a pad in a bank.
Believe it or not some testers actually requested the option to 'layer' a Plug-In and a Sample or even multiple Plug-Ins.
To me it made more sense to just 'Link' the pads (add them to the same trigger-group) as that will have kept things more organised.
Technically they already are since you can drag a recorded audio-track to a pad (it's in the session folder under recordings). And if one needs a 'pad' on the audio-track it's possible to export just one pad and drag it to an audio-track.
Even though I can feed plenty of ideas to Intua (which I already have) it's ultimately their decision to chose to choose what to implement and when.
3.0.6 is in Beta 4 and should be done soon and correct some quite annoying bugs...