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
Beat to the punch
Sure !
In operator A, select a « texture » which is basically « a noise », like « click », « splotch », « crouch »...
Then modulate this operator A through a new operator B and choose « resonator » for B.
send operator B output to the main output.
In operator A, try selecting different noises. Some will get you a guitar, a koto, a mandoline. You may also adjust the attack, shorten the decay, etc according to velocity time.
In operator B, try adjusting the feedback in positive values as well as the cutoff feedback to get the most realistic and organic sound.
That’s it !
Then to go further, you can add another noise triggered by note-off and also going through the resonator to simulate the noises when fingers are lifting quickly from the fretboard.
Enjoy.
Yeah. You can spread things out a little bit more with the chorus, but I'd love to be able to pan the Ops separately and be able to assign each pan to a modulator, essential for wide moving pads. I'm currently putting it through a stereo widener in AUM to get a wider sound, but it's not quite the same as being able to pan and move each sound source around individually.
Regarding the paning of operators:
All operators are mono by its concept - adding a pan to any of the operators would require stereo compution of the opator that gets input of this op, requiring the a doubling of computation. And this for every of the active voices.
So in my opionion, the only possible way for panning (without the need of more complex computation) would be to add panning just to the final mixing stage - the lowest row in the matrix.
In addtion to the need to add new UI knobs (where ?) and also the option to MOD these pan-knobs like the op‘s volume, the other thing to change is to compute the chorus with stereo input (should take too much additional computation). The delay and reverb already are computed in stereo as the first FX (chorus) outputs stereo.
Regarding re-arringing of the half-matrix:
I already had to re-order OPs to maybe insert a new modulator infront of others - the SWAP operation only ‚flips‘ the OP settings, but not the matrix volume/mod settings. It‘s clear that op B has less matrix parameters than op D - but if the possible ones would also be swapped by the operation such a re-arrange would be less pain. The routes previouly not available should use ‚zero‘ volumes and MODs.
.
Here an example, i have the following routing: A and B mod C that is output as shown on the left block of the image below.
I want to re-arrange - so that D is infront of B, allowing for modulation of old-B and old-C.
To re-arrange, i swap D and C, and then the just swapped C (ex D) and B. This currently results in the center block of the image.
You clearly can see that the Matrix volume (and also MODs) were not updated - the patch sound totally different.
BUT if the matrix would also be swapped for the knobs/MODs that are possible, that would result in the block shown on the right, which which sounds the same as the initial patch - and has a free op B (ex-D) to be used to modulate C and D.
.
Maybe someone should propose this simple change as feature request
Very relevant !
I just sent this email to the developer to ask about panning, but it was before realizing that operators were probably operating on 1 channel only :
« Just a small question if you don’t mind.
I was wondering if you would consider adding a pan control for each operator so that we can create stereo presets. Because other than by adding some delay/reverb at the very end, I don’t see how not to get only mono sound. Maybe I am wrong and missed something.
In my opinion, the best and easiest way to do this would be at matrix level : the same way we can choose between « level » and « mod » view, we could tap on « pan » view to modulate the pan of the incoming signal from one operator to the other ones. »
I think we could just add that only the bottom line would be assignable regarding panning. I think also that Chorus could be modified to process in stereo without to much trouble (all Virsyn synths do this), if ever it is not already doing so.
Anyway, the dev will maybe answer me and give other insights about how this could be achieved. But I agree with @Spidericemidas that for big evolving pads, not operating in stereo is suboptimal.
Just got a very kind and thoroughful answer from the developer who confirmed every point you mentionned @_ki
Can't wait to try this; thank you for your time!
+10! I'm disappointed there is no OSC pan - same omission as in Lagrange. In both synths, it's not easy to create sounds with a wide stereo field as a result, without using the inbuilt chorus or delay with different times for L + R channels. There are so many options for creating rich sounds that this is a surprising omission
I believe there is a specific technical reason why the panning of Nambu's Ops cannot so easily be implemented. It's not really an oversight or omission on the Dev's part. I think it would just be far too complex to accomodate in Nambu's code. Something to do with the way the Ops and FM work, if I'm understanding at least half correctly?
It's not too bad though. I've been able to get some widespread pads going on it with a little Chorus spreading and a little slow Delay set at different speeds on L & R. The only thing is, I like to take advantage of the ample architecture in Nambu to make pluck sounds accompanied by Pad sounds in one patch. This means you can't avoid getting more obvious Delays on the pluck sounds when you only really want to use the Delay for spreading the Pad part of the patch.
The fx are global. If there was a way to just route the Ops individually with a send fx setting, that would definitely help and I'd be able to apply Delay only to the Ops making the Pad sound and mute the Delay send of the pluck sound. The same as the Vibrato setting seems to be global in Nambu BUT you do actually have the option to switch off the send to the Vibrato for each Op. That is a cool feature and would be very handy if you could do the same with fx sends.
Despite that little niggle, I'm still absolutely loving Nambu as it is, and I am having a total blast exploring and programming it. Really pleased and amazed with results so far and I know I have hardly scratched the surface of possibilities. Absolutely hooked on it! It's a beautiful thing indeed! 😍
Can't wait til you start posting some videos with your new patches.
Having asked to the developer exactly about stereo and panning, I got his kind and thorough explanation. I think it would be not cool to copy/paste here publicly his message, being initially a private conversation, but you can ask me in PM if you wish.
Anyway, it is very close to what @Spidericemidas speculated.
I've read those explanations, and they make sense to me. However, I think they could implement panning at the output row as nothing modulates anything else there. It might also work at that level for FX sends too.
I could be totally wrong though.
@Spidericemidas @Paulo164 : since you are in communication with developer, perhaps you could ask about panning not at the operator stage but solely on final mixing stage?
TBH though - as it's an AU, there's nothing stopping me from making smaller patches for each operator I would want to pan or separately FX.
Yeah, even without proposing to pan only at final send out, the dev anticipated this suggestion and explained it was not that simple.
Here is the reply (no big disclosure here) :
“I also considered the idea of adding stereo processing only to the final send to the output. However, adding even partial stereo processing to "single voice processing" was a significant CPU cost on my old iPad when playing chords. Because it's not a pure FM synth, there are many things that are difficult to optimize, which is why it's the current specification. Nambu requires a lot more CPU power than my other synthesizers.”
Thanks!
@NeuM "Can't wait til you start posting some videos with your new patches.
"
A thought crossed my mind today about possibly starting a new thread here dedicated to Nambu and the different ways I'm discovering of using it. I would post a patch each time with a description underneath of what is going on in it. People could then install the patch for some reverse engineering and studying if they were at all interested in the workings and possibilities of Nambu. Maybe give others some ideas for programming it themselves, you know?
I wanted to show how it is so much more than just an FM synth. It is in fact a very hybrid synth of FM, Subtractive and with all those extra texture sound sources and a resonator too! All of those elements can be combined and mixed in different ways in the Op Matrix to go much further than just FM. It's so good with hybrid sound potential, it came at just the right time and completely cured my recent rising GAS for chasing down a Roland D50. LOL.
But then, if I created that kind of thread, you'd all already have my patches collected individually over time, and there wouldn't be any point in me releasing a bank of them! 😆
Any route you choose is cool with me. If you do post patches, please make sure you include your famous Spider icon in the description so they're easy to find.
I've never been crazy about the patch organization of this developer's apps. As far as I know there is no way to move patches. You have to duplicate a patch and then save it in a new location.
While it’s not perfect, if you use the DDMF app directional eq, you can at least pan by frequencies. I was able to get some wider sounds using that without having to use the chorus or delay.
Indeed! I'm beginning to get results I haven't got from any other synth.
I learned long ago to work with what an app DOES do, not get bogged down by what it doesn't, and there is plenty to enjoy here, and maybe ingenious workarounds for the absence of our desired features
Ah. You can move patches around to different folders in all the Icegear synths, it's a few steps and not immediately obvious though. You have to highlight/select the patch first and then select the strange line icon at the end of the options in the presets window. Then select the icon with two files overlapping which copies the patch to an invisible pasteboard, so to speak. Then go to another folder you want to paste in and select the icon with two files overlapping with a + on it. That worked for me. It doesn't really move the patch though, it creates a copy for pasting and leaves the original where it was too. I just tested that function again, it worked that way first time but then locked up when I tried moving another one. Same behaviour with the other Icegear synths I just tested it on. But you can unfreeze it by selecting the curved/looped arrow and then it will open the folder again that you are trying to move to, and it still remembers the last patch you copied for pasting.
Anyhoo, it's a bit of a fiddle around, but definitely possible to 'move' (it's really copy/paste) patches between folders the same way in all Icegear synths. I'm just not 100% sure I'm doing it completely correctly, or could be a bug. But yeah as you say, it is duplicating rather than moving.
Nice technique! 👍
Yes to all those points! 😊👍
What irritates me most about these file management misfires in individual apps is that Apple provides all of the code necessary in their API’s to implement a competent file management system, but they are not used.
It isn’t as clear cut as you think about preset management. It should tell you something that so many devs have their own system for doing it…these are smart, creative people that aren’t lazy.
Never called anyone lazy. I said they are not using the API's available to implement already functional file management code available to them.
Preset management isn’t as simple as just using the file APIs.
You didn’t literally call them lazy but you implied that somehow you (who has no experience writing iOS music apps and plugins) see an obvious solution that they (a large number of experienced developers) have failed to see.
It should tell you that what you think is an obvious solution may not actually be a great solution.
Are you going to continue doing this? Please stop.
AU presets aren't files. They're handled differently under the hood.
If a developer takes the additional trouble to write routines to export and import presets to files, then yes there are APIs that make file management easier.
That said, preset and file management does seem to be a blind-spot for lots of developers. I often scratch my head over what they see as logical management of them.