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
I'll second that, Sam does great presets, and the price / number / quality ratio makes them very very cheap
You wouldn't happen to recall if you did anything else? I'm struggling with the same issue. I've got the performance and the preset browser parts up but can't access the actual fx parameters. Can't see the icon for them nor scroll down any further... And just to be clear, I'm talking about the fx plug, not the synth.
I'm on iPhone Xs Max.
@Nikolozi please bring the randomizer back! 😀
L> @Faceless2103 said:
Sorry, I don’t know what I did. I probably turned my phone off and on again but I don’t remember anything else.
Is anyone using Mela 2 on an iPhone 6s/7/8 in 'Zoomed' Display mode?
I mostly need to use Zoomed mode due to my eye sight.
In 'Zoomed' mode parts of the Mela UI is missing especially when used as an AUv3.
(Can't access the 'four box' Icon to enable synth editing).
Stand-Alone works fine in land-scape mode om 'Zoomed' mode.
In 'Standard' mode everything works fine in the AUv3 as well.
This is a minor niggle but something to be aware of.
I created over 1331 presets for mela synth and fx do I need to buy v2 to share them
Yes. It seems this is probably the most requested feature at this point. I'm hoping to implement it in 2.1 update, if everything goes well.
Yes, I agree
You don't need to import individual files. After pressing Import, browse to the folder with extracted presets and tap on "Select All". You can import everything at once.
I'm a bit hesitant to add a zip file compress/extract functionality to the app, when it can be all done from the Files app. But I'll keep this in mind in case. Let's see if it still be needed after the next update.
Yes, this is exactly how I'm planning to do it.
Yes, exactly how I was planing to do it. Good to hear that that seems like an intuitive approach from a user's perspective also.
Nice
All good, keep em coming
I'm planning to have different noise shapes in the future.
Interesting. This can be done via mod matrix. e.g. Noise oscillator routed to one of the filters and its cutoff is key tracked.
These are cool ideas, but I'd rather have noise routed to various FX units as need by the user. For now, one could route A noise oscillator to one of the filters (and maybe add FX to it). But I agree more flexibility would be great (which will happen at some point)
Nice!
Everything can be in scope for Mela in a long enough timeline
But everything you suggested seems reasonable. I may not do it in exactly the way you suggested, but I'm hoping Mela can achieve those sound sculpting possibilities in the future.
Thanks for the feedback Samuel.
It's on the to do list
If AU window (or in standalone mode the iPhone screen) is not wide enough then Mela will not show the synth modules. And will hide the 4 square button (which toggles the visibility of the modules). This is a design decision. I feel the screen needs to be big enough to show the synth modules. This means, on iPhone, in portrait mode, you won't be able to see those modules and will need to use it landscape mode to tweak them.
So, one thing you can do is assign parameters to the perform dials in landscape mode (then save the preset). Then you can tweak the preset in portrait mode or when AU window is not wide enough.
In the future, I'll experiment to see if UI might be able to do more things in portrait. But for now, it doesn't seem ideal to have the UI scroll in both axis to navigate to various parameters.
Woah, nice! Unfortunately, with Mela 1 you can only export 1 preset at a time. With Mela 2 you can export entire User folder (and hopefully with the future updates, there could be custom preset groups to manage presets better). So yes, for you, it probably make more sense to upgrade to Mela 2. I'm happy to provide you with a promo code for Mela 2, if needed (just email me).
Always good!
The 'bit shift' noise (which can be somewhat replicated using a oscillator triggered (decimator frequency) s&h is per note...
...and as such can not faithfully be polyphonically replicated using a global FX unit.
It has to be 'baked in' per oscillator preferably pre-filter.
Think decimating the source sample before it is pitch-interpolated and filtered.
It's a completely different 'sound' depending on where the decimation is done.
Bit reduction at the oscillator level could also yield interesting results.
(think of the 4-bit NES triangle wave as an example, or FM with 8-bit sine-tables etc. etc.).
A 'filter' and 'decimation per oscillator' are two completely different 'things'
It's your app and I respect that
Cheers!
I'll make note of your other suggestions. But I wanted to point out that FX in Mela aren't global. They are per voice. This means you could have Env 2 controlling distortion drive for example.
And so, you could choose 2-2 routing, for example, and have osc 1 (with noise) going into filter 1 (have osc 2 off). And then select FX to be placed before filter 1. This way, you can process a single oscillator using FX. Anyway, this is just to expand on what's possible with Mela today. But obviously, it doesn't yet meet all your needs.
Sorry, if that came off rude. I meant, these are good ideas, I just have a slightly different architecture in mind for Mela, in the future.
Ok, I'll explore Mela 2 further.
Here's a screencap of another 'concept' regarding pitched noise using Drambo.
https://www.dropbox.com/s/wdkj5lb34z422v4/noise2.mp4?dl=0
In this case the decimator frequency is keyboard tracked and also modulated using an 25Hz Square LFO.
The real 'fun' begins when rapidly (5-20ms interval) changing waveform, pitch and other parameters using a step-sequencer.
(Don't worry, I've got other tools for this Drambo, SunVox, SidTracker64, SquareSynth 2 etc.).
Let's keep Mela 2 unique in it's own way
/Samuel
I think I saw someone mention it would be cool if samples could be loaded as oscillators. I’d like to give a big +1 to that idea. Not enough synths with sample oscillators these days, especially with the routing flexibility of Mela
Thanks for clearing that up! However, I really hope you could reconsider that ui/ux choice since as things currently stand, I can’t really use the fx plug inside NS2. NS2 only operates in landscape mode (on iPhone) and there’s no way of resizing the plugin window. It’d be an incredibly cumbersome workflow to have to load the plugin up in some other host, tweak the parameters, assign some macros and then reload it in NS2 again.
The way the synth plug works is perfect, though. You simply scroll up/down to reach the dials you’re looking for. I get that it may not be ideal or elegant from an ui/ux aesthetics standpoint, but in practice, it works just fine.
The synth/fx sound stunning btw. Which is why I’m making this humble little request
Oh, I see. So, if the synth plug-in displays those modules it means it's wide enough and therefore, Mela FX 2 should also. Can you please post a picture what you are seeing? I'll check NS2 on my iPhone too.
Ok, so here’s a couple of screenshots:
Thanks for the screenshots. I see what's going on. So, in this case it's not the width but the height that's not large enough. So the problem is, NS2 seems to give AU instruments much larger height than it does to the AU FX plug-ins. That's why you are seeing the difference. This inconsistency is a bit annoying.
I'll see if I can do something about this. Maybe you could also pass this feedback to the NS2 dev. Would be good if they could give AUs consistent window sizes. Anyway, thanks for the feedback.
ok thanks already bought bundle so now preparing presets to ready share
Nice!
Hmmm. is the 'number pad' that was present it Mela 1 gone from Mela 2?
Can't wait to try these!
Yes, but it's coming back soon, stronger and better. Rewriting the UI was a huge amount work, and a couple of things I wanted to have ready didn't make the 2.0 cut. But they will be added in 2.x updates. For me personally, the number pad is a very important feature.
Ok, great! The annoying thing is, you can’t really do away with that track ribbon at the bottom of the NS2 ui, even though it’s got the ’X’ button next to it. Tapping it just makes the whole AU editing view go away. The ribbon takes up precious screen real estate and I don’t think I’ve ever even used it. One of the very few design gripes I have with NS2.
I could post it on the NS2 forums but I’m afraid it’s going to take quite a while before it gets addressed/some options are provided.
Cool, I'll experiment on my end, to see if I can improve the situation without sacrificing usability.
I noticed the following in my first look at this:
Running the AUv3 in Audiobus. When I open the app Settings (gear icon lower left), it opens a new stand-alone instance of Mela 2. Huh?
Otherwise, the sound is good, and the GUI is very impressive: intuitive and functional. A lot of control in a compact screen.
Ok, I’ve now reported the issue on the NS2 forum. But seeing as they’ve still to implement audio tracks, for example, I doubt this issue will be looked into any time soon...
One other thing: it’d be cool if an asterisk (*) appeared next to the preset name whenever you’ve made changes to the preset that haven’t been saved yet. On my iPhone, I’ve accidentally tapped on the ’next’ arrow a few times when I meant to just open up the preset menu by tapping on the preset name. If a dialogue window appeared, warning the user of losing all unsaved changes, this issue could be avoided.
At the moment, tapping on settings will always open the standalone app. There are several reasons for that but in short it’s because a lot of functionality in settings menu can only be done inside standalone app. In the future updates, I’m planning to split it up and make AUs have their own settings view. This was another thing that didn't make the 2.0 cut.
Thank you, glad you like it