Analog Empire Plucks & Keys Crashes
-
- KVRer
- 18 posts since 9 Dec, 2015
In case, someone from Melda actually reads this:
I could successfully get a free license. I used MPluginManager to install the package, and the activation tab to activate it. MSoundfactory was already installed a few days prior, for Monastery Grand (which works flawlessly).
In a DAW, opening MSoundFactory and trying to load Analog Empire Plucks & Keys, an error message appears, followed by either a crash of the plugin (when DAW has sandboxing) or a crash of the DAW (when no sandboxing).
The error message seems to hint, that parts of the GUI are missing. Needless to say, there is no newer version of either MSoundFactory or Plucks & Keys. See below.
I could successfully get a free license. I used MPluginManager to install the package, and the activation tab to activate it. MSoundfactory was already installed a few days prior, for Monastery Grand (which works flawlessly).
In a DAW, opening MSoundFactory and trying to load Analog Empire Plucks & Keys, an error message appears, followed by either a crash of the plugin (when DAW has sandboxing) or a crash of the DAW (when no sandboxing).
The error message seems to hint, that parts of the GUI are missing. Needless to say, there is no newer version of either MSoundFactory or Plucks & Keys. See below.
You do not have the required permissions to view the files attached to this post.
-
martin-meldaproduction martin-meldaproduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=583716
- KVRist
- 273 posts since 6 Oct, 2022
It looks like something is wrong in your GUI data, the main file is missing. I recommend you to start MPluginManager and click repair install, use latest version 17.04 as these templates have been added recently. I think you are missing file C:\ProgramData\MeldaProduction\Data\GUI\.mfiles.mfs if you are on PC. Let me know if that helped.
Martin
MeldaProduction
MeldaProduction
-
- KVRer
- Topic Starter
- 18 posts since 9 Dec, 2015
First, thank you for the quick reply. Unfortunately, I had no success.
I started with your suggestion of repairing. It didn't change anything. I then uninstalled Plucks & Keys. To my surprise, my DAWs now couldn't find MSoundFactory anymore. And indeed, under the defined "VST plugins directory (64 bit)" path "C:/Program Files/VstPlugins/MeldaProduction"
I could find 2 of the free FX plugins I installed earlier, but no MSoundFactory.
I then again selected MSoundFactory in the MPluginManager and chose to repair again. This brought back the missing plugin files. But now ALL packages for MSoundFactory, when clicked in the plugin, produce this error message, just the GUI parts it states as missing are different, depending on the package. Even Monastary Grand, which used to work just fine, now complained.
I then re-installed Plucks & Keys. This reinstated the conditions laid out in my first post, with the exact same error message (control 35 etc.) and Monastary Grand working without any error report. However, this one time it didn't crash and I was able to do a screenshot, and indeed, pretty much everything from the GUI misses. I was so nervous, that I totally forgot to test, if at least some audio could be heard (assuming there's some kind of default patch). So I can't see for certain, if it is only a GUI problem.
Regarding version number: In MPluginManager, it says "Plugin v17.04" and "Installer v02.04" (the same it said before my initial post).
I started with your suggestion of repairing. It didn't change anything. I then uninstalled Plucks & Keys. To my surprise, my DAWs now couldn't find MSoundFactory anymore. And indeed, under the defined "VST plugins directory (64 bit)" path "C:/Program Files/VstPlugins/MeldaProduction"
I could find 2 of the free FX plugins I installed earlier, but no MSoundFactory.
I then again selected MSoundFactory in the MPluginManager and chose to repair again. This brought back the missing plugin files. But now ALL packages for MSoundFactory, when clicked in the plugin, produce this error message, just the GUI parts it states as missing are different, depending on the package. Even Monastary Grand, which used to work just fine, now complained.
I then re-installed Plucks & Keys. This reinstated the conditions laid out in my first post, with the exact same error message (control 35 etc.) and Monastary Grand working without any error report. However, this one time it didn't crash and I was able to do a screenshot, and indeed, pretty much everything from the GUI misses. I was so nervous, that I totally forgot to test, if at least some audio could be heard (assuming there's some kind of default patch). So I can't see for certain, if it is only a GUI problem.
Regarding version number: In MPluginManager, it says "Plugin v17.04" and "Installer v02.04" (the same it said before my initial post).
You do not have the required permissions to view the files attached to this post.
-
- KVRer
- Topic Starter
- 18 posts since 9 Dec, 2015
ADDENDUM:
Screenshot of the folder you mentioned. The file exists. What I find strange is the dates of the files and folders (2021 was even before I had this PC I'm working on, and the .mfs file states February 7th of this year? I installed Monastary Grand and EZConvolution in April and Pucks & Keys 1 day ago.
Screenshot of the folder you mentioned. The file exists. What I find strange is the dates of the files and folders (2021 was even before I had this PC I'm working on, and the .mfs file states February 7th of this year? I installed Monastary Grand and EZConvolution in April and Pucks & Keys 1 day ago.
You do not have the required permissions to view the files attached to this post.
-
martin-meldaproduction martin-meldaproduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=583716
- KVRist
- 273 posts since 6 Oct, 2022
The screenshots you attached made it clear - I now understand what’s happening on your machine. You still have the old "non-virtual" GUI files in your GUI folder, likely left over from previous installers. We don’t delete these automatically, as some users may store custom GUI data there.
To fix this:
- Delete the folder: C:\ProgramData\MeldaProduction\Data
- Optionally, delete these two files SystemFonts11.cache and SystemFonts11all.cache located in:
C:\Users\<username>\AppData\Roaming\MeldaProduction
- Run MPluginManager and click Repair Installation (without re-downloading).
Based on your feedback, I’ll see if we can improve the installation process further to avoid this. Hope this helps.
To fix this:
- Delete the folder: C:\ProgramData\MeldaProduction\Data
- Optionally, delete these two files SystemFonts11.cache and SystemFonts11all.cache located in:
C:\Users\<username>\AppData\Roaming\MeldaProduction
- Run MPluginManager and click Repair Installation (without re-downloading).
Based on your feedback, I’ll see if we can improve the installation process further to avoid this. Hope this helps.
Martin
MeldaProduction
MeldaProduction
-
- KVRer
- Topic Starter
- 18 posts since 9 Dec, 2015
Thank you so much!
Your instructions this time nailed it!
I did both, the necessary and optional step, and could see that only SystemFonts11all.cache had its date correctly at May 28th, in case that makes any difference.
After repairing without re-downloading, everything works just as intended. No error messages from MSoundFactory whatsoever. I might need to wait, until the demo mode is over (I thought I installed the free version, but it says Demo in the top left corner of the window), to see if anything else is coming up in free mode, but for now the problem is definitely solved!
Your instructions this time nailed it!
I did both, the necessary and optional step, and could see that only SystemFonts11all.cache had its date correctly at May 28th, in case that makes any difference.
After repairing without re-downloading, everything works just as intended. No error messages from MSoundFactory whatsoever. I might need to wait, until the demo mode is over (I thought I installed the free version, but it says Demo in the top left corner of the window), to see if anything else is coming up in free mode, but for now the problem is definitely solved!
