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
@midiSequencer will the pad be midi learn assignable to external controllers to get a play/stop command ?
That would also mean that they should start or not on Link start/stop I guess...Maybe a parameter to set on the pads ?
Also could each pad might have a logic in their repeating ?
Like looping infinitely or to a specific value ? (for each pad )
Also I think a pattern mode where you could play one pattern at the time, then switch between the 4 could be interesting (instantaneously or at the end of the cycle)
Here again maybe a logic in the chaining, like go to next at the end, go to previous at the end, go random to an other, go random but the one already played.
This pattern mode would be also controllable with an external midi controller.
Hope this gives you ideas for your workflows
For Pads I'm thinking Ableton Live clips again.
I am aiming to expose as much as possible via AU Parameters - that way you can automate it how you like. The rest will be via midi cc commands.
But yes - a way of triggering these remotely is necessary too - as is recording.
It records multi (midi) channel - if I added a feature to 'split by channel' - so ch1 to track 1, ch2 to track 2 etc would that be helpful? You would then a) export as a multitrack midi file & b) be able to split the record across pads.
It should still be a 1 button record app - you setup your options before that - mostly so you can do multiple takes then choose which to discard say?
Sounds like ModStep might fit the bill here even though it's not been update in a while
(It can host the AUv3's too in case you want to cut down on app-switching and it can record the Plug-In audio too).
Actually Beathawk 2 do record up to 16 tracks of midi AU (With a 16 bar limit tho):: and its not the easiest thing to control.. The beauty with software, is, it is not set in stone... it can be modified/updated ..all that good stuff..
I say, let’s get these recorders/players to market ASAP... and we can take things from there...
Something special is happening here on Audiobus Forum which I never saw happen on KVR and other forums... We have great developer giving their opinion here which can only be a good thing for iOS music production...
Edit.. can we get an ETA ?
It's 'like it used to be' no AUv3 Midi Plug-In Support nor probability stuff but it does midi clip launching quite well and AUv3 automation can be 'drawn' but not recorded from the Plug-In UIs.(Everyone is waiting for ModStep 2).
Personally I miss the option to send multiple clips to the same 'plug-in' but that can be fixed by hosting the Plug-Ins in AUM or something (Examples would be notes on one track and controller data on another and the only sequencer on iOS that can currently do this is Xequence and even that has it's limitations on number of CC controllers per instrument(12 or so with IAP)).
I've learned to 'work around' limitations instead of getting upset when things don't work 100% my way...
And also I've learned to (mostly lol) 'stay put' since I could 'trash talk' just about any iOS app to oblivion no matter how good it is, there's always room for changes & improvements
(If I can't find anything worth improving in an app I've failed big time).
Probably a couple of weeks for me to publish my app.
Oh, and I have a auv3 midi fx app (realtime midi echo) done already. Was looking to release three together but two will do...
Man I can’t wait, this is gonna be awesome for AUM! 🤤 something I have been wanting for ages.
That's true!
Truly Fully Featured apps take long time to develop and we don't even have a serious clue if the big-names are even cooking something for iOS. I can't for example imagine Ableton doing 'Live' for iOS and sell it for $29.99 it just doesn't make sense unless they severely cripple to push more desktop sales...
(And if they are no one here would dare comment anyway due to 'NDA Hell').
Also 'shooting at a moving target' should be a nightmare for most developers and when we as users are on the 'bleeding edge' on iOS it makes things even more difficult...
(Ie. we use the apps in ways that the developers never imagined them to be used like).
Time will tell what happens. I'm at least looking forward to some serious 'App Cleanup' when iOS12 hits but my 'trinity of apps'(Cubasis, Gadget & BM3) will remain along with plenty of AUv3's and 'support apps'.
Great.. can’t wait...
Appreciate all you developers...
Funnily enough I don't use any of these apps (although I have them all). Never found a DAW I liked that suited my composition style - preferring to work in smaller improvisational chunks I could just record however imperfect.
On the PC I use Cantabile to just record & host vst synths. I'm warming to Ableton live but again prefer clips to arrangements.
I'm sure everyone has their own method of working though... maybe I'm just too impatient!
@midiSequencer is there a possibility that you may "expose" the length of a midi loop (relative to the Link timeline I guess) to other apps ?
I think I may have a cool idea...
Ok, here's the concept of a full AUv3 live sequencer.It's based on the app Midi Recorder as it is (with just an option to "advertise" it to an other app, so being "slaved" of it) + an additional app that connect to all instances of it.
The "beauty" of it is that all midi connections, midi events are not in this sequencer, all is set by the Midi Recorders instances that you have set the way you want, with midi clips you've included and midi connections.
The additional app "Node midi recorder" is "just" a timeline organizer, that organize a playing structure of these Midi Recorder(s). Then, this timeline can be organized as tracks, and these tracks are organized in playlists. (and a sort of DJ mixer player)
Considering that you may know the length of a midi loop, relative to Link sync, you can set a sort of scale for each midi snapshot relative to each other.
So, picture this
1.Each Midi recorder (the actual app)get a unique name (bass , drums, chorus, verse...whatever...) we'll call that a "midi slot".
2.An other app "Node Midi Recorder" where on each row, each slot added (midi recorder app) is appearing automatically. (You may also exclude some, you'll see why later...)
3.On each line of each slot, of this tracker (subdivided in 4 rows as there's 4 pads) , where each line represent the length of this loop you may choose select these actions
a.play
b.stop
c.empty
4.structure your track
5.then each track can be played/organized in the "Master Node"
Not clear at all ? Seems logical...
So 3 sketches to help:
First one, the "node track view" where you can organize your song based on Midi recorder(s) AUv3 available:
https://docs.google.com/drawings/d/1U_nQdAx-5A-otCBE965ECh_x3Qz5ehZqRHk22d8R9zg/edit?usp=sharing
Then, you may "zoom out" to the "Main node view" where you can organize your tracks and play them.
https://docs.google.com/drawings/d/1oKAr1J0NJLXa46rQuRG76bDNlY8AspczAB_XlTH0iF0/edit?usp=sharing
A draft of the global architecture:
https://docs.google.com/drawings/d/14ALXCUMpK8zXa31h3LnEWe4jamoF1jjvv2czKXKlidM/edit?usp=sharing
I think it's a good idea...
Yes I can expose the midi clip length as an au parameter. Changes in that parameter would then affect the end point - so for example you setup to record 4 beats. You capture 3.5 beats. Normal playback is 4 beats, but with au parameter you can shorten this to 2 beats or loop it more to say 8 beats.
All this is non-destructive - meaning you don't lose the last 2 beats if you set the au parm to 2 - the internal recording is still 3.5 beats filled out to 4.
But what you are describing here is a daw app not a clip record/playback app - something like sony acid pro or maybe Genome?
I've always liked that way of arranging but midiRecorder needs to do the basics first with a simple grid of pads.
@midiSequencer
Will the app have a low CPU footprint do you believe? Will it be possible for it to work from the AUfx slot in AUM at some point in the future maybe?
Why would you want it to run in the effects slot? It will not automatically receive MIDI from the 'upstream' apps, if that's what you're hoping to accomplish. You will always need to manually wire MIDI inputs into the plugin, regardless of whether it's placed in the instruments slot or the effects slot.
@midiSequencer yes, it's a way to control multiple instances of Midi recorder.
Agreed that it needs a release of Midi Recorder first...Then you'll see...
This additional app wouldn't interfer with it, (or not so much...just the start/stop, looping number) it would just organize a timeline...
In fact connections will indeed being done with midi, but as it would be "very midi busy and complex" advertising these Midi recorder and connect them to a "master node" would make things easier to set "automatically".
well it means I don't have to open up a new channel specifically for the midi record app. In AUM keeping channels to a minimum is desired.
@[Deleted User] I see your point, but AUM doesn't allow advanced routing options into effects slots. (choosing midi channels etc...) you may see the effect in the midi route page, but it will be up to you to feed it with the right midi channel(s), but also to send the midi signal back to instruments...
That's going to be a bit messy with the midi route page, but it should work...
As it's going to be a real mess to manage with lots of channels, I'd not doing like that atm...I prefer to have lots of channels into AUM.
I would also like to tell you that a future update of AUM will have "midi-only" slots that can be used for MIDI plugins such as this, instead of wasting a whole audio channel strip for it. But yes, I want to keep MIDI routing fully flexible so you'd still need to tap the little button next to the node to choose where it receives MIDI from, there will be no automagic stream of MIDI flowing from top to bottom.
Oh I thought the midi options are the same in the au effect node slots?
Thanks for this! Great news and no need for automatic stream of MIDI flowing from top to bottom when you can just tap on a box and add the functionality.
They are exactly the same. But only for effects that can receive MIDI, of course.
@midiSequencer just to explain a bit better. You set a lot of Midi recorder, then, you have recorded and quantize the way you wanted, with automation etc...
Right, next step would be what ? Export all midi files, import them in Xequence / Cubasis / Modstep, then what ? Do all midi connections again then structure the track ? When you're happy with that, what next ? Export midi snapshot again ? Wow...start to be messy, midi connections might have changed, as channels, and you can't even export a specific part of a midi track with any app...Ok, welcome to the nightmare...
Why not having everything in the same place so you can have some Midi recorder(s) ready for live performing, and some other playing a bit of structured midi ? Then you may also dynamically modify them ?
You may really play and test your tracks for multiple gigs, then, when you find the "perfect" song, you may export all snapshots, then set a final song in whatever daw you want...or not...just stay them here, and just increase your playlist...
@j_liljedahl I meant the midi panel here that you don't have in the effect slot, but that might not have any sense at all...
