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
It sure runs more smoothly on iPad v3 than BM2 does!
Tried it with Audiobus for the first time today, and gotta love how seamless Steinberg done it all (with how new tracks and names are made whenever you change something around on the other end in Audiobus). Really nice!
BUT another crash, on a one track 15 sec audio file recorded. I don't know what's up with all the crashing if it runs rock solid on other people's iPad 2s. I always make sure that nothing else is running, restarting etc before starting up any DAW (like Cubasis). We're all on the same closed system, I'm on iOS 6.1.3 which is the latest for iPad 2. I've tried reinstalling Cubasis a few times too. The first couple of crashes I was just browsing through the presets and midi loops it comes with. Today it was Audiobus w. Figure and Cubasis doing a short recording. Did some trimming on the audio file and poff I was back at the iOS homescreen. Obviously no jailbreak, and I don't have anything running on the iPad (like fetching mails, Bluetooth, very little in the notification area etc). The only thing that differs in this closed system (closed hardware, closed operating system) that I can think of is the "international" setting, which is some cases can cause various problems but not like this where it seems that it is iOS closing Cubasis down due to RAM.
Anyway, lets see what the next Cubasis update does (or if anyone have any suggestions as to what could cause it to be so unstable).
How much space do you have available? You might want to look at a system utility that will show RAM usage.
2gb at the moment. The RAM is the same as on any other iPad 2 running iOS 6.1.3. But yea I do keep an eye on it, and I actually have an old app that's been pulled by Apple that will close a lot of things down (reason it got pulled), and in turn making well over 300mb RAM available. But rarely use it, since I shutting down various iOS services could possibly make things unstable in turn.
I am on a 16gb device, and I know filling up the disk is kinda the same as a fragmented harddrive. But keeping 2 GB available is enough on a 14.8gb device.
@ Those experiencing crashes: I use an iPad too, and haven't had any crashes. I've been stress testing things to see how far I can push things before a crash. I have a 30 second test project that has 23 tracks (including effects) and it lets me run Audiobus Guitarism, and Jamup XT Pro all at the same time without problems. I recognize that a 30 second project isn't very large, but I intend to keep pushing the limits to see how far I can go. The polyphony and CPU usage are fine. I suspect a couple of things that are allowing me to get away with this: It is essential that good RAM management is used, since it is in such short supply on the iPad 2, and I suspect that this is te chief reason for the crashes people see. I either freeze or render everything to audio. Furthermore, rather than rendering out entire tracks, I reuse parts to save RAM. For example, in the string part of a verse that is the same for each verse, I just use a single clip of the verse part for that instrument, and repeat the same clip as needed for each verse. I do the same for the chorus, bridge, etc. The result is that I end up using ram for 3-5 audio clips that use a fraction of the ram an entire track uses. It also saves disk space and polyphony too.
The other thing I do is try to use Cubasis' built-in instruments as much as possible, because I have the ability to freeze the instrument and all of the tracks, which really saves on the resources. Because of my testing, I have become convinced that I could successfully do a full production from an iPad2! There are other resource-saving things that I do too, but these are probably the biggest things.
Now, I haven't run into any bugs, but I'm aware from researching the Cubasis forums heavily that a couple of known bugs exist that have already been fixed and will be in the 1.6 update.
I guess what I'm trying to say, is that everyone has different musical goals, and methods, and apps and such, and maybe examining your own process could shed some light on maybe why you are experiencing crashes when others aren't.
Also, don't forget that the next version, 1.6, will make things even more resource efficient! :-)
Also, when you are ready to bounce down, you can render out all of your tracks and import them into Auria to benefit from Auria's superior audio track automation and effects! :-)
@ChrisG have you hard reset your device recently?
Well it's not a matter of RAM managment in my case. Don't know what is up. Are you all using iOS 6.1.3?
@Mgmg4871 I do that from time to time. But a hard reset could potentially brick a device, very slim chance but it's there (you'd have to reinstall iOS via iTunes). So I try to avoid it. But sure I could give it a go tomorrow and run Cubasis through the same setups I've been doing. Let you know if it works.
I just want to thank all of you for the in depth testing. ..I love this app
Same iOS version here, but I have a 64Gb iPad 2 with 12.7Gb free.
@ChrisG - Yes my 16gb iPad 2 is on 6.1.3. I have 4.6gb available at the moment. My projects don't generally end up being very intense, but I've had an 11 track, five minute song on there with effects on a few tracks, MIDI and audio, Audiobus running with iFretless Bass and Magellan in FX, cutting up and cutting/pasting audio files all over the place. I've also had Glitchbreaks, which seems to push my device a bit, running through Audiobus into the same project. I've had warnings from Glitchbreaks that system resources were running low, but Cubasis has remained rock solid at all times. I would have been running on around 2gb during this project.
@AfxTwn :
If we're talking about the, sample based, sounds, Cubasis falls flat compared to the excellent pianos, organs, strings, guitars etc in GarageBand. Cubasis Halion based rompler have that kinda cheesy general midi module sound to it, the drums it offers are on the other hand better, fresh and more versatile then the rest of the rompler sounds. And it does have the Microlouge synth, haven't tried that one much yet. But only talking internal sounds, GarageBand is way ahead.
But Cubasis has a proper mixer, with a 4 band parametric EQ on each channel. Each channel have 3 additional slots for insert effects, like compressor, limiter and so on. It also have a couple of send effects slots. And master effects plus a brick wall limiter to top it of. And since it does midi and audio in and out at the same time you're not tied to use it's internal instruments, the Audiobus integration is super smooth.
In the end Cubasis offers up a lot more tools for sculpting your mix, and it's really well integrated with the rest of the iOS music app "ecosystem" via Audiobus and midi, unlike GarageBand, which definitely isn't. Personally I'd go with a DAW that has a proper mixer with proper mixing tools, which would be Cubasis in this case.
@mgmg4871 A hard reset seems to have done it. No crashes so far, haven't exactly stress tested it but managed to make two small projects so far. So thanks
@ChrisG Sounds like you're slowly becoming a Cubasis fan. Wait till update when audio engine is optimized to run 2.5x more efficient. Aso the freeze function is really helpful. Are you talking about te AM drums? They are much better than the original. They were added in last update. The Micrologue synth is amazing. Glad reset helped. I recently factory reset mine, after 2 years, and got a surprising boost.
I love Cubasis. However, it needs sample assignable pads and keys for it to replace BM2 as my main daw. I have a feeling I will be waiting for awhile which is torture because I really do love everything about it. Just that one missing function is holding me back.
@Context There's some unknowns in this upcoming update. You might get what you want.
@mgmg4871 Hoping so, but I won't be surprised if it's not in. Either way the support that Steinberg has been giving this app has been phenomenal so I know it's just a matter of time.
I broke out Cubasis for like the fourth time last night and suddenly I love it. I think I've just finally accepted that its not going to do a few things as well as BM2, but for the most part its rockin' good. I find that I can really fly around pretty quickly with ideas in it. There's a ton to be said for that. Still can't really sync up clock correctly, but I'm sure they'll lock that down eventually. Anyway, for all my railing on Cubasis, I'm finally in there and loving it.
@ChrisG Glad to hear that you got things sorted out! :-)
@mgmg4871 Remember, what they said was the efficiency was going to be up to 2.5x in certain cases. I would imagine that a speed increase of 1.5x- 2x would be closer to the average use efficiency that we are likely to see. (Personally, I suspect that the biggest increases in speed will be for those who stay with 16/44.1 rather than those who go 24/96).
@Context Steinberg has made several comments about how they haven't charged anything for any of the 1.x updates. The next update will be 1.6. I would suspect, that if things go as they have been, with 1.x version updates, we may see two to four updates more before Steinberg will want to charge again--for a significantly enhanced version 2. It's been said that they want to get automation to us before the end of the year, so I suspect that we will be needing to pay again sometime next year. This is all speculation, of course, but even if we have to pay again, it will still be cheaper than the yearly updates that Cakewalk charges every year for their Sonar product. :-) I only want to point this out, so people realize that the continued free updates aren't likely to last forever. But I still feel the product is well worth it! :-)
Good choice. It's only going to get better.
@Audiojunkie
Interesting thought, but I don't believe separate paid updates is the way things are going for iOS.
Almost none of the major devs have taken this route so far, Apple included. The Appstore just isn't set up properly for this model, as there is no mechanism for allowing previous customers discounts on updates. In the music space, Intua is the only major example I can think of at the moment (charging for the Beatmaker 2 update), and as I recall they took quite a bit of flak for that one.
I think the way the ecosystem is setup, it makes much more sense for developers to add in-app purchases instead as a way to subsidize further development. This way the user base stays together on the same version of the app (don't forget that supporting multiple apps can be a killer for a small team), and people who want to spend more can maintain their investment in add-ons. For music apps (and especially DAWs) this is a no-brainer with things like add-on effects, instruments, 'pro' features etc.
If people knew, for example, that Wavemachine Labs were starting work on a new paid version of Auria, aside from being pissed off how many people would still be buying those pricey plugs? The revenue (and customer faith) lost there would simply offset any extra they would potentially make from the new app. (Don't forget that having someone locked into your ecosystem due to IAP is also a benefit, if you are forcing them to re-buy from scratch what's to stop them from moving to a competing product at that point?)
Certainly, if you are working on an entirely new concept it deserves another app (i.e. whatever the evolution of Nanostudio turns out to be), but from many perspectives it simply makes more sense for x.0 updates to be free, (support, maintenance, ranking charts, marketing, customer loyalty, etc.)
@busker You have some interesting and valid arguments. I can absolutely see where Auria wouldn't be able to make the change. I really do hope your are right with Cubasis! It does seem strange the way the company has been wording things regarding updates on their forums. Comments like, "We're not charging anyone for 1.x updates," and such... Nevertheless, I will be happy if I am off the mark in my assessments. :-) Edit: I don't want anyone to misconstrue my comments and think I am in any way negative toward Steinberg, because I'm not. I'm very happy with the product that has been developing monthly into one of the top DAWs on the platform. :-)
I hadn't considered that about auria: if they ever wanted to charge for a new Auria 2 app in the future every user would lose all of their Auria IAPs since they're not transferable between apps. Some people have spent hundreds.
@boone51 You floozy! Lol
Lol.
@PaulB, I know. I totally am. I'm not proud. It's just a fact.
So I bought Cubasis
Haven't had time to really get into it although it's very user friendly and easy to figure out. Played with a bit on my lunch break today and laid down a simply synth arp (AB'd in from Yamaha app), MIDI drum beat in Cubasis, and a lead synth. Once I figured out some little quirks it went really well.
Performance isn't as good as I was hoping on my iPad Mini... Gets stuttery kinda quick if there's a lot going on. Hopefully the performance improvements in the next update help.
Finally, the only big annoyance I've noticed so far is the zoom and scroll implementation. I am very used to BM2's way of pinch to zoom and scroll all 4 directions (Up/Down/Left/Right) all in the same motion. Significantly, pinch zooming in BM2 zooms on the specific area your fingers were at... whereas in Cubasis, it (wrongly) zooms to the center of the current view, and then you have to scroll left/right a LOT to get to the right spot. It's SUUUUPER annoying. To say nothing of the loss of BM2's (and NS) arrow/slider buttons... I'm gonna miss those
@jesse_ohio, I've deleted Cubasis off my iPad at least three times now. I am really addicted to BM2, but loved the promise of Cubasis each time I tried it. The midi editor is much better in BM2 mostly because of the issues you mentioned. Still, its a badass little app in its own. I'm looking forward to another session tonight.