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?

13

Comments

  • edited January 2021

    GarageBand has 4/4, 3/4 and 6/8 time signatures - meets most uses

  • @MobileMusic said:
    GarageBand has 4/4, 3/4 and 6/8 time signatures - meets most uses

    And you can have multiple of them in the same tune?
    Most apps I have mentioned indeed can have other time signatures than 4/4. The problem is you have to stick to the same one throughout one tune, which doesn't fit my music where I need 7/8 going to 4/4 then going back to 7/8 (just an example).

  • edited January 2021

    @hellquist said:

    @MobileMusic said:
    GarageBand has 4/4, 3/4 and 6/8 time signatures - meets most uses

    And you can have multiple of them in the same tune?
    Most apps I have mentioned indeed can have other time signatures than 4/4. The problem is you have to stick to the same one throughout one tune, which doesn't fit my music where I need 7/8 going to 4/4 then going back to 7/8 (just an example).

    Do you know Gadget 2?
    Do you know Nanostudio 2?
    Both excellent for music composition.

  • @rs2000 said:

    @hellquist said:

    @MobileMusic said:
    GarageBand has 4/4, 3/4 and 6/8 time signatures - meets most uses

    And you can have multiple of them in the same tune?
    Most apps I have mentioned indeed can have other time signatures than 4/4. The problem is you have to stick to the same one throughout one tune, which doesn't fit my music where I need 7/8 going to 4/4 then going back to 7/8 (just an example).

    Do you know Gadget 2?
    Do you know Nanostudio 2?
    Both excellent for music composition.

    Yep, have and use both for that very purpose and reason. And Auria. But I would wish for my options to not be limited to those few apps, especially given that they all have "issues" of their own of various types. Right now it is just enough for my iOS music creation needs (which is why I'm not panicking about it), but it isn't like I feel overwhelmed by a plethora of seamless options, and if one of those apps were to fail for whatever reason (not uncommon on iOS, and could be for months) I would be stranded.

    As initiallly stated (well, initially for me in this thread) there are work-arounds right now, but I don't consider that in itself to be good reasons for CB3, Zenbeats, BM3, Drambo, Xequence etc (all with advanced timelines basically, most of them also hosts) to not add that standard-for-desktop-daws-functionality as well. In the case of Cubasis I have waited literally years (well, since 2013) for them to implement it. Currently they have opted not to.

  • How does it stand today? Anyone care to update this thread for the curious? Stay with ver 2 or upgrade?

  • @kinkujin said:
    How does it stand today? Anyone care to update this thread for the curious? Stay with ver 2 or upgrade?

    So... I upgraded from CB2 to CB3 when I got a new iPad 8 in January. I’ve tried multi-core mode which wasn’t successful with Moog Model D, so for now going single core, otherwise no problems noticed. I’m sure I will have recently benefitted from the improved time resolution when aligning some takes recorded elsewhere.

  • CB3 has been a real drag at times. Seems there is always something that’s not working that zaps my mood. Of course they are aware and say they will fix it and they might...eventually. This thing has been out for 15 months or so and I still use it but Ive found myself doing more things elsewhere. The improvements over CB2 are significant but the creativity sucking problems are quite sad to endure.

  • The user and all related content has been deleted.
  • I freeze and unfreeze both midi and audio tracks all the time in Cubasis 3. The upgrade was worth it for my workflow.

  • @kinkujin, worth it, IMO. As @ehehehe said, a quick reboot fixes most everything. The GUI feels a lot better and you have the expectations of new features. CB2 was great... but it’s kind of moldering while the world moves on. Wait for a sale, maybe, and go for it. Still, incredible for fifty bucks.

  • edited April 2021

    Probably a dumb question - can you use your auv3 effects in Cubasis 3, thereby not needing the IAPs?

    It's currently at $35.99 on u.s. app store.

  • @kinkujin said:
    Probably a dumb question - can you use your auv3 effects in Cubasis 3, thereby not needing the IAPs?

    It's currently at $35.99 on u.s. app store.

    Yes, no problem, no IAP for Auv3 plugins

  • @crony said:

    @kinkujin said:
    Probably a dumb question - can you use your auv3 effects in Cubasis 3, thereby not needing the IAPs?

    It's currently at $35.99 on u.s. app store.

    Yes, no problem, no IAP for Auv3 plugins

    Yes most seems to perfectly.

    I do like the Waves IAPs though. They're (hopefully) still on sale too and are optimised for smooth running within Cubasis.

  • Although slightly off topic, I've been eyeing up Cubasis 3 and now its on sale, I'm tempted.

    Can anyone give a rough idea how far you can push Cubasis 3 with plugins / synths?

    I currently use Korg Gadget as my DAW, using many Gadget internal synths for layering (I find Gadget's fx are a bit limited) and Taipei to control external Auv3 synths mixed with plugins in AUM.

    I appreciate this is subjective, I've been surprised how much I can cram into Gadget without affecting the CPU too badly.

    The last song I finished, I just about managed 40 tracks in Gadget, controlling 9 auv3 synths, Ruismaker and two instances of Digistix.

    On top of that, various plugins for each bus (FAC Transiet / Wider / LRC5 / Roughrider etc.) and Bark Filter on the master.

    So, I'm wondering, do people find they hit a hard limit fairly early with Cubasis 3, or is it pretty good performance wise?

  • @timforsyth said:
    Although slightly off topic, I've been eyeing up Cubasis 3 and now its on sale, I'm tempted.

    Can anyone give a rough idea how far you can push Cubasis 3 with plugins / synths?

    I currently use Korg Gadget as my DAW, using many Gadget internal synths for layering (I find Gadget's fx are a bit limited) and Taipei to control external Auv3 synths mixed with plugins in AUM.

    I appreciate this is subjective, I've been surprised how much I can cram into Gadget without affecting the CPU too badly.

    The last song I finished, I just about managed 40 tracks in Gadget, controlling 9 auv3 synths, Ruismaker and two instances of Digistix.

    On top of that, various plugins for each bus (FAC Transiet / Wider / LRC5 / Roughrider etc.) and Bark Filter on the master.

    So, I'm wondering, do people find they hit a hard limit fairly early with Cubasis 3, or is it pretty good performance wise?

    Well it's difficult to say. There was a recent update which claimed to drastically improve audio unit performance. I think it was called multi-core rendering. I eagerly enabled it only to get worse AU performance!

    From memory I think it only benefited owners of the very latest, most powerful iOS devices. My pathetic 2019 iPad Air wasn't comparable so I switched off multi-core.
    That said, it's ok. Very much dependant on how well optimized the plug-in is. See the other thread about Moog Model D. They thought they were making it better but it got worse!

    I can usually get 5 or 6 different instrument plug-ins and the same amount of effects without any problems.

  • Thanks, I appreciate it depends on the hardware and what plugins you run.

    I'm on a 2020 Air (A14), so I'll probably take the plunge anyway, if only to get a DAW much more like what I used to use 15 years ago.

    Yeah, I read that thread just hours after my model D updated itsself, fortunately, moog seemed to turn it around within a day or so and its back to normal. Then again, Model D is so expensive to run, I usually freeze it to an audio track anyway (in Zurich).

  • @timforsyth said:
    Thanks, I appreciate it depends on the hardware and what plugins you run.

    I'm on a 2020 Air (A14), so I'll probably take the plunge anyway, if only to get a DAW much more like what I used to use 15 years ago.

    Yeah, I read that thread just hours after my model D updated itsself, fortunately, moog seemed to turn it around within a day or so and its back to normal. Then again, Model D is so expensive to run, I usually freeze it to an audio track anyway (in Zurich).

    Ahhh if you've got an Air 4 you should be able to use the multi-core rendering although hopefully others will chip in to say if it makes a difference.

  • edited April 2021

    I took the plunge, spent 30 minutes trying things to see what’s possible compared to my old gadget/AUM workflow.

    I considered starting yet another Cubasis thread, but instead, here goes.

    I started by making a simple 8 bar loop with some chords using gadget as an Iaa input, controlled by a midi track, and added other instruments and tracks from there.

    First impressions

    • it’s Cubase! Something I haven’t used for nearly 20 years, seems familiar.
    • Pinch zooming in x and y, especially x feels like I need two hands, bit odd, I’ll get used to it
    • Fast, zippy ui, the layout seems pretty logical
    • Remember to click midi thru to get your usb keyboard to send through to gadget, other auv3 embedded synths worked fine.
    • Is there some way of going ‘back’ when editing an fx plugin on the mixer?
    • After some time, the rising bass riff I had running in volt wouldn’t play notes above c3. Every note above c3 played as c3! Choosing another synth and going back to volt solved this (not a stuck note, midi panic didn’t help). This happened twice!
    • Controlled some auv3 synths in AUM, looping the output back to cubase as an audio input. Every 5 minutes, this stream would go silent, had to choose another cubase iaa input to fix it
    • Gadgets iaa input would sometimes stop working, had to restart everything to fix. I have a feeling this started once I introduced aum inputs, not sure.
    • Discovered audio groups then discovered you cannot send the output of an audio group to another group. Damn, that’s killed any chance of bus routing.
    • Oh, related to the above, I can’t sidechain.
    • Keep your wits about you when adding a new track, it seems to get added next to the track you are currently editing, for some reason I expected it to get added at the bottom, user error!
    • Hey, stop choosing a default instrument for me when I add a midi track!
    • Nice to have more granular control on the timeline, separate quantize and swing unlike gadget which is all on or off.
    • Timing seems good, ran 3 a drum machines, one in gadget, one in aum and inside cubasis all played in time.

    I was surprised how many audio bugs I encountered after my first 30 minutes, I must have killed all apps at least 10 times, doesn’t bode well for a big project.

    Anyway, there’s enough here I like to carry on, I supposed like all things iOS, I’ll probably instinctively work around the bugs and weird things and accept them eventually.

  • @timforsyth, one can’t successfully use Cubasis3 without judicious freezing, I think. I freeze tracks as the dsp goes critical. The midi is always preserved. You prob know this stuff, but others may not.

    I agree about that damn piano when you open a midi track. Makes no difference, but would be nice to see an empty slot,

  • @LinearLineman said:
    @timforsyth, one can’t successfully use Cubasis3 without judicious freezing, I think. I freeze tracks as the dsp goes critical. The midi is always preserved. You prob know this stuff, but others may not.

    I agree about that damn piano when you open a midi track. Makes no difference, but would be nice to see an empty slot,

    Another vote for out darn piano.

    I’ve just been slicing up an imported MIDI file of an old track from the previous millenium, went smoothly. Though does anyone know how to get Cubasis to take the tempo from a MIDI file?

    I think I’d have noticed the limited arrange page time precision in CB2, no problem lining up audio in CB3.

  • edited April 2021

    You may like to add any issues you encounter or suggestions to this Cubasis list - they’ve already resolved/enhanced a few issues/suggestions from this list recently which means they are actively looking into it -

    https://forums.steinberg.net/t/make-producing-music-easier-100-issues-suggestions/156430

    I have another 50+ items to add to this list and will do it when I get a chance :smile:

  • @LinearLineman said:
    @timforsyth, one can’t successfully use Cubasis3 without judicious freezing, I think. I freeze tracks as the dsp goes critical. The midi is always preserved. You prob know this stuff, but others may not.

    I agree about that damn piano when you open a midi track. Makes no difference, but would be nice to see an empty slot,

    I didn’t know about freezing, I had a brief play again earlier, I was never pushing things hard in my initial mess about, dsp was under 30.

    That said, I did try freezing and I was amazed how well this is implemented, so easy to unfreeze, tweak and freeze again. Great!

    As for my post, I wanted to quickly get down my initial impressions before routine kicks in and I just put up with niggles.

  • @timforsyth, I’m glad I said something! 👍👍

  • @MobileMusic said:
    You may like to add any issues you encounter or suggestions to this Cubasis list - they’ve already resolved/enhanced a few issues/suggestions from this list recently which means they are actively looking into it -

    https://forums.steinberg.net/t/make-producing-music-easier-100-issues-suggestions/156430

    I have another 50+ items to add to this list and will do it when I get a chance :smile:

    Wow, that’s quite a list, would probably be a good idea to organise it into Deal Breakers, Annoyances and Feature adds.

    Still, like the thread I read recently with the amazing moog team, it’s great that steinberg are actively working on supporting their app, I keep reading threads with people bad mouthing cubasis, and I think it’s good to remember that there are people the on the other side trying to make these apps better. With a bug/wish list that big, must be hard to prioritise.

  • @timforsyth said:

    @MobileMusic said:
    You may like to add any issues you encounter or suggestions to this Cubasis list - they’ve already resolved/enhanced a few issues/suggestions from this list recently which means they are actively looking into it -

    https://forums.steinberg.net/t/make-producing-music-easier-100-issues-suggestions/156430

    I have another 50+ items to add to this list and will do it when I get a chance :smile:

    Wow, that’s quite a list, would probably be a good idea to organise it into Deal Breakers, Annoyances and Feature adds.

    Still, like the thread I read recently with the amazing moog team, it’s great that steinberg are actively working on supporting their app, I keep reading threads with people bad mouthing cubasis, and I think it’s good to remember that there are people the on the other side trying to make these apps better. With a bug/wish list that big, must be hard to prioritise.

    Deal breakers are like lack of audio routing, MIDI stretching, side chaining, time signatures, tempo tracks, Link, Playhead scrubbing...

    Annoyances are like the settings that do not persist across sessions (resolved a few already/partially like track heights, MIDI editor zoom factor), Automation editor listing all parameters from all tracks instead of filtering parameters for the current track only, fixed panels like Mixer, Keyboard, etc that close/replace previous ones, re-saving of projects on just opening them and messing up their modified date and sort order, items in Media Bay not sorting by date properly...

    Feature adds are enhancement and suggestions which the list has so many in it along with simple/graceful solutions on how to resolve them (see Flexible placement of panels), Octave buttons on the keyboard, Ratings, Patterns, Chord library, Drummer, Track templates and Copy/paste track settings, elegant condensed Fonts...

    Big fixes - top priority
    Persistence of settings - level 2
    Enhancements - level 3

    Also apply bug fixes and persistence of settings to v2.

    Done.

  • @timforsyth said:
    I took the plunge, spent 30 minutes trying things to see what’s possible compared to my old gadget/AUM workflow.

    I considered starting yet another Cubasis thread, but instead, here goes.

    I started by making a simple 8 bar loop with some chords using gadget as an Iaa input, controlled by a midi track, and added other instruments and tracks from there.

    First impressions

    • it’s Cubase! Something I haven’t used for nearly 20 years, seems familiar.
    • Pinch zooming in x and y, especially x feels like I need two hands, bit odd, I’ll get used to it
    • Fast, zippy ui, the layout seems pretty logical
    • Remember to click midi thru to get your usb keyboard to send through to gadget, other auv3 embedded synths worked fine.
    • Is there some way of going ‘back’ when editing an fx plugin on the mixer?
    • After some time, the rising bass riff I had running in volt wouldn’t play notes above c3. Every note above c3 played as c3! Choosing another synth and going back to volt solved this (not a stuck note, midi panic didn’t help). This happened twice!
    • Controlled some auv3 synths in AUM, looping the output back to cubase as an audio input. Every 5 minutes, this stream would go silent, had to choose another cubase iaa input to fix it
    • Gadgets iaa input would sometimes stop working, had to restart everything to fix. I have a feeling this started once I introduced aum inputs, not sure.
    • Discovered audio groups then discovered you cannot send the output of an audio group to another group. Damn, that’s killed any chance of bus routing.
    • Oh, related to the above, I can’t sidechain.
    • Keep your wits about you when adding a new track, it seems to get added next to the track you are currently editing, for some reason I expected it to get added at the bottom, user error!
    • Hey, stop choosing a default instrument for me when I add a midi track!
    • Nice to have more granular control on the timeline, separate quantize and swing unlike gadget which is all on or off.
    • Timing seems good, ran 3 a drum machines, one in gadget, one in aum and inside cubasis all played in time.

    I was surprised how many audio bugs I encountered after my first 30 minutes, I must have killed all apps at least 10 times, doesn’t bode well for a big project.

    Anyway, there’s enough here I like to carry on, I supposed like all things iOS, I’ll probably instinctively work around the bugs and weird things and accept them eventually.

    In my experience, the Volt thing is a Volt issue. I believe I’ve had it happen elsewhere and I don’t recall having it with any other synths in CB3.

    Also your IAA issues are only going to get worse as the technology is being deprecated by Apple so less effort is being put in to maintain it.

  • /> @timforsyth said:

    I took the plunge, spent 30 minutes trying things to see what’s possible compared to my old gadget/AUM workflow.

    I considered starting yet another Cubasis thread, but instead, here goes.

    I started by making a simple 8 bar loop with some chords using gadget as an Iaa input, controlled by a midi track, and added other instruments and tracks from there.

    First impressions

    • it’s Cubase! Something I haven’t used for nearly 20 years, seems familiar.
    • Pinch zooming in x and y, especially x feels like I need two hands, bit odd, I’ll get used to it
    • Fast, zippy ui, the layout seems pretty logical
    • Remember to click midi thru to get your usb keyboard to send through to gadget, other auv3 embedded synths worked fine.
    • Is there some way of going ‘back’ when editing an fx plugin on the mixer?
    • After some time, the rising bass riff I had running in volt wouldn’t play notes above c3. Every note above c3 played as c3! Choosing another synth and going back to volt solved this (not a stuck note, midi panic didn’t help). This happened twice!
    • Controlled some auv3 synths in AUM, looping the output back to cubase as an audio input. Every 5 minutes, this stream would go silent, had to choose another cubase iaa input to fix it
    • Gadgets iaa input would sometimes stop working, had to restart everything to fix. I have a feeling this started once I introduced aum inputs, not sure.
    • Discovered audio groups then discovered you cannot send the output of an audio group to another group. Damn, that’s killed any chance of bus routing.
    • Oh, related to the above, I can’t sidechain.
    • Keep your wits about you when adding a new track, it seems to get added next to the track you are currently editing, for some reason I expected it to get added at the bottom, user error!
    • Hey, stop choosing a default instrument for me when I add a midi track!
    • Nice to have more granular control on the timeline, separate quantize and swing unlike gadget which is all on or off.
    • Timing seems good, ran 3 a drum machines, one in gadget, one in aum and inside cubasis all played in time.

    I was surprised how many audio bugs I encountered after my first 30 minutes, I must have killed all apps at least 10 times, doesn’t bode well for a big project.

    Anyway, there’s enough here I like to carry on, I supposed like all things iOS, I’ll probably instinctively work around the bugs and weird things and accept them eventually.

    Exactly why I stay on CB2. Those un explicable bugs coming out of nowhere.

    Also the copy paste of a region keeping both the new and old region selected. That annoy me beyond words and I am not the type to get annoyed by software. I have worked in IT all my life.

  • edited April 2021

    @hellquist : What issues specifically were you referring to in Multitrack Studio? The developer seems really responsive to input . BTW as for Zenbeats, I was under the impression that you could assign time signature per clip.

  • @DukeWonder said:

    @timforsyth said:
    I took the plunge, spent 30 minutes trying things to see what’s possible compared to my old gadget/AUM workflow.

    I considered starting yet another Cubasis thread, but instead, here goes.

    I started by making a simple 8 bar loop with some chords using gadget as an Iaa input, controlled by a midi track, and added other instruments and tracks from there.

    First impressions

    • it’s Cubase! Something I haven’t used for nearly 20 years, seems familiar.
    • Pinch zooming in x and y, especially x feels like I need two hands, bit odd, I’ll get used to it
    • Fast, zippy ui, the layout seems pretty logical
    • Remember to click midi thru to get your usb keyboard to send through to gadget, other auv3 embedded synths worked fine.
    • Is there some way of going ‘back’ when editing an fx plugin on the mixer?
    • After some time, the rising bass riff I had running in volt wouldn’t play notes above c3. Every note above c3 played as c3! Choosing another synth and going back to volt solved this (not a stuck note, midi panic didn’t help). This happened twice!
    • Controlled some auv3 synths in AUM, looping the output back to cubase as an audio input. Every 5 minutes, this stream would go silent, had to choose another cubase iaa input to fix it
    • Gadgets iaa input would sometimes stop working, had to restart everything to fix. I have a feeling this started once I introduced aum inputs, not sure.
    • Discovered audio groups then discovered you cannot send the output of an audio group to another group. Damn, that’s killed any chance of bus routing.
    • Oh, related to the above, I can’t sidechain.
    • Keep your wits about you when adding a new track, it seems to get added next to the track you are currently editing, for some reason I expected it to get added at the bottom, user error!
    • Hey, stop choosing a default instrument for me when I add a midi track!
    • Nice to have more granular control on the timeline, separate quantize and swing unlike gadget which is all on or off.
    • Timing seems good, ran 3 a drum machines, one in gadget, one in aum and inside cubasis all played in time.

    I was surprised how many audio bugs I encountered after my first 30 minutes, I must have killed all apps at least 10 times, doesn’t bode well for a big project.

    Anyway, there’s enough here I like to carry on, I supposed like all things iOS, I’ll probably instinctively work around the bugs and weird things and accept them eventually.

    In my experience, the Volt thing is a Volt issue. I believe I’ve had it happen elsewhere and I don’t recall having it with any other synths in CB3.

    Also your IAA issues are only going to get worse as the technology is being deprecated by Apple so less effort is being put in to maintain it.

    Re: IAA. Despite being deprecated, IAA has if anything been more reliable in iOS 14 than AUv3 for some.

Sign In or Register to comment.