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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Mela 6 by Nikolozi Meladze (Released)

13»

Comments

  • @Krupa said:
    Dare I say welcome to the MelaVerse😅

    You nailed it! From now on it’s MelaVerse! 😅 🎉

  • @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:
    Thanks for the input guys. Another reason I maintained the version number was to distinguish it from the (classic) Mela 3, with a static module layout. And it remains in the App Store because some users do like the older approach or even prefer it. So, I will also rename Mela 3 to Mela Classic (as @Luxthor suggested a while back). Hopefully, this new naming approach will be less confusing to the users.

    Many of us still love Mela3, it’s already a classic in a sense. Renaming it to Mela Classic is just revealing its true name. The same thing is with NFM. If you decide to continue to work on NFM, it could be even better. And then there is MELA, the ultimate synth/tool.

    I want to do an "FM6" module in Mela. It will mimic NFM's Algorithm view, and each Operator will be a sublane, with fully custom module chains. This is all theoretical, but I think it will be pretty epic if it works out.

    There’s a huge gap between musicians who like to use modular and those who don’t even consider it. Imho, the most optimal thing would be to keep NFM, work on it, and make that module in Mela. BTW, this module is new collection worthy.

  • @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:
    Thanks for the input guys. Another reason I maintained the version number was to distinguish it from the (classic) Mela 3, with a static module layout. And it remains in the App Store because some users do like the older approach or even prefer it. So, I will also rename Mela 3 to Mela Classic (as @Luxthor suggested a while back). Hopefully, this new naming approach will be less confusing to the users.

    Many of us still love Mela3, it’s already a classic in a sense. Renaming it to Mela Classic is just revealing its true name. The same thing is with NFM. If you decide to continue to work on NFM, it could be even better. And then there is MELA, the ultimate synth/tool.

    I want to do an "FM6" module in Mela. It will mimic NFM's Algorithm view, and each Operator will be a sublane, with fully custom module chains. This is all theoretical, but I think it will be pretty epic if it works out.

    Mela's future is bright! 🤩

    🧡🧡

    While I can see that for some the simplicity of separate apps works better, I can see definite benefits to working your apps into one common environment that you upkeep and develop.

    Just a few opinions of my own here:

    I would like to see different apps like NFM developed into Mela, but along with it, you may need a little rejigging of the preset browser, to make using different ‘synth models’ for want of a better term, obvious and selectable. Further synth models containing more modules could be sold as packs along with new sounds in the initial pack, with the below idea complimenting and furthering this idea…

    As the app develops, I would like to see some more presets using the same architecture of a synth. These could take the form of IAPs: a certain sound designer could make a synth design using a set type of modules to their liking and then do a pack of sounds for that synth. I appreciate that this model of splitting payment for IAPs could be more work or be problematic in some ways, but it’s an idea and would bring in a new audience of preset tweakers whom pay for sound packs.

    Done in the right way, these may help open up the app to new customers and different markets of people that would look at a modular environment (however user friendly) and run a mile.

    As I say, just a few thoughts to mull over if you haven’t already mulled over a million and one ideas lol

  • @Luxthor said:

    @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:
    Thanks for the input guys. Another reason I maintained the version number was to distinguish it from the (classic) Mela 3, with a static module layout. And it remains in the App Store because some users do like the older approach or even prefer it. So, I will also rename Mela 3 to Mela Classic (as @Luxthor suggested a while back). Hopefully, this new naming approach will be less confusing to the users.

    Many of us still love Mela3, it’s already a classic in a sense. Renaming it to Mela Classic is just revealing its true name. The same thing is with NFM. If you decide to continue to work on NFM, it could be even better. And then there is MELA, the ultimate synth/tool.

    I want to do an "FM6" module in Mela. It will mimic NFM's Algorithm view, and each Operator will be a sublane, with fully custom module chains. This is all theoretical, but I think it will be pretty epic if it works out.

    There’s a huge gap between musicians who like to use modular and those who don’t even consider it. Imho, the most optimal thing would be to keep NFM, work on it, and make that module in Mela. BTW, this module is new collection worthy.

    Yes, I agree with that. I mean, I'm aware that some users like simplicity and don't want to dive into modular environments building synths and effects. And I get the appeal; you just load up a synth you want to use. Which I have no problem with. My approach in music these days is when I want a synth or effect, I just open Mela and build it :)

    And NFM can stick around, and I'll fix bugs if they come up, but as you know, I'd rather build new things into Mela, and steal ideas from my old products and integrate them into Mela.

  • @Fruitbat1919 said:

    @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:
    Thanks for the input guys. Another reason I maintained the version number was to distinguish it from the (classic) Mela 3, with a static module layout. And it remains in the App Store because some users do like the older approach or even prefer it. So, I will also rename Mela 3 to Mela Classic (as @Luxthor suggested a while back). Hopefully, this new naming approach will be less confusing to the users.

    Many of us still love Mela3, it’s already a classic in a sense. Renaming it to Mela Classic is just revealing its true name. The same thing is with NFM. If you decide to continue to work on NFM, it could be even better. And then there is MELA, the ultimate synth/tool.

    I want to do an "FM6" module in Mela. It will mimic NFM's Algorithm view, and each Operator will be a sublane, with fully custom module chains. This is all theoretical, but I think it will be pretty epic if it works out.

    Mela's future is bright! 🤩

    🧡🧡

    While I can see that for some the simplicity of separate apps works better, I can see definite benefits to working your apps into one common environment that you upkeep and develop.

    Just a few opinions of my own here:

    I would like to see different apps like NFM developed into Mela, but along with it, you may need a little rejigging of the preset browser, to make using different ‘synth models’ for want of a better term, obvious and selectable. Further synth models containing more modules could be sold as packs along with new sounds in the initial pack, with the below idea complimenting and furthering this idea…

    As the app develops, I would like to see some more presets using the same architecture of a synth. These could take the form of IAPs: a certain sound designer could make a synth design using a set type of modules to their liking and then do a pack of sounds for that synth. I appreciate that this model of splitting payment for IAPs could be more work or be problematic in some ways, but it’s an idea and would bring in a new audience of preset tweakers whom pay for sound packs.

    Done in the right way, these may help open up the app to new customers and different markets of people that would look at a modular environment (however user friendly) and run a mile.

    As I say, just a few thoughts to mull over if you haven’t already mulled over a million and one ideas lol

    Agreed, focusing on one product is the way to go.

    My goal with Mela is to make modular as approachable. And maybe sometime in the future, it could reach a point where hiding all complexity becomes possible, and as you say, it may become appealing to a new audience. And those who want to dig deep can always do so.

  • @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:
    Thanks for the input guys. Another reason I maintained the version number was to distinguish it from the (classic) Mela 3, with a static module layout. And it remains in the App Store because some users do like the older approach or even prefer it. So, I will also rename Mela 3 to Mela Classic (as @Luxthor suggested a while back). Hopefully, this new naming approach will be less confusing to the users.

    Many of us still love Mela3, it’s already a classic in a sense. Renaming it to Mela Classic is just revealing its true name. The same thing is with NFM. If you decide to continue to work on NFM, it could be even better. And then there is MELA, the ultimate synth/tool.

    I want to do an "FM6" module in Mela. It will mimic NFM's Algorithm view, and each Operator will be a sublane, with fully custom module chains. This is all theoretical, but I think it will be pretty epic if it works out.

    There’s a huge gap between musicians who like to use modular and those who don’t even consider it. Imho, the most optimal thing would be to keep NFM, work on it, and make that module in Mela. BTW, this module is new collection worthy.

    Yes, I agree with that. I mean, I'm aware that some users like simplicity and don't want to dive into modular environments building synths and effects. And I get the appeal; you just load up a synth you want to use. Which I have no problem with. My approach in music these days is when I want a synth or effect, I just open Mela and build it :)

    And NFM can stick around, and I'll fix bugs if they come up, but as you know, I'd rather build new things into Mela, and steal ideas from my old products and integrate them into Mela.

    Of course, you’ll focus on the Mela, but please keep the other two alive. I’m still unable to find a replacement for the Mela3, but I have bounced all the Mela3 tracks. I just need to sample several of my favorite patches, and then I will certainly ease the pressure on you to keep those alive. ;)

  • @Luxthor said:

    @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:

    @Luxthor said:

    @Nikolozi said:
    Thanks for the input guys. Another reason I maintained the version number was to distinguish it from the (classic) Mela 3, with a static module layout. And it remains in the App Store because some users do like the older approach or even prefer it. So, I will also rename Mela 3 to Mela Classic (as @Luxthor suggested a while back). Hopefully, this new naming approach will be less confusing to the users.

    Many of us still love Mela3, it’s already a classic in a sense. Renaming it to Mela Classic is just revealing its true name. The same thing is with NFM. If you decide to continue to work on NFM, it could be even better. And then there is MELA, the ultimate synth/tool.

    I want to do an "FM6" module in Mela. It will mimic NFM's Algorithm view, and each Operator will be a sublane, with fully custom module chains. This is all theoretical, but I think it will be pretty epic if it works out.

    There’s a huge gap between musicians who like to use modular and those who don’t even consider it. Imho, the most optimal thing would be to keep NFM, work on it, and make that module in Mela. BTW, this module is new collection worthy.

    Yes, I agree with that. I mean, I'm aware that some users like simplicity and don't want to dive into modular environments building synths and effects. And I get the appeal; you just load up a synth you want to use. Which I have no problem with. My approach in music these days is when I want a synth or effect, I just open Mela and build it :)

    And NFM can stick around, and I'll fix bugs if they come up, but as you know, I'd rather build new things into Mela, and steal ideas from my old products and integrate them into Mela.

    Of course, you’ll focus on the Mela, but please keep the other two alive. I’m still unable to find a replacement for the Mela3, but I have bounced all the Mela3 tracks. I just need to sample several of my favorite patches, and then I will certainly ease the pressure on you to keep those alive. ;)

    I don't have any immediate plans to remove NFM or Mela 3. In fact, I did some fixes for Mela 3 earlier today. But even if I decide to remove them from the App Store at some point, you will always be able to redownload them from your purchases list.

  • I don't want to derail the thread, just make a comment on a thought.

    I have lots of apps. I mean hundreds!

    For the most part, the vast majority work well on my current iPad. Some obviously are now long gone and others join that list every year - I'm not surprised at this ; how can devs keep long lists of apps up to date?

    We all know many devs on iOS are one person or small teams at most, so how can we expect devs to keep in somemcase over 20 apps in good working order when they have long since stopped selling?

    Well I think this add on to one devs central app hub ideal may be the answer in some ways. I would much prefer an app that had some shared resources and staggered buying option, that made it in some ways easier for the dev to upkeep and for us users to buy the bits we wanted. It could work for many types of similar apps, like a midi app that encompassed many different generating ideas instead of lots of little apps.

    Sorry....off topic....

  • @Fruitbat1919 said:
    I don't want to derail the thread, just make a comment on a thought.

    I have lots of apps. I mean hundreds!

    For the most part, the vast majority work well on my current iPad. Some obviously are now long gone and others join that list every year - I'm not surprised at this ; how can devs keep long lists of apps up to date?

    We all know many devs on iOS are one person or small teams at most, so how can we expect devs to keep in somemcase over 20 apps in good working order when they have long since stopped selling?

    Well I think this add on to one devs central app hub ideal may be the answer in some ways. I would much prefer an app that had some shared resources and staggered buying option, that made it in some ways easier for the dev to upkeep and for us users to buy the bits we wanted. It could work for many types of similar apps, like a midi app that encompassed many different generating ideas instead of lots of little apps.

    100% agree.

    Sorry....off topic....

    All such topics are welcome :)

  • @Nikolozi said:

    I don't have any immediate plans to remove NFM or Mela 3. In fact, I did some fixes for Mela 3 earlier today. But even if I decide to remove them from the App Store at some point, you will always be able to redownload them from your purchases list.

    FWIW, I absolutely love Mela, and have really enjoyed following its progress. It's the one generative tool I use in all my projects, and with a few more synthesis types it will have covered my long-standing desire for Phase Plant on the iPad. Maybe I'll get my head around Drambo at some point, but Mela follows my thought process far more organically. While I just buy each collection immediately it comes out, regardless of whether I have an immediate use for them, this works better for me than having 2387562938759236529 things already included, as I just learn the new stuff as it is drip-fed rather than feeling intimidated by all the things. Buying the collections is my way of indicating that I'd just like you to keep doing what you're doing.

  • @dpeace said:

    @Nikolozi said:

    I don't have any immediate plans to remove NFM or Mela 3. In fact, I did some fixes for Mela 3 earlier today. But even if I decide to remove them from the App Store at some point, you will always be able to redownload them from your purchases list.

    FWIW, I absolutely love Mela, and have really enjoyed following its progress. It's the one generative tool I use in all my projects, and with a few more synthesis types it will have covered my long-standing desire for Phase Plant on the iPad. Maybe I'll get my head around Drambo at some point, but Mela follows my thought process far more organically. While I just buy each collection immediately it comes out, regardless of whether I have an immediate use for them, this works better for me than having 2387562938759236529 things already included, as I just learn the new stuff as it is drip-fed rather than feeling intimidated by all the things. Buying the collections is my way of indicating that I'd just like you to keep doing what you're doing.

    Wow, thank you!

  • I like the name change idea with Mela + Mela Classic :) I haven't picked up Mela yet because I've also been confused at the naming conventions in the past and wanted to make sure this was the one to keep getting updated.

    I also think the pricing model is great! It gives me of a feeling of fairness and I'm sure users that have bought collections before now have been ecstatic with the updates along the way. You've got some wild (good) changelogs!

  • @Goldiblockz said:
    I like the name change idea with Mela + Mela Classic :) I haven't picked up Mela yet because I've also been confused at the naming conventions in the past and wanted to make sure this was the one to keep getting updated.

    Wish I had realised earlier that this was confusing for some, would have made this change just before releasing 6.0. But in my defence, I hardly saw anyone being confused when it went from Mela 4 to Mela 5 :)

    I also think the pricing model is great! It gives me of a feeling of fairness and I'm sure users that have bought collections before now have been ecstatic with the updates along the way.

    Fortunately, reactions mostly have been positive.

    You've got some wild (good) changelogs!

    Thanks :)

  • I made decent tips during yesterday's gig, and I went to get Mela 6 and the collections. Turns out...I already have it and have purchased collections 1 and 2 already!? Since when?! 😂 Yep, my ADHD surprised me again, haha.

    I purchased collection 3 and plan to learn to use Mela throughout today. First, I'll read the help section a couple more times to establish the basic workflow in my noggin, maybe watch a tutorial video or two (I get the feeling @sfm might have a video or two as he's usually right on top of things), and then continue learning Mela kinesthetically by building some sort of Ambient piece.

    Been looking for a replacement for Obsidian (the synth parts, not the sampler part) to use in Cubasis 3, and judging by what I've read so far (and pouring through what modules are available), Mela 6 is shaping up to be that replacement. Well done @Nikolozi . 👏

  • @jwmmakerofmusic said:
    I made decent tips during yesterday's gig, and I went to get Mela 6 and the collections. Turns out...I already have it and have purchased collections 1 and 2 already!? Since when?! 😂 Yep, my ADHD surprised me again, haha.

    You may have purchased Mela 4. When Mela 4 users were upgraded to Mela 5, Collections 1 and 2 were unlocked automatically for them.

    I purchased collection 3 and plan to learn to use Mela throughout today. First, I'll read the help section a couple more times to establish the basic workflow in my noggin, maybe watch a tutorial video or two (I get the feeling @sfm might have a video or two as he's usually right on top of things), and then continue learning Mela kinesthetically by building some sort of Ambient piece.

    This is a good starting place: https://nikolozi.com/mela/tutorials/

    Note that Mela’s features have dramatically evolved since version 4.0, and the Introducing Mela 4 tutorial is slightly out of date. However, most concepts are still relevant. The main difference is lane I/O is done via Audio/MIDI In/Out modules now. The 6.0 release notes have the details. I will create a new “Introducing Mela 6” series sometime after the Mela 6.1 release.

    Been looking for a replacement for Obsidian (the synth parts, not the sampler part) to use in Cubasis 3, and judging by what I've read so far (and pouring through what modules are available), Mela 6 is shaping up to be that replacement. Well done @Nikolozi . 👏

    Thank you 🙏

  • Weeps in iOS 18.

    I mean, I know. One must move forward. But I’m so paranoid about updating this thing.

Sign In or Register to comment.