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
#
Damn. Sorry mate! I know you work on the iPhone quite a bit. Maybe they’ll change their minds in the future. I don’t blame them for not putting it on iPhone but it suck’s for the consumers.
4 instances along with BA-1 and Blackhole on a send bus…brought my iPad Pro M2 to its knees first time I’ve experienced that.
Time to start dreaming about M3 I suppose
Iphone was/is almost 10x the revenue of ipad, so that's a bit off. I'd guess it's more because of usability issues - to make a new ui for a even more niche audience probably doesn't make economical sense. And it maybe never will, I actually wish devs dropped the iphone all together so they could focus solely on the ipad. Would be interesting to see a number comparison of music-making users across platforms. There's alot more iphones, also used more than ipads, but for different things, just as Apple prefers. As a big company they would love to just do one thing, but luckily for us people demand bigger screens. I get it's annoying, having all that power in your pocket though.
@MoogMusicInc said:
These modulation options along with a poly AT keyboard... Sooo fun. And as always, the preset packs are really good, they show off the unique capabilities of this synth, great way to learn to make crazy patches.
Has anyone with the Moogerfoogers done something crazy with this yet? A tutorial for how to use them together would probably be useful to many.
Found a great tutorial, bit on the modulation is from 07:50 onwards
@tekk
Ah, pretty sure when Greg said iPhone sales were lower, he actually meant sales of music apps for iPhone.
Definitely might make sense to forget about iPhone versions for many apps, sorry iPhone users.
If making a complicated app that needs a complex UI, surely it's better to play to the strengths of the device that almost everyone is using - the iPad - than to have to make UI compromises so that ppl can use the app on a phone, despite the fact that few people are using phones. More dev time wasted on making apps work well on both ipad and iphone means that dev costs are higher, prices are likely therefore higher, and that means that ipad users are basically subsidising a small set of phone users. Doesn't make much sense, so yes, I personally agree with you.
Yep, that’s what I meant.
Although I’d like to know how many people USE the apps on their iPhone, even though they didn’t buy them on iPhone 😉
Probably not enough to make a business case, but who knows.
Unless the stats are based on which device has downloaded the app rather than sales. I have no idea.
Indeed, I think I remember you mentioning that before, and it seems a fair point, I'm not sure whether devs have that data, if they're only basing the opinion that phones aren't that important on which store they're bought in, that might not be an accurate reflection, yes, so maybe a dev can comment on this
That sucks but probably for the best
I don’t own an iPad and won’t for at least another year . But after the disaster that was my ButterSynth experience, I can see why certain apps aren’t ported over. I finally get it . Compare it to the Iceworks synths , which operate like a DREAM on the iPhone, especially once you have the layout memorized!
I’m in the same boat as you. It’s only iPhone for me for now, that said, using Drambo and MiRack is a pleasure and I’m yet to have either of them max my cpu.
How is MiRack on the phone? I was worried it’d be too tiny
It is tiny but the zoom and navigation system is fantastic and very intuitive. Once you get used to it it’s not a major issue.
With no facts to back it up, I suspect iPads for music production is more a first world thing and iPhones might be more commonly used in other countries, like say India. And the youth are born with phones in their hands, so there is an opportunity there. Get kids used to your products on the iPhone. Those that are serious (or rich) might one day get iPads. I think a geographical breakdown of app sales and iDevice sales would be very interesting.
Ok cool… that’s why I never purchased RRS IVOKS, because while using the free version as an AU in GarageBand it was so tiny as to be neigh invisible … it made BA-1 look like a billboard lol
Yeah, there is truth there also! Apps like Koala on iPhone might open ppl up to exploring all this, then they realise that there are more possibilities on iPad (and it's better for your damn back, eyes etc) so start making music there. I was thinking about this after making that earlier post. These things are always much more multifaceted than appears.
Yep, exactly. And given that the average age of this forum is about 60 and lots have eye issues, it’s not surprising that iPhone music production is less popular round here.
I’m no spring chicken myself but can cope pretty well with small interfaces like ButterSynth on iPhone.
Yep, definitely true that this forum is not representative.
There's iPhones and there's iPhones going from 4.7" iPhone SE2/8 all the way to the MAX models at 6.7" and still the 6.7" is no where near as 'big' or 'roomy' as a 7.9" or 8.3" iPad minis and for the price of one 'BIG' iPhone you get 2-3 smaller iPads.
If a developer is to add iPhone support they'd have to cover all current screen-sizes which can be a total pita.
And there's no guarantee that a fully vectored UI automagically adapts to all screen sizes retaining usability.
Maybe iPhones will become more 'attractive' as music making devices when Apple adds 'stage manager' and external screen support to them, something similar to DEX on Samsung phones...
So in theory, when an iPhone 'docked' with pointing device and keyboard it will be running iPadOS instead of iPhoneOS and when trying to launch iPadOS apps in the iPhone it would just prompt the user to hook up an external monitor, pointing device and keyboard...
Maybe in 5-6 years we'll be able to dock our 'smart devices' to any screen and run full macOS on them, who knows...
Is it possibe to cross modulate using CV between the VST3 versions and the IOS versions? (I have Moogerfooger on IOS and Mariana on OSX)
I haven't been able to figure out how to do this in AUM, but hoping there is a way.
I would have thought not, but I’d be happy to be proved wrong. There’d have to be a MIDI stage in between the two, I think, and I’m not sure the MFs can output the CV signal as MIDI CC.
Certainly incoming MIDI CC can get smoothed out by the MFs as long as you modulate the CV attenuverters rather than the targets directly, but I think there are missing bits of the chain between two devices.
Thanks, I asked Moog directly about this so hoping to hear something.
Marianna loses the connection to my midi keyboard if I play too fast (not extremely fast) and when I have changed presets 3 or 4 times. I have tried with different buffers.
My business makes websites so I totally
agree with how annoying it is to support different screen sizes.
I’m not interested in docking my iPhone. I’ve made some of my best music on a 6 hour flight, on the train, sat waiting for my kids to go to sleep, on my lunch break in a coffee shop etc. Best thing about your phone is that it’s always with you and you never know when inspiration hits 😉
I am still on an iPad Air 3, guess I should wait with a purchase until I get a more recent iPad.
I am just jamming in AUM most of the time.
Has anyone any experience with an Air3?
Best to email Moog with details
I hate to beat a dead horse, even though there’s no law against it, and I hate hijacking the thread on Mariana (love the sounds!), but to return to the iPhone question: not every app needs to be on the iPhone and I think devs should be able to choose their strategy. However, my workflow is starting a project on iPhone, even just taking advantage of the short snippets of time throughout the day, then transfer to iPad for further development. On the iPhone, I’m mentally free of the “pressure” to complete a project, so I can explore sounds and noodle freely. Then when I sit at the iPad I’m not staring into a “blank page” with writer’s block. I have small snippets (sometimes nearly complete songs) to develop. Of course using NS2 makes this super simple for me. I’d like to have all synth apps on iPhone, but I don’t need it. I think Mariana on my iPhone would be way too CPU intensive. I don’t have any idea of the differences between my iPhone 8+ & my iPad Pro 2018, but I’m assuming that to make an app like Mariana work on older iPhones, it needs to have some skillfully efficient coding.
This thread has me reminiscing about The Early Years: https://dai.ly/x6d0ak
Way back when I was running Beatmaker 1 on my iPod Touch:)
The other Moog apps run on iPhone but I get your point. I’m pretty spoilt with my 15 pro max.
Some apps with simplistic guis make sense for an iphone version, but I can understand why they don't want to support Mariana on iphone which has a quite complex gui and would generate lots of extra support problems etc.