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
this is the same thing I get on my iPad 3 and iPad 4...
Yes yes yes. I have an iPad 2 and it's bad enough that Cubasis is almost useless to me.
That's nasty! :-) I've never even dreamed of jumping around like that in Cubasis on my iPad 2. I'm guessing from the posts above that it was possible to do this w/out problems until recently.
When switching/auditioning synths/apps via IAA in Cubasis, I always stop playback in Cubasis, "release" the synth/app by selecting No Instrument, kill the IAA app, then select a new synth/app. Whew... Tedious, but I'm used to it and can do it very quickly (probably 10-15 seconds). I pretty much never get any of the playback/audio problems that you posted in the vid above.
I hope that there will be an update to improve this soon.
@dj8 good point.......Just tried from launch....without opening any IAA apps whilst playing. Check this vid it glitches out at about 1:30 with I would say normal use....
@DaveMagoo, yeah, that's no good at all. Did you mention above which iPad you're using. It seems a lot of people are having problems w/ the iPad 3?
There are a lot of reports about glitching sound on the Cubasis forum since IOS 7. And I mentioned it too, re: demo playback in a different AB thread.
But, I don't have this problem... So far, I've created songs in Cubasis w 16-20 tracks (ranging from very short to about 4 1/2 mins, and no playback problems. I do mute unused sections and freeze MIDI parts when I'm not making edits to them, if I start having any playback problems.
Is this a new problem for you in Cubasis?
I usually bounce all my parts to audio so to avoid this problem. However, on my iPad 2, 64gb, bought December 2011, running iOS 7, it seems Cubasis can't play more than 5 audiotracks at a time without crashing. They aren't effects-heavy (usually just a studio EQ to roll off the low-end in non-bass instruments, and using the reverb send effect for some sheen), and it was traced to an audio latency problem. The solution? Open Cubasis within AudioBus (which is what I usually do at any rate). It still acts confused when I try to play more than 5 tracks, but at least it doesn't crash.
@dj8 I'm using Ipad air and yeah it's a relatively new problem.
It probably started after 1.7 if I remember right but I couldn't say for sure.
It's a shame as I just started using it again after the dreaded undo bug ready for the automation update.
Will have to see if its certain apps, setups or combinations that cause it to glitch.
Hopefully the Steinberg team are on it, will have to raise it with their customer services.
Do you use IAA without glitches ?
@jwmmakerofmusic will try opening in Audiobus @512 and see what happens....
Hmm, I tried to recreate. It look like the 'action' you guys take to cause glitch is selecting an 'unopened' IAA synth during playback?
@DaveMagoo at 1:30 it looks like you are selecting a synth off screen or did you not do anything except pull up the instrument panel?
I can open 5 diff IAA synths with a loop playing, I get minimal 1 second of glitch when the synth opens, then it plays OK. iPad Mini Ret 64Gb. Synths used Alchemy (most twitchy), iMini, Arctic Prosynth, iSEM, Addictive
I must admit I've never been selecting IAA synths during playback before... I've always stopped first. 1.7 is loads more buggy, but I don't seem to be suffering from this one (famous last words!
)
I use IAA. RIght after watching your video, @DaveMaggo, I tried out Cubasis w/ Addictive, Arctic, ISEM, Cube, Nanologue, and SampleTank and got the results I posted above. (In general, I most often work w Nave, SampleTank, and I've been using Galileo a lot lately, all w/ no problems.)
I would guess that bumping to 512 will improve things...
But, again, I really don't try to switch while a song is playing or keep multiple synths open in the background.
Definitely worth sending a bug report over to Steinberg.
@skoptic I selected a midi track by the icon which brings up the instrument panel which had no instrument selected it was playing some midi into bs-16i....odd....maybe I'll try without bs-16i....
@dj8 said:
Did you mean there was no problems with the results with that setup ?
Even at 512 I'm getting a lot of timing issues - recorded on time and then the track goes out of sync on playback, like bits are chopped out if it.
@PhilW said:
Me too (iPad2 32GB iOS7)
Yes, @DaveMagoo, good results w/ Addictive, Arctic, ISEM, Cube, Nanologue, Sampletank today (and previously w/ Nave and Galileo). As long as I use one at a time, etc.. as mentioned above. Will try out a bunch more synths… Hmm, I hope my iPad 2 doesn't read this thread :-)
I do keep a lot of free space on my iPad (3-4 gb on my 32 gb iPad 2). This came up on a couple of earlier threads… I try to stick to the old 10% rule. It's probably more relevant to mechanical drives, I would guess, but it does seem to help things out. Others would know a lot better about this than me.
I have tried it in audiobus at 512. Still very iffy. Gutted because I resisted buying it as I already have auria and beatmaker but got it on sale. Hope they sort it.
Using a 16 bar piano part (3-4 note chords every 2 bars) & 78 BPM, I tried a couple of things.
First I tried to see how many IAA MIDI parts could play the piano part on my iPad 2. The answer was only 1. Unusable due to glitching when I attempted to add the 2nd IAA instrument.
Second, I was curious to see how many audio parts I could generate and run simultaneously using freeze on an original IAA track playing the 16 bar piano part.
I was able to add, w/ no glitches playback:
ISEM
Nave
ZMors
Magellan
Galileo
Sampletank
Nanolougue
Arctic
That's 9 synth tracks (audio from freezes), including the original track running in IAA. After that I start getting glitches in the sound.
Interestingly, Addictive, Cube, & NLog generated silent freeze tracks (even after restarting Cubasis). So did Nave the first time, but worked after a restart. Bismark didn't seem to work at all.
When I really work w/ Cubasis, I usually have much shorter clips that I work w/, which I think has allowed for the # of tracks to go up further than this...
Updates for the Virsyn stuff is in the works.At least the developer knows about this bug and fixed it recently in Audioverb.
@dj8 What are your glitch results when trying with Audiobus? This would help isolate the issue to the IAA component functionality within Cubasis...
Ahhh, I was afraid someone would ask that question :-) @Audiojunkie. I'll try it out again w/ Audiobus. Something about curiosity and the cat...
Empty freeze with cube. Alchemy, Nave, and iSEM work fine.
Just replaced the IAA tracks with Audiobus for bs-16i/Alchemy and the project works fine !
Although Alchemy is missing completely from the Audiobus side panel ???? Works with the track icon switch though in Cubasis.
I also noticed that when I added and removed Addictive synth as an IAA node to the project to see what would happen, all the midi setup changed. All tracks sending midi data to bs-16i changed to Arctic pro which Is connected via Audiobus.
So the midi thing is clearly a bug in Cubasis triggered by IAA, and the audio phasing glitch is a bug in the same setup.
Went back into Cubasis to see how many audio tracks I could generate and run simultaneously from a 16 bar midi piano part.
I was able to run 9 synth audio tracks and record a 10th synth from the midi track. (I soloed the tracks during recording, but I occasionally re-tried the same track recording w/ all tracks playing and performance was about the same.)
When I got to the 10th audio track, there was pretty heavy glitching during recording and glitches playback on all soloed parts.
I suspect that BM2 can handle this sort of thing a little better (maybe the streaming from disk is handled better)? I'll probably try it in BM2 at some point just out of curiosity. But, either way, BM2's file bloat makes Cubasis the much better choice, IMO. Plus, I'm finding Cubasis to be a much more efficient, productive workflow. Hope they get automation up and running soon.
I'm not a fan of bouncing tracks, at all. I find it tedious and view it as destructive editing… Hoping I can run a lot more tracks simultaneously w/ a new iPad. But, for now, can get by one way or another, as needed.
Don't know if this is helpful, but I was glad to find out a little more about some of the limitations that I might run into w/ current setup.
I have some clicks from a audio loop to another, at this point for me is unusable![:( :(](https://forum.loopypro.com/resources/emoji/frowning.png)
I too get clicks between Audio clips on playback but usually they disappear after mixdown. (Ipad2 32gb)
It seems to me cubasis doesn't work properly on ipad2. Steinberg should mention this on the appstore. Aside from the other known bugs I hope steinberg fixes in 1.8
It's a great DAW after all.
@PhilW said:
That is my BIGGEST complain since months but it seems they are not having this issue or they don't know how to fix it.They just don't reply to most issues reported on their forum.That's most annoying.Support gets more worse the bigger a company is.Sigh.
I find that on the rare occasions that Cubasis skips or clicks on my iPad 2, it's playback only, not in the recorded audio, as it never repeats the error in the same place if I replay the same section.
Hopefully Steinberg will be back from their Hols next week to review and update their forum with some great news![:) :)](https://forum.loopypro.com/resources/emoji/smile.png)
Problem is,people are crying if they just release bugfixes (i'm a bit guilty as well)without introducing new features.But with every new feature the bugcount gets higher and higher.Cubasis WAS a really reliable app the time after release (ok,it was quite"empty"as well).It even run on iPad2 without hickups.Even with AB i can't remember having much trouble back in the days.They should just release the automation finally (THIS will be a new bugfest,i'm sure)and then go just for bugfixes a couple of updates.
Ha I must say I love Cubasis because of the workflow and the concept.
It's had its moments, the undo bug the most memorable, I am confident though that they will address all the issues eventually.
We could expect the next update to be realeased in mid February if they follow the regular updates of recent months, plenty of time to add in some bug fixes![;) ;)](https://forum.loopypro.com/resources/emoji/wink.png)