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 as MIDI input in AB3 ??

NoonienSNoonienS
in General App Discussion

Trying to have different Midi tracks in Cubasis to send to different midi paths in AB3 (to be able to take advantage of state saving). However, as there seem to be no ports defined for Cubasis, all tracks end up sending to all paths. A workaround could have been if there was a Midi effect that could e.g block a specified channel, but I don' t think there is one (yet). Any ideas?

Comments

  • [Deleted User][Deleted User]
    edited April 2017

    With the new midi effects apps maybe?
    Have you got them yet?

  • wigglelightswigglelights

    Check the Cubasis forum - they put up some great sticky posts about what can work and can't work routing-wise with AB3.
    -pretty damn thoughtful I'd say for Lars and the team to spell out those limitations (and capabilities) up front. Could certainly save a ton of headaches

  • [Deleted User][Deleted User]

    Link please?

  • buskerbusker

    This perhaps?

    https://www.steinberg.net/forums/viewtopic.php?f=183&t=115199

  • WillWill

    Haven't tried this yet but think Cubasis would have to expose separate MIDI ports to have them work on discreet AB lanes. You might be able to use a MIDIFlow filter to restrict the MIDI messages to specific channels on each lane.

  • wigglelightswigglelights

    @busker - that's the one I was referring to, thx

    Also this regarding IAA
    https://www.steinberg.net/forums/viewtopic.php?f=183&t=104551
    And regarding AU
    https://www.steinberg.net/forums/viewtopic.php?f=183&t=92984
    And the forum list
    https://www.steinberg.net/forums/viewforum.php?f=183&sid=75f1670a3e27dc59103a94dfc0ae5aaa

  • NoonienSNoonienS

    I checked the "limitations" already (I agree that was a great move by Steinberg)-couldn't see anything matching this issue though. Got all the midi filters as well, but no solution to this issue. As I've understood it, it is not possible to route MIDI to non AB3 apps (which may include Midiflow, but I don't have it)

  • SebastianSebastian
    edited April 2017

    @NoonienS said:
    Trying to have different Midi tracks in Cubasis to send to different midi paths in AB3 (to be able to take advantage of state saving). However, as there seem to be no ports defined for Cubasis, all tracks end up sending to all paths. A workaround could have been if there was a Midi effect that could e.g block a specified channel, but I don' t think there is one (yet). Any ideas?

    No, I think this is probably something that requires an update of Cubasis. I think you should contact them.

    Maybe once Modstep does AB 3 MIDI it'll be a solution for you.

    The solution with the MIDI channel splitter just seems a bit clunky. Or we might have to build a MIDI player into Audiobus but that'll take time, too.

  • NoonienSNoonienS

    No splitter needed really, just the ability to block out a channel (within the lane), like AUM does..

  • cj3000cj3000

    @NoonienS said:
    No splitter needed really, just the ability to block out a channel (within the lane), like AUM does..

    +1
    Would like to have this too.
    Christoph

Sign In or Register to comment.