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.
Update from testing: Recording sequencers into Drambo MidiFx first note bugs?
I tried recording Mididreams Mididrums, Mozaic Metroplex, and Stepbud sequences into Drambo after just pointing the midi output at Drambo MidiFx's input in AUM. I set up the sequences, press record in Drambo, and then press play in AUM. Drambo always misses the first beat/step/note. Am I doing something wrong?
Comments
An update after testing...
When AUM transport is set to instant, Drambo MidiFx does not record the first note of an external sequencer auv3, or sometimes will do something strange like record a chord with random notes, even from a monophonic sequence. This was consistent with Mididreams, Stepbud, Rozetta Bassline, and Rozetta Arp.
When AUM transport is set to have a 1 bar preroll, most sequencers were recorded accurately EXCEPT that the first note length/gate was always abridged to a 16th note, even if it was supposed to be a quarter note. Some sequencers were also recorded as a random 16 note chord as with the instant transport.
I haven't recorded a video of these weird behaviors but can and probably will to submit to Beepstreet.
Is no one else getting this weird midi recording stuff?
I'll check this out myself when I have a chance and post some results, but I have had similar problems with recording MIDI into Cubasis 3 and when recording into AUv3 modules within AUM, so when that happens I tend to set up one empty bar, so that the recording comes in on bar 2, and then I chop off the empty bar afterward. Others here may have a better workaround.
I just tested and confirm this behavior.
I never ran into it because I just host the midi plugins in Drambo standalone when using them.