MeldaProduction

ericb7799 · Post by **ericb7799** » Mon Dec 05, 2016 1:40 am

Been using Melda for a awhile. Recently installed clean Win 8.1 pro, use Studio One 3, Audacity and Reaper and either Melda Effects totally not being found or effects giving errors trying to open. Installed into the default dirs also tried manually into the STeinburg VST dirs but not working. Have tried reinstalling many times and not working. All my others, PC Win 7 pro and Mac work fine with Melda. Anyone have any idea what is going on?

.jon · Post by **.jon** » Tue Dec 06, 2016 8:43 am

No idea, but sounds like the easiest solution would be to just forget Win 8.1 and install either 7 or 10. Windows 8 wasn't a really successful version.

DarkStar · Post by **DarkStar** » Tue Dec 06, 2016 9:28 am

Do plug-ins from other developers install / work OK in those DAWs?

pone · Post by **pone** » Tue Dec 06, 2016 1:25 pm

You'd need to actually tell us what's in the error.

MeldaProduction · Post by **MeldaProduction** » Wed Dec 07, 2016 4:38 pm

My guess is corrupt installation, somehow, no idea

. Maybe missing kernel in C:/Windows or missing styles, just guessing.

steve2KVR · Post by **steve2KVR** » Wed Dec 07, 2016 4:43 pm

...also consider a possible "permissions" problem...IIRC the transition from 7 to 8 had some bumps like that, I was a sys.admin about that time.../s~

ericb7799 · Post by **ericb7799** » Thu Dec 08, 2016 9:29 pm

I have considered the permission issue. I already took ownership of relevant directories and files and also ran ICACLS to "grant everyone" on those.
I should clarify that I'm not actually getting any error messages in most DAWS. Just not discovering any MeldaProduction plugs, so they are not even showing in any effect or plug-in managers. All other plug-ins from other developers are working fine. Even Waves working without too many issues. If I have gotten any error messages, (Reaper one time did throw up some message about styles) when adding a VST directory in the Reaper preferences. Generally though, no error messages at all. The installer completes without error messages. I'm thinking it has something to do with the Melda file placed in c:\Windows.
What is the name of the file that Melda installs in C:\Windows? I know that I can't get Melda to work on one of my computers at work because cannot get admin rights to edit or add/remove any files on the C:\Windows directory. But in that case running the installer always fails on that issue. On this issue the installer completes with not errors and I can see the files in the installation directories after rebooting. But I will check c:\windows and see if that melda file might be missing there.

DarkStar · Post by **DarkStar** » Thu Dec 08, 2016 10:16 pm

MeldaProductionAudioPluginKernel64.dll
and
MeldaProductionAudioPluginKernel.dll

but don't do anything with them; they are essential and, I think, contain >90% of the functionality.

NB: Once Reaper has detected a problem with scanning a plug-in, it subsequently ignores that plug-in. You might try a "Clear cache and rescan".

MeldaProduction · Post by **MeldaProduction** » Fri Dec 09, 2016 9:05 pm

Correct, please check the files are there. If not, I'll let you know which other files to check

. Btw. could you verify the plugin DLLs are where they supposed to be?

DPhil · Post by **DPhil** » Sat Dec 10, 2016 6:30 am

I have a similar problem. Actually my AV gave an alert during the installation, telling me something tries to modify the system folder. Of course I blocked this because this happened never before with any other software and I'll not permit this. Is there a way running the installer without doing stuff in my system folder? I'd only like to test MAutoAlign and MDrumLeveler.

MeldaProduction · Post by **MeldaProduction** » Sat Dec 10, 2016 10:36 am

Basically C:/Windows seems the only reliable placement for shared DLLs (plugin kernel). Microsoft recommends C:/Windows/Shared32, which is a system folder as well, and unfortunately sometimes it just doesn't work. It almost looked like the system would need a restart for that. Other solution is quite more complex using system registry, which is even bigger evil, and hard to say how reliable it is. So we chose the simplest and most reliable option

. There's really nothing dangerous in putting the kernel there thousands of our customers have it there. You AV is just bothering you, so that you feel you need it, but the truth is, you don't.
I personally gave up on AVs with their neverending false alarms (and slowing down the system long) time ago. I just install one from time to time to perform a full scan, and then bye bye again

. Of course, you must NOT use warez if you don't have AV, because pretty much every illegal software contains at least one malware...

DPhil · Post by **DPhil** » Sat Dec 10, 2016 5:48 pm

I sit on the other end of the rainbow and don't see it that bad

Having multiple usb sticks and external hdd for data exchange, also via web, surfing through the web, online banking and so on. I need a AV and with Kaspersky I got one of the best and most reliable ones out there. Never ever had problems with any "good" software at all, but it keeps the bad away and notifies me ^^

If I remember correct there are several developers having their plugin kernels installed to "C:\Program Files" or "C:\Program Files (x86)" and just link from their vst2/vst3 container path to this. Never experienced any issues with that. Never saw a developer putting his files into the system root.

Anyways I just got a friendly reminder from one kvr user that the original ones where from Sound Radix and will install/work like a charme. I think I'll give them a try first before investigating this issue further more. Probably they'll already fit my needs.

Thank you

MeldaProduction · Post by **MeldaProduction** » Sun Dec 11, 2016 2:04 pm

Hehe it all depends on what "good" is

. Because technically writing to a system folder is not wrong, overwriting system files that would be a different story

.

MeldaProduction

KVR Audio

Can't get Melda effects discovered in DAWS