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
There are definitely some bugs but the first two updates killed the critical ones for me. And I’ve yet to use an iOS DAW that didn’t crash or act funky.
They do not scale on my iPhone 11 for sure. Haven’t tried on my iPad yet.
Didn’t realize you could draw in AUv3 automation. That’s a win. I don’t think you can record AUv3 MIDI which is critical to my use of Ruismaker Noir and EG Pulse.
I may give it another try soon though. Perhaps when I get my new iPad.
I believe they are addressing recording AUv3 MIDI
For sure. We all put up with something but this for me is just too constantly annoying..
Yeah I get that that can be annoying. I consider that to be a trade-off with using a touchscreen. I always expect touch screen stuff to be tricky to navigate. I also have an issue with a specific in-app effect not keeping automation during the mixdown.
But I’ll take that over having to manually draw in drum notes and AU automation by hand.
Cubasis 2 is rock solid for me with this, as is NS2, BM3, Zenbeats, Gadget etc hell all of them always worked fine on all five ipads I have owned. Cubasis 3 is the only app I have used that is flakey like this... nothing to do with the nature of touchscreen per se.
I saw this was a feb. 2020 video, is it still doing this for you? (I couldn’t replicate it as of current iOS and Cubby build, Pro 10.5)
Hey @anickt I still have not succeeded in getting Zenbeats to change time sig with in a clip on the timeline, or between clips in clip launch view. The pull down menu just shows whatever the last entry was, and when I change it for a different clip in clip view, or at a different point where the play head is in timeline view, all the other clips or positions with in that clip show the same time sig in the pull down menu.
or elsewhere. I’m still thinking this is my own error, please advise
Change the time signature then create a new clip. The new clip will have the new time signature.
Yah it still does it. Maybe there are some slight hardware differences that happened on the same generation.
Got it! Just took you tellin me a few times...
As many thanks as times you told me, +1
No prob! Glad to help
Please do sneak it in
Same.
Tried Zenbeats again thanks to this thread. On a 2018 iPad Pro, when I tap the button to open the sidebar, the panel stutters across the screen. It’s like running a Java app on the Mac.
Back to Ableton and Logic I guess.
It sucks for those people but why you blaming Roland and not the Stagelight dev for selling out and leaving his paying customer out in the cold? Roland probably have their reason for not doing business in certain country.
Seem like a silly excuse to not use it. Specially since they are giving it away for free.
That is odd and I would report it as a bug. You can do that right from the help support with in the app. They have been very responsive. I know 100’s of folks that have been running zenbeats with no issues and there is plenty of diversity of hardware they are running it on. Yours sounds odd and I am sure they would want to assist in fixing it.
Cheers
This whole thing about the dev selling out.... just like everything we don’t know the whole story on this.
I can’t use it, because it’s not available in my country.
@jolico that’s too bad. What country do you live in? Are there any other apps that you find that problem with?
No, just this one.
They also took the original version “Stagelight” off the AppStore, so I can’t even use that anymore.
Good point but why be mad at Roland and refuse to use it?
My guess is that the costs and effort involved in keeping a DAW updated and running smoothly are just too much for a small team, much less a one person team. Selling an app to a larger company is not likely an easy choice but it sounds like the kind of choice that would allow the app to continue on with more resources and growth potential. Licensing agreements are likely the reason why the old stagelight app couldnt stay online, and perhaps some of the content in the new app is not authorized for use in certain markets, so they couldnt release it in every market yet.
There are a lot of things that go on behind the scenes, but if someone went as far as making a DAW that works well to the point where we fall in love with it, I doubt their goal was to sell it short and leave people hanging. I honestly believe the devs mean to do well.
Nanostudio 2 is my "so close to perfect for my needs" DAW. if only it had audio tracks...and I wish they came "on time" but its a massive task, and the fact nanostudio is as great as it is already is such an incredible feat. If it never gets audio tracks, its still a fantastic midi DAW, and I'll just have to downgrade my expectations to it being more like Xequence, than Cubasis. Still, Obsidian and Slate are insanely useful. I've loaded in like 40GBs of one hits, and resampled so many desktop synths into Obsidian, and it still runs smooth with low CPU usage. I got what I paid for already. The rest is just going to be extra.
Nm
Or have an autosave that saves as "autosave xx-xx-2020" along with the main project that you have to manually save
I guess. People seem to generally hate this in BM3. But maybe it’s because it doesn’t work well in some way. I never really paid much attention as I manage my saves all the time without even really thinking about it,
The fact that Nanostudio 2 and Cubasis 3 has no mappable transport controls makes me rise an eyebrow. And you say this was requested from Steinberg 7 years ago ?! And still is not done...
If a 1 man dev in person of Jim Pavlov can implement it into his Groove Rider, why the bigger players can not.
What is the problem? Can somebody explain this. ( @LFS )
I'm just gonna throw in that when I need simultaneous time signature and tempo changes and very complex arrangements, I have had luck creating a folder in NS2 with multiple saves files. In each one I set up the tempo,time signature, and then mixdown, usually in long chunks (like 16-32 bars or even odd bars like 25 if the track calls for it). Then I plop them in audio evolution mobile, which was a very inexpensive option and arrange from there. I line up the ends of the audio track, and then I can have as many time signature and tempo changes. The only downside is the need for two apps, and mixing down on monitoring headphones so the audio is balanced. This can be done with cubasis also.
The only time this doesn't work is for dynamic tempo changes. If I really wanted to do that, I could probably record ns2 into aem as an iaa, and adjust the tempo manually live. Not sure if there's tempo automation in ns2.
Nowadays I never use daw enabled time signatures. I just count it out. My friend told me a trick he learned, recite apples and pineapples. "apple apple pineapple" for example gets you 7/8 or something like that... Works unless you're doing dream theater stuff.
This also gets around my personal biggest ns2 (and gadget) limitation: no program change. If anybody knows how to change presets via midi or the timeline or program change within ns2 or gadget, I will be forever grateful.
Not gonna say much, but we might be in for some good news in regards to Cubasis 3 in the next few months. Just hold on guys.🤘🏾
Hi @israelite,
Thanks for your message.
Controller support is on our list, highly prioritised.
Best,
Lars
There is a tempo track in NS2.
I actually love that feature in BM3, open previous project x, play it a bit, do some changes for listenin sake, but not permenant...so now you close/crash/end BM3 prematurely...did my project save? did it save all thos changes in-between actual. saves? yes and yes, main og project saved as project x while "autosave" saved a new copies of that project as "project x autosave timestamp" ect after every change and before the crash. now i can either start back at the og project or continue where i was before the crash. i love it, i DO NOT love the way Cubasis 3. saves, it automatically overwrites everything as it autosaves
What about Nanostudio audio tracks ? Any news on that ?