Feature Requests

Layer Module: Layer module lets you create an audio layer easily using its sublane. The sublane takes non-Audio signals, MIDI and Pitch or Poly (non-Audio components), as input. The output Audio signal (or the Audio components of the Poly signal) is the sum of the module's input and the sublane's output. All other signal types pass through unchanged. While the sublane can transform a copy of the MIDI and Pitch input signals, those aren't merged at the output, unlike the Audio signal(s). The module allows you to create synth layers, where each layer can have independent processors such as filters, amp envelopes, panners, and pitch transposition. The Volume parameter controls the volume applied to the sublane's output before the Audio signal summing. Layer is a Mela Lab module and part of Collection 4. Note: Originally, this module was called Instrument.

Dynamic Buses At the moment, both MIDI and Audio buses are limited to 4. There's no reason why it needs to be limited or be a static number. It's purely an implementation detail. It would be great if it could be made dynamic so the users can create and remove buses as needed. A preset may have only 0, 2, or 16 or whatever number the preset needs. Poly buses At the moment, Audio Out collapses Poly to an Audio signal. Sometimes, the user may desire to route a Poly signal to another lane to merge it with the Poly signal on that lane. Or if you are creating a polyphonic instrument that uses feedback, it would require the ability to feedback the Poly signal. So the Audio In, Audio Out and Feedback modules would need to support Poly buses. Poly buses would most likely just carry Audio components of the Poly signal and not Pitch and note information/states. Or at least, if they do carry full information, discard them when merging with another Poly signal. i.e. if 2 Poly signals are merging, there needs to be a way to set whose note/pitch information remains after the merge.

Effect module lets you create self-contained custom audio effects. It contains a sublane called Wet Path. Wet Path sublane receives a copy of the Effect module's input signals. The output Audio signal (or the Audio components of a Poly signal) is the mix of the Effect's input and the sublane's output. While the sublane can transform a copy of the MIDI and Pitch input signals, those aren't merged at the output, unlike the Audio signal(s). The Dry parameter controls the level applied to the module's input before the Audio signal summing. The Wet parameter controls the level applied to the sublane's output before the Audio signal summing. Effect is a Mela Lab module and part of Collection 4. A screenshot of a simple delay effect (with a feedback loop) example attached.

It will be good, If there is a cloud patch storage option for quick exchange between desktop and mobile versions.

Samu had a great suggestion : > 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? 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.

There was a lot of discussion on the Audiobus Forum about adding the ability to tint or set colour to each module: https://forum.loopypro.com/discussion/comment/1386136#Comment_1386136 Either Mela will auto-colour modules from different categories Or the user will colour modules manually Or provide both capabilities Maybe ideally, Mela will auto-colour and then the user can override. The assumption is that the preset will save the overridden colours. And so if the preset is shared, the user loading the preset might see colours chosen that don't match their desired preference. The simplest approach must be taken with the least number of rules. There is also a somewhat related feature request, which focuses more on modulation, but both feature requests probably should be addressed at the same time: https://mela-feedback.nikolozi.com/feature-requests/p/add-html-colour-for-modules-that-also-show-on-modulations Some considerations: How will this affect the themes? It might be a better approach just to drop theme support and instead provide light and dark themes, that way it will be harder for the user to get in a situation where they open a preset and all of a sudden some modules are harder to see. Do we allow arbitrary colours? It might be better to provide a set colour that the user can select, and those colours can always be tested to remain compatible with the rest of the interface. And there might be slightly different versions of those colours depending on the light or dark theme. It should be noted that I often get emails from Mela users telling me how much they love the ability to create custom themes, so I need to be careful. Because this feature request is in direct conflict with custom themes. Maybe there's a solution for this, but it's not an obvious one. Attached is an example provided by Ailerom Update: The feature appears to be a bit controversial, and at the moment, there's no clear agreement on how the feature should work exactly. One big question is, should the colouring be part of the preset or the user's local settings?

Audio-to-Mod Module: It's a Mela Lab module. It's a modulator module whose modulation signal is the average of the left and right channels of the input audio. As all modulations happen at sample rates in Mela, feel free to modulate any parameter to create interesting sounds. For example, modulating a level of another oscillator will result in Amplitude Modulation (AM) synthesis. Modulating the cutoff frequency of a filter will result in FM synthesis. The module supports polyphonic modulation. Read more about Mela Lab here

Add the ability to undo or redo every action in the plug-ins, including: Parameter/Control value changes. Selected preset. Perform View assignments.

i have given the midi sequencing module some thought and have come up with this: a simplified version of the elektron sequencers: 2 rows of 8 steps. When holding a square and pushing one or more keys from the mela keyboard or an external one note and velocity data get written to the step. Double tapping resets the step. There could be a dial for selecting the amount steps: 3,4,6,8,12,16,24 and 32. 3,4,6 and steps will work as expected and disable steps to make the sequence shorter. 12,16,24,32,48,64 will previously greyed out dots beneath the sequencer light up to show that the extra amount of steps has been added. Pressing the dots will make the sequencer show the sequencer page. Dot 2 for steps 9 to 16. Dot 3 for 17 to 24. Dot 4 for 25 to 32 and dot 1 for going back to step 1 to 8. There could also be a dial for speed. Maybe for centre will be 1 (normal speed) going left or right will change the speed by .5 divided or multiplied respectively. All the way to /4 or x4. The could also be a swing button where central is neutral (50) and the offset get subtracted or added up. Lastly there should be a dial for the note gate. There should also be a submenu for selecting a target. Here each step can be manually selected and given a target to modulate and the amount to modulate with, like other modules like the lfo. When a step and a target are sepected they should always send a message when the step is played even when no note has been inserted into the step. This way the module can always be used for parameter switching. It would be nice to have some kind of automatic smoothing between different values on different steps to make the transition sound less jumpy. I think a module like this could have some value as it can be used for primitive parsmeter locking and sequencing. I hope i made my idea clear and that it maybe gives you some inspiration to think more about a new sequencing module. If you have any question: let me know!

Currently it’s hard to reuse components across patches, e. g. specific synth voice setups, FX chains, etc. It would be extremely helpful to extend the library manager to include lanes and sub lanes so that you can also save and load parts of patches.