VST Effects Plugin

[Steven]

I did notice though that when going to update #2, while all still worked, some GUI VSTs would now lose their settings between being deselected/selected, which did not happen with the first update.  The editorless one still has full retention.

i cant reproduce any issues. Can you give me some steps and let me know which VST plugins are being used?

[sveakul]

Short and quick just to show an example:

1. Updated to mb_VST "First Update", using the three VST-2's LoudMax (https://loudmax.blogspot.com/), Wider32.dll (https://upload.disroot.org/r/jcNP90JY#r/TgK3WKfR4SQ4KIcpRwbLbt1CTI/gLwUTbT1hcfpOg=), and the Polyverse "Wider" (https://polyversemusic.com/downloads/legacy/InfectedMushroom-WiderV1.0.zip) (the latter's VST-2 file renamed to "Polyverse-Wider32.dll" to avoid interference with the second example which has the same file name).  Result was that all three show their GUI/Editor and retain their former settings when deselected/reselected.

2.  Update to mb_VST "Second Update."  Now, Polyverse-Wider32.dll will not retain its GUI's settings but reverts to default when it is deselected/reselected.  The other two retain fine.

Granted "one lousy example" isn't a lot to cry foul about, but as Update #1 allows me to have my cake and eat it too with the few plugins I actively use, I will stick with it for now.  I do not experience the "fast slider freeze" issue that Update #2 is meant to address.

[Steven]

that should be working now - same link as before

[sveakul]

Yes!  Update #3 fixes the problem.  Thanks for such a quick fix!

[MusicalCetacean]

Hi Steven, could you take a look at how the VST plugin (or MusicBee in general) handles high sample rate tracks? I've loaded two VST effects into MusicBee (FabFilter Pro Q 3 and Voxengo SPAN) which have real-time spectrum analyzers, and both of them don't display correct spectra when 96 KHz files are being played. The spectrum gets visually "squished" so that the wider frequency range of 96 KHz data is shown within a smaller range (up to ~28 KHz in ProQ 3 and 22 KHz in SPAN), so that spectral content is not shown at the right frequencies.

I suspect a MusicBee issue because those same plugins don't show this squishing when loaded in Foobar2000 (both using WASAPI exclusive mode output). Content above the frequency display range of the plugin is simply not displayed, rather than having the entire spectrum squished into the display range. This is more accurate to the waveform (cross-referencing static analysis tools like Spek).

It's possible to reproduce this issue with the resampling function in the MusicBee Player options. If resampling is enabled and set to 96 KHz, the display in SPAN won't show anything above the 11 KHz marker on a resampled 44.1KHz file, because after resampling, the 22 KHz content is remapped to 11 KHz in SPAN. The issue with 96 KHz files also disappears if they get resampled down to 48 KHz. I would greatly appreciate it if you took a look at this issue.

[nojwe]

Is VST3/64-bit VST supported?

[sveakul]

Is VST3/64-bit VST supported?

No.