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.
Logic Pro for iPad send midi to another channel
Is there any way to send midi data from one channel to another without third party software? If not, how to use plugins that have multiout, like mirack?
Okay, the story with bus idiocy is still somehow solvable, though strange, but how to use plugins that receive midi data multichannel?
Comments
Create a track-stack, the top track will send midi to all tracks in the stack
Lol. I need 8 tracks to send different MIDI data to mirack, I don’t need stack because it’s doesn’t solve the problem.
You can technically do that, whether or not you find a way to make it practical for you is another matter.
Each midi track in Logic can have multiple midi channels recorded into it. You can select any note in the piano roll and change the midi channel of just that note.
So what you can do is create multiple tracks for one instrument (the workaround for this on the iPad is to make a midi region and put in as many separate notes as you want tracks and then use the Oman’s to separate by note pitch resulting in multiple tracks pointing to the same instrument — this is different to a track stack).
i do this for Pure Acid so that I can programme the drums separately, and have made a template so the drums are all mapped to midi channel 10 and the bass line synth plays back on channel 1.
If you mess up, you can select all the notes in a region and change the midi channel of all (or any) of the notes.
if you’re working on part 1 with MIDI channel 1, set the midi for the track and then everything you record will have that channel set. You can then change it for subsequent parts. The built in keyboard can be used for this too (it will output on whatever midi channel is set for the instrument). You just need to remember to change the midi channel each time you add or record notes.
Having each midi channel in a separate lane as per the screenshot below is optional but makes it easier to keep track. There’s nothing stopping you setting each note in a region to a different midi channel.
I feel like the scripter plugin could probably do this, but the editor is only available on MacOS.
Using the environment in Mac Logic this routing would be super easy to do but I guess Apple left out that part completely in the iPad version...
Its not too hard to change the midi channel for each new part you record in the inspector... As you can see above, I've got one part playing the bass synth on midi channel 1 and another playing the drums on channel 10. Both tracks are part of the same instrument.
The environment would have made it easier, but it's still doable now.
I was thinking about routing multiple tracks to an AUv3 plug-in hosted on one track.
(For example If I was to sequence one instance of GR-16 or BeatHawk using 16 tracks in Logic).
I think that’s pretty much what I’ve shown above isn’t it?
In my example I have Pure Acid on one track. I have two regions on separate tracks but using the same instrument. I did this by separating the regions via pitch to get the extra ‘lanes’ for the same instrument. Logic for Mac has a command to make a new track with same instrument — this is the workaround to achieving the same thing. Only takes a second.
One region/track is playing the bass on midi channel 1, the pattern region is playing the drums on channel 10. In the pattern editor you can set each row to transmit on any midi channel you want. I set them all to 10 and saved the whole shebang as a channel strip preset so I don’t have to set it up again.
There is just the one instance of pure acid, receiving on 2 separate midi channels.
I tried the same, but it’s doesn’t send MIDI data to different channels,also I tired in pureacid without luck.Notes or region, doesn’t matter.
It does work. I’ve just tested it and it works perfectly.
You have to set pure acid up in the standalone version to set the MIDI channel the bass and drums receive on.
The midi needs to be recorded with the correct channel (or set to the right channel afterwards).
I’ve setup pure acid like this:
As you can see I’ve got the drums outputting on channel 10 in the inspector.
And the notes on channel 2 (I just changed them from 1 to make sure it works as it should). I also had another separate pattern editor with p-locks for cutoff and resonance. All worked exactly as I wanted it to. You can set any note to any channel in the inspector.
You then need to set the main track to be outputting in all channels.
For me doing that just creates a duplicate instance of the AUv3.
So the instance gets copied with all the settings it’s still a duplicate instance taking up more resources than using one instance fed by two tracks.
Oh well, I very seldom use multi-timbral AUv3s so it really doesn’t matter that much.
It doesn’t work at all. I checked MIDI monitor, so data is sending from channel, but not receiving by pure acid channel. I tired with external instrument (logic plugin) and without.
I didn’t use multiple instances. All my tracks in the screenshots above are pointing to the same auv3. Single instance.
To get multiple tracks, create a midi region and add a note or three on different pitches. Then tap the region then select ‘Convert’->’Separate by note pitches’.
This creates multiple tracks for the same instrument. Then just delete the regions the ‘separate’ command created and you’ve got multiple tracks.
i do this all the time in Logic as I often like to have separate regions for example, having the main note data in a normal midi region and a separate automation in a pattern editor region to get p-locks. Having separate regions means I can loop regions of different lengths too for poly meter type effect with the automation say repeating every 6 bars over an 8 bar midi region.
The screenshot shows that maybe you are running different instances of pure acid on the channels ?
Oh, now it makes sense! The main thing was to do this Convert’->’Separate by note pitches’, which you forgot to mention (or I didn't notice it in the post). Great, now it actually works, though the way to do it is of course EXTREMELY weird. Thanks more for your help!
What I showed above 100% works.
You’ve got the midi out on the track set to 1. You need to edit the notes to output on whatever midi channel you want and set the track to ‘all’ like in my screenshots above.
Each track created by ‘separate by note pitch’ is the same instrument so change the track setting on one and it changes on all of them. So if you have all the pattern rows set to channel 10 but the tracks midi channel set to 1, the tracks setting overrides the notes as it is higher in the hierarchy.
The trick is to change the midi channel of the actual notes in the piano roll. You do this in the piano roll or pattern editor after the fact or just write the data in on the correct midi channel in the first place. You can do that by setting the midi channel in the track inspector, play the built in keyboard then set the track midi channel back to all when you’re done.
If you paste in midi or move a region from another track, just open the region in the piano roll editor, select all notes then set all the notes to the correct channel in the notes parameter panel.
It’s fiddlier than it needs to be — But it most definitely works.
I did mention it, but auto correction changed ‘command’ to Oman’s, but I did mention ‘separate by note pitch’.
This is a weird workaround indeed, but gets around the fact that the iPad version of Logic lacks the Macs version’s create track with same instrument command.
You can’t access the bass synth directly in pure acid without doing this so it’s worth the effort. I don’t like the bass sequencer in pure acid. Too much like hard work! :-D
Glad you got it working :-)
Got it to work
Super nice ‘work around’ thanks for the tip!
Cool glad you got it working :-)
Thankfully my controller (CME XKey) has a quick way to change midi-channel so I don’t manually have to change the midi-channel of the notes.
This kinda makes me wonder why midi out channel is absent in the region settings and only present in track settings!?
Now the next ‘challenge’ is to set up ONE multi-out instance of KQ Dixie, control each part with individual midi-tracks with dedicated audio tracks for each midi-channel…
Good workaround that seems to further proof that Logic 4 iPad was rushed somehow…
Why would that “new track with same instrument” option be missing when it’s perfectly achievable via a hard-to-remember hack?. Same case as the multi-out avu3, or midi control of audio fx. All things that can be done via weird workarounds.
I find this kind of stuff very annoying. Instead of being relieved, every time I encounter one of these “you can do it, here’s how…” workarounds I feel like it’s non-pro. I think on iOS we’re too used to just hacking our way around. Come on, when a useful feature is possible and already there, just add the menu button!.
BTW I was going to thank Oman for the tip! 😂
It was not quite ready for the masses…but I was sure enough ready for it…grateful to the max 🤗
It can be annoying yes, but at least there are functional workarounds. The main bones of the app are solid though and LP4iP allows me to make music the way I want to on the iPad. At last.
I'm able to use Logic pretty much the way I want. It's a massive leap forward over every other iPad app I've ever tried. Most of the workarounds (like the above) don't usually affect me in the slightest. I'd only ever need to mess with multiple MIDI channels for Pure Acid to avoid using Pure Acid's sequencers in Logic. And when I[m using logic I always want to use logic's sequencing as that's the whole point to me. I don't want Pure Acids' stupid baseline sequencer when I'm quicker and more comfortable using' the logic plano roll AND I want to see the regions in the timeline. I want to be able to adjust the parameters of the regions to save me multiple trips to an editor to adjust timing, transposing, muting, looping etc.
The missing commands are missing for a reason. There's only so much of Logic for MAc's UI you can fit on an iPad. Some of those choices will be permanent, I'm sure others will be addressed.
On the Mac if Logic is iLogical to you, you can use Cubase, Live, Bitwig, digital Performer, Reaper, Studio one, Traction, ProTools, Reason etc.
We don't have those on iPad. We do have a whole host of unique, fun and creative ways of making music, but if you want a traditional desktop class DAW it's Logic with all its flaws or a massively cut down version of Cubase.
For some reason people don't complain about the missing features in Cubasis anywhere near as much as they do about Logic. And Cubasis is a very, very long way short of Cubase. Far more so than Logic iPad to Logic Mac that's for sure.
As for the word "pro", that's an argument that is getting boring. In Apple speak "Pro" means "Luxury" more than "Professional".
Most "pro" musicians wouldn't use an iPad to record their band. The iPad is always going to be a different class of device, and I'm glad it's so different. For most uses, a MacBook Air is a cheaper and better platform for making "pro" music than any iPad "Pro".
Pro Shmo. It's a pointless argument. Gorillaz made an album or two on the iPad. They made money from it. So it's Pro. Even though they used GarageBand. Which isn't.
I also want to use Logic’s sequencer. And I want to use Logic for multi-out auv3. And to modulate an audio fx parameter with an LFO.
Is that luxury?. Ok, so on a luxury product I want multi-out without having to go through some hacky workaround. Specially when it’s already there!. Please don’t use the “not enough space on menus” as an excuse.
It feels to me like you have a slight “if you don’t like it use something else” attitude in your response, and I don’t get it. There’s a variety of features that are obviously useful and demanded that currently require some hacky workarounds on the iPad. Shouldn’t be the case, they should be properly implemented and available. How is that controversial or debatable?. It’s not “Logic with all its flaws”, it’s Logic and hoping they fix the flaws, specially in these cases where it’s just a matter of making these already possible features available via a proper UI implementation.
Nah. My point is that we are not blessed with Logic calibre (or better) alternative apps for iPad. It's the best we have for that kind of app by a country mile.
The workarounds enable some features, but there's literally nothing else on the iPad that lets me do things I take for granted on the Mac.
It's far from perfect and desperately needs that first big update but it's a pretty good start.
I'm not making excuses for Logic. The whole of music making on the iPad is a stack of hacks. We're on a forum born from a hack to get audio apps to even communicate with each other. Everything I ever try to do in any other app needs a ton of hacks to get anywhere. Most "DAW" type apps have huge gaping holes in their feature sets or just don't work properly.
In the meantime, you can use annoying hacks to do the things you want, which is better than nothing.
So basically what I'm saying is the annoyances are there and I'm not making light of them, however it gets me so much further down the line than any other app that it's not even close.
Logic might suck but it's the best there is for my needs, hacky workarounds or not.
To be fair, as a Logic on Mac user a lot of the issues don't bother me as I'm so used to doing thing the Logic way. I've used it for 30 odd years. It's second nature. As new features got added I just learnt them the way they were implemented and never needed to learn the whole app in one go. Logic was MIDI only when I started.
For example I don't bother with multi output auv3s. I've never found the benefits worth the extra effort, I prefer using multiple instances instead, works out far easier and doesn't seem to consume any more resources in my experience, so I've basically tried and discounted loads of workflows to come to a happy middle ground where what I want to do gels with the way Logic wants me to do it. I never use multi outs on Mac so I sure as hell won't bother on the iPad.
I did want to be able to programme Pure Acid's bass synth from logic rather than use the built in sequencer so worked out how to do that. Maybe it is a bit hacky but once I'd worked it out I didn't worry about it anymore.
Anyway it's all good... I was just trying to help someone out.
I have the same needs with modulating audio fx parameters, it can only use modifier to modulate fx in midi synthesizers/plugins. That's too bad, it's severely lacking.
tahiche came up with a hack to modulate fx in audio tracks using a side chain as a workaround.
https://forum.audiob.us/discussion/57484/modulate-audio-fx-in-audio-track-sidechain-midi-modulation-hack
Really?. This is interesting… so If I have a multi-out drum app (Drambo, digistix, Fac Drumkit, whatever it may be…) having one instance with multiple outs is similar in resources to having 8 instances in different tracks?. I surely wouldn’t expect that. Itd certainly be a lot easier.
Don’t know on the iPad but on the Mac it seems to be the number of notes actually playing that affects the resources the most. I think Logic does a pretty good job of optimising multiple instances.
If I duplicate a track containing, say, an instance of Alchemy the CPU meter doesn’t even nudge. Playing two instances doesn’t seem any different to the same number of notes In one instance. But it’s been a long time since I bothered testing as I just stuck with multiple instances when I realised it suited me personally much better.
To be honest with the M1 Macs I rarely get close to taxing the system.
If I was running out of CPU cycles I’d run more scientific tests to see what’s optimal but duplicating instances suits me better. Especially for say a drum kit which doesn’t tax the cpu at all. I just duplicate the track to have different fx on different hits and find that much easier to manage.
It suits my way of making music anyway.
It doesn’t matter iPad or Mac. Each plugin instance loads the CPU core, just DYOR and see the difference in CPU utilization of a mac or iPad in multi-out mode and without and see the difference, it's not just there - it's huge when there are a lot of tracks.