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
Has anyone noticed that when inputting modulation in the rise and fall, I always get too short a time, even when the knob is turned fully clockwise? I find this design a bit strange and I can't get the right amount of modulation
@brambos
There is also the osc tune knob. Every time I try to rotate it, it struggles a bit. I like this app, but these two issues bother me. In particular, the modulation range of rise and fall makes the application of this function very narrow. It can basically only make some very short random length percussion sounds.
@brambos
Drag straight up and down. The way the knobs are designed, they work a little bit odd as you move away from vertical. This facilitates them moving more slowly the farther away you move from the knob, but it can throw one off a bit if you're not used to it.
Turn up the curve knob for longer times. Down for shorter times.
Curves are more about changing the way env works than length, and env that works logarithmically does sound longer, but to a very limited extent, and even if the curve is completely clockwise, the rise and fall times are still too short when the modulation source is inserted, which is completely different from when the modulation source is not inserted, so I think it's very likely a design mistake
Can anyone think of a way of using other modules to make the LFO CV unipolar?
I haven't been able to come up with any. However, if you load the FX version, you can jack in an LFO from an outside source such as Drambo's LFO in non-polar mode.
Got it, I'm glad it wasn't just me trying to work it out. That's exactly the solution I've been using so far.
From what I’ve gathered from my modular learnage (learning?), a bipolar lfo will go above and below a threshold (usually 0, so -1 and +1) where a unipolar will only go one direction (Either + or - instead of both)
So let’s say you’re modulating a filter cutoff that’s already open halfway. Unipolar will open it up all the way then go back to half open, where a bipolar will sweep between closed and open.
With unipolar you can set a parameter to the highest or lowest value you want and modulate only in the other direction.
Could you use the wave surgeon for that? Wouldn’t give you full range, probably, just half (with a flat section where the other part of the waveform would have been), but I think it’d make the thing just go one way or the other from zero. I was wondering if you could use the utility section to play around with the offset, too, but I’m not sure if that would work, depends if the attenuators apply an offset voltage if nothing is plugged in. It’s all a bit ”not quite but almost”, though.
I couldn't come up with any solution that worked with the wave shaper. Could be I just don't understand it enough though.
For that application, you could achieve the same thing by instead setting the filter at 75% and halving the LFO amplitude so that at its lowest point the filter hits 50%. Or whatever numbers achieve the filter oscillation that you want.
Positive or negative modulation depth. In Drambo for example if you turn the mod-dial to the left (down) or right (up).
Hmm. Turns out my suggestions don’t work according to the Ape Matrix scope plugin.
Apologies, people: as you were…
Thanks everyone, I think I can achieve what I wanted with the utility module. That said, now I'm not sure if the behavior I'm seeing is really about polarity: should
lfo 1 out → vco 1 cvjust work?Just work to do what? To modulate the vco1 pitch? If so then yes.
Yeah, I'm not seeing the expected results when LFO shape is a square (I get constant pitch with brief interruptions instead of pitch alternating between two values for the same amount of time) or saw up/down (pitch oscillates as if it was a sine/triangle LFO instead).
A square wave is almost like a gate so it turning off (interrupting) your oscillator kinda makes sense. And yes, a saw wave lfo is a lot like a sign wave but just less smooth. Like others, I’m not sure what the results are that you’re looking for.
A screenshot of your routing would probably help immensely
Don't know off the top of my head, does the LFO have Pulsewidth? If so check, if it's set to 50percent, so the positive and negative parts are equal in length.
Edit: maybe a shape parameter, that changes Pulsewidth on the square and fades from upsaw over triangle to downsaw when saw is selected.
Further thought, this time I’ve tested with a scope and I think I’m right for once (FLW). 🤣
If you loop the envelope then you get a proper unipolar LFO (you have to fiddle with rise and fall times to change frequency and shape). But… you can’t do a square wave (just triangle/saw variants), as turning on sustain just kills it stone dead, and of course you then haven’t got an envelope. Possibly you could fake it with synced LFOs to shape the VCA or filter, but it will just cycle regularly so it’s limiting rhythmically.
I think you just need to take the amplitude down. The pitch of the oscillator is just dropping down below audible range. If you patch it to
utility in 1, andutility outtoeco 1 cv, then turn down the attenuator to +20% (about 1:00) or less, you'll get the expected results.[edit] nvm. Still doesn't do what I expected. 🤷🏼♂️
That square wave isn't looking like a square wave on an oscilloscope.
This is what I'm trying
Instrument/- Init -presetI'm not saying this is a bug but I'd like to understand why it works this way.
Edited for clarity.