Why does the MVocoder plug-in end in .mll? It should end in .exe. Waveform 13 sees it but I'm in trial mode FLStudio 21

[bonkers82]

It's odd that the MVocoder plug-in ends in the .mll extension. I'm on day two trying to access other brands' VSTs on a trial version of Waveform13 which is 30 day trial, and FLStudio 21 has a six month trial period--unless they changed it--it's wild that I can't get my MIDI keyboard controller to work on the Waveform 13 software but I can only access the 808 "Drum machine" VST on FLStudio 21. By the way, my MIDI controller works with Music Maker 2024 as it was a full purchase not a trial period. Both DAWs won't launch the MVocoder from the list that I can read...so these programs seem like they can "see" the plug-in but it won't launch. The trial versions of both maybe blocking the access. One thing for sure is, Music Maker 2024 ignored the file extension .mll come to think of it Cherry Audio may use the same tricky file extension. A year ago, I paid for the Cherry Audio mono synth and that bug won't work in Music Maker 2024. Any help would be greatly appreciated. A deep dive into my computing system MeldaProductions Audio Plugins 16 is there so I scroll down what happened to the MeldaProduction MVocoder plug in let me recall the Plug In manager 16th version had a recognizable file extension .exe whereas the MVocoder not so I saw this: .mll how does that launch for Windows OS maybe an older Mac laptop running X though not the latest Apple OS (released earlier in 2024) version maybe can have MVocoder launch and work with whatever DAW. Apparently, there is a trick to open the .mll it's possible Windows Store lacks the App to get this effect Plug-In integrated with any Windows running DAW.

[kvotchin]

WTAF did I just read…

[kritikon]

No idea. Never heard of .mll before and I'm none the wiser which DAW this bonkers chap is using

[Greenstorm33]

No idea. Never heard of .mll before and I'm none the wiser which DAW this bonkers chap is using

Malevolent Link Library. Users of these cursed binaries are slowly driven to madness.

[whyterabbyt]

It's odd that the MVocoder plug-in ends in the .mll extension. I'm on day two trying to access other brands' VSTs on a trial version of Waveform13 which is 30 day trial, and FLStudio 21 has a six month trial period--unless they changed it--it's wild that I can't get my MIDI keyboard controller to work on the Waveform 13 software but I can only access the 808 "Drum machine" VST on FLStudio 21. By the way, my MIDI controller works with Music Maker 2024 as it was a full purchase not a trial period. Both DAWs won't launch the MVocoder from the list that I can read...so these programs seem like they can "see" the plug-in but it won't launch. The trial versions of both maybe blocking the access. One thing for sure is, Music Maker 2024 ignored the file extension .mll come to think of it Cherry Audio may use the same tricky file extension. A year ago, I paid for the Cherry Audio mono synth and that bug won't work in Music Maker 2024. Any help would be greatly appreciated. A deep dive into my computing system MeldaProductions Audio Plugins 16 is there so I scroll down what happened to the MeldaProduction MVocoder plug in let me recall the Plug In manager 16th version had a recognizable file extension .exe whereas the MVocoder not so I saw this: .mll how does that launch for Windows OS maybe an older Mac laptop running X though not the latest Apple OS (released earlier in 2024) version maybe can have MVocoder launch and work with whatever DAW. Apparently, there is a trick to open the .mll it's possible Windows Store lacks the App to get this effect Plug-In integrated with any Windows running DAW.

plugins do not use the .exe extension. On windows, .exe indicates a standalone application, not a plugin. VST2 plugins on windows use the .dll extension, repeat .dll, not .mll. The Melda plugin installer places the .dll files in your plugin folder when run properly. They do not place any .mll files in your plugin folder.

Ive just tested the latest Melda installer, I dont see any evidence of it creating .mll files anywhere. There are no .mll files in any folder associated with plugins, or the Melda software. In fact there are no .mll files on my hard drive.

Which doesnt surprise me, as .mll files are plugins/extensions for the Autodesk Maya 3d application, and I dont currently have that installed on this system.

The only other Melda files there would be on a system that are ones not part of or created by the installer, are melda license files and they have the extension .mlf

I would suggest you reinstall your Melda plugins taking care to ensure that you check the plugin folder location is set properly, and then make sure that your DAW is properly set up to use that plugin folder.
Unless you're using Maya, i have no idea why you would have .mll files on your system.

[MeldaProduction]

No idea. Never heard of .mll before and I'm none the wiser which DAW this bonkers chap is using

Malevolent Link Library. Users of these cursed binaries are slowly driven to madness.

:DDD