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.

Logic Pro: Migration of Cubasis projects

Ideally, you work with only one DAW. For me, it's Cubasis so far. I might want to switch to Logic Pro.

Does anyone migrate Cubasis projects to Logic Pro?
How do you go about it in order to be able to transfer as much as possible?

Comments

  • @Iskander said:
    Ideally, you work with only one DAW. For me, it's Cubasis so far. I might want to switch to Logic Pro.

    Does anyone migrate Cubasis projects to Logic Pro?
    How do you go about it in order to be able to transfer as much as possible?

    Same here if anybody can answer this would help two lost souls!

  • Never tried it, but perhaps some sort of way to do that:

    Import Cubasis project into Cubase Pro Desktop
    Export to AAF
    Import AAF into Logic Pro Mac
    Open it in Logic Pro iPad

    Yes, you need additional desktop software/device.
    Yes, plugins are lost.
    Yes, the result is not foreseeable.
    Yes, only audio. MIDI requires separate handling (SMF)

  • I migrated a project over the last few days from Cubasis to Logic Pro for iPad.

    I did it completely manually. I exported the stems from Cubasis using mixdown, “Create separate files for tracks” with “Include effect tail” off and “Exclude all effects (dry)” on.

    I then manually created tracks in Logic Pro and imported the audio files one by one using the files app in “slide over” configuration so I could see both the stems and Logic Pro.

    I only have the one project that I care about, and wanted to build a new mix template in LP4i, so the manual effort was worth it. Clearly, this level of manual effort would be unrealistic for anyone migrating a number of projects.

    However, if one built a template in LP4i with a reasonable facsimile of the track configurations used in Cubasis, then imported the raw files into this prepared template, it would not be so burdensome.

  • I’m not a fan of sticking to just one DAW/workflow personally. Not ideal for me, so I’m keeping Cubasis 3, ZenBeats, and Logic for right now.

  • edited June 2023

    I can’t imagine keeping multiple DAWs straight in my head, with differing templates for each.

    That on top of continuing to develop piano, organ, guitar, vocal, songwriting and mixing skills.

    LP4i includes everything I need in a single, coherent package (Cubasis most certainly didn’t, lacking busses, takes, support for external hardware effects, delay compensation and the all important track presets represented by audio patches). The fact that I can really construct a “template” with audio patches referring to all my standard bus sends will radically simplify future projects.

    @HotStrange its incredible you can do that!

  • I will not even consider a 'migration' of existing projects to a new DAW.
    But I will slowly start 'exporting' the content created with the other DAW into plain *.wav files.

    I expect to see at least a few updates to Logic Pro for iPad before fully moving on forward...

  • @Iskander said:
    Ideally, you work with only one DAW. For me, it's Cubasis so far. I might want to switch to Logic Pro.

    Does anyone migrate Cubasis projects to Logic Pro?
    How do you go about it in order to be able to transfer as much as possible?

    As many others have said I also have audio (wav) recordings for each track of every project, with MIDI data separately. It’s a must on iOS, because you never know what's gonna happen with updates, deprecation, bugs, etc… for all those app-s. Only problem was with notes, so I included entire data management for my workflow, ofc. you can skip that part. ;)

    Also I had an idea to sample most memorable synth patches with AudioLayer in format which other samplers recognize, never happened. Hope still has not died. 😌

    So transferring to any other DAW kinda is no problem at all. Not much of a help, but there you go…

  • @DovJ said:
    I can’t imagine keeping multiple DAWs straight in my head, with differing templates for each.

    That on top of continuing to develop piano, organ, guitar, vocal, songwriting and mixing skills.

    LP4i includes everything I need in a single, coherent package (Cubasis most certainly didn’t, lacking busses, takes, support for external hardware effects, delay compensation and the all important track presets represented by audio patches). The fact that I can really construct a “template” with audio patches referring to all my standard bus sends will radically simplify future projects.

    @HotStrange its incredible you can do that!

    I wouldn’t say amazing. More like stubborn lol. And I don’t go fully into each DAW to be fair. I mostly work in AUM and use the DAWs to add finishing touches.

Sign In or Register to comment.