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.
Hardware transport controls
Hi, I've acquired the impact lx61 usb midi keyboard. It has knobs, faders, pads and transport controls. But I can't get the transport controls to control anything. Neither cubasis, auria it GarageBand. Is it just not possible on iOS, or is the lx 61 that's the problem? It works perfectly with desktop daws. Cheers
Comments
I would like to know the same. Most computer-based DAWs on the Mac and PC allow Mackie Control to be turned on. I don't see this option in Cubasis for example. This at the moment, this is my main iOS DAW. @Cubasis please add this feature. If not using a Mackie Control protocol, then are there CC#s dedicated to transport that iOS apps could use? Any iOS apps have this function? I just purchased the Korg Taktile49 MIDI Controller and would love to control the transport of Cubasis, Gadget and other apps.
I'll just take a seat right here next to you bsantoro. Surely someone will come along and enlighten us.
I think we should blame they guys who invented midi, they never specified transport controls.
It would have been nice if Audiobus had enabled midi control of its transport buttons as well
I found this:
http://www.indiana.edu/~emusic/cntrlnumb.html
Midi transport messages are system realtime messages, not channel specific so a list of cc's won't help in this case.
Here's a list of system realtime messages:
http://www.indiana.edu/~emusic/etext/MIDI/chapter3_MIDI8.shtml
MMC and MTC specs:
http://www.indiana.edu/~emusic/etext/MIDI/chapter3_MIDI10.shtml
My Korg Taktile has an editing application that runs on the desktop that allows for specific CCs to be assigned to any button or fader; including the transport controls. So, if an iOS music app has the function of transport controls using CC#s, then my hardware device could control it. It would have to be an app that has a built-in sequencer. As far as I can see, Cubasis does not have this feature.
This sounds like something that would be good for MidiBridge. It has a stream byter which can transform any incoming MIDI event from a hardware controller into something else; it can do some serious voodoo magic. I'm sure it could handle MIDI start/stop/continue messages for controlling Cubasis, and should probably work for Gadget too. The KORG docs show some custom mappings to controller messages -- should be something not too hard to wrangle. There's a specific tip for Auria on the Audeonic website which would probably translate to Cubasis:
http://audeonic.boards.net/thread/106/tip-remote-controlling-aurias-transport
MidiBridge made my head hurt a little bit the first time I messed with it, but I've found it to be crazy useful when I need to do something odd, and Nic is my zen master when it comes to MIDI stuff. I'm switching all of my apps over to use his Midibus library; it's rock solid, and his implementation is light years beyond what I had been doing before.
The stream byter isn't pretty, but if you ask around the MidiBridge forum, I'd bet that either Nic, or one of the other users, could help out.
What is interesting is that a number of apps running under IAA along with Cubasis have a controller strip that can start and stop Cubasis, and also initiate and terminate the record function. There must be something in the iOS SDK that allows these apps with IAA to control the transport of Cubasis. Why couldn't this apply to Core MIDI for external MIDI controllers?
The issue is that many hrdware controllers can only generate CC messages from their so-called "transport control buttons. My Korg nanoKONTROL2 and Samsun Graphite are both like that. And the DAWs are correctly implemented to use the well defined MIDI Real Time Transport Control messages (which have been there since the beginning, I would note to scoffers)(well, mostly, there is some confusion about the difference between Start and Continue messages). There is also a much more comprehensive Midi Machine Control protocol that runs over MIDI, but AFAIK only Auria has an MMC option.
Some Apps also use CC messages for their transport control. Korg again - iPolySix and iMS20 for example.
As remarked above, MidiBridges StreamByter is the best way to match up these things. Except for the Korg Apps which are promiscuous so block MidiBridge from doing its work. But the have Midi Learn implemented so there is a work-around.
What cc's are being used for what?
This was the one thing I struggled with trying to make happen in Lemur.
Well I'm happy to know it's just not me who need this and can't get it to work. Was afraid it was an issue with the lx61. Buying new apps for this to work, is not the ideal solution. Guess I could use audiobus remote for transport controls until the devs implements it into their daws. Then I just need the faders and knobs to work.
Agree fully.
@Martygras and @Jakersjaw no need to wait. Check out @dwarman and secretbase's answers.
I would just like for it to work in cubasis and auria. Without buying midibridge. Just like in cubase on my desktop.
But thanks for the answers thoug. Never fails to get help on this great forum.
My nanoKONTROL2 and Graphite both have Mackie HUI machine control modes that work with Auria. Maybe your controller does too? I cannot find it in Cubasis though.
Trying in auria now. But can't seem to make it work. Can you explain the setup for me? The receive and send in auria.
Does your controller have HUI emulation?
Probably not. Can't find anything in the manual about it.
This may be of use:
Start/Stop (MMC)
Start: Sysex F0 7F 7F 06 02 F7
Stop: Sysex F0 7F 7F 06 01 F7
This is what I used in my MIDI Designer Pro template for SECTOR.
MidiBridge is a great app that I recommend having in your toolkit. There have been many times over the past years that I've fixed inter-app midi issues simply by launching the app. Seriously.
lol. this makes absolutely no sense to me
But thanks anyway
@Jakersjaw yeah, sorry about that.
Well, purchased midibridge and did as described in the audeonic link. No dice. Not even in auria. I'm totally new to this midi thing.
Now that i have seen your post about Sysex and some numbers i understand why i became frustrated and thought i was stupid when using midi bridge.
Couldn't pull this off with Auria/MDP either. Double checked everything...used sysex in MDP with the suggested start/stop hex codes, verified that Auria was the target, verified in Auria that MMC was coming from MDP and toggled between the different Mackie protocols. Stumped!
Curious, do you see your controller in MidiBridge on the left hand side? I know my QuNexus ports show up.
@Jakersjaw -- I'd suggest asking on the MidiBridge forum, or sending email to the developer. I'm reasonably familiar with the app, and I think Clif/Apptronica is too, but the best bet would be to go to the source.
@Proto -- wrt the Sysex stuff -- MIDI messages are basically a series of numerical codes. They did it this way to make the messages really short, and easy to build hardware for (it got started 30-ish years ago). Think of it like Twitter hash tags -- if you don't know what they're doing, it's cryptic, but once you know the system, it's pretty easy to understand. #lol #midi-ftw
The start/stop message is a series of numerical (hex) codes -- when a machine sees what's essentially F0 7F 7F 06 02 F7 go by, it starts. The stream byter can see some batch of MIDI come in, and transform it into another batch of MIDI -- and that's the suggestion here for how to rearrange things to get transport control working.
@apptronica
Yes I se the controller, and it responds when I pres the buttons.
@SecretBaseDesign
Think I will try on their forum, thanks
@Jakersjaw have you tried creating a link between your controller and Cubasis (or whatever)? Just select the controller on the left and then click the app on the right.
Without activating the streambyte?
I've tried it with the streambyte activated, and then select auria/cubasis as the receiver.
Can't find a setting in cubasis, to choose midi input.