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
@blueveek Very excited to see how this is progressing!
One thing: not sure how you currently have it, but would you consider making it so that controls can be activated on "finger-up"? E.g. with those tempo multipliers, you adjust the value by pressing down and scrolling, but it doesn't take effect until you lift your finger. This allows you to cue the multiplier you want and precisely activate it. This would also be the case with setting the loop flag, editing notes, etc.
You're building in elements that start to make this as much a "performance" sequencer (think Fugue Machine) as a more traditional editor, but to bring that functionality home, those elements need to be triggered precisely. Now, quantization of the those triggers would be best (again like Fugue Machine), but I realize that's probably not in line with the design intent. However, just allowing trigger on finger-up will make this more precise for performance usage than just triggering on finger-down.
How many steps or measures per sequence?
Nice indeed!
Noticed that in the video the AUM presets menu was used...
@blueveek Will this awesomeness also have 'built-in' clip management & storage making it easier to use the created patterns with other hosts as well?
Here is where I wish iMaschine would be upgraded to have midi and better audio handling.. ‘Export to Maschine’ would be magical..
This is something fundamental missing from a number of midi sequencing apps on iOS.
I think the tempo would have to be unlinked from the host though. I could be wrong, but I don’t think an AU can influence the tempo of the host. If I remember the thread correctly, each instance can be free running at its own, but would be out of sync with the host and other instances and apps.
Yes, not to speak of apps/plugins with their own arpeggiator and LFO clocks that people would expect to work too. Def something the host should support in the first place.
You could use apeMatrix as a host instead and control its speed by MIDI clock though.
Dropping this weekend ??
Trigger and pitch probabilities would be really nice indeed. I've added them on the roadmap for a future update.
The only thing holding me back at the moment is finishing the automation editor. I'm going through quite a few iterations and I'm not 100% satisfied with any of them.
I'm more and more inclined to make the automation part of this separate to the actual piano roll. After all, automation items and automation lanes should technically be decoupled from note entry.
Thoughts?
Amazing! A few sites earlier someone posted a video showing ableton I think with some templates automation curves and a nice way to edit these in a quantized way. That would be really cool!
Having those features from Ableton would be nice indeed, but would also pushback this release a few more months
My lips are sealed
I prefer automation to be separate from the piano roll.
Have you thought about adding a slicer? Sooner or later someone is going to ask if it can slice!!
Pure CC automation could be kept 'separate' for sure but at least the semi-note-related performance values (Note Velocity, ModWheel(CC1), Pan(CC10) and Sustain Pedal(CC64) and PitchBend) could be handy to have in the same window.
The separate CC automation 'window' makes sense when applying automation to a repeating pattern as long as they can be kept in sync
That's my initial reaction.
LOL, I was thinking about that too and came to think of 'synced random playhead playback position'
I like the way it works in logic where you click the button to open the automation data and the notes go transparent in the background with the autmation data in front.
I've never even automated a piano roll lol so I'm cool with it being added later and separate 😆😎
I just automate my synths, effects and channel strips, but now I'm curious lol
That's a very good point.
Without going into detail, here's a few things to consider.
There is only one correct answer: It depends. There are automations, which can be thought more like LFO with custom oscillator shape and for those it makes sense to be decoupled from notes. But then there is heavy use of automation that is coupled to notes. The example that comes to my mind is DNB, specifically "neuro" bass style, which is often used also in dubstep and similar genres. This is some quick example of what I mean:
Personally, I would like to have automations and notes in one instance of piano roll for such cases. If you want to decouple it, there is nothing preventing you from having one instance only for notes and one instance only for automations.
Oh yeah,... neurofunk
Yes, agree. Separate makes sense.
You know, whatever you have currently is bound to be better than what Cubasis has.
Just sayin’.
I agree with @skrat that sometimes you’ll have use cases where you want the automation associated with the notes and other times the automation will be independent of the notes. There could even be an AUv3 app that is dedicated to non-note based automation. It would be very nice for the initial offering of the app to have a handful of parameters you could automate in conjunction with notes as @Samu has posted. You could add them as needed and customize which CC they output to suit your needs.
I wouldn’t be interested in a version of the app with no automation at all. I would prefer a more considered and viable app than one that’s released prematurely as adding additional functionality to a flawed design can end up being very clunky.
There may of course be a market for a note only based piano roll editor and perhaps going for that market first might be reasonable before addressing the more complex issues of automation.
BTW, to not get my words wrong: Do not let automation editor to prevent you from releasing the version 1.0 with piano roll functions only. I always thought that automation editor is at least as complicated as piano roll to implement, if is done properly, so if I can suggest you, take your time for it. I believe it will be easier for you to handle feedback from the first version if it contains less feature and rather polish them. If you then add automations, people who think it’s a must will only get it later, which would be the same as if you’d be postponing the release because of automation.
This is extremely useful feedback folks, thanks for it!
Consensus reached
Roll now
automation later
YOU BET YOUR BIPPY! JUST GIVE US THE DAMN ROLL.
Second the motion....😎
except the slicer. GIVE US THE DAMN SLICER!