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 Synth (All Numbers) Mega Thread

1…8910111214»

Comments

  • NikoloziNikolozi

    @janpieter said:
    Loading Mela as an effect in Reaper (in a way effects and instruments are loaded exactly the same way in Reaper) only results in the audio being passed unprocessed (as I first noticed with Skulptur which is now fixed in that way). You can see that the input busses seem to be grayed out (and the other busses are not seen).

    "In 1" and "In 2" are greyed out because Mela is loaded as an instrument type. I mean, the screenshot is showing AUi, i stands for instrument. It should say just AU. I'll load the Reaper to understand the situation better.

  • janpieterjanpieter

    @Nikolozi said:

    @janpieter said:
    Loading Mela as an effect in Reaper (in a way effects and instruments are loaded exactly the same way in Reaper) only results in the audio being passed unprocessed (as I first noticed with Skulptur which is now fixed in that way). You can see that the input busses seem to be grayed out (and the other busses are not seen).

    "In 1" and "In 2" are greyed out because Mela is loaded as an instrument type. I mean, the screenshot is showing AUi, i stands for instrument. It should say just AU. I'll load the Reaper to understand the situation better.

    I'm citing some of the stuff in the Skulptur thread in the hope that might clarify some things (I am not a dev so I'm on unknown territory here):

    "Perhaps Reaper doesn't support plugin extensions with multiple type headers yet and only looks at the first AUv3 header in the plugin (which is the instrument type)?

    It sounds like Reaper's AUv3 support isn't 100% there yet. Maybe someone with more Reaper experience can chime in here if this is a common issue?" (brambos)

    "I have now implemented audio processing in instrument mode. It doesn't seem to cause any problems and passes Apple's AUVal validation tests.

    So that should make it compatible with Reaper then if our hypothesis is correct." (brambos)

    This intervention seems to have solved the issue with Skulptur in Reaper (I check the latest Testflight version)

  • janpieterjanpieter

    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

  • NikoloziNikolozi
    edited May 2025

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    Loading Mela as an effect in Reaper (in a way effects and instruments are loaded exactly the same way in Reaper) only results in the audio being passed unprocessed (as I first noticed with Skulptur which is now fixed in that way). You can see that the input busses seem to be grayed out (and the other busses are not seen).

    "In 1" and "In 2" are greyed out because Mela is loaded as an instrument type. I mean, the screenshot is showing AUi, i stands for instrument. It should say just AU. I'll load the Reaper to understand the situation better.

    I'm citing some of the stuff in the Skulptur thread in the hope that might clarify some things (I am not a dev so I'm on unknown territory here):

    "Perhaps Reaper doesn't support plugin extensions with multiple type headers yet and only looks at the first AUv3 header in the plugin (which is the instrument type)?

    It sounds like Reaper's AUv3 support isn't 100% there yet. Maybe someone with more Reaper experience can chime in here if this is a common issue?" (brambos)

    "I have now implemented audio processing in instrument mode. It doesn't seem to cause any problems and passes Apple's AUVal validation tests.

    So that should make it compatible with Reaper then if our hypothesis is correct." (brambos)

    This intervention seems to have solved the issue with Skulptur in Reaper (I check the latest Testflight version)

    Ah, thanks for that. @brambos is correct, I'm seeing the same issue. Looks like when Reaper detects kAudioUnitType_MusicDevice type (aka Instrument), it ignores that Mela also supports kAudioUnitType_MusicEffect type (aka Audio Effect with MIDI in support). I'll email Reaper dev to let him know.
    (At the moment, I'm not planning to add back side-chain for the isntrument type due to the GarageBand bug, but I'll look into it in the near future)

  • NikoloziNikolozi

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

  • janpieterjanpieter

    @Nikolozi said:

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

    Yes. But I think the two issues might be related.

  • janpieterjanpieter
    edited May 2025

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    Loading Mela as an effect in Reaper (in a way effects and instruments are loaded exactly the same way in Reaper) only results in the audio being passed unprocessed (as I first noticed with Skulptur which is now fixed in that way). You can see that the input busses seem to be grayed out (and the other busses are not seen).

    "In 1" and "In 2" are greyed out because Mela is loaded as an instrument type. I mean, the screenshot is showing AUi, i stands for instrument. It should say just AU. I'll load the Reaper to understand the situation better.

    I'm citing some of the stuff in the Skulptur thread in the hope that might clarify some things (I am not a dev so I'm on unknown territory here):

    "Perhaps Reaper doesn't support plugin extensions with multiple type headers yet and only looks at the first AUv3 header in the plugin (which is the instrument type)?

    It sounds like Reaper's AUv3 support isn't 100% there yet. Maybe someone with more Reaper experience can chime in here if this is a common issue?" (brambos)

    "I have now implemented audio processing in instrument mode. It doesn't seem to cause any problems and passes Apple's AUVal validation tests.

    So that should make it compatible with Reaper then if our hypothesis is correct." (brambos)

    This intervention seems to have solved the issue with Skulptur in Reaper (I check the latest Testflight version)

    Ah, thanks for that. @brambos is correct, I'm seeing the same issue. Looks like when Reaper detects kAudioUnitType_MusicDevice type (aka Instrument), it ignores that Mela also supports kAudioUnitType_MusicEffect type (aka Audio Effect with MIDI in support). I'll email Reaper dev to let him know.
    (At the moment, I'm not planning to add back side-chain for the isntrument type due to the GarageBand bug, but I'll look into it in the near future)

    Thanks! Mela is great!

  • brambosbrambos

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    Loading Mela as an effect in Reaper (in a way effects and instruments are loaded exactly the same way in Reaper) only results in the audio being passed unprocessed (as I first noticed with Skulptur which is now fixed in that way). You can see that the input busses seem to be grayed out (and the other busses are not seen).

    "In 1" and "In 2" are greyed out because Mela is loaded as an instrument type. I mean, the screenshot is showing AUi, i stands for instrument. It should say just AU. I'll load the Reaper to understand the situation better.

    I'm citing some of the stuff in the Skulptur thread in the hope that might clarify some things (I am not a dev so I'm on unknown territory here):

    "Perhaps Reaper doesn't support plugin extensions with multiple type headers yet and only looks at the first AUv3 header in the plugin (which is the instrument type)?

    It sounds like Reaper's AUv3 support isn't 100% there yet. Maybe someone with more Reaper experience can chime in here if this is a common issue?" (brambos)

    "I have now implemented audio processing in instrument mode. It doesn't seem to cause any problems and passes Apple's AUVal validation tests.

    So that should make it compatible with Reaper then if our hypothesis is correct." (brambos)

    This intervention seems to have solved the issue with Skulptur in Reaper (I check the latest Testflight version)

    Ah, thanks for that. @brambos is correct, I'm seeing the same issue. Looks like when Reaper detects kAudioUnitType_MusicDevice type (aka Instrument), it ignores that Mela also supports kAudioUnitType_MusicEffect type (aka Audio Effect with MIDI in support). I'll email Reaper dev to let him know.
    (At the moment, I'm not planning to add back side-chain for the isntrument type due to the GarageBand bug, but I'll look into it in the near future)

    Yeah, the proliferation of weird hosts and their own inconsistent interpretations of standards is what's holding me back from going full on MacOS.

    Keeping everything working on iOS is complicated enough as it is, and I'm not familiar at all with the desktop world (and frankly not really interested in it either).

  • NikoloziNikolozi

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

    Yes. But I think the two issues might be related.

    Can you elaborate on this, so I can understand this issue? What do you mean by Mela doesn't seem to process MIDI?

  • janpieterjanpieter

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

    Yes. But I think the two issues might be related.

    Can you elaborate on this, so I can understand this issue? What do you mean by Mela doesn't seem to process MIDI?

    When I implement an MIDI processor in Mela and try to use it as a MIDI effect in Reaper it just passes the original/incoming MIDI on. The MIDI modules in Mela seem to receive the MIDI and process it (as I can see when I insert a monitor module) but Reaper doesn't seem to pass the processed MIDI on.

  • janpieterjanpieter

    Just as with the audio: Reaper doesn't pass the processed signal (MIDI or audio). That's why I thought the issue might be related.

  • NikoloziNikolozi

    @brambos said:

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    Loading Mela as an effect in Reaper (in a way effects and instruments are loaded exactly the same way in Reaper) only results in the audio being passed unprocessed (as I first noticed with Skulptur which is now fixed in that way). You can see that the input busses seem to be grayed out (and the other busses are not seen).

    "In 1" and "In 2" are greyed out because Mela is loaded as an instrument type. I mean, the screenshot is showing AUi, i stands for instrument. It should say just AU. I'll load the Reaper to understand the situation better.

    I'm citing some of the stuff in the Skulptur thread in the hope that might clarify some things (I am not a dev so I'm on unknown territory here):

    "Perhaps Reaper doesn't support plugin extensions with multiple type headers yet and only looks at the first AUv3 header in the plugin (which is the instrument type)?

    It sounds like Reaper's AUv3 support isn't 100% there yet. Maybe someone with more Reaper experience can chime in here if this is a common issue?" (brambos)

    "I have now implemented audio processing in instrument mode. It doesn't seem to cause any problems and passes Apple's AUVal validation tests.

    So that should make it compatible with Reaper then if our hypothesis is correct." (brambos)

    This intervention seems to have solved the issue with Skulptur in Reaper (I check the latest Testflight version)

    Ah, thanks for that. @brambos is correct, I'm seeing the same issue. Looks like when Reaper detects kAudioUnitType_MusicDevice type (aka Instrument), it ignores that Mela also supports kAudioUnitType_MusicEffect type (aka Audio Effect with MIDI in support). I'll email Reaper dev to let him know.
    (At the moment, I'm not planning to add back side-chain for the isntrument type due to the GarageBand bug, but I'll look into it in the near future)

    Yeah, the proliferation of weird hosts and their own inconsistent interpretations of standards is what's holding me back from going full on MacOS.

    Keeping everything working on iOS is complicated enough as it is, and I'm not familiar at all with the desktop world (and frankly not really interested in it either).

    100%, to keep it simple, I prioritise iOS and Logic for Mac, but I have tons of workarounds in my code even for Logic's AUv3.

  • NikoloziNikolozi

    @janpieter said:

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

    Yes. But I think the two issues might be related.

    Can you elaborate on this, so I can understand this issue? What do you mean by Mela doesn't seem to process MIDI?

    When I implement an MIDI processor in Mela and try to use it as a MIDI effect in Reaper it just passes the original/incoming MIDI on. The MIDI modules in Mela seem to receive the MIDI and process it (as I can see when I insert a monitor module) but Reaper doesn't seem to pass the processed MIDI on.

    I don't know if Reaper supports MIDI out from AUv3s. Again, it's been a while since I checked AUv3 support in Reaper, does it work with any other AUv3 plug-ins?

  • janpieterjanpieter

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

    Yes. But I think the two issues might be related.

    Can you elaborate on this, so I can understand this issue? What do you mean by Mela doesn't seem to process MIDI?

    When I implement an MIDI processor in Mela and try to use it as a MIDI effect in Reaper it just passes the original/incoming MIDI on. The MIDI modules in Mela seem to receive the MIDI and process it (as I can see when I insert a monitor module) but Reaper doesn't seem to pass the processed MIDI on.

    I don't know if Reaper supports MIDI out from AUv3s. Again, it's been a while since I checked AUv3 support in Reaper, does it work with any other AUv3 plug-ins?

    I just tried Modalics EON-arp (which Reaper 'sees' as an AUi and VST3): the VST3 works as intended, het AU version not!

  • NikoloziNikolozi
    edited May 2025

    @janpieter said:

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:

    @Nikolozi said:

    @janpieter said:
    As for audio: in Reaper Mela doesn't seem to process MIDI (Drambo has the same issue (or Reaper is the one with the issue of course)). It just seems to pass it on unprocessed...

    Sorry, I'm confused, is this another issue?

    Yes. But I think the two issues might be related.

    Can you elaborate on this, so I can understand this issue? What do you mean by Mela doesn't seem to process MIDI?

    When I implement an MIDI processor in Mela and try to use it as a MIDI effect in Reaper it just passes the original/incoming MIDI on. The MIDI modules in Mela seem to receive the MIDI and process it (as I can see when I insert a monitor module) but Reaper doesn't seem to pass the processed MIDI on.

    I don't know if Reaper supports MIDI out from AUv3s. Again, it's been a while since I checked AUv3 support in Reaper, does it work with any other AUv3 plug-ins?

    I just tried Modalics EON-arp (which Reaper 'sees' as an AUi and VST3): the VST3 works as intended, het AU version not!

    Cool, hard to say whether it's Modalics' limitation or Repears. But I'll look into it.

    Just to save time, would you be able to email me a super simple Reaper project with Mela, where you have it configured to Mela MIDI out to be captured by Reaper?

    (My email can be found in Mela's Settings)

  • janpieterjanpieter

    done

  • SquishySquishy

    Wait… there’s Reaper on iOS?!? I thought auv3 referred to iOS apps only

  • NikoloziNikolozi

    @Squishy said:
    Wait… there’s Reaper on iOS?!? I thought auv3 referred to iOS apps only

    Reaper on macOS. AUv3 also works on macOS. Hosts that support AUv3 on macOS include Ableton, Logic, GarageBand and Reaper. And many plug-ins, including Mela, that work on iOS work on Mac.

  • SquishySquishy

    Oh neat! Learn something new erryday! Love mela btw, keep up the great work

  • NikoloziNikolozi

    @Squishy said:
    Oh neat! Learn something new erryday! Love mela btw, keep up the great work

    🙏

  • NikoloziNikolozi
    edited May 2025

    Leaving the link to the Reaper bug report here for future reference: https://forum.cockos.com/showthread.php?p=2868852

    CC: @janpieter @brambos

  • brambosbrambos

    @Nikolozi said:
    Leaving the link to the Reaper bug report here for future reference: https://forum.cockos.com/showthread.php?p=2868852

    CC: @janpieter @brambos

    That sums it up nicely. Thanks! 🙏

  • janpieterjanpieter

    @brambos said:

    @Nikolozi said:
    Leaving the link to the Reaper bug report here for future reference: https://forum.cockos.com/showthread.php?p=2868852

    CC: @janpieter @brambos

    That sums it up nicely. Thanks! 🙏

    Thanks!

  • drewinnitdrewinnit
    edited June 2025

    Edit: noob question that i figured out myself 😅

  • NikoloziNikolozi

    @Nikolozi said:
    Leaving the link to the Reaper bug report here for future reference: https://forum.cockos.com/showthread.php?p=2868852

    CC: @janpieter @brambos

    Just a heads up, the Reaper developer addressed the AUv3 issues I reported in the latest pre-release: https://forum.cockos.com/showthread.php?t=304824

    • Instrument MIDI out works
    • MIDI Processors also work
    • If an AUv3 uses the same name for multiple plug-in types it no longer just shows one.

    Mela currently uses the same name for all 3 plug-ins types (Instrument, Audio Effect and MIDI Processor). In v6.13, Audio Effect and MIDI Processor will be called Mela FX and Mela MIDI. Keep in mind that the only difference between the types is the number of audio and MIDI inputs and outputs. Otherwise, their features are identical, and any preset created in one type can be opened in another.

Sign In or Register to comment.