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.
Triggering Patterns in BM2 Sequencer
Can I directly assign a midi trigger to a specific pattern in BM2's sequencer? Or will I need to use an outside program like Genome to handle those types of clips?
Essentially, I want to be able to assign a midi trigger to a short midi clip assigned to a synth or sampler in BM2 - tied to current tempo.
Comments
Don't think so
You would have to record audio and trigger as samples from drum pad instrument to get same effect
Genome is the (only) answer.
@Matt_Fletcher_2000 said:
Thanks - only problem that I see with Genome in this regard is that it doesn't appear to respect the 'one shot' launch setting all the time. I'll hit the same pattern several times and most times it will do a one shot - but sometimes it just keeps looping.
Also surprised it doesn't have an immediate trigger. Granted, a 16th triplet will probably work, but hate to add any unnecessary latency to my process. In most instances, I'm wanting trigger one shot midi phrases to my synths in real time with my drummer - not tied to a click, though Genome will be tied to midi tempo for each song.
Was also hoping to find a tap tempo in Genome, but not seeing anything so far.
From what I can determine, Genome properly triggers one shots when launch quantization is set to 1/16 - but is intermittent when set to 1/16T. I sure wish there was a setting for no quantization, but I can potentially live with this.
Now I need a midi controllable tap tempo/clock source for everything...
I forget if MidiBus has tap tempo or not (and midi in). But if it does, try that. It's very light on system resources.
Nic w/Audeonic says it doesn't but it's coming.
Cool. MidiBus has helped me out in a number of occasions. Seems to sync anything with minimal overhead.
Yup. Handy for recording - but probably doesn't have what I need for a live situation.
What I really need is a way to set an initial tempo for each song in my live set, then have the potential to tap tempo when I need it. I would probably set up BM2 as my master application and open a session with everything I need for the entire show (all samples, and other synth/fx apps needed). Then, for each song in my set, I need to be able to send synth patch changes and midi clock to all apps to change tempo. I then wanted the ability to tap tempo on any song where I feel I need to lock in time better with the live drummer - so my need is more complex than just having tap tempo.
The problem is that I've gotten used to this workflow in Ableton, and now I'm trying to move to an Ipad based rig. I have the ability to set clock tempo for each song from my setlist app (Setlist Maker running on an Ipod touch) - which I'm successfully sending to all my IOS apps. But SLM doesn't support tap tempo and inserting something in the middle of the chain I can simply tap tempo on may not work.
I can probably live without tap tempo until something comes along. Just wanting to see if it was a possibility.
Maybe loopy? (As someone said in another thread I think).
@Matt_Fletcher_2000 said:
Maybe.
Loopy has 3 things I need here - the ability to bind midi cc to tempo, the ability to bind midi to tap tempo, and the ability to be the master clock for other apps.
I have this working at some level, but have also had some mysterious freezes and crashes between Loopy and BM2. Guessing this could potentially work, but have to find the right way to set it up. Possible I have some odd midi loop going on, but no easy way to monitor inside of the apps. I've been testing with Loopy being used as an app inside of BM2 and outside. A little different results in each case, but eventually something fails.
My preference would be to have clock control pushed from my primary DAW (though none seem to support the midi functionality) - or something like MidiBus, that's designed specifically to be a clock source for all.
Sounds like there are plans to add a 'live mode' for direct midi tempo control and tap tempo to MidiBus.
Getting closer - thanks for the suggestions.
Actually - BM2 appears to be the only app not playing well with Loopy's clock. It will work for a while, then just go haywire.
But - after thinking through my workflow - not sure I actually need BM2 tied to midi clock. Only using it to play (non-time-stretched) one shot samples and host some sampled keyboard sounds. It would be nice to get it working so I can have BM2 delays tied to BMP, but most effects are on the synths, and they are clock slaving just fine, so far.
Loopy works for the few time-stretched samples I need, and I'm triggering synth phrases (loops and one-shots) through Genome - which seems to be slaving perfectly to Loopy. Genome is working great with the synths I have it tied to.
I have direct tempo control via CC and Midi enabled tap tempo through Loopy. I can send the CCs for default tempos through Setlist Maker to set up each song - then tap tempo in as needed during each song. Very cool.
Only minor issue I have with Loopy's tempo CC implementation is that tempos can be anywhere from 45 to 300 via CC, giving you tempo variations that have to be within 2 bpm. So - 45,47,49, etc. And the calculations being used don't allow them to be exact - so every tempo is averaged to the hundredths of milliseconds (120bpm is actually 119.29 - or 121.30). Not a big deal for my needs, but something to note.
Regardless - think I'm in business. Now I have to see if this combination doesn't buckle once I program up the whole show and put it through it's paces during rehearsals.
Thanks again -
Do you really need BM2? Sounds like Genome could drive all your midi/synths.
Is it that you've run out of slots in loopy for audio samples or something?
Taking BM2 out of the equation is bound to make it more stable.
I have plenty of one shot samples - something I can't do at all in Loopy (without some advanced midi manipulation). I also need to load up 'everything' needed for my entire show in a single session. I'm not standing over my ipad, and do not want to be opening session files for each song. Loopy's limitation of 12 samples doesn't cut it for me here.
By last count, I have about 8-9 time-stretch loops, 40 one shot samples, and 45 midi clips to run.
Possible there is something else other than BM2, though BM2 seems to be able to stream samples pretty efficiently.
Ah. Got you.
But do you need BM2 to drive any midi? Could that all be done with Genome. Might be more stable. (I found BM2 crashes a fair bit especially when accepting midi clock signals - and also sending and receiving midi at the same time).
Actually thinking about simply turning off clock input on BM2 if it won't play nice. I don't think BM2 needs to send any Midi - only receive.
All midi clips can be pushed from Genome - mainly to synths, though possibly to a BM2 sampled keyboard or two.
I'll see how it all comes together as I move everything from my current Ableton rig. I'm sure I'll have to make some adjustments.