All MeldaProduction plugins updated to 14.12

[Nspace]

The Samplitude VST3 issue still exists! Something new about it?

The issue keeps coming out at Samplitude forum (you have to be registered to access it).
It is already acknowledged and since the developers have been increasingly responsive plus the new X6 version is coming sometime in May, then a fix is to be expected as part of the release, which will then be ported to version X5 as well.

[DaveClark]

Magix Samplitude Pro X? Suite versions have had serious problems with VST3s for over two years, especially with MeldaProduction plugins. I warned MeldaProduction about this probably two years ago, maybe more. I never received a reply.

Example project in which MCabinet 15.01 doesn't work properly when loaded into Samplitude Pro X5/X6 Suite, not even most recent Pro X6 Suite as of 23 October 2021, Build 21443:

http://www.execonsultingtx.com/wp-conte ... litude.zip

Project contains VIP file and the relevant Guitar Solo WAV file. Unless the project MIDI file is in the VIP file, it probably won't load the MIDI file, but that isn't required.

I've been working with the support folks at Magix for over two years on problems with VST3. Pro X6 Suite is better, but this project still doesn't work in two different Win 10 machines, i7 Sandy Bridge from 2013 and i5 from 2018, and verified by Magix support. Just move the Output knob to see if the volume changes or not. The Magix support folks contacted their developer(s) with this latest information about two weeks ago.

You can get the plugin to start working by various fiddling-arounds, but it's still not right. If you quit and restart Samplitude, then load this project unedited, it will fail again.

Before I developed this project, the VST3 non-functionality was intermittent, with Pro X5 Suite much more likely to fail than Pro X6 Suite.

MeldaProduction FREE VST3 plugins all seem to work, but the more recent paid-for ones can malfunction.

Intelligent Sleep on Silence and Smart Bypass settings do not seem to help, but these functions may be the source of Samplitude's difficulties.

Sometimes the MeldaProduction VST3 plugins will show "Sleeping" when they are supposed to be Active, but other times when they are malfunctioning the plugins will show "Active." That status indicator cannot be trusted when hosted by Samplitude Pro X5/X6 Suite.

The Magix developers may need some help from MeldaProduction to track this problem down. If I had a debug version of MCabinet, I might be able to do it myself, but of course, I don't have that. I believe that there is some miscommunication between host and plugin during instantiation of the plugin. I don't believe that Magix developer(s) are all that familiar with VST3 due to the number of problems I've seen over the past two years. Interestingly, other Magix products, even their entry level MusicMaker works with VST3s better than Samplitude. Entry-level Acid also works fine.