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 perhaps it's better than it sounds from that description
But now it's more as it was advertised originally in his demo, whereby you can play the step sequencers via Drum pads. Just had a go and it's great fun
Yes! Gonna try this.
I might need some help with the setup here... how are you playing via drum pads? Thx
each emitter has a little menu which you can access at the bottom, the three lines, when an emitter is selected. there you can assign your CC or just midi learn an input trigger which I did with my pads.
The midi port menu has been improved as well.
Very nice update. The three lines icon at the bottom for each emitter opens the settings panel on the right. Couldn't be easier. Triggers work great. This is all kinds of fun. There goes my weekend...
Yeah this is now all kinds of fun. Lots of possibilities now including syncing to other sources
The long wait was worth it. Was wondering about if this app was done, but the dev came through with the additional goodies. Cool. Always liked this app.
You wouldn’t
Made my day
So, is there a way that triggering via MIDI will start a sequence rather than just advance through a sequence with each trigger? It's cool enough to be able to manually cycle through sequences but would be nice to also trigger a sequence to autoplay as well.
Not that I can see yet, hopefully he won't stop there and continue to add more functionality. But then you can always use another external sequencer to trigger the emitters to mimic this autoplay behaviour
something like StepPolyArp with it's CC step sequencers at the bottom is good..then you can choose the time subdivision in SPA. So that way you wouldn't have to use the Senode clock at all, just use external clocks.
That works. Just more complex, which is ok for now. @sebastianarnold any plans to keep extending features with midi controllers?
Hey, were we able to send midi out to external synths from each emitter all along, or is that new?
Hi, now there is a way to start and stop sequences using MIDI: you can add bindings for EMIT (+) and CLEAR (x) and keep the clock running. Please see the help file for more options: https://senode.org/help_1.0.3.html
Time is a little short these days, but I will continue to develop Senode, so keep the ideas coming!
Best,
Sebastian
Odd. Crashing back to the 'desktop' from second page of the opening tutorial....can't seem to get past it (12.9/12)...I mean I can go into something else, but without benefit of the tut
Ah well....will go to the help file listed above, just letting you know... @sebastianarnold
Whoops, thanks! I can reproduce this on iOS 12 and will provide a fix soon....
This looks very interesting. Must check out the videos.
So let me get this straight ... I could sort of map out a “performance” by setting up pre-conceived sequences. Then depending on how I perform at the time (say via a midi keyboard) it will trigger these nodes to perform and then ... off into different nodes depending on how I trigger them?
So, in a way it would be like setting up Rozeta but with less randomness? In fact, could one use a Rozeta to trigger Senode say in ApeMatrix? Hmmmmmmmm...
It can be set up as random as Rozeta if you want but you can also have more control over the sequences too. You could certainly trigger the emitters from Rozeta, but it's not as easy as doing it via hardware ports. At the moment it's easier to send midi to AUM/apeMatrix rather than receive it, so you'd have to use a core midi routing app to get the midi out to Senode. Midiflow adapter or Midifire should work.
Thanks for the great update @sebastianarnold
I hope you might add a core midi port for Senode, for other apps to send to, this would help connecting other apps more easily. Ableton Link is my next wish though and also different ways of entering notes and chords other than the keyboard would make me use this more and copy/paste modes for the canvas etc. Having scales too for the emitters etc.
It seems quite selective about which software can make the Senode keyboard trigger the keys to record. It works with steppolyarp, but I can't get this to work with Thesys or some others. So maybe adding a Senode midi receiving port would help here
Yeah it's a bit clearer now, can cycle through different trigger options with your finger
So not to be thick but, I could load senode in AUM, send it’s midi to other synths? Receive in merely to use Senode’s internal synth, correct? ( I say merely, not having a clue how capable the internal synth is). Thanks.
You can route MIDI -> Senode -> MIDI, no need to use the internal synth.
You can't load Senode in AUM, it's completely standalone, so no IAA or Audiobus, but can send and receive midi. The main way I use it is to send midi to synths hosted in AUM/apeMatrix or hardware synths.
How novel!
Yes, that link to the online help is quite handy. Still tinkering and learning a lot. Very cool app.
Thank you gentlemen.
Bought it to support the ongoing effort. Here’s hoping we get au or IAA or audiobus support in the future.
Yeah, so, this app is very very interesting. More later, once I’ve worked with it some more but this is ... game-charting stuff for me.
Yeah but even better would be AUV3 support,
I know that's unlikely to happen though, at least any time in near future so Audiobus is more likely.
@kinkujin said:
First up, figure out the app, build stuff. Then figure out the getting-the-midi-out thang. I see this as being pretty darned powerful and could easily lose myself in it.
I'll not pepper the dev with requests for interoperability until later.