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.
Surface Builder not letting notes through
Hi guys, I've made a control surface in surface builder in Logic 2.0 for ipad, thing is when the plugin is enabled notes from the piano roll and from midi regions/clips don't reach the synth so it doesn't play. I've added a keyboard object in surface builder and that doesn't play the instrument either. Anyone know what I'm overlooking here? Edit: intermittently the keyboard object does send notes out of surface builder, but Logic's own piano roll and clips do nothing.
Also. The mapping via midi learn intermittently doesn't work after a few minutes, same thing happens with LK midi control surface.
Also does anyone know what the 4pockets support email is? The support link in the app store doesn't link to the correct website.
Thanks
Comments
support @ 4pockets.com
Thanks 🙏
So I think I've solved the issue and I think these are the steps that solved it. First thing is to set Logic to run in the background, seems that every time it closes or (I assume) unloads itself from the RAM midi plugins stop sending midi cc down the plugin chain. Sometimes it decides to stop running and reload in either case, at that point surface builder stops sending CC. The way to fix this is to play a note on the piano roll, now that the track receives a midi note suddenly the plugin can send out cc again. This behavior happens with other control surface plugins too.
To solve the issue of notes in a midi clip not playing the instrument, you long press the midi plugin tile, and select on "record midi to track here".
The logic piano roll still doesn't work though. I really hope a connected midi controller will.
On further testing after connecting Digitakt as a midi controller. The moment I learn a Digitakt knob to a surface builder knob, that knob stops sending midi cc to the AUv3 synth. Is this supposed to happen? I fail to see the point of mapping a midi controller to surface builder if it stops sending midi cc to the plugin it's controlling.
I have disabled "logic pro virtual in" in logic settings, I have no idea what that setting does, could that be the issue here?
Also midi note on messages from Digitakt don't get through to the AUv3 synth at all. I've checked all the Digitakt settings are correct and it's basically functioning as a midi controller, logic is definitely receiving notes and cc from digitakt
An app can create Virtual MIDI In and Out ports. These can be used to interconnect different stand-alone apps. Since you're just using a hardware controller with Logic Pro, you don't need the virtual port. I assume you're loading Surface Builder as an AUv3 plugin in Logic?
Yup, correct. Thanks for clarifying
I’ve tried that and received no response, regarding the control pass-through question. I do observe that the last time I checked the URL there was no active site, so I have to wonder if anyone’s monitoring.
That's unfortunate
. How long ago did you email him?
I tried using loopy pro as well in Logic to do the same thing, it should technically be able to. But it straight up crashes whenever any midi message gets transmitted through it
I believe you may have set up a feedback loop. As I understand it, you were sending midi from loopy pro AU to logic’s virtual in port (rather than the Loopy AU midi out) and were also listening to Logic’s virtual in.
Normally, you should send the AU’s midi to the AU’s midi output port.
I believe the question is how to set up Logic so that works.
I actually turned logic virtual in off entirely in the whole DAW and used the MIDI out option in loopy. Yet still pretty much any note (or cc to I guess) going into loopy crashes it. It works just fine in cubasis, and other midi control plugins work fine with logic. Something with how the two interact is causing loopy to crash
Sorry double post
You are correct on that point. As odd as it sounds, that is how Surface builder works in any app, not just Logic. I believe it's an oversight on the developer's part. It's been reported earlier, but would not hurt if you report it again. It's a big shortcoming of the app.
(also pinging @4pockets_paul if you're out there. 😉)
Paul is usually good about email to the support address, but I think he's a bit like me ... when eyeballs deep in a fascinating new project, sometimes email gets overlooked.
Okay. So I've mailed him too. Hopefully this gets fixed.
Meanwhile i'm looking for a similar plugin, all I'm trying to do is make a bank of macros for an AUv3 and control it with knobs on a midi controller. This should be this complicated 😄. Any suggestions?
Do you by chance have Loopy Pro? That would be excellent for this.
I never tried it, but maybe Knob Lab. It’s free to try in a single knob configuration.
I do. But I've been trying for 3 days straight to get it to do this with logic but it crashes every time and doesn't send out any midi cc
Thanks for the suggestion. I believe this doesn't have an Auv3 version? I need it to be a midi insert
oops. I assumed it did have an AUv3 version.
TouchOSC in popover mode maybe? I don't have Logic, so I can't say if it supports popover mode.
I'm not sure that would work, I believe OSC needs to be open to send midi data. The issue is I'm using a Digitakt to sequence midi cc by parameter locking them on several different tracks. If I open / select a different track then touch OSC on the first track will stop sending CC. At least that's as far as I'm aware. Correct me if I'm wrong
I can confirm that LP does this well, and does a lot of other nifty stuff as a Midi plugin/controller. I’ve never tried it in Logic, though, only AUM. My only resistance to it is the limitations on UI design.
I’ve tried using TouchOsc but it’s a nightmare to program on the iPad, the script language is miserably documented, and it’s not AU, which means I’m back to doing the app-switching thing - which I just can’t get comfortable with - or using a second iPad as a control surface, which I still can’t do consistently.
OP’s problem using Loopy Pro seems specific to Logic Pro. And might be related to setup as they are seeing no midi output from loopy pro in logic.
If you replace loopy pro with lk in your Logic Pro project and have showmidi after lk, does ShowMIDI see midi sent by lk’s faders or keyboard?
Yeah. Any plugin that maps (including LK) shows cc coming out in "show midi". Loopy pro crashes the moment any sort of midi message passes along the track its on when an instrument is also loaded
In order to understand what is going, let’s take this one step at a time to understand what is happening. You mention loopy crashing when midi “passes along the track”.
Let’s back up a little and gather a little information that may help identify the source of the problems. Sorry if these seem redundant with any troubleshooting you have done but I’d like to see if we can isolate the relevant details.
If Logic’s transport is not running, does moving LK’s faders on LK’s controllers page (set to send to LK Out) send midi to ShowMIDI?
If you replace LK with Loopy Pro and have (for test purposes) a project with no midi input and no midi bindings and only a fader widget that sends a MIDI CC to Midi Out, does moving the fader show midi n ShowMIDI?
Try all of that without Logic’s transport running.
When TouchOSC is used in popover mode, it is open and in the foreground. It will work with any app that supports popover mode. However it has to be on-screen covering up shit that you want to see, so its a pain.
(actually I think the right term is slide over mode)
Hey. So yeah, LK registers in showmidi. Loopy pro does not show anything at all in ShowMidi.
And loopy crashes if I touch a note on the logic piano roll. That's pretty much all there is to it. The reason I mention this is because sometimes other plugins like LK need to "hear" a midi not in logic to activate, otherwise they sort of "time out" and stop sending CC, this happens usually after minimizing logic
Can you confirm that each of these is true:
I am making sure because these little details may be important and I haven’t seen confirmation that they are true.
It is sending the cc to midi out
What is a project profile and where do I find it.
Also, wanted to say thanks for all the help.
Profiles are where midi mappings are stored. Choose Control Settings and you will see the profiles listed. Tap on them to see if there is anything there.
I apologize for all the questions but I am running blind on this since I don’t have a device that can run Logic and sometimes little details turn out to be relevant. Otherwise I would investigate myself. Apparently, not many people are using Loopy this way in Logic as this is our first report of an issue.
I just want to narrow things off before handing the info off to Michael who is working round the clock finishing up the new release.
There's a "default" profile in there, opening it says "there are no binding yet"
Fyi. I inserted loopy as an instrument instead of a midi plugin. Now it sends midi cc (I was able to control an FX plugin). Problem is I can't control an instrument because IT is the instrument. Sending midi from it to another track doesn't work as intended either so this doesn't solve anything, but shows that something is messed up with the using loopy as a midi insert. Inserting another loopy in as a midi plugin causes a crash if there is already a loopy in the chain