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
Hah, first that had me LOL for real, then I was thinking "hey, he was actually a guitarist, right?" so I checked him up on Wikipedia, which as we all know is a rabbit hole where I ended up on this page: https://en.wikipedia.org/wiki/List_of_people_who_disappeared_mysteriously
Some of those stories would be good inspiration for a song or two I think!
Aaaaand in other news... drag and drop doesn’t work...
It does work, just bring up the Files.app and drag from there to the pads...
is transient detection coming in the near future?
Nope. Tried drag and drop directly to pads.. no go.. what gives?
I think I will wait until a fix to BM3 update 3.0.4 is submitted and released.
Hi there!
We are asking for an expedited review so hopefully 3.0.5 will be available shortly.
You should be fine without airplane mode now, it was just a bogus sound-pack causing a random memory corruption. Pretty unexpected to say the least, since we go through beta-testing for every updates.
Anyway, we are deeply sorry about this; gladly, we were able to work on a fix straight away.
Thanks for the understanding and support!
Cheers,
Mathieu.
FWIW, I'm also encountering problems of crashing when loading older files with the Model 15 AU synth in the project. The app crashes when I try and bring up the AU UI for the Moog synth...
Will give a good look at crash reports tomorrow for sure! You can always share crashing sessions to [email protected], I have Model 15 so I can probably reproduce it easily!
If you take a look at your own forum you will see other people reporting this exact problem with other au’s. It seems anything saved with the previous version will crash when opening the UI.
This is nothing new (speaking of the AudioBus issue). It's been the same from initial release. BM3 shows up as an AudioBus midi output destination but doesn't work. You yourself have reported this on more than one occasion.
I've provided you with the way to work around that previously, so won't repeat it here.
I believe it also did not work with IAA midi input. I don't know if that's still the case or not, but I suspect it is.
You don't have BeatMaker 3 enabled as a MIDI input in the top screenshot. I think that's your problem here.
I think you need to hold your finger on the item so it 'lifts up' before you can drag it...
@tja See my comment above. If you're sending to "Beatmaker 3" from Chordflow, then you need to enable "Beatmaker 3" as an input in BM3. I do think that's your issue with Chordflow.
Yes, the workaround with AB3 is to use MidiFlow Adapter. Not a great workaround IMO, but it's there.
Yes, those issues, as well as the dumb workaround of having to add a sample in order to set midi should be addressed. And yes, it's odd that they've let that one sit around for so long unfixed when they've worked on so many other less basic issues. But it's their prerogative to set their own priorities, no matter how odd they seem.
+1 @mathieugarcia
Thanks Samu.. I got it working, of sorts..
In videos I have watched, the file lifts up and there’s a green cross and you can drop it straight into BM3.. mine don’t show the cross, but when I hold a sample then press with a second finger, the file app slides away, then I can drop into BM3..
Bit of a fiddly pain in the ass, but it works..
Midi connections are really difficult to understand. My basic rule of thumb is, make the two ends match. If the sending app is sending to Beatmaker 3, then Beatmaker 3 should be set to receive on Beatmaker 3. If Chordflow output was set to ChordFlow, then Beatmaker 3 should be set to receive from ChordFlow.
You would think ChordFlow would be configured to send to BM3 and BM3 would be configured to receive from ChordFlow, but that isn't how it works (normally).
Sometimes I envision it as a cable. If I labeled a cable as BM3, then I would want to make sure that the end of the BM3 cable was plugged into my "ChordFlow" hardware and also into my "BM3" hardware. I wouldn't plug in a cable labeled BM3 into ChordFlow and a separate cable labeled "ChordFlow" into BM3.
Confusing. I know. Cudos to AudioBus for trying mightily to simplify things. Too bad more developers aren't on-board.
Why is the new phasemaker not scaling up as the rest of the makers?
I’ll reboot and take some Poison
Reading this thread on here and on the Beatmaker forum tells me there’s some serious AUV3 issues while using the new update. Not being able to bring up the actual plug in with older sessions, and plug ins not adapting to window size. Hoping a fix comes soon
+1 @mathieugarcia
And maybe it's better to hold for a 3.0.6 update for the AUv3 fix .
Ok, dudes.. iPad Air 1.. why doesn’t drag and drop work with one finger? Have to tap BM3 with another while holding the sample...
That's weird because on the Air 2 (iOS11.1) I can just drop the sample on a pad while the Files.app UI is still on screen. If I need to reach a pad under the Files.app UI i can just move it to the other side of the screen before starting the drag...