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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Midi-Routing in cubasis with external keyboard
Bear with me, I'm still new to making music with an Ipad
(.. did it professionally years ago with LogicPro - but thats a long time ago)
When I play a Midi-track in cubasis which has an IAA-instrument assigned to it, cubasis doesn't seem to route the incoming Midi from my Kurzweil USB-keyboard to the Midi-out Channel, set in the left bar of the Midi-track. It works with the internal cubasis keyboard (I can hear the correct instrument set to that channel in the IAA-instrument), it does not work when I play on my external keyboard. I only hear the sound coming through CoreMidi (direct connection between keyboard and instrument I guess)
Example:
- create Midi-track in cubasis, set SampleTank as IAA
- switch to SampleTank, set LiveMode and set piano to first instrument, bass to second etc.
- switch back to cubasis, create new Midi-Track, No Instrument, Midi-Out to SampleTank, channel 2
In Cubasis the internal keyboard of course plays the selected bass-track (channel 2), but the external USB-keyboard still plays piano. ONLY if I would change on my keyboard to Midi-Out channel 2 it plays the bass. That clearly means cubasis doesnt route the incoming Midi to the IAA instrument.
Is that normal? Am I missing something?
I learned already that I can't disable that direct connection (CoreMidi). I could live with that if at least I can play externally what track I select inside cubasis.
Thanks again
Comments
Yes, I'm running one IAA Sample Tank instance and want to use it multitimbral inside cubasis (up to 8 sounds I believe). You need to set ST to Live-Mode (top left). Then switch back to cubasis and create new Midi-tracks with no instrument assigned to them, just the Midi-Out should go to the Midi-channels of SampleTank. Internal cubasis keyboard plays the correct sounds, depending on what track you select - external USB-keyboard doesnt care at all.
yes .. that doesnt seem to help - Incoming Midi doesnt seem to get routed to the Midi-OUT channel of the selected track.
can't believe that ... there must be something
@borisb2: MIDI Thru in Cubasis is broken (doesn't correctly remap the channel), known bug since 2013. You can file a(nother) report at the Steinberg Forums, or maybe @LFS is listening! ;-)
as I said, playing the tracks with the internal cubasis keys is all fine. Depending on what Midi-track I select I can play the correct sound set up in ST ..
Playing AUv3-instruments or internal cubasis synths (micrologue, minisampler) is also fine. Even with the external keyboard i can play the AUv3/internal sound if I'm on that track. It's really only related to IAA
ah.. thats interesting and good to know.. thanks
I don't want to rant too much at this point. I'm still impressed on how powerful the Ipads have become. I'm impressed on how little money you have to spend to get good professional sounds. Its' just, from my past (making music) I remember this is one of the most basic things you need to do: you hook up a keyboard to the sequencer, you create tracks with instruments, you play and record. It does work with AUv3 and internal stuff ..it does not work with IAA. I never would have thought this causes so much trouble on the Ipad
@borisb2 if you are willing to do the sound (AUv3, IAA) hosting and the keyboard / sequencing stuff in two separate apps, then there's at least one sequencer I know of that handles MIDI Thru correctly and in general has very comprehensive MIDI editing and controlling madness, but I won't mention names here for stylistic reasons
or just concentrate on AU and not use IAA at all .. which kicks out SampleTank into uselessness ..boom
.. done.
Is there any AU SamplePlayer available that sits somewhere between MicroSonic from Steinberg and ST?
Or, if I'd choose to work more with AuriaPro and Lyra (which seems to have good sounds as well): are there any AU drum-machines/player available similar to ClassicMachines for Steinberg?
I guess xequence could solve the problem? 😎
Can I import the midi from xequence to Cubasis if needed?
Yes, Xequence has MIDI export and Cubasis has good import, so there should be no issues there.
I'd go as far as to say the midi-implementation in many apps is 'broken' as in that they accept midi-input from multiple sources at the same time with no way to 'disable' certain inputs.
If we for example take Korg iM1 it can accept midi from an external keyboard connected thru Core Midi (This can not be disabled) and the host it is connected to using IAA.
My suggestion to all app developers would be to 'disable' CoreMidi Input when an app is connected to an IAA-Host.
@borisb2 : have you tried the suggestion of freezing you'd sampletank tracks as you go, so that you only have one live midi channel at a time rather than using it multi-timbales? (It will also be more Resource efficient and allow more glitch-free tracks at once)
no, haven't tried it yet .. first I need to be able to hear the correct sound
(playing with the external keyboard) ..
... unless you meant not using the Live-mode at all in ST?
to ask more general:
I'd like to know, who of you guys is using cubasis with an external keyboard and IAA-instruments inside cubasis .. and if you use it, what is your workflow?
@borisb2 : yes, I mean not using live mode. I think you will find it straightforward (and way less CPU-intensive, too) to do a track at a time. Record your sampletank MIDI then freeze the track. Then record your next one.
Hi boris2,
By default, most iOS apps receive from all CoreMIDI ports and from VirtualMIDI. Some apps, like Cubasis, allow you to select which ports should be received.
If MIDI Thru is disabled, Cubasis doesn’t forward the MIDI input, it only routes the internal keyboard and track playback to the MIDI output.
If MIDI Thru is enabled, Cubasis forwards the MIDI input to the output, without modifying anything, i.e. the output channel is ignored for MIDI Thru. This behavior will be changed in a future update.
Regarding IAA and CoreMIDI, if an IAA app is connected to Cubasis on one MIDI track, and you also send MIDI to it from another MIDI track, the latter is completely independent from IAA, it’s CoreMIDI and is directly received by the other (IAA) app, without going through IAA.
In general, we recommend AU in favour of IAA because it doesn’t require manual MIDI routing and because IAA is limited to 1 connection per app.
If you must use IAA, the best way is to disable all MIDI input except Cubasis in the IAA app and use an IAA instrument on a MIDI track. However, multiple channels with IAA instruments are not supported yet by Cubasis.
Additionally, we will have a closer look at the feature request "MIDI Thru Re-Channelize" for the update after the next one.
Best,
Lars