getmusicbee.com
MusicBee & Add-Ons => Customizations => Plugins => Topic started by: Steven on June 07, 2014, 07:40:58 PM
-
This plugin hosts VST effects plugins (but not instrument plugins)
https://getmusicbee.com/download/plugins/mb_VST.zip
unzip and put mb_VST.dll in the plugins folder. The source folder for the VST plugin dll's needs to be configured in the Plugin preferences panel but the default is the normal VST location so should work without modification.
The installed VST plugins should show and be selectable (the same as any winamp or MusicBee DSP plugin) in the Equaliser and DSP window
This plugin has a dependency on the Visual Studio 2010 runtime. You can download and install the runtime from:
https://www.microsoft.com/en-us/download/details.aspx?id=5555
-
Wow, Thanks steven ;D
-
I have updated the VST plugin zip to better handle editing VST parameters - a VST configuration dialog now stays open when songs change and should also now work better with some plugins can generate "access violation" errors
-
Changing from the "default" directory to another does not work for me. My plugins are located in C:\\Program Files (x86)\Vstplugins.
-
did you restart musicbee?
-
Restarted... The correct directory is selected in Preferences/Plugins. When I start the Equaliser/DSP panel none of my VST plugins show up. All of the other plugins "HDCD" etc. are listed but no VST.
-
i forgot to include bass_vst.dll
http://www.mediafire.com/download/soj85cck887a3hq/bass_vst.zip
unzip and place in the musicbee application folder
-
Great! Thank you very much :) :) :)
A.
-
Bass_vst fixes my problem...thanks. MusicBee is unhappy about several vst plugs and crashes. Removing them fixes the problem.
-
can you let me know the name of a couple of them so i can check what is going on.
-
Installed the latest version (2.4.5270)
Added the patch (2.4.5272)
Added mb_VST.dll to the Plugins folder
Added bass_vst.dll to the MusicBee folder
Created a VST folder within Plugins
Set the destination folder to C:\Program Files (x86)\MusicBee\Plugins\VST in Preferences\Plugins
Added VST plugins to the VST folder
Restarted MusicBee
No plugins show at all
OS is Windows 8.1
-
Set the destination folder to C:\Program Files (x86)\MusicBee\Plugins\VST in Preferences\Plugins
Set the destination folder to C:\Program Files (x86)\MusicBee\Plugins\VST
-
that's what I said I did
-
I just installed the new version of MB and the VST plugins are working great now :)
-
A couple of VST plugins seem to have some graphical problems.
For example two very good sounding VST equalizers (PSP Neon (http://bit.ly/PSP_Neon) and DMG Audio EQuality (http://bit.ly/DMG_Audio_Equality)) seem to work great sound-wise, but are hardly usable since any adjustments in their settings are not being graphically represented.
Edit:
Could some other MB user check this out?
(it could also be due to my older graphics card)
-
Thanks for the VST support!
I can confirm that some VSTs have graphical/interface problems. I'm trying to use TB Isone VST, but the interface doesn't respond or update with your mouse clicks so you can't really adjust things.
-
i was able to adjust the settings on the two i tried, but it was erractic. At least for the IB Isone, you can right click in the boxes to directly edit the values.
However i dont think there is anything i can do to help with the GUI handling - i expect there is something about the native VST plugin that MB is using that doesnt work well with some of the VST effects plugins.
-
Too bad. Thanks for having a look at it so fast.
-
Unfortunately sometimes MB (I use stable 2.4 release) forgets my exact current cofiguration of VST-plugin. Looks like MB doesn't remember preset I always use. So I force to go to settings of VST-device and check working preset. But while I was using Foobar, there was no necessarity to check behaviour of VST-plugins...
-
Doesn't work with mathaudio room eq vst properly http://mathaudio.com/download.htm. Whenchanged from bypass mode to eq there is no sound output. Any fix for this?
-
Hey, this doesnt work anymore! I can't load any vsts, it doesnt show anything. Also the bass vst thing isn't up anymore, thats probably it
-
VST also not working anymore. It worked fine but suddenly it stopped working. It does not show up anymore. None is selectable in the DSP plugins area. I do use a spectrum analyzer to sort out the rubbish. Hopefully it will be working soon again.
-
plugin has been updated with a fix for the initial loading of the available plugings not always working:
http://www.mediafire.com/file/fxp4xjrz4yur7aj/mb_VST.zip
-
Doesn't work with mathaudio room eq vst properly http://mathaudio.com/download.htm. Whenchanged from bypass mode to eq there is no sound output. Any fix for this?
Change the Routing from MIDI to Left+Right
-
Nice! :D But the refresh rate of the loaded VST plugin is buggy. Still the plugin works. Kindly please fix the bug soon.
-
I can't get any VST items to work. I've installed them, I've set the path, I've restarted, I've run as Administrator, etc. I cannot get any of the VST items to even show up as existing. I've used the newest update plugin as well.
-
I can't get any VST items to work. I've installed them, I've set the path, I've restarted, I've run as Administrator, etc. I cannot get any of the VST items to even show up as existing. I've used the newest update plugin as well.
I confirm, mine doesn't show either.
-
the VST plugins need to be the 32 bit version
-
the VST plugins need to be the 32 bit version
(http://image.prntscr.com/image/a3d31eeaaeda4f08aaf300d993c86567.png)
Yes, the plugins are 32 bit on a 32 bit OS.
Tomorrow I'll make an install on the Office PC to check if it's the system or the Musicbee plugin which is broken and report back.
-
I'm posting it here on the wishes of the moderator
I installed Musicbee for the first time a few days ago, everything went smooth except that it did not detect my VST plugins and as suggested by others in the plugins thread, I'm not the only one having this issue. Today I made a fresh install on my office PC, with the same results.
Plugins are all 32 bits and I've tried all things like starting the app elevated and changing the path of the VST plugins etc but no success.
Any help around this?
-
i assume the bundle you install creates separate folders for the VST2, VST3 and RTAS files so try configuring the plugin to point to the VST2 folder only.
The plugin cannot handle VST instrument plugins and i am not sure about whether VST3 works or not
-
the VST plugins need to be the 32 bit version
I'm using the 32 bit versions.
-
i assume the bundle you install creates separate folders for the VST2, VST3 and RTAS files so try configuring the plugin to point to the VST2 folder only.
The plugin cannot handle VST instrument plugins and i am not sure about whether VST3 works or not
So are we not supposed to move the .dll files to the MusicBee folder?
-
@Steven
The path of the VST2 plugins precisely matches the one in the Musicbee preferences. VST plugins are 32 bits just simple VST2 NO VST3 or VSTi
Any other ideas ?
-
i assume the bundle you install creates separate folders for the VST2, VST3 and RTAS files so try configuring the plugin to point to the VST2 folder only.
The plugin cannot handle VST instrument plugins and i am not sure about whether VST3 works or not
So are we not supposed to move the .dll files to the MusicBee folder?
no - where did you see that instruction? You need to configure the MB Plugin in Preferences/Plugin to point to the folder the VST plugins are installed
-
another possibility is there may be a dependency on some C++ runtime files that you dont have installed. Apparantly the developer of the BASS_VST.dll which musicbee uses for this plugin will be doing something to address that in a few weeks tiime.
-
i assume the bundle you install creates separate folders for the VST2, VST3 and RTAS files so try configuring the plugin to point to the VST2 folder only.
The plugin cannot handle VST instrument plugins and i am not sure about whether VST3 works or not
So are we not supposed to move the .dll files to the MusicBee folder?
no - where did you see that instruction? You need to configure the MB Plugin in Preferences/Plugin to point to the folder the VST plugins are installed
Confusion over your phrasing. Anyway, I guess the only way to fix this is for someone to actually watch my computer as I do it. Obviously something is not happening, and it's either within MusicBee or the software I'm installing.
-
Hi Steven, loving Musicbee! Best program for music organisation and playback I've ever used! I don't suppose you have any updates on the VST host plugin at all however? I have a pair of great speakers that so happen to annoyingly resonate and I use the fabfilter pro-q to sort them out. I've followed all the steps listed in the thread but I'm still not getting anything coming up. Thanks :)
-
another possibility is there may be a dependency on some C++ runtime files that you dont have installed. Apparantly the developer of the BASS_VST.dll which musicbee uses for this plugin will be doing something to address that in a few weeks tiime.
Finally encouraging news. Thank you Steven.
-
The Steinberg sound level meter https://www.steinberg.net/en/support/unsupported_products/slm_128.html doesn't get recognized. Does it not recognize vst3 plugins?
-
another possibility is there may be a dependency on some C++ runtime files that you dont have installed. Apparantly the developer of the BASS_VST.dll which musicbee uses for this plugin will be doing something to address that in a few weeks tiime.
I tried installing C++ runtime 2017 which ended in an unspecified error. My guess it requires some specific update to be installed from Microsoft. I think it's the issue why the plugin's aren't working. I'm waiting for Steven as he said something will be done regarding this.
-
another possibility is there may be a dependency on some C++ runtime files that you dont have installed. Apparantly the developer of the BASS_VST.dll which musicbee uses for this plugin will be doing something to address that in a few weeks tiime.
I tried installing C++ runtime 2017 which ended in an unspecified error. My guess it requires some specific update to be installed from Microsoft. I think it's the issue why the plugin's aren't working. I'm waiting for Steven as he said something will be done regarding this.
in the case of this plugin its supposed to be the 2010 runtime.
You can get it from here:
https://www.microsoft.com/en-us/download/details.aspx?id=5555
let me know if it solves the issue and i will add some instructions to the install if it fixes the issue
-
in the case of this plugin its supposed to be the 2010 runtime.
You can get it from here:
https://www.microsoft.com/en-us/download/details.aspx?id=5555
let me know if it solves the issue and i will add some instructions to the install if it fixes the issue
Yes sir it did, thanks a lot. Wouldn't it be a better idea to incorporate the C++ runtime dependencies with the plugin?
Thanks for the support Steven, highly appreciated.
-
Hi,
I have Windows 10 64bit & Musicbee v3.0.6276.
I've installed your plugin in "C:\Program Files (x86)\MusicBee\Plugins", checked that 2010 runtime is installed but the plugin just does NOT show up in the DSP window. Like it is not installed at all.
I've tried to run Musicbee as admin but still no luck.
Any ideas?
-
Hi,
I have Windows 10 64bit & Musicbee v3.0.6276.
I've installed your plugin in "C:\Program Files (x86)\MusicBee\Plugins", checked that 2010 runtime is installed but the plugin just does NOT show up in the DSP window. Like it is not installed at all.
I've tried to run Musicbee as admin but still no luck.
Any ideas?
In version 3.0.6276, the path of Plugins in Preference section is "C:\Program Files (x86)\Steinberg\Plugins". You must change that manually to "C:\Program Files (x86)\MusicBee\Plugins". I don't know if it was the same path in Windows 10 coz mine is Windows 7.
-
Btw, I was amazed with MusicBee (thank you very much Steven). Using ASIO as sound device in MB and enabling resampling of 48k in preferences, MB excels in sound in every player i tried in Windows system. Now, having tried and using two free VST plugins, ReaXcomp (multiband compressor from cockos) and TDR VOS SlickEQ (3-band parametric equalizer from Tokyo Dawn Lab), MB even pushed further with customizable sound enhancer to your own taste, be it just a multi media speaker system or a powerful audio system at your home. Great piece of software !!!
Here are the links of that plugins:
ReaXcomp - http://www.reaper.fm/reaplugs/ (just download the 32bit version of ReaPlugs Vst and uncheck all other plugins except ReaXcomp when installing. After installation, go to C:\Program Files(x86)\VstPlugins, copy the "ReaPlugs" folder to MusicBee plugins folder.
SlickEQ - http://www.tokyodawn.net/tdr-vos-slickeq/ (just download the Windows (no intaller) package and extract it to MusicBee plugins folder.
As I posted above, if it is the first time you are putting plugins in MB, then you must change the preference path of its plugins as in my case to "C:\Program Files (x86)\MusicBee\Plugins". (Apply)
MY SETTINGS:
Important: The position in MB’s DSP window of these two plugins, ReaXcomp must be over SlickEQ (or ReaXcomp first then SlickEQ). The 2 plugins must be active with no other DSP turned-on or the MB’s default EQ.
For ReaXcomp:
(In my case, moving the slider control of ReaXcomp crashes MB, so I just input values numerically).
If no values indicated, leave other config as it is.
Band/Frequency/Threshold/Ratio/Attack/Release/Gain
Band1/80Hz/-18/2.5/1.0/200/6
Band2/250Hz/-16/2.0/1.0/200/3
Band3/6000Hz/-3/1.0/10/100/0
Band4/12899/-3/1.0/10/100/1.5
You can increase bass boost by decreasing threshold to -3 if it is too weak for you.
For SlickEQ:
LOW: 80Hz, gain 4.0dB, curve is V or A (red-lit indicator)
MID: 144Hz, gain 1.7dB
HIGH: 6.5kHz, gain 3.5dB, curve S 0r Z (blue-lit indicator)
Click “AUTO” button (blue-lit indicator will turn off) so as not to activate auto-gain.
Increase OUT GAIN to 2.4dB if desired.
You can increase or decrease gains in frequencies in to your liking to compensate sound produced by your amplifier.
******************
Some modification to my previous ReaXcomp settings: (for 6000Hz & 12899Hz)
Band/Frequency/Threshold/Ratio/Attack/Release/Gain
Band3/6000Hz/0/2.0/1/200/0
Band4/12899/0/2.0/1/200/0
Changing values of threshold, ratio, and attack same as that of low ranges make these two frequencies more active I think, especially by increasing the threshold to negative values.
**********************
Here's another modification to my settings, and I think it improve much the function of the compressor (ReaXcomp);
- I gave values to "knees" and made changes to frequencies of mid and high.
band/freq/threshold/ratio/KNEE/attack/release/gain
1/80Hz/-16/5/2/3/160/6
2/250Hz/-16/5/2/3/160/1.7
3/1000Hz/-1.5/2/4/50/100/0
4/6000Hz/-1.5/2/6/50/100/0
I made changes also to SlickEQ;
LOW: 80Hz, gain = 0.2 (or increase if weak)
MED: 1260Hz, gain = 1.2
HIGH: 6.5kHz, gain = 2.0 (or increase if weak)
Try also to enable auto gain.
-
I recently did a clean install of Win 10 to get the creators update and for some reason I get an error about this plugin doing something bad in C++ (sorry about the technical description). I tried installing the VC Redist Steven linked on the first post, but windows tells me I have a newer version already installed, so I'm not sure where to go from here.
For the record I'm using the latest 3.1 beta (and everything worked ok on my previous install - also 3.1 beta)
-
Here's the error I keep getting:
(http://i.imgur.com/tdritXT.jpg)
-
Here's the error I keep getting:
(http://i.imgur.com/tdritXT.jpg)
I did not get if your running on 64bit of win10. If so, did you install both version of that C++ required; since i think MB is running on 32bit only.
-
I've tried both runtimes and get the same msg. that I have a newer version (I'm x64 btw)
I've had the plugin working before so I have no idea why it's giving me this error now.
I'm not going to worry too much about it, I don't use VST that often to begin with
-
Hello there,
I've registered specifically to describe what happen to me:
I've installed the plugin, worked perfectly for some time
After, I couldn't see the vst but they were active as I can still listen to the sound improvement
I've update the plugin to the new version and I was able to see the vst again (in the list)
Now it came back to the same situation, the effect are on but they are not visible (so i can't configure them)
Any ideas?
Thanks :D
-
Try with the latest 3.1 version of MB from the first forum topic to see if that makes any differences. It's working fine for me.
-
Try with the latest 3.1 version of MB from the first forum topic to see if that makes any differences. It's working fine for me.
Thanks for the reply :)
Updated with 3.1 but the situation is the same
The strange thing is the VST are actually loaded (if i move and put back the .dll file of the plugin I can hear the difference)
I can reinstall it, i guess, but I would like to find a solution...as I said before, when i update the plugin, at first restart, it was working fine, then...no :/
If i go to preferences-->plugin i can't see the plugin (can't uninstall)
Does anyone else experiencing something similar?
EDIT: I've managed to find the VST settings in C:\User\AppData\Roaming\MusicBee\VstSettings.dat , after delete, I can find the plugin back in the preferences and all the VST (obviously I need to set-up the sound again)
Maybe a bug from an unsupported VST?
-
Reply to
Try with the latest 3.1 version of MB from the first forum topic to see if that makes any differences. It's working fine for me.
Thanks for the reply :)
Updated with 3.1 but the situation is the same
The strange thing is the VST are actually loaded (if i move and put back the .dll file of the plugin I can hear the difference)
I can reinstall it, i guess, but I would like to find a solution...as I said before, when i update the plugin, at first restart, it was working fine, then...no :/
If i go to preferences-->plugin i can't see the plugin (can't uninstall)
Does anyone else experiencing something similar?
EDIT: I've managed to find the VST settings in C:\User\AppData\Roaming\MusicBee\VstSettings.dat , after delete, I can find the plugin back in the preferences and all the VST (obviously I need to set-up the sound again)
Maybe a bug from an unsupported VST?
Not been to this forum lately....
I hope that you had figured out your problem, if not, maybe this one will help.
*** In my case all plugins are in this directory, "C:\Program Files (x86)\MusicBee\Plugins", and see to it that all plugins are 32-bit (X86) versions, since MB is running on 32 bit.
*** One question though, are you using those plugins that I use or this is different plugin? Coz' I cannot guarantee it's compatibility with MB.
-
I am using Portable Musicbee since I have to change computers every now and then. I do all the editing on one computer, of which I am an administrator, but do the playing on another computer of which I am not an administrator. I have tried to copy the VST folder to the portable drive but the two computers show different lettering for the same drive. Is it possible to set the VST plugin in MusicBee to point to the portable drive no matter what letter it is registered on the computer? Can anyone help please?
-
I am using Portable Musicbee since I have to change computers every now and then. I do all the editing on one computer, of which I am an administrator, but do the playing on another computer of which I am not an administrator. I have tried to copy the VST folder to the portable drive but the two computers show different lettering for the same drive. Is it possible to set the VST plugin in MusicBee to point to the portable drive no matter what letter it is registered on the computer? Can anyone help please?
Yes, as long as the VST you are using is within the MB plugins folder. Just type the correct path of the plugins folder of MB in plugin's preference section, and see to it that the "mb_VST.dll" is there also.
Btw, for the information of all, my VST plugin dlls are copied from the original VST plugin folder when the VST is installed in "Program Files(x86)\VSTplugins", that's X86 since we only need 32bit plugins.
-
Hello,
Using MusicBee 3.1rc4 in WASAPI event mode. Installed mb_VST, which shows up in plugins as active. In DSP plugins section, the VST plugins in my VST folder show up and are selectable. However, after selecting one (Loudmax limiter) and restarting MB to be sure, no signal is being passed through the limiter--even wild settings have no audible effect on the music, and the Loudmax GUI meters show no signal is coming through it when a song is being played. Same thing when trying a different limiter (Yohng). Both limiters are in use successfully on other players on same PC (uLilith, Foobar). I do have Visual C++ 2010 redist installed (and 2013/2015). The bass_vst.dll is present in the MB directory. Everything is 32-bit (Win7sp1).
I see others have had issues with the VST plugins showing up at all; in my case they show up fine and are selectable/settable, just are not being used. Am at my wit's end as to what the problem may be--any ideas much appreciated! Hopefully as a new MusicBee user (GREAT player!) I have just missed a setting somewhere.
-
...I see others have had issues with the VST plugins showing up at all; in my case they show up fine and are selectable/settable, just are not being used. Am at my wit's end as to what the problem may be--any ideas much appreciated! Hopefully as a new MusicBee user (GREAT player!) I have just missed a setting somewhere.
Found the solution to this here:
https://getmusicbee.com/forum/index.php?topic=22824.0
-
Hello -
I've installed the VST Effects plugin in MusicBee 3.1. In Preferences, I changed the VST location to my preferred 32-bit VST plugin location.
When I restarted MusicBee, initially (for about 2 seconds) it looked like it was scanning plugins. Then I get the error:
"Runtime Error! Program: C:\Program Files (x86)\MusicBee\MusicBee.exe R6016 -not enough space for thread data"
The error dialogue provides an OK button, but when I click it the same error immediately pops up repeatedly. There is no way to proceed except to crash MusicBee via the Task Manager.
I've tried restarting MusicBee a few times, but the errors occur almost immediately. Any ideas?
-
Any thoughts?
-
Following up on this inquiry again.
-
When I restarted MusicBee, initially (for about 2 seconds) it looked like it was scanning plugins. Then I get the error:
"Runtime Error! Program: C:\Program Files (x86)\MusicBee\MusicBee.exe R6016 -not enough space for thread data"
The error dialogue provides an OK button, but when I click it the same error immediately pops up repeatedly. There is no way to proceed except to crash MusicBee via the Task Manager.
I've tried restarting MusicBee a few times, but the errors occur almost immediately. Any ideas?
You might have a problematic/unsupported VST plugin. I would remove all VST plugins in the folder and try adding one by one.
-
I just want to give all of you a hint. A friend of mine makes music and he knows everything about vst effects. He told me that a lot of free vst effects are not coded from scratch but made with a bulding bricks tool what doesn't make them very stable. They often cause problems in host programs.
So with that in mind it would be better to make a list of plugins that work without problems here. He tried some eq plugins for me and found one from a professional audio software company named Bluecat Audio. Here is the link to the EQ VST: https://www.bluecataudio.com/Products/Product_TripleEQ/
Please install the 32bit version to your musicbee VST folder and report if it works flawless. Maybe you know other free plugins that also work without problems? Please post it here so others can test and confirm.
Greetings from Cologne.
Elisa :P
BTW: Musicbee is such an amazing software. :-*
PS: I realised that the downloadlink isn't described as 32bit. So here is the link: https://www.bluecataudio.com//Vault/Products/Product_TripleEQ/BlueCatTripleEQVSTSetup.exe
-
Hi, I just have another hint. If your VST effects don't show up in the list than you have one plugin what causes that. You allways should separate them and try to add one by one to avoid crashes and the disappearance of your VSTs.
Here are some other plugin wich are working without any flaw. At least on my system.
- http://www.voxengo.com/product/oldskoolverb/ < Reverb (really cool)
- http://www.lesliesanford.com/vst/plugins/ < Delay/Reverb
- https://vladgsound.wordpress.com/plugins/nova67p/ < EQ
:)
-
Hi all -
Thanks for taking the time to respond. I really appreciate it.
Re: redwing - I have literally hundreds of VST plugins. Having to add them one-by-one would be extremely tedious.
Re: Elisa Cologne: Agreed that MusicBee is excellent! I really enjoy using it. And yes, I use several Blue Cat, Voxengo and VladG (as well as TDR) plugins.
So, the thing is: I use the same batch of plugins in various DAWs with no issues - neither during initial scanning of the entire batch of plugins, nor with actual use. So I suspect something is wrong with the MusicBee VST scanning process itself, rather than the plugins. I wonder if maybe it literally can't handle as many plugins as I have, which is why it reports: ""Runtime Error! Program: C:\Program Files (x86)\MusicBee\MusicBee.exe R6016 -not enough space for thread data" ...
-
Yeah, of course the Musicbee VST Plugin is just a vehicle, but Musicbee's intention isn't to load all kind of VSTs, because it makes no sense to use Flanger oder Delay in already finished songs. You only need EQ. Maybe Room, Dynamik and sattle Distortion/Saturation. So i would suggest to only copy usefull and working VSTs into the Musicbee folder to avoid crashing or not showing up of certain VSTs. My friend told me, even audio software has sometimes problems to load every VST Plugin, because some of them are buggy too.
So i think you should just take a look at your best and most usefull plugins, copy (separate) them into the Musicbee VST Folder and try out if they work properly. My friend did so and now I'am happy to have a nice EQ, because I don't like those EQs with just fixed frequencies. I also hope the Musicbee Plugin is getting better so that we can use more plugins. For a moment I was really happy because I had the Reaper EQ running in Musicbee but then it didn't work anymore (You can't delete bands.).
LG Elisa
-
Elisa, thank you for your notes. Really helpful.
In my case, I'm less interested in using plugins for listening enjoyment (EQ, saturation, etc.) and more as a vehicle for using MusicBee as a quick test tool when I don't want to fire up a DAW to check various aspects of audio using metering, room correction, track coherence, etc.
So now I've noticed another issue. Per your thoughts, I've created a unique MusicBee VST folder, set the MusicBee VST plugin to use that folder, and copied one core monitoring plugin, Sonarworks Reference 4, into the folder.
MusicBee successfully scans the Sonarworks plugin and lists it under "Equaliser and DSP Settings", which is good. I can activate the Sonarworks plugin, launch the plugin interface and make edits. The problem is, anytime I make a change to the plugin, the change is not reflected in the audio output unless I uncheck (deactivate) and recheck (activate) the plugin again in the Equaliser and DSP Settings window. I can literally perform the most audio-mangling changes in the plugin interface, and nothing changes in the actual processing until I uncheck and recheck the plugin. Effectively, it seems like the MusicBee VST plugin just takes a single snapshot of the Sonarworks plugin settings at activation and uses those, regardless of changes, until the plugin is deactivated and reactivated.
I tried another plugin, DMG Audio's TrackControl, and making changes in its interface does nothing to the audio output whatsoever, even after deactivating and reactivating the plugin.
At this time, it appears the MusicBee VST plugin may be in a fairly broken state. It obviously works with your plugin selections, but it's looking like some of the basic plugins I'd want to use simply don't work through its hosting mechanism.
-
I have to agree. Most pugins don't work or just don't work like they are supposed to. Thats the reason I wrote, it would be better to make a list of working plugins rather than wondering why most of the VSTs don't run properly. This Musicbee plugin needs a lot of fixing and can only be used for testing or with a view VSTs. The list of crashes and freezes is longer than the list of working VSTs.
So I'am sorry, but your planned workflow with Musicbee doesn't work at the moment. But who knows ... maybe there is a fix around soon? Lets hope. ;)
-
Ultradust and Elisa,
I have the same issue as Ultradust; the 3rd-party VST plugin shows up in the list and can be selected, but no audio is being passed through the plugin until the mb_vst plugin itself is deactivated/reactivated. When I discovered the latter, I thought my problem had been solved and posted here to that effect, later to find out that once exiting MusicBee and re-opening it, the VST plugin no longer was being used until mb_vst was once again deactivated/reactivated--not an ideal solution. This was with the LoudMax VST plugin, which I have used without an issue on 2 other players each using different VST hosting methods.
As a workaround I am now using MusicBee with the Winamp VST Host available here: http://www.pcjv.de/applications/winamp/ ; I found that unpacking the dll from the downloaded installer and selecting it via MusicBee's "Import Winamp" button by the DSP Plugins window results in a selectable choice in the DSP list. This host allows you to load only one active VST plugin at a time, but by using to load just the Acon "EffectChainer" plugin, multiple VST plugins may be used through that interface. This is working fine for me using LoudMax and a Meier Crossfeed plugin simultaneously with the latest MusicBee.
BTW the EffectChainer is no longer listed in the Downloads secion at the Acon Digital Media website, but can still be downloaded from there at this link: http://www.acondigital.com/software/EffectChainer102us.exe (http://www.acondigital.com/software/EffectChainer102us.exe) ; and the documentation here: http://www.acondigital.com/docs/EffectChainer10us.pdf
See if those solutions work for you until the mb_vst.dll gets a revision.
-
Nice work-around, sveakul. I will give it a try. Thank you.
:)
-
sveakul - yes, I am also using the Winamp VST host and using a chainer (Blue Cat PatchWork (https://www.bluecataudio.com/Products/Product_PatchWork) in my case) as a workaround. Still, would like to see the native MusicBee VST plugin work well at some point. :)
-
Hi ultradust,
Yes I would much rather use the MusicBee plugin than an 8-year old workaround designed for another player. When I first posted about this issue I went to the Bugs forum, and Steven offered to let me download a debug version of the plugin that creates its own logs he could analyze. I didn't follow that up because I thought I had solved the problem with the first deactivate/re-activate action, which as you know too was not a "sticky" solution.
Is it possible you might volunteer to run the debug version? I know it sounds lame not to do it myself, but you are using more advanced VST plugins, and have experienced the activate/decativate issue, plus one where MB would not allow you to vary the working VST in real-time, and also where nothing at all could make the VST function. Therefore, your results in the form of the debug log would be much broader, resulting in a better picture of exactly what the problems may be than my one-issue one-VST version would. So, if you feel like it, I encourage you to post in the Bugs forum and ask Steven for the mb_vst.dll debug version to try.
Thanks in any rate for sharing your experiences here! I'm glad that you too are able to use the same decent workaround for your own VSTs as I found. Sure wish I could spring for that Blue Cat chainer though!! :-\
-
sveakul, thank you for your excellent analysis and request. I'm really glad to meet someone thoughtful and committed to maximizing technical performance like you on this forum.
I believe the thread you were referring to is this:
https://getmusicbee.com/forum/index.php?topic=22824.0
I've posted there and requested the debug version.
-
Thanks a lot ultradust for agreeing to request the debug version mb_vst.dll and do the testing! Much appreciated. I feel that Steven will be able to find the needed fixes in short order after getting the logs. Hard to see how it could be a problem with the VST plugins themselves when the old Winamp host performs fine in the same environment. I'll be watching here and in the Bugs forum to see what comes of it.
-
Winamp's DSP plugin works far better then the native vst plugin for MusicBee. Far more plugins are compatible using the "8 years old" solution. I think the real culprit with the MusicBee's plugin are the Bass dependencies from un4seen and since the Winamp's plugin doesn't require those, it supports large lists of plugins.
I did some tests based on the information shared in above posts and found that none of the DMG audio plugin's work. Blue Cat's Patchwork also appears to have the same exact issues of compatibility like the MusicBee's VST plugin. Acon Digital chainer won't work. Host application returns error. DDMF Metaplugin as well as Image-Line's Modular host "report" working on every level "technically" but there's no audio output. But when hosted within the Winamp's DSP they work fine so the issue is definitely at the MusicBee's end.
mb_VST also apparently takes ample time to scan the plugins after the start-up. If you instantly open the DSP window, there are no plugin's in it, close it, open it after a while and voila! all are there. Winamp's DSP is always there as if it's build inside the application.
I'm myself using Winamp's DSP and it work flawlessly, the only problem being the inability to host more then one effect, no support for vst3 and inability to save/recall multiple snapshots/presets. Apart from the Equalizer, I always need a declipper because of the large collection of field recordings. When using a chainer, it adds to the latency and with that many loops hardly an ideal solution.
No doubt the VST plugin needs to be fixed. Some very extensive testing/debugging needs to be done. However, we can't expect Steven to do everything alone. Someone with the coding knowledge needs to volunteer to get it fixed. I'm ready to do any testing/debugging if it helps.
Also, I don't agree with Elisa on the point that most of these plugins are developed casually. There're like 5000 reputed companies in this field with semi-large to very large research and development wings with personnel being highly talented and experienced. Most of the stuff on the market is as solid as the Adobe's.
-
For anyone looking for a solution, I did some more test and found a host that appears to be working fine with mb_VST. Unlimited effects, instruments, VST3, custom programs/blanks, wet/dry, and tons of other stuff. Everything that an advanced DAW would offer. An ideal solution really ( or more like an ideal alternate solution :P )
http://www.mutools.com/mux-product.html (http://www.mutools.com/mux-product.html)
(http://t14.imgchili.net/116538/116538664_11.jpg) (http://imgchili.net/show/116538/116538664_11.png)
-
Thanks for the heads-up on this wealstarr, nice. Keeps everything in one folder and almost half the price of the BlueCat chainer.
I noticed that on the mutools website in the docs area for MUX, there is a section (http://www.mutools.com/info/docs/mux/using-vst-plugins.html) that leads with "MuTools apps support VST plug-ins up to VST version 2.4." Did you find that it does take VST3 also? Web documentation is often out-of-date; couldn't try it myself as the plugins I use are all 2.4.
I hope your work on the mb_vst host will open up use for any plugin but until then nice to know about a chainer that works right now with it "clean."
-
Thanks for the heads-up on this wealstarr, nice. Keeps everything in one folder and almost half the price of the BlueCat chainer.
Minihost Modular by Image-Line is Free, efficient, easy to use and has a very low memory footprint. Also, it doesn't come bundled with all the factory patches/presets/modules basically useless for the users who just want to process audio through VST's for listening pleasure, perfectly suits them. But unfortunately not compatible with mb_VST. If this plugin ever get an update, I'll be sure to test it's compatibility again.
oh! and my bad, MUX doesn't support vst3 format yet. Comes as a surprise though for the professional utility it is.
-
Just some additional observations when using this plugin host and compatibilities from my own testing:
1. Tried replacing the bass_vst.dll that mb_vst wraps with version 2.4.0.8 from the Github repository (https://github.com/r10s/BASS_VST/tree/master/bin/win32) which is dated February 27, 2015, newer than the one supplied by MB (which is the same one available at the normal BASS un4seen address ) which is dated 9/17/2013 but has a "2.4.5" version number. The changelog posted at the BASS forum (http://www.un4seen.com/forum/?topic=5559.msg125834#msg125834) indicates:
v2.4.0.8 contain the following enhancements:
BASS_VST_Get/SetChunk added: plain binary parameter data handling
BASS_VST_Get/SetProgramParam length parameter added: to yield better .Net interoperability
Default/last parameter value handling optimized: as some VSTs can dynamically add/remove parameters
Unfortunately, this newer bass_vst.dll did not stop me having the same errors/crashes with certain VST plugins on mb_vst as the MB supplied one did. Decided to keep it anyway, I'm a sucker for a newer build :)
2. Partly repeating wealstarr's obs here: Acon Effect Chainer does not load, nor does the Case Meier Crossfeed <sob!> or LoudMax.
3. Both the Unlimited (Sonic Anomaly) and the Maxwell Smart 3 limiters load and work great; which one to use is a matter of taste. Nice metering and more flexibility on the Unlimited.
4. The Bauer crossfeed VST (http://bs2b.sourceforge.net/download.html) works when loaded alone, or with the Maxwell Smart 3 limiter, but crashes if the Unlimited is chosen.
For what it's worth. I am using the Bauer and the MS-3, but if you don't need headphones crossfeed the Unlimited is the more flexible and better-GUI limiter.
I am happy with the default MB equalizer, but found that the rather cool free TDR Nova equalizer VST also works with mb_vst, at least on its own, didn't try a combo with other VSTs loaded.
Of course what is really needed is either a re-write of mb_vst or a bulit-in VST host like with the uLilith player. Here's hoping somebody will take this on. Until then, if you've tested other stuff that works with mb_vst, post here and help us out.
-
Hello gaiastar,
Following up here on your questions concerning VSTs in the "Questions" forum.
1. "Unlimited" works like most compressor/limiter combinations (incl. Voxengo Elephant) in that it allows you to apply a peak gain across a chosen portion of the input audio's dB range while trying to eliminate any distortion effects of peaks it is limiting and keep the boosted audio range sounding "natural." I say "trying" because various CL's have varying success, and how you adjust the "threshold" and "output" levels as well as response speed, etc. is important. This sounds more intimidating than it actually is. The best place to start is read the manual that comes with the "Unlimited" download at Sonic Anomaly, then start experimenting with the slider positions. Like so many things it's all up to what sounds best for YOU.
How you have the MusicBee internal equalizer set vs. somebody else's setting is going to affect what compressor/limiter settings you decide on. With the equalizer set to what sounds best to me BEFORE loading the limiter, I then have the latter set to a -1.5db Threshold and a -.49db Output, with "Character" and "Response" set to .2 These are pretty conservative settings so you may want to reduce your Threshold for a "louder" sound. It's easy to experiment with because MusicBee will apply the changes while you have audio playing, not wait for a "restart".
2. I'm not using any "audio analysis" plugins myself but there a ton of free VST's out there to try, including ones that just provide a spectrum display. Beware though that many will NOT work with MusicBee's mb_vst host, as you can see by the preceding posts on this thread. You can find a lot of them here:
https://bedroomproducersblog.com/free-vst-plugins/
A free spectrum analyzer I have used with other VST-capable players is the Voxengo SPAN:
http://www.voxengo.com/product/span/
Tell us what works/doesn't work for you! We are all hoping that somebody gives mb_vst a re-write soon.
-
Would love to hear from anybody out there using the MusicBee VST host, and if so, what is working/not working for you in terms of VST plugins?? Got real quiet real quick in here :(
-
Greetings. I'm attempting to use the following VST plugin in MusicBee (new user).
https://www.audeze.com/audeze-reveal-plugin
(https://i.imgur.com/ydEgBal.png)
It is a plug-in for my (and all Audeze) headphones that tunes the audio just a little bit to maximize their features. I've used it with Foobar for a long time, but am giving MusicBee an audition to see if it's time to transition over. Well, after setting up the VST host plug-in, I am able to see and activate the plugin in the DSP interface normally.
Unfortunately, the "Mix" dial in the application appears to be misbehaving. The higher I turn the "Mix" dial (the dial with "Dry" and "Wet" at the 7 o'clock and 5 o'clock positions, respectively) the quieter the volume gets. At 100% "Wet" the sound is completely off. The only effect this dial should have is changing the sound a little bit, but it should have no affect on the volume itself. The "Gain" dial appears to be behaving normally.
Not sure if I'm doing something wrong or if it's a current limitation of the MusicBee application, but given it works in Foobar and JRiver and in wanting to make a decision on whether to keep using MusicBee, I thought I'd ask. It's pretty important to me. :(
Any insights will be appreciated!
-
Hello and thanks for posting. Unfortunately, the MB VST status at this point is, either the VST plugin you try works, or it doesn't work, as you can see by reading this thread. Steven is not currently working on mb_vst, and the 3rd-party BASS component it depends on, bass_vst.dll, hasn't been updated in several years. So it's a matter of finding another VST plugin that does the same thing and giving it a try.
I'm not sure what the "Mix" option on the Audeze plugin actually does, but if it involves headphones crossfeed, a crossfeed VST that does work with the MB host is the Bauer stereophonic-to-binaural DSP, which gives you the choice of the C.Moy, Meier, and its own default algorithms. Again, it plays nice loaded on its own but can cause a crash if another (but not all!) VST plugin is loaded at the same time. BS2B is here: https://sourceforge.net/projects/bs2b/files/plugins/VST%20plugin/2.1.0/vst-bs2b-2.1.0-win32bin.zip/download (https://sourceforge.net/projects/bs2b/files/plugins/VST%20plugin/2.1.0/vst-bs2b-2.1.0-win32bin.zip/download)
Again I encourage those who find VST plugins that DO work properly to post here and help others out with the same dilemma!
-
Understood, sveakul. I'll reach out to Audeze to see if maybe they can tweak their application in a future update to be more compatible with MusicBee.
And unfortunately, I'm not versed enough in the plugin to know what it's doing either, only that the left dial subtly changes the sound.
The features MusicBee has really makes me want to transition over, but this makes me pause a little bit. Otherwise, it's a great application and the skin I'm using on it makes it look exactly like my Foobar setup. I didn't expect everything to transition over perfectly, so I'm content in waiting for a possible solution from either Audeze or MusicBee.
-
dreams-visions, one thing you can try is bypassing the MusicBee VST host system altogether and instead loading "Winamp VST Host", a dsp plugin that functions in place of mb_vst.dll and bass_vst.dll. That plugin is available here: http://www.pcjv.de/applications/winamp/ (http://www.pcjv.de/applications/winamp/)
After downloading the latest version, use 7-zip to extract dsp_vst.dll, and put that in the MusicBee plugins folder, then restart MB and check the DSP Plugins window. This plugin allows only one VST to be used at a time, however, it will successfully load the EffectChainer VST host plugin, which can then be used to run multiple VSTs at the same time. The link for that is in the post here: https://getmusicbee.com/forum/index.php?topic=13022.msg135966#msg135966 (https://getmusicbee.com/forum/index.php?topic=13022.msg135966#msg135966)
I used this solution for a while, but when my needs went down to only one VST (a limiter) that worked fine with the MB native host I stuck with that. But try this and see if it allows you to use all the Audeze plugin's controls. Then please let us know the results!
-
Just found out that another developer has been making some improvements/changes to the bass_vst.dll, which has always been a 3rd-party project and not the work of either Un4seen Developments or Steven. In a thread at Un4seen he posts a link to his midi player project that, when downloaded and unzipped, contains 32 and 64 bit binaries for the modified bass_vst.dll as well as the source code. His mods to the one on the Git are listed as and I quote:
- Modified IDLE_UNLOAD_PENDING_COUNTDOWN from 10 to 5 sec. Since some plugins require complete unload before reload 10 sec wait time is too much.
- Added cleanUpPlugins() function to remove loaded plugins before unload. It matters when you load/unload bass_vst dynamically.
- Added Visual C++ 6 project for x86 version.
- Added BASS_VST_SetEditKnobMode (knobMode 0: circular, 1: circular relative, 2: linear)
- Modified BASS_VST_PARAM_INFO members maximum characters to 24.
(I know VST specification dictates maximum 8 character but it is ridiculously low and no plugins/hosts respect this limit.)
You may want to try this version if you are having problems with certain VST's and MusicBee. A quick first test showed it didn't correct two of my obvious "offenders", but your mileage may vary. The forum thread containing the relevant link is here: https://www.un4seen.com/forum/?topic=18255.0 (https://www.un4seen.com/forum/?topic=18255.0) ; check the second post.
-
>:(
I put mb_VST.dll in the plugins folder
and bass_vst.dll in the main MB folder
I am running WIN10 64Bit - MB 3.2.6827
on trying to install the Runtime Package i got an error "newer version of this ... is already installed".
further ...
Set the VST plugins directory to: C:\Users\xxx\Desktop\MusicBee\Plugins\VST (this is where MB is installed)
and put bs2b_vst.dll there (was looking for a convolver for my DT1990Pro)
started MB new many times now ...
VST Host shows up in the settings/plugins section, but no stereo-to-binaural effect shows up.
What am I missing?
-
Hi nepanitukka: The runtime error (I assume you were trying to install VS 2010 C++) was just because you already have a newer version of Visual Studio runtimes installed. I'm not sure if the latest VS is backwards-compatible to plugins built with 2010, but Windows 10 has the Microsoft "Universal CRT" (https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt/) which to my understanding allows projects that were built with older redists to run. So, we'll leave that one alone for now.
1. In Prefs/Plugins, does vst host show as being enabled (if it is, a "disable" button should show)?
2. In the 'source folder for the VST plugins" box below, is the correct path to the folder containing bs2b_vst.dll indicated?
3. If any of the above needed to be done, save afterwards and restart MusicBee.
4. In Prefs/Player/Equaliser & DSP(button on lower right)/Equaliser & DSP Settings page, does bs2b_vst.dll show up in the list box of DSP Plugins? If so, check the box next to it; then, double click it to bring up its GUI and make any adjustments you require. Be sure its box stays checked. Exit the DSP window, Save, restart MB just for good measure.
Any luck now? I have the bs2b_vst.dll installed (MusicBee 3.2.6856, Windows 7SP1 32-bit), and it works for me (I use it to apply some Meier crossfeed for headphones). However, you should know that VST support on MB is a bit "twitchy", in that if you are using other VST plugins at the same time, it can cause a fail in one or the other (or not). And there are cases where some plugins simply won't work at all. But as I say, this one does for me, so hopefully it will for you too despite our different OS platforms.
-
Thanks for your answer.
Hi nepanitukka: The runtime error (I assume you were trying to install VS 2010 C++) was just because you already have a newer version of Visual Studio runtimes installed. I'm not sure if the latest VS is backwards-compatible to plugins built with 2010, but Windows 10 has the Microsoft "Universal CRT" (https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt/) which to my understanding allows projects that were built with older redists to run. So, we'll leave that one alone for now.
yes, was trying to install the runtime (in the XP days you had to install all versions that were needed by different programs) - Didn´t know about the "universal CRT"
1. In Prefs/Plugins, does vst host show as being enabled (if it is, a "disable" button should show)?
Yes - there is a "disable" button
2. In the 'source folder for the VST plugins" box below, is the correct path to the folder containing bs2b_vst.dll indicated?
Yep
3. If any of the above needed to be done, save afterwards and restart MusicBee.
Yep - restarted many times
4. In Prefs/Player/Equaliser & DSP(button on lower right)/Equaliser & DSP Settings page, does bs2b_vst.dll show up in the list box of DSP Plugins? If so, check the box next to it; then, double click it to bring up its GUI and make any adjustments you require. Be sure its box stays checked. Exit the DSP window, Save, restart MB just for good measure.
No! it´s just the standard DSP Plugins ...
I tried also to set my standard VST Plugins folder in MB ... But also there - none of the VST plugins are showing up under Prefs/Player/Equaliser & DSP
Any luck now? I have the bs2b_vst.dll installed (MusicBee 3.2.6856, Windows 7SP1 32-bit), and it works for me (I use it to apply some Meier crossfeed for headphones). However, you should know that VST support on MB is a bit "twitchy", in that if you are using other VST plugins at the same time, it can cause a fail in one or the other (or not). And there are cases where some plugins simply won't work at all. But as I say, this one does for me, so hopefully it will for you too despite our different OS platforms.
The crossfeed is what I am looking for ... anyone else is running this on 64BitWIN10?
No luck for now.
I tried also deinstall, delete and reinstall of the mb_VST.dll and bass_vst.dll ...
............
Which versions of the two dll´s are you using? I picked them here in the thread ...
-
You may want to try this version if you are having problems with certain VST's and MusicBee.
Yeeha! Using this bass_vst.dll it´s up and running ...
-
You may want to try this version if you are having problems with certain VST's and MusicBee.
Yeeha! Using this bass_vst.dll it´s up and running ...
Hey, terrific! I'm glad that info I posted about the alternative bass_vst.dll (version "2.4.0.10", mod 02/04/2017) helped somebody. I have been using that one as well since I found out about it, although the one at the GitHub location (version 2.4.0.8, mod 02/27/2015) was working for me also. As far as the MusicBee mb_VST.dll host I've always had the latest one from the plugin site, ver. 1.0 mod 01/04/2017.
Please let us know if you have good/bad experiences with other VST's using this combo so others may benefit.
I also like to use an adjustable limiter which I find is needed for a lot of radio stations with bad clipping/compression, and have found that attempting to use bs2b_vst.dll ahead of the "Unlimited" (by Sonic Anomaly) limiter will cause MusicBee to crash when attempting to play, though either will work fine alone. However, using the "Maxwell Smart 3" limiter instead after the crossfeed plugin causes no problems. As you can see by the whole thread, it's kind of a hit-and-miss situation with MusicBee and VST's.
-
Hey, I am writing to get help with adding a specific VST to the MB.
The VST I am looking to add are from here https://goodhertz.co/
I dont seem to be able to get it done :(
I have installed the plugin and set the folder right: It did not work
I have isolated only one plugin, it did not work,
I dont know what is wrong.
Could it be because the plugin is 64 bit and MB is 32 bit ?
Sorry if what I say is not enough, will provide more information.
Any help will be appreciated.
Thank you for your time !
-
Yes, they'll need to be 32-bit plugins to work with a 32-bit host.
If you describe what type of VST effect you are looking for, maybe I or others can suggest one that we already know works well with MusicBee.
-
Well basically, what I am trying to do is achieve something like this, just for the fun of it and to get my hands dirty with some compressors and the likes.
https://www.youtube.com/watch?v=bF0sZNFSibg
could you suggest me ones with compressors and the likes, anything that you can use to play around with the sound. Hell, I would love it if anyone could suggest me their favorite since I just discovered this plugin and want to see how peoples are using it :)
So yeah, you can give me a list of VST's if you want to :)
Just trying things out here !
Thank you for your time !
-
The only VST I currently use with MusicBee is a compressor/limiter, "Unlimited" by Sonic Anomaly; works fine with the MB host and allows the adjustments I need, plus the bonus of being free: https://sonic.supermaailma.net/plugins (https://sonic.supermaailma.net/plugins)
-
Wow, will surely check that out ! :)
Thank you for the help sveakul !
It is much appreciated.
-
Hi,
I am writing again :-X
I took a better look at the the image on the VST plugin itself and saw the VST called AALTO.
I downloaded it's trial version to check if it works but it does not seem to load up.
It is 32 bit and I have set up the folders right.
Has anyone been able to use this. I am just curious since it is show on the image itself. Figured it would work.
Thank you for your time!
-
I'm not sure what you mean by "I took a better look at the the image on the VST plugin itself and saw the VST called AALTO"--image on WHAT plugin? It's certainly not an "image" on the plugin I mentioned. Madrona Labs produces Aalto, not Sonic Anomaly.
-
Based on some information on the bass forum i have updated this plugin:
- should no longer have a dependency on the old visual c++ runtime dlls being installed
- makes use of the chunk api so all settings should now be persisted (only applies to some VST plugins)
Its important you download and replace both these files:
https://www.mediafire.com/file/ar4og0r1hd9m5o6/bass_vst.dll/file
in the folder MusicBee is installed
https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file
in the Plugins sub-folder MusicBee is installed
-
Thanks Steven for working on these updates! I have been using the bass_vst.dll version 2.4.0.10 for a while as modified by Falcosoft (discussed over at the bass forum). With your new version, there hasn't been any problems using the one VST I have settled into, but noticed that the same problems I've had trying a couple of others persist--for example, LoudMax.dll loads without errors, but no signal is being passed through it, while MeierCrossfeed.dll upon loading will throw this error message:
That said, I am certainly not a prolific VST user and hopefully others can give your mods a more proper test with a wide variety of plugins. I'm pretty much settled on the conclusion that VSTs are one of those things that can never be counted on to work cross-platforms. The stablest example I have found is the uLilith player (which I use for one-off file playback before deciding if I want to include it in my MB library), which has a built-in VST host that has yet to not work with a plugin.
-
the reported error with MeierCrossfeed.dll is fixed - it had no editor for configuration.
for loudmax.dll, it visually appears no signal is being processed but changing the parameters works ie it is working.
-
Steven: re-downloaded both your posted files and now the MeierCrossfeed.dll doesn't throw an error. When used within uLilith's host it does show a simple slider control when asked to open a "parameter window", so I assume that's coming from uLilith as opposed to the VST plugin itself. Not actually useable without that though, so I'll look for another crossfeed solution. FYI I was trying the one at the link here: https://hydrogenaud.io/index.php?action=dlattach;topic=108412.0;attach=10037 (https://hydrogenaud.io/index.php?action=dlattach;topic=108412.0;attach=10037) .
Can confirm that loudmax.dll actually does work, sans its VU meter readout--funny though, if you click on a slider and hold, the meters come to life, but then freeze when you release the mouse.
Thanks again for these revisions, I hope there is some more user feedback generated so as to get a clearer picture of what now works vs. what still is problematical.
-
Some more testing: with both the new mb_vst.dll and the new bass_vst.dll, noticed that the limiter Maxwell Smart 3 (https://static.kvraudio.com/files/1955/maxwell_smart_3.zip (https://static.kvraudio.com/files/1955/maxwell_smart_3.zip)) creates pulsing artifacts while loaded; rolling back mb_vst.dll to the original version, but KEEPING the new bass_vst.dll, result in clean playback with that VST.
-
the old mb_vst.dll is not applying all the settings (the chunk settings)
while it is true what you say about the pulsing effect with the default settings, i believe MB is applying them correctly and adjusting the vst settings removes that effect
-
With the new mb_vst.dll I personally can find no setting of the MS-3 limiter that eliminates the pulsing effect; on the other hand, Sonic Anomaly's unlimited.dll continues to work just fine (ergo, I stick with that). Granted that it will take a lot more than the experiences of one user to provide any accurate assessment, especially as we're dealing with such a wide variation of possible VSTs.
One more for the road: Acon's EffectChainer.dll v.1.02 (http://www.acondigital.com/software/EffectChainer102us.exe (http://www.acondigital.com/software/EffectChainer102us.exe)) loads but there is no access to the interface when double-clicked, required to actually set it up.
So hey everbody, if you're reading this and you use any VSTs, how about letting us know your experience with the new files, while Steven has found enough time to do some tinkering on this plugin?
-
Steven: I notice that your mb_vst plugin from the link on its MusicBee Addons/Plugins page has not been updated to match the one you posted here on January 6; is this just an oversight or is it because you are still testing with it?
-
i will leave this a while
-
OK, thanks for the info! As I mentioned the original still works well with the new 2.4.0.9 bass_vst.dll now in the MB 3.3 updater; the chunk data support by your new mb_vst may well fix other folks' issues though.
PLEASE, any VST users out there, do some TESTING, and POST! While the verdict is still open and Steven is still working with the plugin. Where is everybody??
-
i will leave this a while
Thank you for the much needed update. More plugins work now. Snapshots are also being saved now. TDR and DDMF plugins that previously just bypassed the audio are working now. It's important to mention that TDR Nova is one of the best free dynamic EQ out there.
However, DMG plugins still not working. The audio is filtered but the GUI is unresponsive. It works only for the first time it's activated/deactived then becomes unresponsive as soon as the track changes or any links/toolbars are clicked and stays that way.
@Steven: can you help me with this plugin ? https://dmgaudio.com/products_equick.php (https://dmgaudio.com/products_equick.php) The plugin works fine, only the GUI is not responsive. I purchased it for a hefty price it makes me sad I can't use it :(
-
Hi wealstarr, good to see you back here and glad to know the new VST changes helped you with more plugins. Did you update both bass_vst.dll (now in the regular update zip for MB 3.3) AND the mb_vst.dll from the link in Steven's post here (https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file (https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file))?? I had issues with a previously problem-free VST (Maxwell Smart Limiter 3) that disappeared when I rolled back to the original mb_vst.dll (but kept the new bass_vst.dll). Also, can you check if the Acon Effect Chainer is loading for you now? A no-go for me with any file combination.
-
Hi sveakul good to see you too bud. Yeah I've updated the new mb_VST. I already had the newer version of bass_VST.dll that is 2.4.5.0 so I skipped that from Steven's post.
Although it's still buggy but solves a lot's of issues, the most prominent of which was not saving the snapshots/banks. I've tested the latest version of this plugin with quite a lot of plugins and it saves the snapshots just fine. All Voxengo plugins had this issue but it's solved now. And all the Toneboosters, Sonible, Fabfilter, Acon plugins are working as they should, no errors. Oh! and Tokyo Dawn Labs plugins are also working fine without any errors.
However, DMG Audio plugins still have that GUI not responding issue that I was seeking the help for. So it's still work in progress. We can only hope that Steven get around one last time to update this plugin and it becomes stable and fully functional.
I did't try Acon chainer but I did tried another VST based wrapper with the mb_VST plugin and it's working the same way the mb_VST works. Fine with the plugins that already work and buggy with the plugins that have errors with mb_VST plugin. I don't think we need a wrappers anymore within Musicbee since the snapshots are being saved now and multiple plugins can be hosted. Moreover wrappers solve nothing that mb_VST throws errors for. I think the wrappers are only needed if a plugin has no support for VST2 or for the bridging of 64bit to 32 bit. More and more companies are now ditching the 32 bit versions. Toneboosters being the latest in the list. Someone also complained about Goodhertz plugins not being detected, cuz they are only 64 bit. It should also be noted that the wrappers will add unnecessary latency to the stream.
Here's a wrapper that you should try out
https://ddmf.eu/metaplugin-chainer-vst-au-rtas-aax-wrapper/
I will await for your analysis and please continue posting in the thread, you've been a lot of help.
-
Hi wealstarr,
Great on using the newly modified mb_vst.dll host!
You mentioned that you didn't also go to the new bass_vst.dll because you already have the "newer" 2.4.5.0 version. Actually, if you mean the one originally supplied with MB before now, which was the same as the one at the regular un4seen.com download link, the mod date on that is actually 9/17/2013, so a much older build. My own belief is that the version number on that one is a typo for "2.4.0.5". Supporting that would seem to be that there is a bass_vst.dll over at Github with a mod date of 2/27/2015 with a version number of "2.4.0.8", with these listed enhancements:
"BASS_VST_Get/SetChunk added: plain binary parameter data handling;
BASS_VST_Get/SetProgramParam length parameter added: to yield better .Net interoperability;
Default/last parameter value handling optimized: as some VSTs can dynamically add/remove parameters."
These changes resemble the ones made by Steven and note that his own version was given the number "2.4.0.9" which follows the Github one's convention.
So, you might want to try using that one and seeing if it helps solve issues still outstanding after going to the new mb_vst.dll. I still have plugins that will crash or produce the "dead GUI", but worth a shot.
Thanks for the tip on the chainer, will take a look!
-
Hi again sveakul,
Thank you for pointing out bass_VST details. If it wasn't for you, I would have never guessed. Okay so I grabbed to newer one from Steven's post but unfortunately it does not solve the "dead GUI" issue for DMG Audio plugins. Appears like I have to stick with Toneboosters for now.
Thank you again for the help, sveakul. Highly appreciated.
-
An interesting recent post at un4seen on bass_vst.dll versions: http://www.un4seen.com/forum/?topic=18504.msg129790#msg129790 (http://www.un4seen.com/forum/?topic=18504.msg129790#msg129790)
Also note the 2.4.0.10 build with a 12/15/2018 mod date downloadable here: https://github.com/Falcosoft/BASS_VST/releases (https://github.com/Falcosoft/BASS_VST/releases)
-
Some recent news about the status of bass_vst.dll is over at the un4seen forum. In summary, there is a new version available in "beta" status that incorporates additional functions from the "BaseHead" version merge; as the source code for those was only recently made available, this version is currently the ONLY one that has them. In addition to some fixes, these functions have been added:
BASS_VST_ChannelCreateEx
BASS_VST_ChannelSetDSPEx
BASS_VST_CheckPreset
BASS_VST_StoreOldPreset
BASS_VST_StorePreset
BASS_VST_RecallPreset
BASS_VST_HasEditor
BASS_VST_EditorInfo
BASS_VST_ReadPresetInfo
BASS_VST_Dispatcher
This new version, mod date 6/11/2019, still retains the old "2.4.0.8" version number, which will be changed to "2.4.1" when the release version is available. The development version package posted now (https://www.un4seen.com/stuff/bass_vst.zip (https://www.un4seen.com/stuff/bass_vst.zip)) is still awaiting some tuning on the OSX version, but the Windows version may be good-to-go as-is and is ready for testing.
Many thanks to Ian Luck at un4seen for providing this info. MusicBee VST users may well see compatibility improvements when using the new bass_vst.dll with Steven's updated mb_VST.dll host with its chunk data capability (uploaded by him at https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file (https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file) , NOT the same as the one now in the regular "Plugins" download section of the MB website).
-
MusicBee VST users may well see compatibility improvements when using the new bass_vst.dll with Steven's updated mb_VST.dll host with its chunk data capability (uploaded by him at https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file (https://www.mediafire.com/file/f6ebbedyyw2sqq4/mb_VST.dll/file) , NOT the same as the one now in the regular "Plugins" download section of the MB website).
I have now updated the Plugins page as well
-
Thanks Steven!
-
I am relatively new to MusicBee. Given the universal appeal/usage of VST plugins in pro audio, this VST support feature of Musicbee is impressive.
Reading through this thread, signs are it is all due to Steven, so, like others, I acknowledge Steven's abilities and efforts to establish this capability.
I have a question: If I run a VST effects plugin that splits two-channel stereo into 4 channels, will Musicbee output those 4 channels to my DAC ?
Background info:
a) My Dac is usb connected to a windows pc and supports 6 channels; it has an Asio driver available, should it be required.
b) The particular VST plugin acts like a LF and HF filter, taking in two full-range channels and putting out 2 LF and 2 HF channels.
-
I dont think it would as the final output is done through the bass library - MB and the bass library dont have any mechanism to dynamically react to changes to the number of output channels
-
Thanks for your reply, Steven.
Just to make sure I grasp the breadth of your "no" - when you say Bass library will not "dynamically" react to channel numbers, does that also exclude me pre-configuring MB to always output 4 channels to obviate the need for dynamic adjustment ?
-
Un4seen has made a Final release version of the updated bass_vst.dll, "a merging of the two BASS_VST branches, with some new features and fixes added too." Version 2.4.1, dated 8/23/2019, now available here:
http://www.un4seen.com/download.php?z/5/bass_vst24 (http://www.un4seen.com/download.php?z/5/bass_vst24)
VST users, it would be appreciated if you could test this version with MusicBee as I will be doing and post your results here. Be sure that you are using the newest version of Steven's VST host plugin mb_VST.dll (July 8, 2019) from the Plugins site here: https://getmusicbee.com/addons/plugins/16/vst-effects-support/ (https://getmusicbee.com/addons/plugins/16/vst-effects-support/)
-
Hi everybody,
I have a brand new mb3.3 latest download installed on win10.
I have installed the Ozone8 VST plugin. 2 dlls iOzoneelements and ozone elements) in the standard steinberg directory.
Added the mb_VST.dll in the plugins directory. My C++ runtime is at a higher level than the one suggested in the mb plugins page, so I did not install the runtimle linked from the mb plugins page.
The VST plugin does not appear in the DSP/EQ window.
Tried to put the ozone dlls in another directory and modified the mb preference accordingly...without success.
Replaced the mb_bass.dll with the un4seen new one, without success.
Stopped/restarted mb for all tests...
Any clue ?
Thank you. Regis.
-
Maybe I am missing something here, but isn't Ozone 8 a software suite?
If that's the case, just copying some dll from it wouldn't seem likely to work?
-
I succeeded to make the Ozone VST plugin to run with foobar, putting the right dlls and foobar extensions in the right places....but I prefer mb ;O) and would like to get rid of foobar.
-
That's surely interesting.
But still, Ozone 8 is a suite isn't it?:
"Mastering Software Suite with 12 Modules, Tonal Balance Control, Neutron 2 Advanced Integration, Spectral Shaper, Master Assistant, Intelligent Track Referencing, and Redesigned Interface - Mac/PC AAX Native, AudioSuite, RTAS, VST2, VST3, and Audio Units."
Did you get all modules to work under foobar2000?
And there is only one dll that made this work?
-
I succeeded to make the Ozone VST plugin to run with foobar, putting the right dlls and foobar extensions in the right places....but I prefer mb ;O) and would like to get rid of foobar.
Regis: you NEED to install the Visual C++ 2010 runtime for the mb_vst.dll host to run. The VCs are not downwards-compatible for many applications written specifically for specific versions. I need 2008, 2010, 2013, and 2017 installed for all the applications I use to run properly.
The latest bass_vst.dll (2.4.1) is now included in the latest MusicBee 3.3 update patch (https://getmusicbee.com/patches/MusicBee33_Patched.zip (https://getmusicbee.com/patches/MusicBee33_Patched.zip)) so there is no need to get it from un4seen at this time. Be sure to extract all the files in the patch into your MusicBee directory, allowing them to overwrite existing ones.
The MusicBee VST host in my experience is much more stable than the two unmaintained ones for Foobar. That said, there are no guarantees every VST plugin will be able to run properly in it. Let us know how things go after installing the 2010 runtime.
-
...and after installing the VC++ 2010 runtime and placing mb_vst.dll in your Plugins directory, be sure that in Preferences/Plugins that "vst host" shows up and is enabled, and that you have correctly specified the path to where the VST plugins are located in the "source folder for the VST plugins" path box.
-
Thank's very much !!
I'll test and feedback.
No pb wit the VST plugins location, I wil use the default one. vst host shows up and is enabled.
So the test will be to install the C++ runtime linked from the mb vst page. I will remove the un4seen dll and come back to my installation dll, then I will unpack and install the patched zip files,
Then I will cross my fingers...and expect the magic to take place !
-
GOOD NEWS !!!
I had an uplevel C++ 2010 runtime. I uninstalled it (I don't think I run any application which requires this runtime at this specific level), then I installed the C++ 2010 runtime linked from the mb VST plugin page.
Then I included the updated zip files into the mb directory...
tic tac tic tac...
AND IT WORKS ! at least the plugin appears, requires me to authorise it with my accreditations, so do I...and the parametric equalizer appears successfully ! First tests are VERY encouraging.
To answer your question about the Ozone suite, I'm only interested in their parametric equalizer plugin. They offered a free V8 license just before they upgraded to V9. Adding this functionnality to MB adds real value to me. I'm part of the tellementnomade French community. I'll feedback to them also.
Thank's again.
I'll feedback to tell if it is fully working (according to my requirements).
PS: please be kind with my english writing...I'm French...
-
Glad to hear you had success! Just wanted to mention that there was no need to uninstall the later VC redist before you installed the 2010 version. All of the C++ runtimes co-exist just fine on the same computer; there are 4 currently installed on mine.
Another free parametric equalizer VST I know works with MusicBee you may want to try is the TDR Nova (https://www.tokyodawn.net/tdr-nova/ (https://www.tokyodawn.net/tdr-nova/)).
-
I'll have a look at TDR Nova, thank's.
Regarding the C++ runtime, must be my English but I tried to say that I had a C++ 2010 runtime already and this runtime was at a upper level than the one MB uses. I also have multiple C++ runtimes, but Windows does not allow multiple maintenance levels for the same runtime (Windows installer rejected the 2010 backlevel runtime installation). My conclusion is that the 2010 runtime level I had is not compatible with the 2010 runtime level required by MB.
And Iconfirm that it works nicelly.
-
More feedback:
I have tested the TDR plugin (the 4 bands free version) which works nicelly both settings and listening.
I have tested the QRange plugin which works nicelly both settings and listening.
BUT the Ozone plugin is not fully working:
the settings is working nicelly (window opens and I can set any of the Ozone option)
the listening is NOT working nicelly. Thre sound is hashed (I don't know how to describe it in English), meaning I recognize the song, one or 2 seconds seem to be ok, then it is saturated with cracks for one or 2 second, then it is ok, then saturated, and so and so. Like waves of problem coming with the music.
This happens even if I don't set anything within Ozone, just have it selected in the VST plugin section.
I tried ASIO4ALL, WASAPI shared and exclusive mode and Directsound MB settings with the same result (the worst being with ASIO). Also tried to increase buffer sizes (I have enough ram).
Any clue ?
Thank's !
-
Be sure you're using a 32-bit plugin, not 64-bit. Also, and hopefully Steven can clarify on this, I don't think the MusicBee host is fully compatible with VST3 plugins. I know the Nova is VST2, as are the others I've used successfully. Have you tried other 32-bit VST3 plugins? Same problem happen?
-
Double checked:
Removed the dlls from the Steinberg Plugins directory.
reinstalled the Ozone plugin with a custom install, selected VST2 only plugin. Used the dlls installed in the 32 bits (x86) programs directory.
Restarted MB.
Same result.
I'll try the VST3 ones, just in case...
-
VST3 plugin does not load. I get an error message when MB scans the plugins directory telling about missing files.
-
Hi dear MB fellows,
I don't succeed in making the Ozone plugin to work when playing music.
It works nicelly with foobar (foo_vst_0903 vst support).
I can run any test. If the conclusion is that Ozone is not supported, then I'll go with foobar, no problem. And wait for MB to support it one day...
Thank's for an answer.
-
Hi Regis: specific VST plugins may have issues for all sorts of reasons. Steven may be willing to provide a debug version of MusicBee for you to run that may provide clues in the resultant log. In the meantime, IMHO it seems a shame for you to abandon an entire music manager/player platform due to a single third-party EQ.
-
Just registered to ask this:
got the vst plugin for long time, used some and worked fine.
But it stopped recognizing the new Vst, tried changing the location, it just resets the setting.
Only old vst are shown; any chance that, somehow, it needs some sort of refresh?
thanks :)
-
Welcome jack16277! My first question is, what version of MusicBee are you using? Please update to the latest 3.3.7246 version from the links at the post here: https://getmusicbee.com/forum/index.php?topic=27074.msg166596#msg166596 (https://getmusicbee.com/forum/index.php?topic=27074.msg166596#msg166596) .
Then, update to the latest version of the MB VST host plugin, which was updated July 8, 2019 (despite same version number), here: https://getmusicbee.com/out/?type=addon&id=16&r=https%3A%2F%2Fwww.mediafire.com%2Ffile%2Ff6ebbedyyw2sqq4%2Fmb_VST.dll%2Ffile (https://getmusicbee.com/out/?type=addon&id=16&r=https%3A%2F%2Fwww.mediafire.com%2Ffile%2Ff6ebbedyyw2sqq4%2Fmb_VST.dll%2Ffile) .
Also remember that only 32-bit VST and VST2 plugins are supported, not VST3.
After confirming the above, please let us know if you are still having problems getting new plugins recognized, and what they are.
-
Thank you for the welcoming, Sveakul :)
So, Musicbee and the plugin are the last versions; plugins are 32-bit.
I've created a folder "c:\Program Files (x86)\MusicBee\Plugins\vst" with the .dll inside.
Everything worked and still works, it's just doesn't see the new VST (32-bit and VST2 versions). I guess, the best way is to try a VST that you know works.
I'll probably have to reinstall everything, and will do, just wanted to try different options first.
Thank you :)
-
You probably already tried some or all of this, but anyway I would:
1. Uninstall "vst host" using the uninstall button in Prefs/plugins; close MB.
2. Rename the folder you now have your VSTs in in File Explorer/Window Explorer.
3. Open MB, reinstall the MB vst host plugin, enable it, and manually enter the new source folder's path/name in the source folder path box; close MB.
4. Open MusicBee, and see if all your VST/VST2 plugins are now recognized, or just some of them. If the latter, which ones are still not being seen?
Before any of this, be sure you are running MB in Administrator mode.
-
Hi dear fellows,
Let me expose why I have decided that I need the EQ VST plugin.
I need to equalize my room (from REW information) in the low frequencies to get the best of my system; I have a pb around 55hz in my room).
I also want to equalize my Mr Speaker Ether C headphone (increase low frequencies and 6k/8k peak suppression).
Doing so within my player is a real value to me.
I agree that i could do so with QRange which works perfectly with MB...but there are other functionalities within Ozone that I would like to explore.
So it would be a dream to get Ozone to work within MB...but I will survive if it takes some timeor does not happen.
Thank's for your time and friendchip anyway.
-
You probably already tried some or all of this, but anyway I would:
1. Uninstall "vst host" using the uninstall button in Prefs/plugins; close MB.
2. Rename the folder you now have your VSTs in in File Explorer/Window Explorer.
3. Open MB, reinstall the MB vst host plugin, enable it, and manually enter the new source folder's path/name in the source folder path box; close MB.
4. Open MusicBee, and see if all your VST/VST2 plugins are now recognized, or just some of them. If the latter, which ones are still not being seen?
Before any of this, be sure you are running MB in Administrator mode.
I've done all the steps, but somehow it still doesn't see the new VST; changing the folder, only resets the settings, but only the same are working.
I've tried something:
- created new folder with another VST (not used before)
- it works
- copied the old working VST into the new folder
- now only the new one is found
So it makes me think, it's not a .dll compatibility problem, but some sort of error in the scan for new VST
Anyway, I'll probably have to reinstall to be sure, or maybe try it on another machine.
Thank you for the reply Sveakul
-
Yeah, it sounds like once the initial scan of the VST folder in the path box is made after installing the host plugin, it never "repeats" the scan/looks again at the folder. This is good info for Steven to know about, thanks for reporting it! One thing you might try is manually adding the new-added VST; open your MusicBee3Settings.ini file in the Appdata subfolder into Notepad, and find the section "<PlayerDspState>". Under it you will see entries for the VST plugins it did find. If the one you added does not appear there, try adding the new one using the same structure/params as you see used in the "found" ones (be sure to back up the file first!!). Then restart MB--do the new ones appear, and, can they be selected/activated?
I would have tried it myself but all my available VSTs are already in my folder (and do show up). With that info, hopefully Steven can spot the problem with the discovery process.
-
OK, curiousity killed the cat, I downloaded a new VST plugin never used before, and placed the dll in my standard folder for VSTs that my MusicBee vst host plugin points to in its path statement. And, the new VST plugin DOES show up just fine in my list of selectable "DSP Plugins." And if selected, works.
Anyway, this disproves the theory that MusicBee is no longer scanning the VST folder after initial installation of the vst host.
jack19277, I think you may be dealing with a Windows permissions issue. I run Windows 7 Pro SP1 as an Administrator (carefully), MusicBee Portable installed to C:\MusicBee, and my VST plugins folder is at C:\VSTPlugins, so both outside of the normal Windows hierarchy. Why don't you try creating a new VST folder right off the drive root and not in Programs, and pointing MB to that instead. Any luck?
"For completeness sake", I'll mention that while unchecking the new plugin in MB and then deleting it from the VST folder does remove it from the list of selectable DSPs, it does not delete its entry in <PlayerDspState> within the MusicBee3Settings.ini file. Neat-nicks like me can clean it out manually however ;D
-
A feature request:
Many VST plugin developers are now deprecating 32-bit versions, and supplying only 64-bit versions, of their plugins.
For now, MusicBee is a 32-bit application, so hosting 64-bit plugins doesn't work. I'd like to see bridge functionality similar to jBridge (https://jstuff.wordpress.com/jbridge) which enables MusicBee to host 64-bit VST plugins.
(Side note: I know that João, the developer of jBridger, has allowed the tool's bridging functionality to be integrated into third-party applications previously. Bridging is rendered on-the-fly, transparently for the user. Perhaps he would allow integration for MusicBee.)
-
hmmm i'm no expert and i would like to ask: is there any chance that these vst will work?
https://www.hpl-musicsource.com/software
https://nugenaudio.com/haloupmix/
i have tried putting both 64bit dll (i'm on win7 x64) in the vst folder i've set up but i get no sight of them in musicbee, not even in dsp settings.
thanks.
-
i have tried putting both 64bit dll (i'm on win7 x64) in the vst folder i've set up but i get no sight of them in musicbee, not even in dsp settings.
Read the post directly above yours
-
i have tried putting both 64bit dll (i'm on win7 x64) in the vst folder i've set up but i get no sight of them in musicbee, not even in dsp settings.
Read the post directly above yours
;D facepalm. thanks, i will try with 32bit then.
-
Hello. Anyone else have experience with this vst plugin: https://www.hpl-musicsource.com/software
Its geared towards headphone use but its not evident to me if its meant for general purpose use or specifically for music mastered for it (they have a small catalogue). The translation on the site isn't clear to me.
-
Check here everyone for an updated version of mb_vst.dll that fixes some issues: https://getmusicbee.com/forum/index.php?topic=35414.msg193811#msg193811 (https://getmusicbee.com/forum/index.php?topic=35414.msg193811#msg193811)
-
Check here everyone for an updated version of mb_vst.dll that fixes some issues: https://getmusicbee.com/forum/index.php?topic=35414.msg193811#msg193811 (https://getmusicbee.com/forum/index.php?topic=35414.msg193811#msg193811)
Thanks sveakul. Maybe ask a moderator to post this on the first post of the thread?
BTW, does plugin still require Visual Studio 2010 runtime ??
-
Hi, can we put the vst gui into a panel? like in the right side bar? I have good resizable vu meter and other monitoring vst, it would be a great setup to be able to put them somewhere in the panel layout.
-
Not presently, but you should post this request in the Wishlist forum; would receive a +1 from me, although my screen is rather "sufficiently obligated" already.
-
Not presently, but you should post this request in the Wishlist forum; would receive a +1 from me, although my screen is rather "sufficiently obligated" already.
Thanks, just posted. https://getmusicbee.com/forum/index.php?topic=35884
-
Hi, just installed the thimeo stereo tool to my music bee equalizer. when i take it off bypass i get no sound .all the graphics and bars are moving .this is the free version. any help would be appreciated. thanks,bob.
-
Be sure that:
1. You are using the latest version of MusicBee from the Download page (3.4.8033).
2. You are using the latest version of Steven's VST Effects bridge from the Plugins page (this was updated December 28, 2021)
3. You are using the latest version of the bass_vst.dll (ver. 2.4.1.2, updated January 20, 2022) (https://www.un4seen.com/stuff/bass_vst.zip (https://www.un4seen.com/stuff/bass_vst.zip))
Please use this forum for future related posts: https://getmusicbee.com/forum/index.php?topic=13022.0 (https://getmusicbee.com/forum/index.php?topic=13022.0)
-
Ok ,i figured out how to get sound to play. now only on certain songs the bass is really distorted but on most songs everything is fine. this software is amazing. just wish i new how to use everything.
-
Is my graphic equalizer supposed to lock up? i cant use it even if i bypass sound or uncheck it in the equalizer plug ins.
-
Not all VST plugins will run correctly in MusicBee; VST3 for example is not supported, nor of course 64-bit plugins. From what I can see, "Stereo Tool" is a complex plugin and may be taking over control of the built-in equalizer when loaded. I use MB with a single VST (Sonic Anomaly's "Unlimited" compressor/limiter) which works great and doesn't bother the EQ, yet others refuse to work at all. Actually the last free player I've seen with a basically stable VST host was the now abandoned "uLilith." Foobar's own non-native VST host plugins are a "crash-test environment". The lack of free development on these lead me to believe their code is "not for the squeamish."
THAT SAID, maybe others who are using Stereo Tool successfully with MusicBee will post here and share their experience.
-
THANK YOU ,FOR THE ADVICE. I THINK I,M GOING TO DELETE IT AND DO WHAT YOU SAID.
-
THIS IS GOING TO SOUND STUPID BUT CAN YOU TELL ME HOW TO INSTALL IT?
-
I HAVE TRIED EVERYTHING I KNOW AND THAT FILE WILL NOT GO INTO THE EQUALIZER,I EVEN RAN MUSIC BEE AS ADMINISTRATOR.
-
I HAVE TRIED EVERYTHING I KNOW AND THAT FILE WILL NOT GO INTO THE EQUALIZER,I EVEN RAN MUSIC BEE AS ADMINISTRATOR.
See hiccup's post: https://getmusicbee.com/forum/index.php?topic=36102.msg197589#msg197589 (https://getmusicbee.com/forum/index.php?topic=36102.msg197589#msg197589)
-
Now, THIS is interesting! Falcosoft has released a modified bass_vst.dll that will automatically call JBridge (if installed) and allow 64-bit VST plugins to be used with a 32-bit host (or visa-versa). The bass_vst.dll will automatically detect the bit mismatch and call JBridge to "correct" it to run with the host. Pretty cool! No, I have not installed JBridge to try it out (yet). https://github.com/Falcosoft/BASS_VST/releases (https://github.com/Falcosoft/BASS_VST/releases) . Also has a fix for people using Roland Cloud plugins.
-
Could not get sonic anormaly unlimiter to load. had computer guys try to get to load, they think something is up with the link. one is a I T guy and the other writes code. has anybody else downloaded that link?
-
Sonic Anomaly is no longer in business. You can still download the Unlimited plugin from Web Archive's copy. Follow the link below:
https://web.archive.org/web/20181203014924/http://sonic.supermaailma.net/plugins (https://web.archive.org/web/20181203014924/http://sonic.supermaailma.net/plugins)
The working download link is under the description of the plugin, or, click here to download directly:
https://web.archive.org/web/20181203014924/http://sonic.supermaailma.net/sites/default/files/download/Unlimited-VST.zip (https://web.archive.org/web/20181203014924/http://sonic.supermaailma.net/sites/default/files/download/Unlimited-VST.zip)
Unzip the dll inside into a folder. Then, in MusicBee follow the Preferences path hiccup gave you and specify YOUR folder path in the white box, as I have done with my own folder below:
(https://i.imgur.com/YJrHzYo.png)
Then be sure you have selected Unlimited in the list of DSP plugins in MusicBee under the equalizer.
-
Hi.
I've finally had a chance to try the VST Plugin for a spectral analyzer/spectogram VST, which worked yesterday. After installing the plugin, it opened the Musicbee VST Plugin UI that let me choose which VST to load/run.
All good and swell, and filtered down the ones that worked, and left the ones in a local directory in the portable folder (*:\*\MusicBee\Plugins\VSTs\), where the few I am after worked.
Today though, I can not find a way to access either UI... i.e. the neither the Musicbee VST Plugin UI, nor the VST UI itself does show when I switch: Controls -> DSP Effects ON (this was the mystery trigger yesterday that gave me access....). No luck today though...
What's the secret sauce here to show the Musicbee VST Plugin UI and/or the VSTs UIs...?
I can't seem to find any way at all...
Cheers.
c.
-
There isn't a "Musicbee VST Plugin UI" per-se, but VST plugins show up on the "DSP Plugins" list in the "Equaliser and DSP Plugins Window", accessible by hitting the "Equaliser & DSP" button in the lower right corner of Prefs/Player/Sound Effects.
Just curious, you said you installed a spectral analyzer/spectrogram plugin VST, did you need it to show something different than the "works great" non-VST Spectrogram Panel plugin by zkhcohen (https://getmusicbee.com/forum/index.php?topic=25944.0 (https://getmusicbee.com/forum/index.php?topic=25944.0)) ?
-
Oh - thanks sveakul! I looked up and down the menus... my skin I've settled on years ago was hiding that button very well... :D
I was always missing a way to scale/isolate a given frequency area directly in musicbee. So with the VST plugin for MB I now can call up quick visualizers/eqs with value scaling (like Span - https://www.voxengo.com/product/spanplus/ for a good free option)
c.
-
Glad you found it! I had the free SPAN at one time and it worked fine, although the "SPAN Plus" looks like it's worth the money. It's kind of a shame that the MusicBee "Floating Window" can't be used to display a VST's GUI, I believe that is on the Wishlist.
-
Got pointed to a ton of free 32-bit VST plugins to try with MusicBee on this website:
https://www.airwindows.com/wp-content/uploads/RetroWinVST32s.zip (https://www.airwindows.com/wp-content/uploads/RetroWinVST32s.zip)
Explanations of the functioning of each plugin:
https://www.airwindows.com/wp-content/uploads/Airwindopedia.txt (https://www.airwindows.com/wp-content/uploads/Airwindopedia.txt)
Thank you to the developer Chris Johnson. FYI 64-bit versions are also available on the home page.
-
@Steven: I have a simple 32-bit, VST-2 plugin that works in MusicBee when added (free open-source Wider32.dll from Airwindows), but it is impossible to bring up the interface in order to make adjustments (double-clicking does nothing). Is there any reason why such a basic interface like the one below would not be displayable by the MusicBee VST plugin? Can this be fixed? A link to the plugin itself is under the image. Thanks for your attention.
(https://i.imgur.com/vjhfRqW.png)
https://upload.disroot.org/r/jcNP90JY#r/TgK3WKfR4SQ4KIcpRwbLbt1CTI/gLwUTbT1hcfpOg= (https://upload.disroot.org/r/jcNP90JY#r/TgK3WKfR4SQ4KIcpRwbLbt1CTI/gLwUTbT1hcfpOg=)
-
The information as returned by the bass vst plugin for that dll indicates it has no editor.
I am aware there is a configuration dialog shown by foobar
-
Thanks Steven for taking a look at this. I have reported the issue to Ian at the un4seen forum and hopefully the bass_vst.dll can be corrected to show the presence of the editor. I also tried the Falcosoft version but same problem.
-
The information as returned by the bass vst plugin for that dll indicates it has no editor.
I am aware there is a configuration dialog shown by foobar
Steven here is some information I received from Falcosoft on the un4seen forum about how this kind of slider can be enabled by the host. Is this something you feel you could add?
"According to VST 2.4 specification a GUI editor is an optional feature for plugins but providing a default interface for such "editorless" plugins is mandatory for VST hosts.
You can do this by:
1.Using BASS_VST_GetProgramCount() to get the number of programs provided by the plugin then loop through them and use BASS_VST_GetProgramName() to get the program names. BTW providing more programs are also optional for plugins. In case of Wider32.dll there is only 1 and it has no name...
2. After the above for each program you can use BASS_VST_GetParamCount() to get the number of parameters for the program then loop through them and use BASS_VST_GetParamInfo() to get the parameter name, meta info about iits value etc.
3.Finally you can use BASS_VST_GetParam() to get the value of a parameter and BASS_VST_SetParam() to set the value of a parameter."
-
i have added support for editorless vst plugins
https://getmusicbee.com/download/plugins/mb_VST.zip
i will spend a bit of time to see if i can address a couple of issues with certain other types of plugins before updating the official VST plugin link
-
same link has been updated with fix for certain vst plugins with their own editor locking when dragging a slider quickly
https://getmusicbee.com/download/plugins/mb_VST.zip
-
Just confirming it works flawlessly with FabFilter Pro-Q 3.
-
Thanks Steven for the valuable feature addition! I can confirm that the first update works flawlessly, with the editorless VST plugin mentioned before now displaying a full settings editor, which works and retains its settings between selection and/or MB restarts.
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 have stuck with update #1 due to the above, and will continue to test any new versions you post. Thanks again for allowing use of a whole range of VSTs that were unusable before.
-
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?
-
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/ (https://loudmax.blogspot.com/)), Wider32.dll (https://upload.disroot.org/r/jcNP90JY#r/TgK3WKfR4SQ4KIcpRwbLbt1CTI/gLwUTbT1hcfpOg= (https://upload.disroot.org/r/jcNP90JY#r/TgK3WKfR4SQ4KIcpRwbLbt1CTI/gLwUTbT1hcfpOg=)), and the Polyverse "Wider" (https://polyversemusic.com/downloads/legacy/InfectedMushroom-WiderV1.0.zip (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.
-
that should be working now - same link as before
-
Yes! Update #3 fixes the problem. Thanks for such a quick fix!
-
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.
-
Is VST3/64-bit VST supported?
-
Is VST3/64-bit VST supported?
No.
-
Can't get this to work, I have been trying for the past hour and there is absolutely no way to get this working for me. I followed every step possible, but no vsts are showing up in the equalizer section.
-
Can't get this to work, I have been trying for the past hour and there is absolutely no way to get this working for me. I followed every step possible, but no vsts are showing up in the equalizer section.
Welcome to the forum, and thanks for sharing Joja2k.
-
So I have placed the vst dll file into the music bee plugins folder and created a new vst folder within the plugins folder. I have placed my 32 bit vst files into that folder and set the vst host in preferences, plugins to "C:\Program Files (x86)\MusicBee\Plugins\VST" . Restared music bee, and nothing is showing up. I did place the new bass dll. file into the music bee folder as well, but still nothing is showing up. What am I doing wrong exactly? Cheers!
-
Not sure if putting your VST files in MusicBee's plugin folder is a good idea. Since they are not actually MusicBee plugins.
Have you set this correctly?:
(https://i.imgur.com/sIOCxbv.png)
-
Apparently with the Installer version of MusicBee you end up with more than one Plugins folder, one at the path you gave and another at user/Appdata/Roaming/MusicBee/Plugins, but all I can address is the Portable version where you have one version of everything all in the same place. Anyway, check this:
1. You are using the latest 3.5.x version of MusicBee
2. You have the file mb_VST.dll in the Plugins folder (which one IDNK but not in both)
3. You have the file bass_vst.dll in the MusicBee main folder with MusicBee.exe.
4. Move the folder with the VSTs in it outside of the MusicBee structure, like C:\VST, and change "source folder" in the VST host section of Preferences to read that.
Now restart MusicBee and see if the VSTs appear in the DSP list.
-
Hi again, I tried everything that sveakul listed, musicbee is on the latest version as well. https://imgur.com/OJ5aeWt (https://imgur.com/OJ5aeWt) https://imgur.com/jptECKj (https://imgur.com/jptECKj) That's how I have my stuff setup, tried moving everything as i've said. I have a feeling like it's not "scanning" for the vst's at all.
-
Hi again, I tried everything that sveakul listed
If the screenshot with your most recent reply is current, then you did not try everything sveakul said.
4. Move the folder with the VSTs in it outside of the MusicBee structure, like C:\VST, and change "source folder" in the VST host section of Preferences to read that.
-
What phred said. Your pictures show you didn't create a folder for your VST effects outside of the MusicBee tree at all, just put another one where the old one is.
1. Make a new folder on your hard drive directly off the drive letter, like "C:\VST."
2. Move all your VST effect plugins to that folder.
3. Delete the folders you made in the MusicBee Plugins folder, "VST" and "VSTs".
4. Go back into the host preferences and replace the path with the new one, C:\VST.
5. Add the new folder to your antivirus white-list (exclude list) to be sure that doesn't interfere.
-
The pictures were taken prior to making any changes. I took the pictures, tried all that sveakul wrote and then posted my answer.
-
Please post a screenshot of your current VST settings.
-
https://imgur.com/YJRHDmF (https://imgur.com/YJRHDmF) https://imgur.com/bxclPom (https://imgur.com/bxclPom)
-
i really don't understand you. 1st screenshot is pointing mb vst host plugin to "C:\VSTs" folder, and 2nd screenshot shows "C:\VST" folder.
-
The two folders have the exact same vsts in them, I just renamed them as i saw someone wrote that maybe you can try to create a whole new folder and and write the path manually, maybe it would work out.
-
There is ONE folder in your picture https://imgur.com/bxclPom, "C:\VST" . The folder path you wrote in the host preferences path, according to your own picture https://imgur.com/YJRHDmF, is "C:\VSTs." Change the name written in the box to match the name of the folder; in other words, make BOTH of them "C:\VST".
-
Whops, my bad, thanks for pointing that out but bad news unfortunately. Still nothing showing up in musicbee's eq section
-
@sveakul thank you for that bass_vst update. But I like my long range barrel plugged into my gun so that when I'm shooting, there's no air gab in between. Same with the VST, I don't want additional tools to be able to get around a shortcoming . I'll submit a request for 64 bit version of Music bee tomorrow, god willing.
-
@Steven
The new bass_vst freezing the plugin's state and no amount of knob tweaking and moving sliders making any change. Older one works as expected.
The newest mb_VST.dll has an inaccurate window geometry.
-
@Steven
The new bass_vst freezing the plugin's state and no amount of knob tweaking and moving sliders making any change. Older one works as expected.
The newest mb_VST.dll has an inaccurate window geometry.
Are you referring to a particular VST plugin? Which one? By "older one" do you mean an older version of that plugin, or bass_vst.dll?
-
Are you referring to a particular VST plugin? Which one? By "older one" do you mean an older version of that plugin, or bass_vst.dll?
No, I'm referring to bass_vst
-
I meant, what is the plugin you are referring to here: "..freezing the plugin's state and no amount of knob tweaking and moving sliders making any change." I am only using two simple VSTs (LoudMax, a limiter/compressor, and Wider, a stereo expander) and their sliders move and produce changes as expected. This is with bass_vst.dll version 2.4.1.6 (or 2.4.1.5) and the current version of mb_VST.dll from the Add-Ons section of this site.
-
Initially Hofa, but when I realized, after updating bass_vst that controls no longer respond, I tried Fabfilter too with the same result. Once I reverted to old bass_vst from 2018, everything went back to normal.
-
Hi everyone,
Just signed up on the forum. I have the same problems as the others : I've installed 4 VST dlls in my C:\BBE Sound folder, set that path in the plugins preferences and I'm unable to see them on myEQ/DSP window. Those plugins are the 4 official plugins from BBE which can be found here : https://plugins.bbesound.com/products/b1757-Sonic-Sweet/
No need to mention that they are the official ones, got a licence key for them, not a cracked version from the dark web.
Please advise,
I'm running MB 3.5.8447 on windows 11 on a pretty recent machine.
Thanks in advance,
Jeremy.
-
The Sonic Sweet plugins indicate that they require a 64-bit VST host. As MusicBee and its VST host are 32-bit, that's why they cannot be used.
-
Thanks for your quick reply. Does that mean that they will be useless forever or is it planned to have a 64 bits version of MB somewhere in a near future ?
-
Thanks for your quick reply. Does that mean that they will be useless forever or is it planned to have a 64 bits version of MB somewhere in a near future ?
Probably useless forever as there's been no mention of MB's developer releasing a 64bit version. I'm not saying it won't happen. Only that it doesn't appear to be on the roadmap.
-
Thanks for your quick reply. Does that mean that they will be useless forever or is it planned to have a 64 bits version of MB somewhere in a near future ?
Probably useless forever as there's been no mention of MB's developer releasing a 64bit version. I'm not saying it won't happen. Only that it doesn't appear to be on the roadmap.
I am not sure about all this, but I think the main and essential problem is that the VST plugin needs to be 64bit.
And while the BASS_VST.dll was released by the BASS developer (who is responsible for most audio-related dll's in MusicBee), it was originally coded/created by somebody else, who seems to have completely left the stage.
So chances are extremely small that there will even be a 64bit version of BASS_VST.dll that MusicBee could then use.
edit
It seems I was wrong, and the BASS_VST.dll should already support 64bit plugins.
But the next obstacle then would probably indeed be if MusicBee is 64bit.
What I am not completely sure about is if perhaps such a 64bit plugin then could work on 32bit MusicBee.
I am guessing not though, since pretty much all software that I know that uses plugins require the two to match.
cut-to-the-chase: This is most likely never going to happen.
edit:
The people involved in this thread will already know this, but I thought it might be good to add this to this thread for posterity.
- VST was designed by a company with very deep pockets and a very large budget (Steinberg, owned by Yamaha), and is intended for use in professional audio software created by companies that also have deep pockets and large budgets.
- VST is not, and was never intended for use in consumer applications.
Considering the complexities involved, it would pretty much be a miracle if some single person would be able to create a reliably working plugin.
And do it for free.
P.S.
And, as a non-coder I always assumed: 'how hard can it be to update an existing piece of software from 32bit to 64bit?
And then I gooooooogeled gooooogl'd gooogeld performed some searches on the matter and shut-up. ;-)
(hmm, somebody in the future using a coding plugin for ChatGPT might type: "write 64bit versions of MusicBee and BASS_VST.dll". So perhaps keep your hopes up…)
-
Just some comments:
The bass_vst.dll has been released in both 32 and 64-bit versions as long as I can recall; the latest 64-bit version is 2.4.1.6 from 8/31/2023. The MusicBee vst host, mb_VST.dll, has only been available in 32-bit, like the MB application itself.
Of great interest to me is the fact that the Foobar2000 developer released a vst host plugin for his player (https://www.foobar2000.org/components/view/foo_dsp_vst3 (https://www.foobar2000.org/components/view/foo_dsp_vst3)) that allows either 32 or 64-bit VST plugins (in VST2 or VST3 spec) to be used in either 32 or 64 bit versions of Foobar. In other words, if your OS architecture is 64-bit, you can use even a 32-bit Foobar with 64-bit VSTs. It's quite a piece of work and I can attest it works beautifully in both versions. So, given that "What one man can do, another can do," there is still hope on the horizon given the restraints of personal time and interest.
-
Just some comments:
The bass_vst.dll has been released in both 32 and 64-bit versions as long as I can recall;
Thanks for correcting my assumptions.
As some weak excuse: they were partly based on what the BASS website shows:
(https://i.imgur.com/iEFD6Ue.png)
But I now realise that only refers to the Windows version, and not to the plugin itself.
So as a hypothetical, perhaps something might be done with MusicBee so that the existing (and 4 years old) VST plugin could be made to work for 64bit VST plugins?
Without 'upgrading' MusicBee to a 64bit application as a whole?
-
I did try to replace bass_vst.dll in MB folder by the last 64 bits version but it doesn't work either. (Should I replace all the bass dlls maybe ?)
Tried also the Foobar component which works like a charm indeed (and Foobar is x86 also), so my guess is that this is the bridge that should be modified accordingly
Thanks for your replies gentlemen
-
Do not use 64-bit BASS dlls (or any other 64-bit dll!) in 32-bit MusicBee, they will not function. As long as you have the latest 32-bit bass dlls supllied by the MusicBee patch you should be fine (and the latest mb_VST.dll from the Add-Ons section).
For those braver than I, there is a tool that is supposed to make vst3 plugins work in vst2-only hosts (still must be the correct bit architecture), somebody with more time than I can try and report:
https://audiosex.pro/threads/free-vst3-to-vst2-converter.58250/ (https://audiosex.pro/threads/free-vst3-to-vst2-converter.58250/)
-
Tried also the Foobar component which works like a charm indeed (and Foobar is x86 also), so my guess is that this is the bridge that should be modified accordingly
foobar2000 v2.x is available in both x86 and x64 versions.
Are you sure you are using foobar2000 x86 with a x64 component?
-
I'm positive !
-
Tried also the Foobar component which works like a charm indeed (and Foobar is x86 also), so my guess is that this is the bridge that should be modified accordingly
foobar2000 v2.x is available in both x86 and x64 versions.
Are you sure you are using foobar2000 x86 with a x64 component?
The host component itself, foo_dsp_vst3, installs as either an x86 or x64 dll depending on the Foobar v2 architecture, but even the x86 version is able to host 64-bit VST plugins with a x86 Foobar. The 32-bit dll runs both a 32 and 64-bit VSTHost.exe, and even the last 32-bit v1 version of the player (1.6.16) can use it. Quite a piece of work.
-
Just host Exite audio KHSMR Chain as a 32 bit VST2 inside Musicbee and then host all your various vst2/3 32bit/64 bit plugins inside it.
Works well.
Edit: KSHMR can't host cross architecture stuff. My bad. I work with so much stuff, I forget what does what. Maybe Bidule or Metaplugin ?
-
And while I'm here, to all you music lovers out there. Get this while black friday is on, it's a steal
https://www.nomadfactory.com/products/p724-All-Tec-EQs-v2/
(https://inc2.plugivery.net/i/2KOdW7CsYG-0h-fb0JSarUh07Z-pmaVDpa-FqezU28jUjpyshaDvztbL1IhXdJlzrJ-Z0s9DcKxgbbSHqpqcV1d0ow/img.jpg)
Altec lansing FTW!!!
I think Universal audio also makes Altec lansing emulations but theirs cost more.
You play the music with it, you don't want to turn it off.
-
hi
can I know which is the last BASS_VST version ?
I use the last musicbee portable version and it's 2.4.1.0
should i upgrade it?
thanks in advance
-
can I know which is the last BASS_VST version ?
That's not so difficult, go to the source:
https://www.un4seen.com/
-
Often the latest version of a Bass plugin isn't posted on the public release page, but at their "stuff" subdirectory, e.g. https://www.un4seen.com/stuff/bass_vst.zip (https://www.un4seen.com/stuff/bass_vst.zip) .
The developer has stated those are "...'in development' updates that are made available between releases. They are still 'release' builds and usually fine for production use." I live dangerously and use these all the time, never had a problem but have had them FIX problems. The latest bass_vst.dll version there is 2.4.1.6 from 8/31/2023.