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.

For those that upgraded to Cubasis 3 from Cubasis 2. Was it worth it?

24

Comments

  • Thanks folks.

    I’ve just bought CB3. I’ll let you know in a couple of days.

  • edited July 2020

    .

  • Yes and no... it’s getting there... overall, yes For my needs. I love it but miss some of the old features. In certain cases the older version functions better with audiobus and Inter-App. I’m happy.

  • For me, it's an investment in an essential IOS platform.

    Cubasis 2 is frozen.

    Cubasis 3 is getting enhancements and will get updates.

    Buy now or buy later. Maybe wait for a sale.

    But once you buy in you can participate in providing feedback and influence the product
    effectively through the support process.

    It represents a very traditional approach to building music projects. It's also one of
    the very few active products being funded by one of the massive music/business Corporations (Yamaha). The good news is that they seem to respect platform standards and attempt to stay current with trends in IOS music API's (MIDI FX for example) and
    industry standards (MPE).

    I suspect they will continue to drive enhancements that make it more compelling and
    differentiable from competitive offerings.

    It also makes the case that some categories of product require such a huge engineering investment that the price needs to reflect the sunk costs of development. $50 in this case.

    The Fab Filter products adopt a similar pricing strategy with $30 for highly developed FX apps.

    IK Multimedia's B-3X product takes a "synthetic" instrument development into a whole new category of product with the $99 pricing which involves multiple businesses in collaboration (Hammond/Suzuki + IK M).

    I admit it took a gift card for me to see the $50 entry fee as less of a barrier to action
    and a very slow News cycle for IOS releases.

  • edited July 2020

    @McD said:
    For me, it's an investment in an essential IOS platform.

    Cubasis 2 is frozen.

    Cubasis 3 is getting enhancements and will get updates.

    Buy now or buy later. Maybe wait for a sale.

    But once you buy in you can participate in providing feedback and influence the product
    effectively through the support process.

    It represents a very traditional approach to building music projects. It's also one of
    the very few active products being funded by one of the massive music/business Corporations (Yamaha). The good news is that they seem to respect platform standards and attempt to stay current with trends in IOS music API's (MIDI FX for example) and
    industry standards (MPE).

    I suspect they will continue to drive enhancements that make it more compelling and
    differentiable from competitive offerings.

    It also makes the case that some categories of product require such a huge engineering investment that the price needs to reflect the sunk costs of development. $50 in this case.

    The Fab Filter products adopt a similar pricing strategy with $30 for highly developed FX apps.

    IK Multimedia's B-3X product takes a "synthetic" instrument development into a whole new category of product with the $99 pricing which involves multiple businesses in collaboration (Hammond/Suzuki + IK M).

    I admit it took a gift card for me to see the $50 entry fee as less of a barrier to action
    and a very slow News cycle for IOS releases.

    This, also although I have the rest of the iOS DAWs, and currently am trying to master another one, when I had to produce something quickly for a client I unquestioningly reached for Cubasis the First, and now trust Cubasis the Next. It sits in the middle of all of DAWs and feels open and homey, with very smooth implementation of iOS standards mentionEd above (pretty easy to set up an AB sesh, or IAA instruments or AUv3 what have you). I’m also pleased to have it on the phone. It’s smooth for my use and I like it enough to buy in on Android

  • @McD, Hammond B3x is now $129. I didn’t buy it at $79. Not sorry about it.

  • @cyberheater said:
    Thanks folks.

    I’ve just bought CB3. I’ll let you know in a couple of days.

    Another poster abducted by aliens...?

  • It’s informative to read this track through. Things have changed a lot in six months.

  • edited December 2020

    From my short personal experience I tell you this:
    Got CB3 on black Friday sale, enjoyed it and survived it crashing occasionally. Then Steinberg released an update recently and the performance dropped so much (getting crackling sound issues with a clean project and only one AUv3 loaded) I start to regret buying it. And all this on A12 apple chipset.

  • I also feel that CB2 is still a more solid environment, it’s much more responsive when zooming and dragging regions etc. CB3 feels a bit sluggish in comparison to me, on a 2019 iPad Mini A12 chip. A bunch of the behaviors changed as well, no more scrubbing playhead or preview button on EQ, when you split a region on CB2 the next region is selected so you can keep splitting it up - CB3 you have to reselect the region then reselect the scissor tool. Gets tedious.

    Love the feature set of CB3 but CB2 feels better to use somehow, IMHO.

  • @israelite said:
    From my short personal experience I tell you this:
    Got CB3 on black Friday sale, enjoyed it and survived it crashing occasionally. Then Steinberg released an update recently and the performance dropped so much (getting crackling sound issues with a clean project and only one AUv3 loaded) I start to regret buying it. And all this on A12 apple chipset.

    Did you try to set the audio engine latency to off in the setup/audio menu?

  • edited December 2020

    @kdogg said:
    I also feel that CB2 is still a more solid environment, it’s much more responsive when zooming and dragging regions etc. CB3 feels a bit sluggish in comparison to me, on a 2019 iPad Mini A12 chip. A bunch of the behaviors changed as well, no more scrubbing playhead or preview button on EQ, when you split a region on CB2 the next region is selected so you can keep splitting it up - CB3 you have to reselect the region then reselect the scissor tool. Gets tedious.

    Love the feature set of CB3 but CB2 feels better to use somehow, IMHO.

    Yah it is a shame. For arranging, CB2 got really solid. Being able to drag audio clips to the edge of the screen and have the view autoscroll was a must for something like this on touch screen and they nailed it in CB2 but now that behaviour is completely broken in CB3 and it is like Steinberg needs ultra micro level bug reports to fix anything. They claimed to fix this but only did it in one direction. Yes, up, down, and right still need to be fixed, not just left! Sigh/groan.

  • Wow, I was about to get CB3 because of the easier folders, responsive interface, 8 inserts, and subgroups...
    But if it's heavier in CPU with the app itself rather than CB2, what's the point ?... :(

  • @crony said:
    Wow, I was about to get CB3 because of the easier folders, responsive interface, 8 inserts, and subgroups...
    But if it's heavier in CPU with the app itself rather than CB2, what's the point ?... :(

    +1

  • Totally worth it, but must update to 14.3 for AU responsiveness. Just finished a 45:00 project using it.
    Some freezing, no problems.

  • Working great for me. My go to DAW.

  • One of the main reasons I never used CB2 was the lack of folders in media bay. With that fixed I’m giving CB3 more time. So far so good. I find the app stable and like the CB3 interface better than CB2. I’m not pushing it very hard but it’s running fine on an Air 2

  • edited December 2020

    @GLacey said:

    @israelite said:
    From my short personal experience I tell you this:
    Got CB3 on black Friday sale, enjoyed it and survived it crashing occasionally. Then Steinberg released an update recently and the performance dropped so much (getting crackling sound issues with a clean project and only one AUv3 loaded) I start to regret buying it. And all this on A12 apple chipset.

    Did you try to set the audio engine latency to off in the setup/audio menu?

    Was using almost all possible config options. And yes there is a performance difference but to my surprise DSP usage often lowers when loading another AUv3 (!)
    When working in NS2, you just launch it and having fun. When launching CB3 I now wonder
    with what it will surprise me this time.
    Hopefully one or two further updates will make it a comfortable and reliable working environment.

    I am seconding the thoughts about economics. It can be definitely improved.
    Pianoroll is somehow complicated in comparison to NS2 which is smooth and very intuitive.
    When coping midi parts in sequencer they are not pasted behind the copied part but almost randomly (probably depending on play cursor position).
    Why there is no option to automatically quantise freshly recorded part?
    Sometimes humanised beats and melodies are welcome but the fact that to avoid it, user has to manually select a part and press quantisation button every time makes creating process longer than necessary.

    Having some hopes about the future since Steinberg is listening to the users.

  • edited January 2021

    @israelite said:

    @GLacey said:

    @israelite said:
    From my short personal experience I tell you this:
    Got CB3 on black Friday sale, enjoyed it and survived it crashing occasionally. Then Steinberg released an update recently and the performance dropped so much (getting crackling sound issues with a clean project and only one AUv3 loaded) I start to regret buying it. And all this on A12 apple chipset.

    Did you try to set the audio engine latency to off in the setup/audio menu?

    Was using almost all possible config options. And yes there is a performance difference but to my surprise DSP usage often lowers when loading another AUv3 (!)
    When working in NS2, you just launch it and having fun. When launching CB3 I now wonder
    with what it will surprise me this time.
    Hopefully one or two further updates will make it a comfortable and reliable working environment.

    I am seconding the thoughts about economics. It can be definitely improved.
    Pianoroll is somehow complicated in comparison to NS2 which is smooth and very intuitive.
    When coping midi parts in sequencer they are not pasted behind the copied part but almost randomly (probably depending on play cursor position).
    Why there is no option to automatically quantise freshly recorded part?
    Sometimes humanised beats and melodies are welcome but the fact that to avoid it, user has to manually select a part and press quantisation button every time makes creating process longer than necessary.

    Having some hopes about the future since Steinberg is listening to the users.

    Have you tried Auto Quantize and Note Ends under quantize drop down toolbar menu to automatically quantize recorded notes and also note ends? See Help > Project View > Tools > Quantize

    These options are also available in v2

    Aside from immediately tapping Undo after recording, notes cannot be de-quantized later on.

  • CB3 still doesn't do multiple time-signatures/tempos in one tune, right? Until it does there is no point for me to purchase it, as that also is the main reason I couldn't really use CB2 (which I own, including all IAP's) in my actual production. It was forever "it's been added to the feature request list" but never ever materialised. Until I see it in the feature description of CB3 I won't be upgrading. Both Auria Pro and NS2 does have those things though, so I'm not stressing too much about it regarding CB3.

  • I bought CB2 because I thought it would be a ‘real DAW’ experience on iOS but quickly stopped - especially when NS2 came out. I found aspects of the UX very frustrating and hated its look. The development timeline for NS2 is obviously glacial and some of its lacking features drove me finally to get CB3 in the BF sale.

    At first I was pleased but I find it can’t do even simple stuff without crackles on a 10.5 iPad Pro running 13.6.1.

    Yes, I’ve tried the various settings for latency. The only thing I haven’t done is upgrade to 14.3 but I don’t want to do that yet.

    Therefore I am disappointed with CB3 and back on NS2 - and loving it even more this time because it actually works (except where it doesn’t obvs). :smile:

  • @MobileMusic said:

    @israelite said:

    @GLacey said:

    @israelite said:
    From my short personal experience I tell you this:
    Got CB3 on black Friday sale, enjoyed it and survived it crashing occasionally. Then Steinberg released an update recently and the performance dropped so much (getting crackling sound issues with a clean project and only one AUv3 loaded) I start to regret buying it. And all this on A12 apple chipset.

    Did you try to set the audio engine latency to off in the setup/audio menu?

    Was using almost all possible config options. And yes there is a performance difference but to my surprise DSP usage often lowers when loading another AUv3 (!)
    When working in NS2, you just launch it and having fun. When launching CB3 I now wonder
    with what it will surprise me this time.
    Hopefully one or two further updates will make it a comfortable and reliable working environment.

    I am seconding the thoughts about economics. It can be definitely improved.
    Pianoroll is somehow complicated in comparison to NS2 which is smooth and very intuitive.
    When coping midi parts in sequencer they are not pasted behind the copied part but almost randomly (probably depending on play cursor position).
    Why there is no option to automatically quantise freshly recorded part?
    Sometimes humanised beats and melodies are welcome but the fact that to avoid it, user has to manually select a part and press quantisation button every time makes creating process longer than necessary.

    Having some hopes about the future since Steinberg is listening to the users.

    Have you tried Auto Quantize and Note Ends under quantize drop down toolbar menu to automatically quantize recorded notes and also note ends? See Help > Project View > Tools > Quantize

    These options are also available in v2

    Aside from immediately tapping Undo after recording, notes cannot be de-quantized later on.

    Thanks, it's there. Was looking for it in a wrong place (app setup options)

  • edited January 2021

    @israelite said:

    @MobileMusic said:

    @israelite said:

    @GLacey said:

    @israelite said:
    From my short personal experience I tell you this:
    Got CB3 on black Friday sale, enjoyed it and survived it crashing occasionally. Then Steinberg released an update recently and the performance dropped so much (getting crackling sound issues with a clean project and only one AUv3 loaded) I start to regret buying it. And all this on A12 apple chipset.

    Did you try to set the audio engine latency to off in the setup/audio menu?

    Was using almost all possible config options. And yes there is a performance difference but to my surprise DSP usage often lowers when loading another AUv3 (!)
    When working in NS2, you just launch it and having fun. When launching CB3 I now wonder
    with what it will surprise me this time.
    Hopefully one or two further updates will make it a comfortable and reliable working environment.

    I am seconding the thoughts about economics. It can be definitely improved.
    Pianoroll is somehow complicated in comparison to NS2 which is smooth and very intuitive.
    When coping midi parts in sequencer they are not pasted behind the copied part but almost randomly (probably depending on play cursor position).
    Why there is no option to automatically quantise freshly recorded part?
    Sometimes humanised beats and melodies are welcome but the fact that to avoid it, user has to manually select a part and press quantisation button every time makes creating process longer than necessary.

    Having some hopes about the future since Steinberg is listening to the users.

    Have you tried Auto Quantize and Note Ends under quantize drop down toolbar menu to automatically quantize recorded notes and also note ends? See Help > Project View > Tools > Quantize

    These options are also available in v2

    Aside from immediately tapping Undo after recording, notes cannot be de-quantized later on.

    Thanks, it's there. Was looking for it in a wrong place (app setup options)

    Also pasting events, notes and automation data points is always at the Playhead position. Events are pasted into the currently focused track and if the Playhead is over an existing event, it is pasted right next to the event in the empty space (we can keep pasting event clips this way consecutively - eg: loop event clips)

  • edited January 2021

    Well, I finally bought CB3.2...
    Reimporting a little project by sharing it from Cubasis 2 works well, but a bigger project crash CB3...(the process of export form CB2 works well, I see the compression of files, then, it runs CB3, loading, then, crash...)

    Is there an other way of doing this ?... (IOS 14.3)

    EDIT : ok, I found out, just export your track, then import it into Cubasis 3. But don't "open in" Cubasis 3 if you have an other track running, it's going to mess everything... (had to delete 164 empty projects...)

  • @hellquist said:
    CB3 still doesn't do multiple time-signatures/tempos in one tune, right? Until it does there is no point for me to purchase it, as that also is the main reason I couldn't really use CB2 (which I own, including all IAP's) in my actual production. It was forever "it's been added to the feature request list" but never ever materialised. Until I see it in the feature description of CB3 I won't be upgrading. Both Auria Pro and NS2 does have those things though, so I'm not stressing too much about it regarding CB3.

    @hellquist : That’s a huge issue for me too . It means I also can’t use Xequence. But you know you can always record in 4/4 onto an audio and remove subsequent bars that way if there are no cymbal crashes etc. I love NS2 but the lack of updates on it turns me off. Think of where Cubasis will be 3-5 years from now. Also I think Zenbeats allows you to mix time signatures although I ha e mixed feelings on that one for sure . Come to think of it I wonder if you can record into xaequemce and just remove bars to get some odd meters in there.

  • edited January 2021

    @Telstar5 said:

    @hellquist said:
    CB3 still doesn't do multiple time-signatures/tempos in one tune, right? Until it does there is no point for me to purchase it, as that also is the main reason I couldn't really use CB2 (which I own, including all IAP's) in my actual production. It was forever "it's been added to the feature request list" but never ever materialised. Until I see it in the feature description of CB3 I won't be upgrading. Both Auria Pro and NS2 does have those things though, so I'm not stressing too much about it regarding CB3.

    @hellquist : That’s a huge issue for me too . It means I also can’t use Xequence. But you know you can always record in 4/4 onto an audio and remove subsequent bars that way if there are no cymbal crashes etc. I love NS2 but the lack of updates on it turns me off. Think of where Cubasis will be 3-5 years from now. Also I think Zenbeats allows you to mix time signatures although I ha e mixed feelings on that one for sure . Come to think of it I wonder if you can record into xaequemce and just remove bars to get some odd meters in there.

    Sadly, unless I've missed an update and fail to find the settings, Zenbeats to my knowledge can't do it either. The only other DAW that can is MultiTrackStudio For iPad, but that one has other issues as well (of course, they all do).

    I too love NS2, and I too am disheartened by the lack of updates and feature additions. I understand that people have priorities, have to make a living, have families etc, we all do, but I am not clear on why everyone opts to not communicate about what they are working on and what the release plan is. I don't think anyone would mind if the plans changed, both regarding features or dates, but it would be incredibly more useful for all users, and would in one fell swoop remove all the "I wonder if that will ever happen" questions that fill forums and Facebook groups.

    For some reason multiple time-signatures/tempos, which is in all DAWs on desktops, is an enigma yet to be solved by most iOS DAWs. Also on iOS there is the eternal power struggle on "who is syncing to whom" where they all want to lead and no one wants to follow, which massively limits us, the users, possibilities in filling in the various apps competence gaps with our own solutions. If they built in good stable sync for both leading and following a whole new world of possibilities would open up for iOS musicians as we then could use whatever apps in whichever combination, and also would remove some of the stress for developers in adding loads of functionality that rarely will be on par with all users fave apps specialist functionality anyways, just to get to the basics. Ah well.

  • @hellquist What you've said confirms my view of desktop as a halfway reliable production environment and iOS as the rather new experimental playground that does show a few serious highlights which make us hope that if we only try hard enough, iOS can be on the same level, in a different way.

    Indeed, DAWs that slave to external sync are rare: Beatmaker 3, KORG Gadget 2, Groove Rider and anything you can load in Audiobus. And only BM3 will actually time stretch audio according to external tempo changes.
    But on the desktop, the situation is not much better. Ableton Live can follow MIDI clock and LINK obviously, but most DAWs want to be the master as well. And Cubase/Cubasis are definitely not part of the game. Not even when you're only using MIDI tracks. Requested by users maybe 1000 times but it just won't happen. Like numerous C3 bug fixes too.

  • The update was not worth it to me. The only new feature I’ve used so far is being able to re-order fx. Very disappointed that they dropped the ball on a time track. It makes CB seem like a toy, not a real DAW.

  • @ralis just to let you know after testing a bit more, with an heavy project that putted my iPad pro 11 on the knees with CB2, with CB3 no problem at all...

    The group tracks needs more polish (I was expecting a kind of folder, to optimize space, but it's just a master track "alone")

    The mixer is a breeze, really.

    The UI is great.

    The import/export/sharing and folder organisation is really great.

    I still have some problems importing some projects, opened a ticket, will see how it goes...Hopefully well.
    I also have weird issues with rendering tracks sometimes (begin of the track is cut because of an old IAA plugin) also the track last longer with empty space at the end.
    Also sometimes AUv3 plugins drops, I need to deactivate reactivate them...

    That said, I'm using C3 more like a mixing/mastering tool, and I think it does the job pretty well, but still needs a bit of polish.
    But yes, for me, it was worth it.

    I'm creating with AUM+X2 for midi which is lightyears ahead in midi editing.

  • @rs2000 said:
    @hellquist What you've said confirms my view of desktop as a halfway reliable production environment and iOS as the rather new experimental playground that does show a few serious highlights which make us hope that if we only try hard enough, iOS can be on the same level, in a different way.

    Indeed, DAWs that slave to external sync are rare: Beatmaker 3, KORG Gadget 2, Groove Rider and anything you can load in Audiobus. And only BM3 will actually time stretch audio according to external tempo changes.
    But on the desktop, the situation is not much better. Ableton Live can follow MIDI clock and LINK obviously, but most DAWs want to be the master as well. And Cubase/Cubasis are definitely not part of the game. Not even when you're only using MIDI tracks. Requested by users maybe 1000 times but it just won't happen. Like numerous C3 bug fixes too.

    Regarding desktop: aye, true as well. However, most of the DAWs on desktop are closer to "feature complete" compared to the iOS DAWs. The more feature complete a piece of software is, the less sync dependent it can afford to be I guess. My main bugbear with lack of following/leading sync though is that in our iOS bubble, there are lots of apps that only do a very special little thing, only solving part of the music-making puzzle.

    Many users try, often in vain, to combine those apps to a "perfect" solution for them, but very often find themselves running in to rather hard brick walls. Handle midi over there, handle audio clips over there, add some synths over there and sample a bit over there. Sounds great on paper. Too often those apps are not really prepared for users that wish to solve anything outside the scope of what that specific apps handles though.

    Actually I also think it comes down to the economy of it all too. Even though the market has slightly adjusted itself upwards in pricing, iOS is nowhere near desktop pricing. The users expectations for low prices and sales is high, even on apps that cost 1/10'th of the desktop equivalent. People hold off a $7 purchase, waiting for it to get to $5.

    This obviously hinders developers in spending unlimited time on their apps unless they are true altruists and/or are already financially independent (which is rarely the case for one-man indy dev shops). I'm actually not sure the economy actually is there either, yet. That we are enough people on iOS willing to purchase these things. But I digress and I also didn't mean to derail this thread, hehe, sorry about that. :)

Sign In or Register to comment.