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.
Chordjam - Saved Sessions don’t include sequencer presets?
Fellow Chordjam users …
The manual seems to imply that saving a Session includes the sequencer presets, but I can’t get this working. I can load individual sequencer presets on the saving tab, but they end up being the same whatever Session I have loaded. Loading Sessions doesn’t seem to recall the sequencer presets which were in place when the Session was saved.
I wonder if somebody can help clear this up and show me what I’m doing wrong, as I want to create a number of different sessions with different sequence of presets for working on a number of different tracks.
Thanks in advance 😬
Comments
My understanding from reading the manual is that the Sessions, Sequences, and Pads are all saved as separate presets of there own type, and you have to save them explicitly.
When you save a Session, the current Sequencer and Pad settings are saved and recalled with the Session. You can create a new Sequence or Pad preset by saving them in each of the other panels.
The saved Sequences and Pads in these other panels are independent of the Session save, and they are each saved and recalled in there own panels.
Yes that seems to be it, on rereading the manual. It’s a very odd setup … it would make more sense to save the current presets as part of the session, esp when it’s billed as a performance feature.
It seems it’s not possible to save the current presets as a set, but only as individual presets.
It’s a wonderful plugin otherwise, but this feature could have been much more useful if implemented differently.