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.
Comments
Update of Teraverse is now available, no longer crashes wavetable presets.
But there is no sound with Wavetable presets. That's something that has to be done...
yes; a sample/ wavetable section in Add or the block sequencing/ morphing from AddStation, where each block is an instance of Tera!
Not sure how useful that would really be? AddStation is an additive synth so by design, it works with sine waves. If you try and do additive synthesis with 512 harmonically rich waves (like most wavetables), things can get very noise very quick.
I see; thanks for explaining.
Just uploaded a new version 1.4.2 with a new MONO/POLY button instead of a menu.
It's also possible now to directly write an App Review / make a Rating.
Please test this function intensively
Awesome. Thanks.
@VirSyn Bumped into an interesting ‘bug’…
When selecting the ‘Formant Filter’ it’s shown twice in the patch!?
Guess it’s a bug since they both share the same values and editing one changes the other
@VirSyn , I sent an email but I thought I would try here too.
Would it be possible to add the ability to save presets as favorites?
That would be so great.
Favorites list, yes please.🙏🏼
Anyway, came to ask if anybody knows this problem with Tera Pro: No matter what I do, pitchbend is four octaves. The normal pitchbend setting does not work, and the MPE-pitchbend setting does equally nothing (not running it MPE).
And it is ALL the presets. I run it inside AUM as auv3. (I also tried running it stand-alone with same result.)
Definitely on my list.
That sounds strange. Couldn't reproduce here. Have you checked the the BEND setting in the COMMON module ?
Each preset can have its individual pitch bend and some presets have 48 set here.
Ah, thanks for checking in here!
Yes, I have the issue no matter what the PB setting in Common is.
I have tried rebooting the iPad also, but issue persists.
Hi Virsyn,
I have now unistalled Tera Pro, rebooted iPad, re-installed Tera Pro, but still no matter any pitchbend settings, all I get is the 48 half-tones (four octaves).
What to do?🤷🏼♂️
I also installed Tera Pro on another iPad. Same four octave pitchbend all over.
And nobody else has this problem?
I am using a seaboard so the pitch bend is as it should be with 48 semitones. But I am having my own issue..
I am having trouble removing/reducing the velocity sensitivity of patches - even without any ADSRs being connected to velocity in the modulators. It really affects playability of MPE patches, I cannot lightly press notes and gradually press down to increase volume, as the maximum volume from there is much much quieter than if I press down hard initially.
Any help would be greatly appreciated!
With controllers like Seaboard or Linnstrument you cannot expect any synth “factory” preset to behave like you want it to.
My best advice would be to program a patch from scratch, and thereby learn how to setup velocity and pressure parameters so that they work right for you. Then you will become better at translating that to other patches.
Thanks for the response, @LarsDaniel ! So I am referring here to patches designed from scratch. I agree that it is a lot to expect for factory presets to work out of the box, unless they were designed with our controllers specifically in mind. My issue is that it seems like some of my patches are somehow automatically velocity sensitive (even from scratch), and I see no velocity parameters to modify. But after having another go at it this morning, i think that what was causing me trouble was the “Damper” setting on the Karplus module. Without that enabled, the volume difference is much less pronounced. So possibly the damper is velocity sensitive?
The Pitch Bend setting in COMMON works as expected for me. The one catch I saw was if there are two layers (top bar shows A+B), there is a bend setting for each layer, so you need to change both to get the correct effect.
Have you maybe enabled MPE in the app settings, so you're using the MPE value? Note that your MPE controller may be enabling MPE by sending RPN 6. You could check this with a MIDI monitor.
Thanks!
It is not the dual layer thing. But good idea to check if anything looks suspicious with a midi monitor. Will do.
Ok, with my iPad isolated from the rest of my system, pitchbend works as it should.
(I remembered that the Moog Model D has a pitchbend wheel, so I could route that midi to Tera.)
So it must be a faulty MPE enabling somewhere.
So, try changing the MPE bend setting, and see if it takes effect. That could prove that it's using MPE.
Well, the odd thing is that no matter what the MPE bend range is in Tera, it responds with the +/-48 range.
But it gets even weirder. Actually this is probably the hardest midi riddle I have had to solve in my 38 years of using midi.
So, the setup is Keyboard (Matriarch) into Hapax. Hapax into AUM on iPad, here midi goes to Tera (auv3). Bend on Tera is now +/-48 no matter what.
So in AUM I setup a Model D and route its midi to Tera and then bend behaves exactly as expected.
So at the same time, I have this instance of Tera that reacts in two different ways, depending on who is sending the pitchbend.
I tried connecting the keyboard directly to AUM (not through Hapax) and then pitchbend was normal.
I looked at the midi data going to Tera, and the pitchbend messages coming from Hapax look different than those from the other sources. But I am not a coder/midi tech so I don´t know what that implies.
I tried a couple of other synths to see if any of them had the same weird +/-48 bend: Synthmaster 2, normal. Trooper, normal. But Bleass Alpha, same +/-48, while doing a bend on its built-in keyboard was +/-2.
So I assume we are talking about an MPE bend thing, that some synths respond to and others don´t. But why the hell is Hapax transforming the Matriarch pitchbend into something that apparently is an MPE thing?
I guess I will have to write the Squarp team an email.
EDIT: Trying to get somebody to confirm the weirdness over at the Hapax forum now.
@LarsDaniel Could you post a screenshot of the different pitch bend messages coming from Hapax? Also, do you see any unexpected CC messages coming from Hapax, like B0 64 and B0 65 (all values hexadecimal)? Those are the way you select a MIDI Registered Parameter Number (RPN). They might indicate that it is configuring MPE, or Pitch Bend, to suit itself. If you could post them, we could tell what is happening.
@uncledave I have worked on this all day now, and it all boils down to this:
If I send to Tera on midi channel 1, all is well with bend. I assume that this is because ch 1 is the control channel in MPE. If I use any other channel than 1, I get +/-48 bends. If I go into the settings of Tera, and set it to recieve on a specific midi channel, say ch 3, one would believe that it would know that it should not be doing MPE, but no.
I wonder if you can duplicate this?
(About the NRPN: nothing is received. Also, just for good measure, I set AUM to filter out all but note and PB.)
@VirSyn At your end, does Tera respond to normal bend if not on midi channel 1? And why does the midi settings not seem to work? (As in the above example).
Yes, I see the same thing. Notes sent to Tera Pro on MIDI Channel 1 use the Pitchbend setting in COMMON. Notes on other MIDI channels always use a Pitchbend of 48 semitones, ignoring the MPE Pitchbend setting. This is true even if MPE is enabled.
So, your workaround is to use MIDI channel 1 until this is resolved. If you cannot do this, you could insert StreamByter between the controller and Tera Pro, with the following one-liner:
Remember to Install Rules and it will do the job.
@uncledave Thanks for confirming this. 👍🏻
And yes, I was thing the same about having a midi processor inserted before Tera. Because I do like synth.
Hi @VirSyn!
I wanted to write to your support, but you have no support link on your website. I found a contact form, but it seemed broken, as it only lets me write in capitol letters, and it makes you look like an idiot with caps lock on. 🤷🏼♂️
But here is my bug report:
Tera Pro (as AUV3 in AUM) only responds correctly to pitch bend on midi channel 1. Also, the settings regarding midi channels does not seem to work at all, and likewise with settings for MPE bend. It only does +/- 48.
Also, when using Tera Pro in MPE mode, there does not seem to be any way you can set the modulation destination of channel pressure. I tried using midi learn, but the learn function does not recognize channel pressure. In general, I would say that having ONLY midi learn, and not a way of manually entering (via typing) you desired source, can in some cases be problematic.
So for now, Tera Pro is not usable at all for MPE, and is only generally usable (if you want to use pitch bend) on midi channel 1.
@LarsDaniel Sorry about the bug. In the meantime i tracked it down and this will be fixed with the next "Second WAVES" update coming very soon.
You can use the MPE Controller like Timbre (CC74) and Channel pressure (Aftertouch) simply by using it as a modulation source in any modulation slot. No need to use MIDI Learn.
Thanks! This is good news.
Recently got Tera Pro and a few days later,the Wavetable IAP. It can sound very good and is deep, while the interface is IMO logical and neat. But, I've had crashes using it in Drambo. In the latest crashed project I had three instances of TP: Touching a Drambo knob mapped to a parameter in one instance repeatedly caused all instances to crash, My iPad is 5th gen and it's on OS13.3. This project had TTAP and AUX Space in the send slots, and the there was only one AU processor in the thee racks with the instances of TP (a chorus). There were no CPU spikes and CPU usage was at about 40 to 50 percent. I'm slightly hesitant about updating the iOS because everything works pretty well and I don't want quicker battery drain or more CPU usage that the latest ios could cause. But, if it would make TP stable, I'd do it, but I'm doubtful this will be the case.