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
Yeah, but I'm speaking of only when an AU midi fx is in play. It will record my pad notes but not from my keystep... Though I'll do further tests to make sure my brain isn't too fried.
Gotcha. Well this sucks. I literally just bought this app for my new iPad. Any alternative apps that offer some similar functionality?
I see no changes with IAA and with connected midi devices. Only AU midi FX.
Is that app AUv3? It doesn’t mention in the app description. If it’s Standalone / IAA, then it may just be a settings problem. Never heard of that app before now.
It should work...the midi routing is a little bit of a pain to setup @ times. Are you trying to record the Arp from the KeyStep? Can you get the key step to play notes in your BM3 synth? I can get the arp notes from my NanoKEY Studio to record into BM3 fwiw...
With a MIDI AU fx inserted?
Yeah it's standalone, I just assumed it was AU.
So far I've only tested recording Rozeta Arp midi notes...I can't seem to record Rozeta Collider midi notes for some reason...I have to record it as a separate audio track if I want to keep it for a track.
What's odd, is that Rozeta Collider records just fine in Cubasis.
AU midi fx generated notes won't record. But also they won't send to external hardware.
It also seems to block incoming notes from an external keyboard. It will of course trigger an app loaded on a pad fine.
Edit... seems I was wrong. Reset the system and can now record incoming notes fine.
Don’t blame you for not reading all of this gawdawful thread, but yes, the big brouhaha is that AUv3 midi FX do not get their midi notes recorded. Intua checked in to say that they would change that, but did not say when.
Not that I know of but there probably is. That app looks great!
Has anyone figured out how to run two Rozeta Rhythm AUX on a single bank and have one Rhythm Sequence the top eight pads and the second Rhythm sequence the bottom eight. Activating the second Rhythm seems to cut off the first one’s audio even though you can see the Pads are playing.
Just caught up with like 150+ new comments, but I believe the issue is recording anything AU midi, specifically AU midi FX.
Buuuuut, I could be wrong.
And yes, it was a sad read.
Edit: shit, turns out there was more to read.
Thanks for the appraisal and for a return to forum norms.
I poked around with it, and don’t think you can. But you could do two banks.
@Dawdles Please, for your sake, just stop. You’re embarrassing yourself.
Life is too short to be arguing about Beatmaker, new updates will come, hopefully you get the features you want in those updates.
I’m just waiting for the scenes recording feature like ableton. But I’m really patient
So is this out on iPhone now? 😂
saving aux presets like an fx rack.
a way to deduplicate samples
Just had a chance to sit down with the new updates a bit.
First observation:
Stuff was wildly fucked up in both BM3 and GarageBand. A system reboot fixed that.
Subsequently, apart from the crashes I've had (yeah..) I really love the changes. The MIDI AU implementation is loads more logical to me than the previous setup, and the benefit of that alone has given me loads of inspiration and generated tons of ideas. Hand in hand with that is the transient slicer, which kicks arse!! I'm listening to some chopped up psychedelic khomus insanity right now which wouldn't have happened if not for those two features. I think workflow is MASSIVELY improved in this update.
Specifically with regard to the MIDI AU implementation, I completely get why people are wound up over the changes, but honestly it felt much better designed and more creative in the current implementation. It works like a MIDI EFFECT (MIDI in, different MIDI out), which is totally logical and intuitive. For example, all Rozeta generators can really be thought of as MIDI effects -- they take in MIDI which specifies things like key, active pattern etc. and output pattern data. So, my scenes/timeline in BM3 was simply what instructions the Rozeta instances needed to generate the performance. Playback is perfect! After that, it's really easy to print the audio output onto an audio track (which worked perfectly with almost no setup). It's a great workflow and you can even see on the pads screen, what notes the Rozeta modules are outputting, which is really cool! We've heard word from the source that it'll be possible in the future to print directly to MIDI which actually doesn't really make sense to me unless it was printing to a separate MIDI lane that bypasses the MIDI AU -- otherwise the MIDI AU's track itself will play back incorrectly after it has been printed into the lane containing it's control information.
While I did have some stability issues and problems with re-loading a session, I have absolutely zero issues with the design decisions taken by the BM3 team!
I mostly hear you, but not all (midi in, different midi out) effects are as intuitive. I´m looking at you, Rozeta LFO. It outputs midi cc curves, so intuitively it shouldn´t do anything with midi note messages, don´t you agree? In the current 3.0.11, if you add LFO as an effect then midi events for that pad are not passed through Rozeta LFO, and the output becomes silence. Is this a BM3 bug, or perhaps a Rozeta LFO bug given this interpretation of what midi effects should do? What say you, @brambos?
On another note, in order to get Rozetas hosted in AUM to play different banks in BM3, I now had to, for each bank, select Midi in port as the un-intuitive ALL. Is that new, or has it always been like this? I can´t remember having done that before. The other parts I do remember (set each bank to separate channels corresponding to the Rozeta channels, and turn off in BM3 settings the Omni mode where the focus bank receives all midi).
I like
Yeah, I think this update is a massive improvement personally.
I really don't want them to muck around with how MIDI au is now, because it's more logical for the reasons you have mentioned. I can use Routemidi if I want that MIDI data from Rozeta recorded (that is handy for layering up sounds) and record my transposition notes. It's far smarter this way.
Only one crash so far. Very impressed.
Well, don’t think it’s out yet.. but the countdown for the long awaited update is on.. August release?
Wonder what coming?
Test..