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.
Patternbud bugs? Receiving pattern change CC and using pattern change actions
I’m wondering if anyone has encountered these problems using Patternbud. I’m frustrated, because the app would be a perfect way to arrange the use of other sequencers. I was trying to use two instances of Patternbud, one to sequence other bud apps and sequencers (A), and another instance to sequence/change the patterns of the first Patternbud (B)
I found that the Patternbud (A) receiving pattern change CC consistently changed patterns after receiving the CC message by exactly one note late.
To test and see if this was because Patternbud (A) wasn’t changing to the CC pattern change in time OR if it was because the other Patternbud (B) app was sending the pattern change CC late, I used LK to sequence the Patternbud (A) hooked up to sequencers. In either case, the Patternbud (A) receiving pattern change CC was late by a single note.
I then tried to see if the patternbud follow actions worked for pattern changes….this would mean that at least one patternbud instance could cycle between two of its own patterns by using its own follow actions to change pattern. I found that this function did not work…the pattern would change momentarily then revert to the pattern it was on. Even if this did work, it wouldn’t allow for one to do much of a complex arrangement.
Has anyone seen these problems? @Poppadocrock, I know you use a lot of bud apps and wonder whether you’ve encountered this.
I’m sad because Patternbud, if it worked precisely, would be a relatively efficient way to send CC and program changes to multiple sequencers, allowing for arrangement of a bunch of live instruments. LK is rock solid for this, but entering precise CC automation on the piano roll is fiddly because of the size of the pianoroll grid and how you need to drag tiny automation nodes to precise CC/PC numbers rather than just enter them with a keyboard. Patternbud has a much better UI for this sort of single purpose, though LK would mean you could launch scenes and do live arrangements on the fly more flexibly.
@cem_olcay, FYI on these issues. I can upload a video showing this occur when using two Patternbud and a MelodyBud or Rozeta cells. Patternbud seems to have the exact problem that Polybud displays when receiving pattern change CC that I emailed you / tagged you about last week (changing patterns one note late after receiving a pattern change CC value).