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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Cubasis 3: "Upgrade"/Re-purchase)

Who has done the iPhone version purchase of Cubasis? I personally didn't because I already had the original and didn't see spending $50 for an iPhone version that I wouldn't use any midi gear/or complex features on my phone with. I figured without LINK and that I have so many other linear arranging type apps, I didn't see the value in rebuying this version.

Wondering how that is working for you?

What do you use it for?

Do projects easily port over to the iPad version?

Any other comments or relevant information about it?

Comments

  • I have and use it on my phone. Latest update fixed my problems with it. I’ve ported down to my phone from the iPad. It worked just fine. Haven’t tried the other direction but I would think it’s just as easy and successful as long as you have the same apps on both devices.

    I’m using it to create beats and house music, though I definitely haven’t finished anything yet.

    For my purposes, it’s the most complete and familiar DAW experience on mobile. That is very likely due to Steinberg Sequel being my first DAW. That and I don’t do really complex stuff yet.

    For anything that is more complex, my plan is to use the other apps I have to record in AUM then port that into an audio track in Cubasis.

  • I’ve got CB3 in iPad & iPhone and it’s much better for me. In my case I need more time to compose and record/arrange/try various things and I find I can now work on a track while on my phone in my car on my lunches from work. It’s easy to send projects back and forth and I’m getting a lot more done now. Nice to be able to mix on my car sound system as well as my studio monitors for results that sound good in both places. For me it’s more tools for better use of time.

  • I have no idea why, but it’s unusable for me. Even very simple things need to be frozen out as samples otherwise it crashes so hard it takes the entire iPad out with it. iPad Pro 9.7” with all the storage, your mileage may vary.

  • @drcongo said:
    I have no idea why, but it’s unusable for me. Even very simple things need to be frozen out as samples otherwise it crashes so hard it takes the entire iPad out with it. iPad Pro 9.7” with all the storage, your mileage may vary.

    Hi @drcongo,

    Using Cubasis 3 on its own, this should be not the case.

    Do you use 3rd party instruments or effects plug-ins that might lead to these issues?

    If you agree, please let me have your E-mail via private message, to further exchange about your issues.

    Thanks
    Lars

  • Hi @drcongo again,

    Please do me a favour and follow these steps:

    • In Cubasis: go to Projects/Templates and double tap "New Project"
    • Shut off Cubasis
    • Shut off and restart your iPad
    • Launch Cubasis and work with the app on its own

    Important:
    Please make sure to not load any 3rd party instruments/effect plug-ins.

    Please let me know if the app maintains fully unusable (which should definitely not be the case).

    Thanks,
    Lars

  • @drcongo said:
    I have no idea why, but it’s unusable for me. Even very simple things need to be frozen out as samples otherwise it crashes so hard it takes the entire iPad out with it. iPad Pro 9.7” with all the storage, your mileage may vary.

    Have you tested with the new update? It was pretty unusable before it but it’s working okay now.

  • Yeah, this is after the update. I couldn't get it to do anything at all before.

    @LFS I'll report back in the thread over at your place. The project that I was trying to work on had 3 Classic Machines tracks and two AUv3 instruments (Pure Acid and DRC - both chosen as being among the least resource hungry and rock solid in AUM / Beatmaker 3). DRC was using Blackhole and Pumphouse inserts, but I froze that straight away. Two of my classic machines tracks had to be frozen too, one using UltraTap and the other using Replicant 2. At the point that I gave up, it was just three frozen audio tracks, one Classic Machines track and one Pure Acid track. No effects.

    I'll give your steps above a go and report back on the Steinberg forums, but to be honest, if the thing doesn't work with 3 audio tracks, one Classic Machines and one AUv3 then the thing doesn't work as a DAW. I don't think I have any use for it if it can't use AUv3s.

    Worth noting to others in the thread though that I might be just utterly cursed and Cubasis could be fine for everyone else.

  • @RUST( i )K said:
    Who has done the iPhone version purchase of Cubasis? I personally didn't because I already had the original and didn't see spending $50 for an iPhone version that I wouldn't use any midi gear/or complex features on my phone with. I figured without LINK and that I have so many other linear arranging type apps, I didn't see the value in rebuying this version.

    Wondering how that is working for you?

    What do you use it for?

    Do projects easily port over to the iPad version?

    Any other comments or relevant information about it?

    I might have to retract my earlier statement. After adding in a couple more tracks and an fx app or two, I’m starting to have stability issues in Cubasis 3 that I do not have with Xequence 2 and AUM.

  • Sorry @YourJunk, but I’m also overjoyed to discover that I’m not alone.

  • @drcongo said:
    Sorry @YourJunk, but I’m also overjoyed to discover that I’m not alone.

    Yeah, one Shockwave track, three Ruismaker Noir tracks, and Pumphouse on Shockwave. Four bars, and it either won’t load or the audio distorts. I can get it to play right a third of the time.

    Alas, I may have to resort to Xequence + AUM.

  • FPCFPC
    edited February 2020

    This is deeply worrying.

    I've been holding off 'upgrading' to V3 altogether because a) I'd only had v2 since April and didn't feel I'd had enough experience with it anyway and b) I was getting crashes and, more annoyingly, timing errors on looped sections.

    I was so hopeful that V3 would solve everything from the start so to hear that it's still an unstable environment make me sad.

  • edited February 2020

    Pumphouse on Shockwave seems an absolute guaranteed car crash in Cubasis. As is having a timeline more than about 20 bars long.

    I’m teaching myself to work with AUM and Xequence 2 now. It’s quite an alien workflow for me, but I think this combo is much more worth my time than waiting for Cubasis to get back to its glory days.

    @FPC Cubasis 2 is waaaaaay more stable than 3, especially running on iOS 12.

  • Lol. Pure Acid seems to give me crashes on 2.8.x but, of course, only in conjunction with other stuff so it's really hard to replicate for reporting to Lars.

    Sadly I'm starting to consider my other options. I too was thinking about AUM and Xequence 2 but I'm a traditional DAW guy so just like you this method will take some learning.... Maybe it's time to dust off NS2 - bought and never used!

  • LFSLFS
    edited February 2020

    Hi @YourJunk, Hi @drcongo,

    Thank you for your messages.

    In order to support you, it is mandatory to know about your steps, including the information about all third party apps used in your projects.

    drcongo already reported, that Cubasis 3 runs as expected on its own. So, there might be some 3rd party apps in the game ir other aspects, that leads to creating these issues.

    Once we are able to reproduce the problem, we can either discuss with the involved 3rd parties, or evaluate possible solutions.

    • To allow us to do this, please use the bug reporting form below, and let me know about the exact steps.
    • If possible, break it down to simple steps.
    • In addition, please feel free to share the project with us via Dropbox (download link via private message).1.

    Please note, that doing it this way, helped us to resolve most of the issues included in 3.0.1

    Thank you very much for your help!

    Best wishes,
    Lars

    Bug Reporting Form

    1. Summary/Title
      (Provide a short but descriptive sentence that summaries the issue or feature request)

    2. Description
      (Provide a detailed description and list the step by step process to reproduce the issue to help the team to understand and reproduce the problem)

    3. Expected Results
      (Describe what you expected to see)

    4. Actual Results
      (Describe what you actually saw)

    5. Environment
      (Count the hardware and software including version numbers being used)

Sign In or Register to comment.