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
I'm still waiting for the day when Gadget gets a proper 'Time Line' for both Audio and Midi. I do get the some people love the 'scene based stuff' but then we should at least we should have tools to 'split & merge' scenes and do selective copy & paste from one scene or gadget to another scene or gadget...
Cubasis is what it is but it has come a long way from the initial release but still missing things that make me go WTF?(Like where are the triplet grid-lines? My 'logic' says that if there's a quantise value present there should also be grind-lines for that quantise value).
I could go on all day questioning the decision making logic the Cubasis developer team-leader has regarding features as it's far from logical. Sure I do get it's a small team but still...
I can wait with the grid-lines if the current top-priority is on fixing the timing issues
@espiegel123 , you are having a similar problem! Have you reported it? Thanks.
@MobileMusic, do you have any insight as to what might be causing this?
Try playing with settings under Setup > Mixdown / Share
@LinearLineman : I ran into an issue freezing a LayR track . The LayR developer mentioned that he was in communication with Steinberg about problems freezing LayR. I did not report that particular issue since the dev was actively communicating with them about that issue. Generally, I try to report all problems I run into to devs directly--as that is how things are most likely to get on their radar. Even if devs sometimes visit this forum, it is best to report issues directly. I am a dev for a different platform and sometimes there are bugs we would have addressed if people had reported them . But either we didn't know about them because people didn't report them or we didn't realize how an issue was affecting people. Individuals often assume devs must know about issues that are causing them problems and so don't report them. That can leave devs unaware of the problem or the significance.
The LayR developer mentioned that in the LayR case, it was related to Cubasis using a small memory buffer when freezing tracks which resulted in failed freezing of some LayR tracks.
I ended exporting the MIDI for that project and importing into Auria which was able to freeze it fine.
@MobileMusic , I have used the real time adjustment in settings for mixdowns. What is the difference between that and the Audio Unit compatibility setting below it, please?
The first says for inaccurate, the lower for plug in failure.
Cubasis manual is not updated with Audio Unit Mixdown Compatibility Mode setting yet ( @Lars ? ):
https://www.steinberg.net/fileadmin/files/PRODUCTS/Apps/Cubasis/Cubasis_Help/SETUP.html
It was added in v2.4:
Optional AU mixdown compatibility mode added to setup, for AU plug-ins that return noise or silence on export.
Here is what Lars said about it before:
Please go to Setup/Mixdown / Share and enable "Audio Unit Mixdown Compatibility Mode", which has been added for instruments that consume massive CPU. Make sure to deactivate the option again, when not required.
https://forum.audiob.us/discussion/25356/solved-model-d-issue-cubasis-2-4
Also see:
https://forum.audiob.us/discussion/27114/cubasis-mixdown-issue
https://forum.audiob.us/discussion/25464/cubasis-is-it-just-me
https://forum.audiob.us/discussion/26488/cubasis-massive-problems-with-freezing-tracks
https://forum.audiob.us/discussion/25904/poseidon-auv3-update
@JenaMu6 I just scanned this thread, and I really think the problem is with the latency settings. It sounds as if you think that lower latency is easier on the CPU. It’s the opposite. The higher the latency, the less CPU related crackles you will have. If you haven’t already, then you may want to try increasing the latency to medium or high to see if that helps.
If you already tried ... then nvm.
Which Apps have this behavior? I'll bet it's iSymphonic. They seem to push the edge of what can be called an AUv3 App and not work well. Since you're using MIDI as one stop before Audio I would look into playing these Phat sounding Apps directly into Cubasis as Audio. I think AUM channels or maybe AudioBus3 can do that. Maybe someone will know and I'll give it some testing with iSymphonic.
Being totally honest... It's not just Cubasis. All iOS DAWs leave much to be desired. Once upon a time I had a fantasy of doing most of my work on the ipad, but the raw horsepower is just not there when it comes to a DAWs. Individual apps are great (incredible even!), but a "workspace" that can handle what I'm doing still doesn't exist.
It's not really the DAW's fault. It's heat.
I think we need Desktop Phones with 8.5" x 11.5" video displays
with a landline CAT-5 internet connection. Then they could run really hot and give us 16GB RAM and 4-8 smokin' cores that don't throttle back to avoid setting on fire in our pockets. "And it's retro"... maybe put a handset with a curly cord on it. Then IOS could be a killer 'cause it could track:
Does heat exterminate all bugs? Probably not. But there would be more stuff to buy or covet.
2gb ram isn't much really and does that include the OS? I don't know. CPU intensive synths with or without Effects just bounce to an audio track and then reuse or remove track to free up CPU. You are not going to score an orchestra say with a lot of instrumentation. A song? You can do that. Many do. Lots of people use Cubasis. The best way to go about it is finding out how they do it? What synths they use. How many instruments they can load? Their tips and tricks. It will cause you less frustration that way.
I come from computer pc/mac - I have a surfacebook2 and obviously the ipads and you just feel your way around but be realistic. Audio tracks aren't a problem. If I create 10 in cubasis, they should play back fine and be no issue. So perhaps there is something you can do to fix it. It just depends. We all produce differently and so never have expectations other then an IPAD won't be able to compete with a proper computer certainly with more then 2gb ram and work your way from there.
The more that I let my iOS environment be its own thing, the happier I am. I think of my iOS setup as being a different beast from my desktop setup. I think one can free oneself from a lot of frustration by not thinking of one's tablet/phone setup as a mini-desktop environment. While there are moments where I might wish I had this or that capability of a desktop environment, I have far more moments when I think "wow, this is so liberating and engaging in a different way" and I am backing to doing cool stuff that I wouldn't do otherwise. And, I'll use the desktop DAW when I get to that point in a track.
iOS and its apps available today are not really 21st century tech.
Just have a look on the MacOS and Windows ecosystem, I can hardly imagine anything not possible with all the software available there today.
Yes and the apps cost about ten times as much
I use workarounds. For instance, LumaFusion currently has only 3 video tracks. To get the 4th track, I export 2 tracks into a video and use that video on a track that gives 2+2 = 4 tracks of video.
Hi JenaMu6,
So far, we are not aware of stability issues, and you should not experience anything like this, using Cubasis on its own. However, using third party instrument or effect apps - depending on the apps - can lead to issues often or mostly unrelated to Cubasis.
To have a look at the issue, please provide us with a proper bug report including all detailed steps, as described here:
https://www.steinberg.net/forums/viewtopic.php?f=183&t=105096
Additionally, it might be helpful to have the project to reproduce the issue, plus a short video that visualises the problem.
Please feel free to upload these information via WeTransfer, DropBox or similar, and let me have the download link via private message.
Thanks for your support!
Best,
Lars