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
Or a button/function to strip the colouring info from the preset.
Cool, I'll keep this in mind.
There's a way to deal with this, like having multiple rings or having multi-segmented coloured rings. But I'm not a fan, it becomes too busy rather than useful.
>
Regarding colour blindness, you might know more than me about this. I always assumed that those who are colour-blind have certain accessibility settings enabled to deal with it. I'm sure the majority of apps don't take colour blindness into consideration. Is this not a useful assumption?
👍
I guess the main question is, for those that want tinting, do they expect to have different colouring schemes for different presets or would they always want to colour the module the same way? For example, should all LFO modules be the same colour or should each LFO module have different colour to distinguish them from each other?
For me, it's always want to colour the module the same way. Or at least be able to set a module colour globally.
Yeah that would make sense to me also, get some colour association going with the types…
Categories or every module? There are 80+ modules already, and the number will only grow, so I imagine tinting them one by one could be a bit laborious. I guess maybe you will have a few favourites that you use regularly, which you will tint while keeping others default.
I think categories, as best as can be done. There’s a limit to how many would be useful I guess, a UX person probably has a stat or a chart on it somewhere 😅
Absolutely and it pretty much already is. If one wants to go for sub-categories as well the MIDI note (7) family is a good example where it could make sense. It's a start as someone said..
That's for you to decide. What is a more elegant solution from the developer's perspective? Besides the global theme, you could offer options to change an entire category or an individual module. Under the hood, everything remains separate. For example, if I choose to change the entire category to one color and later adjust just one particular module to a different one, it would still be possible.
In my opinion, the majority of users will probably only change a few categories and several individual modules, that's all. And I guess half of them will never even use the feature.
Categories would be plenty for me. Just to easily differentiate between a filter, effect, address, oscillator, midi module etc.
At the moment, I don't see an elegant solution. But that's often the case when developing a product. Sometimes, it feels like there's no good solution, but something emerges eventually. IME with Mela, I often get feature requests that don't make sense at the time, or I don't see a way to integrate that idea even if I wanted to, but then as the product evolves, it reaches the point where a feature request that didn't make sense all of a sudden has an elegant solution. And then I implement it. I have a feeling it's going to be the case here. I'm not going to rush, but I will collect feedback so I'm aware of what the users want.
Yes, that makes sense.
Agreed. Just need to find a good solution that is best for the user. In other words, it doesn't get in the way of the users who don't care about the feature and those who do can use it quickly and easily.
I guess you also want the ability to define categories because, from Mela's perspective, filters, audio effects and oscillators belong to the Audio Processor category.
One thing I've been playing around with in Drambo lately is processing modulation signals like they would be audio and using them to modulate parameters. (various pulse thru a filtered delay/echo as one example).
As for Mela a module that converts modulation signal to audio and back could be something to add at some point?
I think this would be another module where the sublane feature is going to be really useful. I created a feedback post to track it https://mela-feedback.nikolozi.com/feature-requests/p/module-to-convert-modulation-signal-to-audio-and-back
Some thoughts:
I imagine it will be similar to the Audio-to-Mod modulator module, except it will have a sublane and a modulatable dial.
The sublane will not receive any input and won't merge its output.
It will have a dial/slider that the user will modulate.
The modulation signal then will be sent to the sublane as input.
The user will have audio processors in the sublane to transform the modulation signal.
The processed audio will be converted back to the modulation signal.
There probably will be a Depth parameter.
Visualiser of the resulting modulation signal will also be useful.
I would want to have separate colour for those elements but if it is fixed groupings that would not bother me. I.m not looking to turn Mela into a rainbow. Just to help make some sense of the UI. I can't imagine more than 5 or 6 colour groups would be needed.
How would something like an A,B,C ....... etc of 5 or 6 definable colours and for each module you select which colour group, (C for crystal ocean teal for e.g.)
Ok here's another video I just finished. It's a bit longer than usual, but I think covers a lot of important topics many of might be interested in.