https://www.foobar2000.org/components/view/foo_dsp_vst3
Best used with latest foobar2000 v2.0 beta - please do not report annoying behaviors with old foobar2000, they're well known; foobar2000 v1.6.14 will also support this component properly.
UPDATE: foobar2000 v1.6.14 out, you can now use VST adapter properly without running foobar2000 betas.
Now that's awesome. Played with it, no crashes yet. I noticed, it's possible audio for few plugins changes not while operating the plugin GUI, but only after closing it - why is that? E.g. Chow Tape Model: https://chowdsp.com/nightly.html
With 64-bit v2 beta 13, using the Sonic Anomaly "Unlimited" 64-bit compressor/limiter VST I get "Unrecoverable playback error: VST refused audio stream format" no matter what the stream format is. Not sure how the new "Override output channels" settings needs to be set, but get the same error with it set to either "none" or "stereo." I use the default wasapi exclusive audio output.
I use the 32-bit version of the same Unlimited plugin successfully with Foobar 1.6.12 via the old Yohng VST wrapper.
Attached is the 64-bit version of the VST if someone cares to try it themselves (this was a free download from now-defunct Sonic Anomaly).
AMAZING, thank you so much for this Peter! It's been the only missing feature of FB2K for me for a long time, and the two old VST wrappers were no longer updated and very buggy. And it supports VST3! I am over the moon and will test it today and report back.
Hey Peter, maybe you can make a deal with https://www.airwindows.com/ guy to include some into fb2k, whose UI-less plugins also are included into the Surge synthesizer. Lots of them are about dynamics, so maybe make sense in an audio player.
BTW, considering CLAP support? I guess it will become relevant.
I tried to use this plugin with audio measuring VST's (ex. Voxengo span) but nothing happens. I do not want to use any audio changing plugings just measuring tools (Peak, RMS LUFS, PLR, Spectrum....). Is it possible yet?
BTW, considering CLAP support? I guess it will become relevant.
Yep, this would be the icing on the cake :) Some relevant info here:
https://u-he.com/community/clap/
https://cleveraudio.org/
Suggestions:
a) Please allow removing of the VST directories. One may just want to use hand picked VST directories.
b) A "find as you type" search field in the VST picker would be nice.
I tried to use this plugin with audio measuring VST's (ex. Voxengo span) but nothing happens. I do not want to use any audio changing plugings just measuring tools (Peak, RMS LUFS, PLR, Spectrum....). Is it possible yet?
From the web page: https://www.foobar2000.org/components/view/foo_dsp_vst3
"Current limitations: Because of the sandboxing, VST can't show live audio data being played."
But TBF this was mostly the case with the older 3rd party wrappers too, you couldn't really use graphical/metering VSTs with them because the delay was so bad. It's no biggie I guess but does preclude some nice metering options I have like Youlean Loudness Meter, DMG Track Meter, iZotope Insight etc.
I tried it out with a few thigs today (all VST3 64 bit, in 32 bit FB2K 1.6.13) and all except the aforementioned worked flawlessly!
This couldn't have come at a better time for me. But as soon as I load the component in foobar, Windows anti-virus pops up and says it has detected a trojan Win32/Wacatac.H!ml. 10 out of 67 engines on Virustotal.com also detect stuff. False positives, I assume? Nobody else has any problems with Windows anti-virus when using this?
Hey Peter, maybe you can make a deal with https://www.airwindows.com/ guy to include some into fb2k, whose UI-less plugins also are included into the Surge synthesizer. Lots of them are about dynamics, so maybe make sense in an audio player.
BTW, considering CLAP support? I guess it will become relevant.
I might actually add some to foo_dsp_effect. I am trying to get beta 2 done, by fixing every major issue it has before adding more DSPs.
I see that code is sanely licensed, so maybe someone could do it all as VSTs, too.
Hey Peter, maybe you can make a deal with https://www.airwindows.com/ guy to include some into fb2k, whose UI-less plugins also are included into the Surge synthesizer. Lots of them are about dynamics, so maybe make sense in an audio player.
BTW, considering CLAP support? I guess it will become relevant.
Thanks Squeller for the airwindows link, a ton of VSTs to play around with now with the new v2 64-bit host!
To have an effect which keeps dynamics on more stable levels, which is crucial e. g. in louder environment vs. classical music, for sure this can be resolved with some upward expander/limiter combination.
BUT it needs to look ahead (e. g. volume down before a sudden loud passage).
Is that possible within the plugin hosts sandbox?
I'm willing to find a decent VLevel dsp alternative.
@Squeller , have you tried LoudMax (https://loudmax.blogspot.com/)?
@Squeller , have you tried LoudMax (https://loudmax.blogspot.com/)?
Thx, testing it.
@Squeller , have you tried LoudMax (https://loudmax.blogspot.com/)?
Thx, testing it.
Cannot do the job, to busy (quick changes) in loudness adjusting, such a plugin is required to react quickly at some points, but overall keep more stable levels.
I tried to use this plugin with audio measuring VST's (ex. Voxengo span) but nothing happens. I do not want to use any audio changing plugings just measuring tools (Peak, RMS LUFS, PLR, Spectrum....). Is it possible yet?
Hello
@wojak , actual VST wrapper implementation doesn't support that.
For such a kind of need and for complex VST configuration is more appropriate route the audio output to a separate (and appropriately featured) DAW.
I do that via digital loopback on SPDIF interface.
Regards, Andrea
New version out.
If you open a VST configuration panel while playing, live audio going thru the DSP will be also sent to the configuration panel, so VSTs can be used as measuring/visualisation tools now.
There's a delay between shown audio and playback, which is normal - set smaller output buffer to work around it.
New version out.
If you open a VST configuration panel while playing, live audio going thru the DSP will be also sent to the configuration panel, so VSTs can be used as measuring/visualisation tools now.
There's a delay between shown audio and playback, which is normal - set smaller output buffer to work around it.
To me the live measuring/visualization VST-plugin feature is the main reason for using Foobar2000, and it's an awesome component addition. Foobar2000 becomes an even more powerful tool. That said, I'm having trouble setting it up with this latest version. I'm running Windows 7 Sp2. I've installed the Foobar2000 v2.0 beta 13, and the VST 2.x/3.x Adapter 0.7 released today. v2.0 runs fine. But I'm having these three problems with the VST installation:
1. In my previous set up (v1.6.11) using the VST 2.4 adapter, under Preferences --> Playback --> DSP Manager I could see the list of Available VST plug-ins, and the Active ones. I do get the list of available plugins with Foobar2000 v2.0 beta 13 and the new VST host plugin. However none of my x64 plugins, or any other purchased plugin that I have installed show up under Available. Perhaps this is due to the path used to find them?
2. In my previous set up in Preferences --> Components there was a subheading "VST-plugins" which listed the VST-plugins in use, the I/O of each and the path where they were stored. I don't get that now. This is no big deal from my usage point of view, but perhaps an indication of what might be wrong?
3. One that does show up under Available is the Meier Crossfeed. If I activate this, it's added to the Active list. However, when I then proceed to View --> DSP the Meier Crossfeed doesn't show up there. In v1.6.11 there would be two DSP headings under View --> DSP, where the second one showed all the installed Active DSP plugins, such as for example the Meier Crossfeed.
I'm sure I'm overlooking something, and any assistance or hints would be appreciated.
Updated to .7 over .6 today, and right away noticed the absence of a configuration window for one of VST plugins I had been successfully using with .6 and always showed the window. Before the update the StereoFX64 from airwindows showed a configuration panel as below:
(https://i.imgur.com/GE5Ao0U.png)
Now, the config panel does not appear, and based on the sound the plugin's previous setting seems to have returned to the default. Can this be fixed? Foobar v2 beta 13 64-bit, Windows 10 22h2.
How do we use this plugin in practice?
The only way I managed to use it is via Library, Configure, Playback, DSP manager, Active DSPs, ...., and manually choosing needed vst each time. I did not find any other way to see measuring panels/windows. I use Voxengo Span, AnSpec, Correlometer, Oscarizator, dpMeter5, Izotope Ozone Imager. To be able to see anything measured I must repeat the procedure described above each time. I also saved VST plugin in DSP chain presets and enabled DSP switcher on the Toolbar. I can pick VST plugin to be "used" but to no effect.
Do I miss some other, easier, more intuitive way to do it? If not, it would be nice to have such a way,
Ok, so I figured out that by double clicking the VST 2.x/3.x Adapter in the Available DSPs I could access the folders containing the VST effects. I'm using Izotope Ozone 9 advanced which I had previously tried to get working with Foobar2000 through using jBridger without success. So it's a huge step to be able to use this 64-bit application in the 64-bit version of Foobar2000.
Compared to running the VST effects 32-bit in Foobar2000 1.6.11 in the VST 2.4 adapter, the VST 2.x/3.x Adapter introduces noticeable lag in Foobar2000 2.0 beta with several seconds of silence to respond to changes. Starting playback after a stop takes a long time, approximately 6-8 seconds.
Only one VST effect can be run at a time, whereas in Foobar2000 1.6.13 with VST 2.4 several effects can be run simultaneously, changes are immediate, and playback after stop starts immediately, too. However VST 2.4 only runs 32-bit and not VST3 applications.
Here's hoping that the speedy development of the 64-bit VST application continues so that it's soon comparable to the ease of use of VST effects with VST 2.4 in Foobar2000 v 1.6.
Compared to running the VST effects 32-bit in Foobar2000 1.6.11 in the VST 2.4 adapter, the VST 2.x/3.x Adapter introduces noticeable lag in Foobar2000 2.0 beta with several seconds of silence to respond to changes. Starting playback after a stop takes a long time, approximately 6-8 seconds.
What kind of changes? I'm not seeing the re-starting playback lag you mention at all here.
Only one VST effect can be run at a time, whereas in Foobar2000 1.6.13 with VST 2.4 several effects can be run simultaneously, changes are immediate, and playback after stop starts immediately, too. However VST 2.4 only runs 32-bit and not VST3 applications.
You can run several effects simultaneously, you just need to add another instance of VST 2/3 Adapter to the DSP chain with the additional VST plugin chosen. I am doing that now, running LoudMax (a VST2) and Wider (a VST3) in the same chain:
(https://i.imgur.com/Tm4XykF.png)
Updated to .7 over .6 today, and right away noticed the absence of a configuration window
Yup, a) absence of VST configuration windows is new (UI-less VSTs?). b) For some reason Melda FX don't pass audio through. Fb2k is silenced.
Compared to running the VST effects 32-bit in Foobar2000 1.6.11 in the VST 2.4 adapter, the VST 2.x/3.x Adapter introduces noticeable lag in Foobar2000 2.0 beta with several seconds of silence to respond to changes. Starting playback after a stop takes a long time, approximately 6-8 seconds.
What kind of changes? I'm not seeing the re-starting playback lag you mention at all here.
Only one VST effect can be run at a time, whereas in Foobar2000 1.6.13 with VST 2.4 several effects can be run simultaneously, changes are immediate, and playback after stop starts immediately, too. However VST 2.4 only runs 32-bit and not VST3 applications.
You can run several effects simultaneously, you just need to add another instance of VST 2/3 Adapter to the DSP chain with the additional VST plugin chosen. I am doing that now, running LoudMax (a VST2) and Wider (a VST3) in the same chain:
(https://i.imgur.com/Tm4XykF.png)
Thank you for the heads up on how to get multiple VSTs. Now that I knew how that worked, I found that in F2k 2.0 beta with the VST 2.x/3.x Adapter I could only see one VST interface window at a time. To get another one up, I needed to close down the one in use. I need several open simultaneously.
With F2k 1.6.11 and the VST 2.4 I could have four or more windows up simultaneously enabling multiple visual monitoring along various dimensions. I could be changing parameters in one VST, and seeing how they play out in different VST tools simultaneously. I wanted to make a comparison to F2k 20 beta with the new VST adapter.
So I set up trial using various VST tools, the main ones being Izotope Ozone 9 Advanced, and Izotope Ozone 8 Advanced. In F2k v 2.0 beta I used VST2, as well as VST3 versions, and 32-bit as well as 64-bit versions . In F2K 1.6.11 I used the VST 2.4 component to host the VST, and Ozone 8 Advanced 32-bit version.
I set up the comparison using Ozone 8 Advanced VST2 32-bit using the VST 2.x/3.x Adapter in F2k 2.0 beta, and VST 2.4 in F2k 1.16.11. Ozone can serve as a host to various VSTs from its own modules. I set up comparisons using their 8-band parametric equalizer with an initially flat frequency curve, which also displays phase delay, phase response, group delay; the Imager which shows the stereo image and few other things, the Maximizer enabling control of any clipping, and the Post EQ VST window showing what the total output looks like. So four VST tools inside the overall Ozone wrapper. I used identical VST-tools in both Foobar versions with the only difference being the VST adapters hosting them.
In F2k 1.6.11 with the VST 2.4 starting playback was immediate. Changing song, same thing. Modifying the VST view, say from the Equalizer to the Imager was equally immediate. Same when modifying the the parametric equalizer, sound immediately changes and everything works very smoothly.
In F2k 2.0 beta with the VST 2.x/3.x Adapter and the same Izotope Ozone 8 VST2 32-bit starting a track, or changing a track took between 5 - 6.5 seconds. This pauses sound. Modifying which VST is being viewed inside the Ozone host from the Equalizer to the Imager resulted in a 4.3-5 second delay. So this was a straightforward comparison of identical settings.
I then proceeded to, in F2k 2.0 beta, try the Ozone 8 Advanced 32-bit VST3 version, using the same tools. This resulted in a delay of 5-5.6 seconds to start or change track. So the 32-bit VST3 was a little bit faster when changing tracks, but still substantial pauses. Changing which VST is viewed inside the Ozone host took 4.5-5 seconds.
Next I tried Ozone 9 Advanced VST3 64-bit in F2k 2.0 beta with the VST 2.x/3.x Adapter hosting. I was using three VST tools inside Ozone. Starting tracks was now down substantially mostly around 3 seconds, occasionally 4 seconds. Modifying parameters in the VST tools resulted in delays of 2-3.6 seconds, essentially twice as fast as the 32-bit version of Ozone 8.
I also tried Ozone 9 Advanced VST2 64-bit in F2k 2.0 beta with the VST 2.x/3.x Adapter hosting. It displayed equal times to the VST3 version.
I also tried stand alone modules from Izotope Ozone, and other providers. 64-bit VST2 and VST3 versions. Here stand alone VST2 version delays for changing tracks were around 3-3.5 seconds, and the VST3 version 2.5 seconds. The shortest pause was 2.5 seconds. Other providers' tools introduced a 3 second pause when starting or changing tracks.
So in F2k 1.6.11 with the VST 2.4 component as host I'm presently running Ozone 8 32-bit with six VST-modules simultaneously. In addition two other VST monitoring modules are running, displaying visuals continuously. So all in all 8 VST-modules. Changing tracks, modifying parameters, are all without any delays.
I'm running Windows7 SP1, on a six core 3Ghz processor with 24GB of memory, software on SSD, tracks on hdd. This may have some influence, I don't know. It looks like available primary memory of 10GB is identical regardless of which set up I'm using.
To me the 64-bit version of Foobar2000 and this initial VST 2.x/3.x Adapter 0.7 version are among the best news I've had all year as it enabled me to try the Ozone 9 Advanced version. I hope there, in time, will be solutions available to the limitations I'm experiencing.
Sorry about the stupid regression with missing popup for simple effects, fixed just now in 0.8.
Regarding startup delays -
These are due to startup of VST host process per DSP instance. I can probably work around them by keeping a persistent process. The current solution can indeed get nasty with multiple VST effects in the chain.
Sorry about the stupid regression with missing popup for simple effects, fixed just now in 0.8.
Regarding startup delays -
These are due to startup of VST host process per DSP instance. I can probably work around them by keeping a persistent process. The current solution can indeed get nasty with multiple VST effects in the chain.
Thank you for the reply and for the update! It would be fabulous if you can create a work around by keeping a persistent process. I experienced significant lag of a couple of seconds even with just one VST in the chain compared to the VST 2.4 immediate response as outlined above, but perhaps this is unavoidable? For "play" of a track this is not such a big deal, it's with interaction, such as changing a parameter where the lag between trying different settings becomes more of a problem, due to the brain's need to use working memory to make reliable detailed comparison of auditory signals. I e, the brain becomes unreliable if the comparison of two sounds are more than 10-15 seconds apart.
Note: foobar2000 v1.6.14 released, with changes relevant to new VST adapter backported, so if you want to use this component properly, you're no longer required to use foobar2000 v2.0 betas.
Also, I know I'm repeating myself, but PLEASE use LATEST foobar2000 with the VST adapter.
ALL foobar2000 versions PRIOR TO v2.0 beta 13 / v1.6.14 RESTART the VST with EACH CHANGE OF SETTINGS. Some of the above reports sound like exactly that. The old foo_vst component had its own workarounds for this limitation, some of them resulted in general instability and unpredictable behavior. I'm fixing this properly.
I released foobar2000 v1.6.14 today mainly to fix this. Please make sure you have updated foobar2000 before reporting bugs in this component.
Thanks.
Going over other reported issues-
Confirmed odd interaction with live changes of ChowTapeModel settings, will look into it.
Also, I know I'm repeating myself, but PLEASE use LATEST foobar2000 with the VST adapter.
ALL foobar2000 versions PRIOR TO v2.0 beta 13 / v1.6.14 RESTART the VST with EACH CHANGE OF SETTINGS. Some of the above reports sound like exactly that. The old foo_vst component had its own workarounds for this limitation, some of them resulted in general instability and unpredictable behavior. I'm fixing this properly.
I released foobar2000 v1.6.14 today mainly to fix this. Please make sure you have updated foobar2000 before reporting bugs in this component.
Thanks.
Going over other reported issues-
Confirmed odd interaction with live changes of ChowTapeModel settings, will look into it.
Thank you! A question, in the future will using multiple visual VST interface windows simultaneously be possible, or is that something the new VST adapter will not support?
A future version will add better means of using VSTs as visualisations / keeping their panels open outside of foobar2000 DSP manager.
New update, fixed missing live config tracking with ChowTapeModel and more.
Still "VST 2.x/3.x Adapter 0.8 (2022-11-23)"
https://www.foobar2000.org/components/view/foo_dsp_vst3
Not "Current version: 0.9, released on 2022-11-24"
Thanks.
@Air KEN VST 2.x/3.x Adapter 0.9 (2022-11-24) is available for download
Hi :) NetRanger
really?
Still "VST 2.x/3.x Adapter 0.8 (2022-11-23)"
MD5: 221c1b5f1be4447543d63b518f735452
foobar2000 v2.0 beta 13 64bit
I also tried with other WEB Browser (Google Chrome, Vivaldi, Microsoft Edge)
I also tried it on another PC (Win10, Win11, Ubuntu)
orz
Hi :) NetRanger
really?
Still "VST 2.x/3.x Adapter 0.8 (2022-11-23)"
MD5: 221c1b5f1be4447543d63b518f735452
I also tried with other WEB Browser (Google Chrome, Vivaldi, Microsoft Edge)
I also tried it on another PC (Win10, Win11, Ubuntu)
orz
for me "Adapter 0.9"
Hi :) NetRanger
really?
<snip>
It's there. Using Firefox here.
Hit Ctrl/F5 to force a page update
foobar2000 v2.0 beta 13 32bit and foobar2000 v1.6.14 are fine.
foo_dsp_vst3.dll (2022-11-24 03:07:38 UTC)
VST 2.x/3.x Adapter 0.9
MD5: 221c1b5f1be4447543d63b518f735452
A future version will add better means of using VSTs as visualisations / keeping their panels open outside of foobar2000 DSP manager.
New update, fixed missing live config tracking with ChowTapeModel and more.
Fabulous, thank you!
Hi :) NetRanger
really?
Still "VST 2.x/3.x Adapter 0.8 (2022-11-23)"
MD5: 221c1b5f1be4447543d63b518f735452
foobar2000 v2.0 beta 13 64bit
I also tried with other WEB Browser (Google Chrome, Vivaldi, Microsoft Edge)
I also tried it on another PC (Win10, Win11, Ubuntu)
orz
Same thing here. The
64-bit foobar v2 beta 13 still shows the vst adapter version as ".8" in the components list after attempting to update to .9 using either "check for updates" or manually downloading and applying .9.
This did not happen with foobar 1.6.14 which correctly shows ".9" after auto-update. Apparently the 32-bit version of v2 does update correctly also.
Peter can you fix this?
Looking at the downloaded package for ".9" shows that the dll in the "x64" subfolder has the same date/time/size as that in the ".8" package, while the 32-bit dll has definitely been updated from the .8 package in all 3 attributes.
Yeah, I was always worried that some idiot could trigger an updateloop by uploading a component with version number mismatch.
...
Turns out I'm the idiot.
Version 0.9 reuploaded. No code changes, added proper 64bit binary.
solved. Thanks. :)
foo_dsp_vst3.dll (2022-11-24 22:57:06 UTC)
VST 2.x/3.x Adapter 0.9
foo_dsp_vst3.fb2k-component
MD5: 0a1f8a6cb97f1129bbb1904d15b307e0
https://www.foobar2000.org/components/view/foo_dsp_vst3
Best used with latest foobar2000 v2.0 beta - please do not report annoying behaviors with old foobar2000, they're well known; foobar2000 v1.6.14 will also support this component properly.
UPDATE: foobar2000 v1.6.14 out, you can now use VST adapter properly without running foobar2000 betas.
Peter, thank you very much for F2k and VST adapter. I will donate you for your work.
This is truly awesome. Unfortunately, as in sveakul's case, certain 64-bit plugins give an "Unrecoverable playback error: VST refused audio stream format" error. Meanwhile, the 32-bit equivalent works with the old foo_vst plugin. I'm using foobar v1.6.14 and v9.0 of the plugin.
In my case, this occurs with Minihost Modular, which seems to be the slickest and easiest option to automate plugin parameters I've found so far (even if I still haven't figured out how to use a simple LFO with them yet). I'd really love to have this work, or just find another solution for some really simple parameter automation. Whether it's VST hosts, racks, whatever else.
If anyone wants to test it, here's a copy. It's free, but only available for Image-Line customers:
https://mega.nz/file/UhpHHASZ#EjhBsAKaHkRbGgTg_r3Gx_SbAzFd1UNPV-kxhAZ4lls
(Can't seem to upload to the forum, maybe it's too big?)
Automating several VSTs within a (hopefully free, user-friendly and lightweight) host would really take all of this to the next level. If you get weird enough with it, it can basically turn a music library into an endless generative music machine, especially for ambient - or just seamlessly blend between different impulse responses and reverbs to spice up your room's ambience, Closest I've gotten so far to figuring out basic LFO automation is with Plogue's Bidule, but it's a real pain in the ass to use:
http://little-scale.blogspot.com/search/label/bidule%20basics
How hard would it be to make a plugin where you can easily draw and stretch an LFO curve, and then route that curve's animation to somewhere else? I must be a dumbass, because I can't figure this out or find the right tools for it, which I'm sure must exist. It's easy enough in a DAW, but not inside any self-contained VST host I've found so far.
How hard would it be to make a plugin where you can easily draw and stretch an LFO curve, and then route that curve's animation to somewhere else? I must be a dumbass, because I can't figure this out or find the right tools for it, which I'm sure must exist. It's easy enough in a DAW, but not inside any self-contained VST host I've found so far.
See, this is what I mean - at this point, I'd just settle for finding a plugin like the one on the left. The easier it is to route, the better - but whatever, it would still be much easier than typing unintuitive LFO values into Bidule's various little boxes.
(https://i.imgur.com/IBl7I6r.png)
Sorry to spam the thread with this, but I reckon others might be interested in automating some of their VSTs as well. And I can't seem to find the best way to do this, while still keeping in mind foobar2000's inherent limitations of functioning like a DAW.
Hello
@Gadgety and
@cooldude , for such a kind of "relatively" heavy use of VST effects, I would suggest you to use an external DAW.
I am personally using Cantabile (they have also a free Lite version that does a lot) connected through SPDIF loopback (my DAC has this option). If you do not have any digital loopback, probably you can achieve the same result using ASIO4ALL virtual interface wrapper.
Cantabile alone does not introduce significant overhead (on my old 32bit CPU with Windows 10 32bit, it is only about 2-5% when minimized to icon).
ASIO4ALL instead (at least the version I tested 2 years ago) requires significant CPU power (15-20% on my same old 32bit PC). That's why I am using physical SPDIF digital loopback and not a virtual loop via ASIO4ALL.
Regards, Andrea
Hello! Selecting fabfilter stops playback and displays "Unrecoverable playback error: Could not negotiate VST audio format"
Sorry to spam the thread with this, but I reckon others might be interested in automating some of their VSTs as well. And I can't seem to find the best way to do this, while still keeping in mind foobar2000's inherent limitations of functioning like a DAW.
I think you're really off the track. Parameter automation of VST effects? Making Foobar a DAW? C'mon, really? Use any of those numerous VST fx which have internal modulation.
(Win 10 - 64bit)
I've been running v1.6.13 with the Yeong VST adapter, the only VST I use is the Electri-Q equalizer, which has been working fine,
but decided to try Peter's new VST, so just updated to v1.6.14 and successfully installed the new VST adapter.
It shows in the DSP manager as active, and version 0.9.
Problem:
When I use the VST pull-down, and select Electri-Q, it doesn't bring up a config window ( Electri-Q doesn't have one)
It opens Electri-Q -- BUT when I close the pull-down, Electri-Q disappears.
I can't find any way to open Electri-Q, without going to the pull-down again (where it won't stay open)
I'm expecting Electri-Q to open with Foobar, as it did with the Yeong VST, why doesn't it ?
Should it appear in the "View", DSP list ?
Advice appreciated, thanks,,,,
I'm expecting Electri-Q to open with Foobar, as it did with the Yeong VST, why doesn't it ?
Because Peter didn't make it work this way, and IMO it would be very unusual if a VST host would open all n (with n = 1 .. 1000) VST fx and instrument windows on startup. Maybe Peter can add an option "Open UI on FB2K startup", what's the use case? Permanently fiddling EQ?
This EQ plugin... it's veeeery old, right? I think I remember it.
I'm expecting Electri-Q to open with Foobar, as it did with the Yeong VST, why doesn't it ?
Because Peter didn't make it work this way, and IMO it would be very unusual if a VST host would open all n (with n = 1 .. 1000) VST fx and instrument windows on startup. Maybe Peter can add an option "Open UI on FB2K startup", what's the use case? Permanently fiddling EQ?
This EQ plugin... it's veeeery old, right? I think I remember it.
Thanks Squeller:
Yes it's old, and no longer supported, but it does what I want and haven't found anything better.
Maybe that's why the plugin didn't work, I don't know. But I've gone back to the Yeong VST - which works fine with it.
Guess I just need to not try fixing what ain't broke :( .....
I'm expecting Electri-Q to open with Foobar, as it did with the Yeong VST, why doesn't it ?
, what's the use case? Permanently fiddling EQ?
Actually, yes....
I feed my Soundcard's analog outputs to my Sansui power amp's direct in. (no tone controls).
Electri-Q is my tone control / preamp.
Very flexible, I can create a infinite number of curves and easily switch them in or out as desired.
I won't comment on the sound (I know that's a no - no), but - I love it.
I'm unable to get IK Multimedia's ARC Room correction working.
It loads the vst, i can see audio coming through the visual aspect of the plugin, but changes in the plugin do not affect the music.
Has anyone been able to get room correction software working through the VST component? What am i doing incorrectly?
Foobar Build: foobar2000 v2.0 beta 17
Component Build: 0.9
I'm unable to get IK Multimedia's ARC Room correction working.
It loads the vst, i can see audio coming through the visual aspect of the plugin, but changes in the plugin do not affect the music.
Has anyone been able to get room correction software working through the VST component? What am i doing incorrectly?
Foobar Build: foobar2000 v2.0 beta 17
Component Build: 0.9
I'm having this issue after upgrading to beta 20/21 where VSTs do not retain config and show signal passing but don't effect the audible stream. I can drop gain to zero and the meters drop to zero but audio is unaffected. Can you confirm whether changes you make to the VST config are retained? Make a change, close and reopen and see if the change is there or if it has reverted to default again?
Version 0.10 out, lots of bugs fixed again. In particular, changes in settings of some VST3 effects weren't saved/used at all.
The new 0.10 VST completely kills the audio on my Foobar v2 64-bit Beta 22, when using VST3 and VST-2 64-bit plugins that worked fine with previous .9 adapter on Beta 21 and Beta 22. Same issue after using the updater or doing a clean install of .10.
On the other hand, after updating the adapter on Foobar 1.6.14, all VST plugins continue to work fine.
Which exact VST plugins are you using? Sounds like 64-bit float mode isn't working.
With 32-bit foobar2000, that uses float32 internally, float32 data is passed to VST. With 64-bit foobar2000, float64 data is passed to VST, which would explain what you're experiencing.
Hello Peter, That's right 64bit does not work at aal. Can't hear the music or save any ...
Best Regards Nick
Which exact VST plugins are you using? Sounds like 64-bit float mode isn't working., which would explain what you're experiencing.
LoudMax64.dll and Wider.vst3 (together or singularly same fail).
Thanks, Peter, that sorts out my issue, the DMG plugins are working again.
FWIW FB2k 2.0 beta 22 64-bit on Win 11.
There is one minor bug, there are certain places where you can engage a text control to manually enter a value for example on a gain slider, by double-clicking. The double click activates the text control, but it won't accept any text input.
Thanks again for all your work!
Version 0.10.1 out, made float64 mode opt-in as many popular effects falsely report that they support it.
Version 0.10.1 out, made float64 mode opt-in as many popular effects falsely report that they support it.
Works fine now with the float64 opted out, thanks for making the update.
Tried the VST3 64-bit version of LoudMax, LoudMax.vst3, with the .10.1 adapter (+v2 64-bit beta 22), and the settings once made will neither save for the first use nor be restored afterwards. Using the VST2 version (LoudMax64.dll) everything works fine, so no big deal, but for those expecting the VST3 version to work I thought I'd mention it.
Unfortunately, something still isn't "quite right" with 0.10.1 and the v2 64-bit beta 22 Foobar. I don't have the time right now to go into a detailed proper example, but in summary, when playback is started with one VST DSP chain (2 separate VST effects) it seems like one of the effects never kicks in, until a second chain is selected (which then works normally), and then the original chain returned to, at which time it too sounds as expected. This is repeated every time a new playback stream is selected. I am using the toolbar DSP switcher.
This doesn't happen at all with 0.10.1 and 32-bit Foobar 1.6.14. I've had to roll back to .9 again on the 64-bit v2 to get normal VST operation. I know it's a sadly lacking description, but if anyone else has noticed something that resembles this, please post.
This doesn't happen at all with 0.10.1 and 32-bit Foobar 1.6.14.
Well, after updating just now to 1.6.15, the same behavior described above is now happening with v1! As above, rolling the VST adapter back to .9 also fixes it. I'm wondering if the newly added process of flushing unstead of re-initializing the DSPs when changing tracks/streams is the reason.
Well, after updating just now to 1.6.15, the same behavior described above is now happening with v1! As above, rolling the VST adapter back to .9 also fixes it. I'm wondering if the newly added process of flushing unstead of re-initializing the DSPs when changing tracks/streams is the reason.
1.6.16 makes those changes optional.
1.6.16 makes those changes optional.
Thanks for the heads-up! Updated, and now I'm back to .10.1 on the VST adapter and have original performance. I hope we get the same option for v2.
I'm unable to get IK Multimedia's ARC Room correction working.
It loads the vst, i can see audio coming through the visual aspect of the plugin, but changes in the plugin do not affect the music.
Has anyone been able to get room correction software working through the VST component? What am i doing incorrectly?
Foobar Build: foobar2000 v2.0 beta 17
Component Build: 0.9
new version 0.10.1 allows the usage of ARC which allows me to utilize room correction. Thank you
@Peter for remediating the issue.
Does this VST dsp work with more than stereo?
Beta version 23 is a huge improvement in terms of speed and smoothness when interacting with the VST plug-in. Thank you, Peter!
The only thing missing compared to v1.6 with foo_vst 2.4 adapter is being able to run multiple plugins and having more than one VST interface open at any one time.
Version 0.11 out, again many VST3 bugs fixed.
Note about LoudMax, it saves configuration properly only if you play some sound while configuring it.
Does this VST dsp work with more than stereo?
Should work. Do you know any specific VSTs that fail?
Version 0.11 out, again many VST3 bugs fixed.
Note about LoudMax, it saves configuration properly only if you play some sound while configuring it.
Updated 1.6.16 to version .11, now I get the message "Unrecoverable playback error: VST refused audio stream format - got: 2ch, VST wants: 1ch" on every stream. VST chain and settings (LoudMax.dll and Wider.vst3) not touched between update. Rolled back to .10.1, all back to normal.
Version 0.11.1 out, fixed VST2 regression from 0.11.
Version 0.11.1 out, fixed VST2 regression from 0.11.
Updated to 0.11.1, Foobar 1.6.16. More problems:
1. When chain is 2 32-bit VST-2's (LoudMax.dll and Wider32.dll), all is well
2. When chain is 1 32-bit VST-2 (LoudMax.dll) and 1 64-bit VST-3 (Wider.vst3), audio is totally lost on the right channel.
As before, reverting to 0.10.1 fixes things.
Version 0.11.1 out, fixed VST2 regression from 0.11.
Updated to 0.11, Foobar 1.6.16. More problems:
1. When chain is 2 32-bit VST-2's (LoudMax.dll and Wider32.dll), all is well
2. When chain is 1 32-bit VST-2 (LoudMax.dll) and 1 64-bit VST-3 (Wider.vst3), audio is totally lost on the right channel.
As before, reverting to 0.10.1 fixes things.
I tried running IK Multimedia ARC2 (VST2) and iZotope Vinyl (VST3) and that works as intended. (Other than Vinyl bypass not working, but that's known by Peter alreaady)
I tried running IK Multimedia ARC2 (VST2) and iZotope Vinyl (VST3) and that works as intended. (Other than Vinyl bypass not working, but that's known by Peter alreaady)
DotNoir, this is with 0.11.1 not 0.11, right? I had a typo in my original quoted post, now corrected. Did you test with FB 1.6.16 or with v2? I haven't bothered testing with v2 until we get a beta that includes the option to not use the new DSP flush, as exists in 1.6.16.
I tried running IK Multimedia ARC2 (VST2) and iZotope Vinyl (VST3) and that works as intended. (Other than Vinyl bypass not working, but that's known by Peter alreaady)
DotNoir, this is with 0.11.1 not 0.11, right? I had a typo in my original quoted post, now corrected. Did you test with FB 1.6.16 or with v2? I haven't bothered testing with v2 until we get a beta that includes the option to not use the new DSP flush, as exists in 1.6.16.
Yes, this was with v2 beta 23 x64. And the latest 0.11.1. VST plugin.
Just updated to v2 64-bit beta 24 and vst adapter .11.4. Is there any way to fix these anomalies in two VSTs that the adapter mistakenly interprets as not being compatible with a regular stero input?
1. Unlimited64.dll-- produces the playback error "VST refused audio stream format - got: 2ch, VST wants: 6ch". While the VST does also accept 5.1 input by design, it's not at the exclusion of normal stereo input, and works fine with that on other players. I have tried changing the "Override output channels" setting on the adapter from stereo to 5.1 or 5.1 (side) and get the same error. Same issue affects the 32-bit version of the plugin (Unlimited.dll).
2. Wider.vst3 (and the 32-bit version)-- produces the result of completely losing the right audio channel. While this VST is designed to work with Mono or Stereo inputs, it seems the adapter is defaulting it to one channel.
Note: while issue #1 has been present with each version of the adapter through .11.4, issue #2 does not exist in the .9 or .10.1 versions.
Thanks for any help you can give on these.
Channel count issues should be fixed in 0.11.5, thanks for reporting.
Does this VST dsp work with more than stereo?
Should work. Do you know any specific VSTs that fail?
I tested two upmix VSTs and while the gui of the VSTs shows that they work only the left and right channel is in the output.
The VST adapter is working very well (v 0.11.5., in 2.0 beta 23). I also discovered that you've added the VST visualizations enabling having panels open outside of the DSP manager. Very impressive progression in such a short time. Also I discovered that more advanced VST-plugin functionality that wasn't working previously now works. Thank you!!
I still have a lot to learn how Foobar2000 works. Could an active DSP, running in the VST adpater, be placed in the DSP chain presets? I'm assuming the DSP chain presets would be loaded at start up.
Channel count issues should be fixed in 0.11.5, thanks for reporting.
Thanks Peter, the fix worked perfectly for those VSTs!! I'm so glad about those I hesitate to mention this, but I noticed one regression affecting GUI-less VST2's--they no longer show a numerical value under the adjustment sliders interface, making them difficult to use. This was lost somewhere between 0.10.1 and 0.11.5. As I only have one VST in that category (Wider64.dll byairwindows), it's hard to know if the regression affected all others of this type or just this example.
(https://i.imgur.com/qJPBDtv.png)
Version 0.11.6 out, slider labels fixed, thanks for reporting.
Does this VST dsp work with more than stereo?
Should work. Do you know any specific VSTs that fail?
I tested two upmix VSTs and while the gui of the VSTs shows that they work only the left and right channel is in the output.
Hello,
Same here. No signal from rear, center and LFE channels of (at least one) 5.1 upmix VST with no error reported. Upmix VST was working fine with old VST component. (Foobar 1.6.16 and VST component 0.11.7). Thanks for your work BTW.
Cheers.
Same here. No signal from rear, center and LFE channels of (at least one) 5.1 upmix VST with no error reported. Upmix VST was working fine with old VST component. (Foobar 1.6.16 and VST component 0.11.7). Thanks for your work BTW.
Are you talking about the stock Foobar DSP "Upmix to 5.1"? That's not a "VST" nor is it related to the new VST adapter. Needs to be moved to a separate topic if so.
Same here. No signal from rear, center and LFE channels of (at least one) 5.1 upmix VST with no error reported. Upmix VST was working fine with old VST component. (Foobar 1.6.16 and VST component 0.11.7). Thanks for your work BTW.
Are you talking about the stock Foobar DSP "Upmix to 5.1"? That's not a "VST" nor is it related to the new VST adapter. Needs to be moved to a separate topic if so.
I am using foobar for years and I know what is a VST plugin and what is not...
Whoa, OK, just trying to get the picture straight. I'm sure it would help Peter to know the name/company of the specific plugin you mention that isn't functioning correctly with the 0.11.7 VST adapter.
Whoa, OK, just trying to get the picture straight. I'm sure it would help Peter to know the name/company of the specific plugin you mention that isn't functioning correctly with the 0.11.7 VST adapter.
Hello,
@sveakul: I just realized that my answer was a bit harsh. Sorry for that: it was not my intention. I am using an old VST2x86 plugin (DTS Neural Upmix from 2010, I think), but it is working fine with the old VST2 component. The DSP chain is: DTS neural upmix followed by Isone Pro Surround 5.1 from Jeroen Breebaart for headphone listening (another VST2x86 plugin).
In Isone Pro GUI, each single channel can be heard separately: all surround channels stay silent.
I also checked that Isone Pro is working fine with foobar component "upmix to 5.1": so the problem comes from the upmix plugin.
In DTSNeural Upmix, there is also a strange behaviour. Each channel can also be heared separately trough DTS GUI: however, checking each channel one by one does not change anything: it is always the stereo output that is heard.
With the old VST component, all is working as it should.
I can help by checking new test versions of the VST adapter, if you want.
Cheers
Sorry for interrupting your bug reports.
I just would like to thank Peter for this great addition. Yeong VST still worked but touching the pull-down menu "view" crashed foobar. This new component (v0.11.7) works great for me so far. I am using a free tape-emulation plugin. IMHO this outperforms even expensive tape-emu plugins. Maybe it is just a perfect match to my ears, I don't know - but I would recommend it for all people to have a try:
https://senderspike.wordpress.com/2019/11/12/downloads/
I mean the SN03/SN03 Tape Recorder Plugin v1.31. I do have a hi-fi system where highs are a bit harsh. Others my say they are very precise but it is too much for my ears. I never managed to get the right setting to smoothen it out with an EQ plugin. This one magically does it. I just reduce Hi's and augment Lo's slightly.
I'm trying this new VST host, and noticed the VST plugin display update is very sluggish.
I am trying this plugin: https://www.bestfreeplugins.com/download.php?p=Gonio3
foobar2000 v1.6.16 with foo_dsp_vst3 v0.11.7
Does this VST dsp work with more than stereo?
Should work. Do you know any specific VSTs that fail?
I tested two upmix VSTs and while the gui of the VSTs shows that they work only the left and right channel is in the output.
Hello,
Same here. No signal from rear, center and LFE channels of (at least one) 5.1 upmix VST with no error reported. Upmix VST was working fine with old VST component. (Foobar 1.6.16 and VST component 0.11.7). Thanks for your work BTW.
Cheers.
Hello,
I have found a solution to this problem: I just put "channel mixer" component before calling the VST upmixer to create 6 channels (output: 6 channels; upmix mode: copy with LFE, Center and Rear channels to 0) and it worked as it should. It seems that VST upmixers do not work properly with VST adapter 0.11.7 if the 6 channels (for 5.1 upmix) do not exist in the DSP chain before calling the VST. This channel creation should be implemented in the VST adapter itself to avoid the use of channel mixer.
Cheers
foobar2000 v1.6.16 (upgraded from v1.6.12) with foo_dsp_vst3 v0.11.7
Audeze Reveal VST3 Legacy plugin (VST3 32 and 64-bit): https://drive.google.com/open?id=1EvQPdEHVtYNrKP19-JvyMIZA4MYoUjjg
Sound disappears on the first seek until the track is changed (or active DSP chain is updated in any way).
Currently, after closing VST settings window, the only way to open it again is to close VST adapter window and then open it again. Possibility to reopen VST settings window without to need to close and open VST adapter itself would be nice.
At last! A properly made replacement for my old adapter (https://hydrogenaud.io/index.php/topic,84947.0.html). Nice! I'm putting up a deprecation banner in that thread.
foobar2000 v2.0 beta 24 + foo_dsp_vst3 v0.11.8 (x86)
FabFilter Pro-Q 3 VST3 32-bit
Im apology for my english.
FabFilter stop working when I move forward audio track with seekbar.
If stop and play again or I change track, FabFilter work again.
Sorry for the dumb question, but...
Is here a way to get the "Active DSPs" list to show under the "View>DPS" menu item?
Thanks!
Tried the new VST plugin last night. Unfortunately it seems it only works through the standard foobar2000 playback / DSP menu and not when you use the "UPnP/DLNA Renderer, Server, Control Point" component (old, I know, but the only one we have), through it's DSP menu. Is there a reason? Can this be fixed?
foobar2000 v2.0 beta 24 + foo_dsp_vst3 v0.11.8 (x86)
FabFilter Pro-Q 3 VST3 32-bit
Im apology for my english.
FabFilter stop working when I move forward audio track with seekbar.
If stop and play again or I change track, FabFilter work again.
Whoa, just noticed this bug myself! And it's been there since at least 0.11.7, presents on any fixed file when the VST is part of the DSP chain. Playback starts with VST effects active, but as soon as the seek bar is moved, the effect stops working. Stopping and re-play or changing tracks re-engages the effect, as foo2k_bls describes. Would have noticed it earlier if I hadn't spent 90% of my Foobar use on radio streams. Affects both 1.6.16 and v2 64-bit beta 25.
Tried the new VST plugin last night. Unfortunately it seems it only works through the standard foobar2000 playback / DSP menu and not when you use the "UPnP/DLNA Renderer, Server, Control Point" component (old, I know, but the only one we have), through it's DSP menu. Is there a reason? Can this be fixed?
I forgot to say: The plugin searches for VSTs but never stops to do so and never finds any.
Thanks a lot for the new plugin, Peter. I would like to suggest a few improvements:
1) Add the ability to create a mapping of outgoing channels to the user himself with the ability to redirect, since many multi-channel vst plugins do not use standard channel layouts. Also, Windows has a maximum of 18 channels, but some VST plugins support more.
2) Add a limit to the input channels on which the effect will work. For example, if the playlist contains tracks 2.0 and 5.1 at the same time, and the effect is set to Upmix 2.0->7.1, then track 5.1 should not be processed by this effect. Similarly for 5.1->9.2 it should only work for tracks with 6 channels.
Peter, please, pleeeeeease :D...
VST UIs as standard, dockable UI elements.
foobar2000 v2.0 beta 24 + foo_dsp_vst3 v0.11.8 (x86)
FabFilter Pro-Q 3 VST3 32-bit
Im apology for my english.
FabFilter stop working when I move forward audio track with seekbar.
If stop and play again or I change track, FabFilter work again.
Any seekbar movement while playing reset VST adapter. Hope this could be solved.
Any seekbar movement while playing reset VST adapter. Hope this could be solved.
Same here, https://hydrogenaud.io/index.php/topic,123342.msg1023129.html#msg1023129 (https://hydrogenaud.io/index.php/topic,123342.msg1023129.html#msg1023129)
This sounds interesting. I mainly know to use VST in DAW software, what kind of use can I get out of using it in foobar?
The same as whatever you might want to do in a DAW. EQ, reverb, compression, saturation, metering etc. I use it for EQing and crossfeeding my headphones, making general EQ adjustments, testing out new plugins on already familiar material etc.
foobar2000 v2.0 beta 24 + foo_dsp_vst3 v0.11.8 (x86)
FabFilter Pro-Q 3 VST3 32-bit
Im apology for my english.
FabFilter stop working when I move forward audio track with seekbar.
If stop and play again or I change track, FabFilter work again.
Any seekbar movement while playing reset VST adapter. Hope this could be solved.
Same here - https://hydrogenaud.io/index.php/topic,122847.msg1026715.html#msg1026715
Hello.
I have been using Foobar v1.6.4 for many years with various vst plugins at the same time, and never had any problems!
Installed Foobar v2.0 and VST 2.x/3.x Adapter and happy life ended....
I can't run VST plugins.
I installed a VST 2.x/3.x Adapter into active DSPs.
I have selected the required VST plugins.
But they can't be launched!
Where do you run these plugins from? In the Wiew-DSP menu, there is one standard equalizer. There are no required plugins!
I need to open three VST plugins at the same time.
The VST chain in your image should first be named and then saved using the DSP chain presets box beneath the list. Then, selecting the name from the presets box and pressing "Load" will activate that chain.
Putting a "DSP switcher" box on your toolbar will allow you to easily switch to any saved chains using their names (see images).
The "one equalizer" can be chosen as many times as needed from the "available DSPs" list when you are creating your chain.
@NickMan
Does it mean that there is a VST Plugin that cannot be used?
for example:
-FabFilter Saturn 2
-FabFilter Pro-Q3
-Ozone Imager 2
Do you work one (FabFilter Saturn 2) ?
Thank you for your help!
I gave the plugin chain a name and saved it.
I made a DSP switch in the toolbar.
But I still can't enable all plugins at the same time.
It used to be like this:
In foobar v 2, I'd like to have this feature.
This is impossible?
But I still can't enable all plugins at the same time.
It used to be like this:
OK, I understand now that by "enable" you mean to be able to view and adjust all the VST plugins' GUI interfaces at the same time. Yes that is not possible now, but I would support adding that feature, also the ability to seek through a song without losing the VST effect which is irritating.
But I still can't enable all plugins at the same time.
It used to be like this:
OK, I understand now that by "enable" you mean to be able to view and adjust all the VST plugins' GUI interfaces at the same time.
Yes! Exactly.
I experiment a lot with sound, so I need quick access to the GUI of all plugins.
But I still can't enable all plugins at the same time.
It used to be like this:
also the ability to seek through a song without losing the VST effect which is irritating.
I've heard of this problem, but I've never experienced it myself.
The only problem was the lack of support for VST3 plugins.
Hello
Is it possible to make this adapter show up automatically each time Foobar starts?
I mean, when I start Foobar, I go then to View > Visualization > Visualize with VST... and then I have to choose a plugin.
And I have to do so each time I close Foobar and start it again.
Is it possible to make Foobar "remember" that each time I launch it, the plugin I chose last time should be loaded with Foobar automatically, without the user having to click View > Visualization > Visualize with VST... again?
@ironmine
Preferences > Playback > DSP Manager > Available DSPs → Active DSPs (VST: 2.x/3.x Adapter)
...click Select VST effect
DSP chain presets <name> → Save
Default UI can be displayed in Toolbar.
"DSP Switcher"
Columns UI: Toolbars > DSP preset
----------
View > Visualization > Visualize with VST... is not a setting.
This function is for display after setting.
@ironmine
Preferences > Playback > DSP Manager > Available DSPs → Active DSPs (VST: 2.x/3.x Adapter)
...click Select VST effect
DSP chain presets <name> → Save
Default UI can be displayed in Toolbar.
"DSP Switcher"
Columns UI: Toolbars > DSP preset
----------
View > Visualization > Visualize with VST... is not a setting.
This function is for display after setting.
I have done all that. I also have DSP switcher.
Yes, Foobar starts and the DSP switcher remembers the last chosen plugins preset (so the sound is processed by the VST plugin I selected in the VST adapter), but this VST plugin's window is not shown automatically after Foobar is launched, so I need to click lots of buttons again just to get to the VST plugin parameters.
When I used George Yohng's VST wrapper, it always conveniently showed up automatically every time I launched Foobar.
Do you mean "I want to display VST plugin windows at startup"?
wait for the answer.
Even "Keybord Shortcuts" can only do "Visuzlize with VST".
Neither Popup Panels nor Flowin seem to help.
Do you mean "I want to display VST plugin windows at startup"?
wait for the answer.
Yes.
Is there Visualization Switcher for Foobar, similar to DSP Switcher?
Or any other way how to make Foobar start up with Visualizations according to the user's preferences?
Well, as this new VST adapter is so user-unfriendly and inconvenient for use, I came back to using the good old George Yohng's VST wrapper (http://www.yohng.com/software/foobarvst.html).
It does not work with Foobar v.2.0 64-bit version, but it works with its 32-bit version.
And it is able to display the VST plugin window at Foobar's startup, just the way I want.
Excuse my bluntness, I cannot help but wonder: why was George Yohng able to create back then (his plugin's webpage was last modified on 2013/10/01) a good reliable user-friendly VST adapter which still works wonderfully up to this day, 10 years later, while the creators of neither the buggy VST adapter 2.4 (https://hydrogenaud.io/index.php/topic,84947.0.html), nor this new hapless VST adapter can repeat his success?
Doesn't work properly with VST3 plugins that adapt to set output. I'm no dev but VST3 should be dynamically taking in "track channel numbers" in a DAW. Plugins like the Halo Upmix use this to adjust themselves automatically.
I tried the Halo Upmix VST3 and it doesn't work, it stays stereo. Setting channel overrides does nothing.
I tried the old VST2 32 bit versions of Halo Upmix with the old 2.4 plugin from a decade ago, and that works, although only in 5.1 i.e. 6 channels.
Ideally, I would use the ASIO component and set up output for my 12 channel ASIO, and use Halo Upmix to upmix stereo music to 7.1.4 .
This, however, requires letting the VST3 plugin know that it has 12 channels available, so that it can adjust itself.
After that, the wrapper needs to properly output the audio in multichannel.
Why create this VST adapter, if there is no VST plugin window showing when Foobar plays?
What's the point? How to adjust the settings of a vst plugin while music is playing?
How to adjust the settings of a vst plugin while music is playing?
While the music is playing, go to Prefs/Playback/DSP Manager, and in the Active DSPs list click the "..." button next to a VST plugin you have added to your Active list, which will open its GUI and allow you to adjust it during playback.
Granted, it would be nice to have the ability, already requested, to assign an active VST like a Foobar UI Element to a floatable foo_flowin type window, so it could open with Foobar (or not) and be positioned as desired.
Why create this VST adapter, if there is no VST plugin window showing when Foobar plays?
What's the point? How to adjust the settings of a vst plugin while music is playing?
I was thinking the same thing. After reading through the topic and not getting an answer i take it's better to stick with using the 32bit version of Foobar2000 and George Yohng's VST Wrapper.
Of course you can show the editor and adjust it with the new VST component while playing back
I tried the Halo Upmix VST3 and it doesn't work, it stays stereo. Setting channel overrides does nothing.
I also noticed that I'm getting only stereo.
I tried the old VST2 32 bit versions of Halo Upmix with the old 2.4 plugin from a decade ago, and that works, although only in 5.1 i.e. 6 channels.
The VST 2.4 adapter works with 7.1! For Halo Upmix you have to set FCL and FCR in the Matrix Mixer to SL and SR. Otherwise side/back is mixed together.
But I still can't enable all plugins at the same time.
It used to be like this:
In foobar v 2, I'd like to have this feature.
This is impossible?
But I still can't enable all plugins at the same time.
It used to be like this:
OK, I understand now that by "enable" you mean to be able to view and adjust all the VST plugins' GUI interfaces at the same time. Yes that is not possible now, but I would support adding that feature, also the ability to seek through a song without losing the VST effect which is irritating.
The main reason I use Foobar2000 is the possibility run the VST plugins on my music. I would also really support the possibility to run several UI interfaces simultaneously. This is the way I used to run it with the previous VST-host on previous Foobar2000 versions. The ability to run VST3 plugins on Foobar2000 v2 was a major improvement as my latest software suite purchase was VST3 only. However, just as NickMan and Sveakul I run some VSTs where the effects were visible in other VST applications, and I could see those effects by switching between the windows. As it is now, I can't see the effects in the other applications and this would be on my wishlist for future updates.
That said I wonder if this is even possible to be constructed within the current VST3 capable VST-host implementation; i e is there any point in pining for it? I ask because I have no idea of the current VST 2.x/3.x Adapter 0.11.10 works, other than that it seems to be sandboxed outside of Foobar2000.
If this possibility indeed is there, perhaps we could make an entry to the "[Suggestions / Wishlists] for future updates" thread?
HI Folks -
Wondering if anyone has seen this error
"Unrecoverable Playback error : Could Not Negotiate VST Audio Format"
I only seem to get this if i seek forwards or backwards.
Currently using FOOBAR2000 V2.0, and this seems to be specifically a problem with the AmbioOne plugin (The ambisonic RACE crosstalk eliminator by Weldroid).
If i take it out the VST chain - no problem.
It would be tempting to say the problem lies with this plugin - but this worked with the earlier VST plugin version - had done for a long time, so im not sure its the plugin itself, but more with the new way the VST plugin handles AmbioOne?
Have tried forcing stereo format - but this doesn't seem to change behaviour.
Not a killer issue - as i dont skip through tracks very often - but seems to be the current VST Plugin / Foobar2000 V2.0 / AmbioOne VST where I see this issue. Thought id write it in.
I haven't had that problem, but experience other problems.
Peter, if you read this. I'm using iZotope Ozone 9 Advanced, both the VST2 and VST3 versions, with the VST2.x/3.x adapter, and in both Foobar2000 v 1.6.16 and 2.0, x64, running on Windows7 Sp2.
Here are the problems:
First, the program has the ability to turn on and off stereo and mono. So if I turn on mono, the software vectorscope displays it as mono, but the sound out of Foobar2000 is still stereo, so something overrides the functionality.
Second, the program can switch channel, so left becomes channel right and v.v. Same as for stereo mono, this does not effect the audio out of Foobar2000.
Third, certain changes made to a sound file can be heard as only the delta between previous and new settings. This doesn't work either.
For the first two points I've tested the previous version Ozone 8, both VST2 and VST3 and the first two problems are not present. They work in Ozone 8. The third bullet cannot be tested as it was not a feature in version 8 of Ozone.
iZotope claims they have no reports on problems of the sort I'm experiencing. They claim it must be either the DAW (foobar2000), the adapter, or the OS, Windows7, but neither are supported. When I bought it they claimed it would work with Windows7, but not officially supported.
I've asked what changes they have made to how these features were programmed between v8 and v9 but have not received any replies, and probably won't.
First of all, the VST adapter is OK, evetything works as it should be exept one thing.
All the meters included in VST plugins doesn't move smooth. Regardless if it is a needle meter or a bar meter, VST2 or VST3 the movement is choppy, there is no smoothness.
It looks like a low FPS.
The same plugins in audio editors run very smooth.
----
Foobar 2.1/64 bit -> ASIO output or WASAPI /push output
Feature request - the ability configure foo_dsp_vst3 to just send 2.0 channels to the VST plugin, and drop the rest.
Feature request - the ability configure foo_dsp_vst3 to just send 2.0 channels to the VST plugin, and drop the rest.
Ok then, applying the "Downmix channels to stereo" DSP before putting a VST plugin (especially ones that only work on stereo channel and not surround sound) does the similar trick right? What's the problem with putting "Downmix channels to stereo" DSP before VST plugin?
How do we use this plugin in practice?
The only way I managed to use it is via Library, Configure, Playback, DSP manager, Active DSPs, ...., and manually choosing needed vst each time. I did not find any other way to see measuring panels/windows. I use Voxengo Span, AnSpec, Correlometer, Oscarizator, dpMeter5, Izotope Ozone Imager. To be able to see anything measured I must repeat the procedure described above each time. I also saved VST plugin in DSP chain presets and enabled DSP switcher on the Toolbar. I can pick VST plugin to be "used" but to no effect.
Do I miss some other, easier, more intuitive way to do it? If not, it would be nice to have such a way,
I'm in a similar situation.
Can I use it without following the steps configure > Playback > DSP Manger > Active DSPs?
Is there an easy way to call VST?
Feature request - the ability configure foo_dsp_vst3 to just send 2.0 channels to the VST plugin, and drop the rest.
Ok then, applying the "Downmix channels to stereo" DSP before putting a VST plugin (especially ones that only work on stereo channel and not surround sound) does the similar trick right? What's the problem with putting "Downmix channels to stereo" DSP before VST plugin?
Oh, it's because I want 2.1 for music playback.
( DSP chain = Resampler(SoX) -> MathAudio HEQ -> foo_subwoofer ) => 2.1 output => ASIO { Topping DM7 }
At the same time, I want to use VST for visualization (screen candy) for which the plugin only supports 2.0.
For example, StereoTool v3.
That's why I asked for this VST feature request.
At the same time, I want to use VST for visualization (screen candy) for which the plugin only supports 2.0.
For example, StereoTool v3.
That's why I asked for this VST feature request.
Oh, some if not most VST plugins only support stereo audio even for audio analysis VSTs whereas native fb2k visualizations like built-in peakmeter can support multichannel audio (provided these components makes use of all channels and/or lets you take any channels you want to visualize, rather than just stereo).
tbh, I don't have experience with VST plugins since I'm not a music producer guy (but I'm a JS coder (https://codepen.io/TF3RDL) after all), so my assumption is kinda very rough, but given the fact that my own audio visualizations like this one (https://codepen.io/TF3RDL/pen/VwENJbB) that involves multiple channels only react to left and right channels (except on AudioWorklet-based visualization (https://codepen.io/TF3RDL/pen/MWLzPoO) where it reacts to all channels, not just stereo when I put the 18ch .wav file (https://drive.google.com/file/d/1rB2GyB5ii7mWySXbi5eKWdthJ-6z6_SL/view?usp=sharing) into the visualizer), I said that similar thing could happen when comes to VST plugins that don't support more than two channels (hence the feature request, especially with "Visualize with VST" part) in foobar2000 through VST 2.x/3.x Adapter component
Has anybody tried to successfuly use VST plugins from Waves bundle, for example Waves NX?
Whenever I try to open anything, I got completely empty "VST Effect Configuration" window. If an audio file is playing at that moment, I receive the following message:
Unrecoverable playback error: VST refused audio stream format - got: 2ch, VST wants: 1ch
I'm using Foobar2000 v2.0 and VST Adapter 0.11.10. The other VST3 plugins that I tried are working perfectly (for example CanOpener Studio 3). The problem is happening only with Waves plugin in Foobar2000.
Any help is much appreciated.
Error Report? / Feature Request
Please sort "all" VST3 plugins in plugins dropdown menu or add a search box to search for a VST plugin name.
On my computer, there are more than 100 VST3 plugins installed. But VST adapter only sorts the first about 60 plugins and after that it starts to sort the yet not listed plugins again from the beginning of the alphabet. And after the next about 30 plugins, there's no sorting at all. So it's very hard to find a plugin. (In the "Folders..." selection window, only folder "C:\Program Files\Common Files\VST3" is selected on my computer).
It also would be great if only effect plugins are listed and instrument plugins are automatically excluded.
Thank you very much for this great VST adapter. Keep up the good work!
The controls in ARC4 (IK Multimedia ARC System v4) VST plugins (v2/v3) don't work in real time with current (v0.11.2) VST Adapter, only takes effect if the VST added/removed from the stack. Any idea?
In search of a middle ground between Advanced Limiter and Hard -6dB Limiter of Foobar2000, I try various VST plugins. Along the way, I discovered a weird thing: if you process a WAV file with a VST plugin inside any sound editor, the duration and number of samples stay the same, but if you add a VST plugin to the conversion chain of Foobar2000, they increase a bit. For example: 0:04.000 (384 000 samples) becomes 0:04.001 (384 126 samples).
Why is that? Is this a bug,
@Peter?
Windows 7 x64, Foobar2000 2.1, VST adapter 0.11.10, VST plugins (LoudMax (https://loudmax.blogspot.com/), W1 Limiter (http://www.yohng.com/software/w1limit.html)).
Extra samples are caused by attempting to comply with VST tail samples feature.
VST tail samples tells host application how many extra samples to feed to the VST to prevent audible glitch at the end, for an example due to interrupted reverb. For an example, a reverb DSP tells the host application how long the reverb effect is so the host application can feed additional null samples and produce longer output if doing offline processing, which is exactly what happens here.
If this is problematic, I can add an option to suppress this.
You might also want to try "don't reset DSP between tracks" in Converter, which processes whole batch of tracks on one instance of the DSP, as one audio stream, adding tail samples only once, at the end of last track in the batch.
@Peter I'd like to get the output as identical as possible between Foobar2000 and the audio editor, i.e. without extra length. I also tried the batch method with the option "don't reset DSP between tracks" by processing a couple of previously generated audio files (sox --null --bits 24 --rate 48000 sin.wav synth 30 sin 6000 vol -1db), but both turned out to be longer than 30 seconds after conversion.
@Peter, let me add some details. Before encoding modern loud music in a lossy way, sometimes you need to use a limiter that can suppress intersample peaks (https://www.audiosciencereview.com/forum/index.php?threads/practical-example-of-intersample-peak-greater-than-6-dbfs.14095/). In this case, LoudMax (https://loudmax.blogspot.com/) or stuff from Airwindows (https://www.airwindows.com/) comes to mind. And before encoding audiobooks, sometimes you need to suppress excessive noise. If you do this via VST adapter 0.11.10 under Foobar2000 2.1 x64, the duration of the output file increases from one to hundreds of milliseconds — silence is added. And if you do this via a sound editor like Audacity, then the duration remains the same. Also, I've noticed that Audacity has some VST latency compensation, but am not sure if it is related.
Is there anything else I could add to help resolve this issue?
(https://i3.imageban.ru/out/2024/04/06/e03c55cf1ebc04af65e7b390272d7443.png)
(https://i2.imageban.ru/out/2024/04/06/d2adfbdafd74358c1c4ef7367b4e2aba.png)
(https://i3.imageban.ru/out/2024/04/06/f9b5cfa1164a004b331a6abe435b59ca.png)
Duration Samples xxHash Filename
---------- --------- ------------------ --------------------------
0:17.000 749 700 fb9d2331508131cf original.wav
0:17.000 749 700 25ae3c78e20a23df out.audacity.adclip8.wav
0:17.000 749 700 9b2a4fdce1b8fe24 out.audacity.loudmax.wav
0:17.100 754 110 6fbdb65beeccfafe out.foobar.adclip8.wav
0:17.001 749 761 f124c1615b67e7ee out.foobar.loudmax.wav
Hi there,
Anyone here managed to get the uBACCH VST3 to work in foobar2000?
(https://shop.bacch.com/pages/downloads)
I keep getting crashes.
(https://i.ibb.co/fCqnzFC/2024-04-07-1716-u-BACCH-64bit.png)
And in Windows Event Log:
Faulting application name: fooVSTHost64.exe, version: 0.0.0.0, time stamp: 0x6475c8cd
Faulting module name: uBACCHaudio.vst3, version: 0.0.0.0, time stamp: 0x650893e2
Exception code: 0xc0000005
Fault offset: 0x00000000004e9297
Faulting process id: 0x13f8
Faulting application start time: 0x01da88cd95d37085
Faulting application path: C:\foobar2000.portable.soekris.usb\user-components\foo_dsp_vst3\fooVSTHost64.exe
Faulting module path: C:\Program Files\Common Files\VST3\BACCH Laboratories\uBACCHaudio.vst3
Report Id: 1da6e591-89f2-40b7-8e8d-be4cb2b42f6e
Faulting package full name:
Faulting package-relative application ID:
@Peter I'd like to get the output as identical as possible between Foobar2000 and the audio editor, i.e. without extra length. I also tried the batch method with the option "don't reset DSP between tracks" by processing a couple of previously generated audio files (sox --null --bits 24 --rate 48000 sin.wav synth 30 sin 6000 vol -1db), but both turned out to be longer than 30 seconds after conversion.
Behavior changed in version 0.12, tail samples are ignored unless enabled in advanced preferences.
...
All the VST meters (RMS/PEAK) are not moving smoothly. I mean, there is no delay but needles or bars are not moving as they should. It is like frames per second were too low so visualisation is a kind of choppy.
The same meters in every DAW or audio editor move smoothly.
All the VST meters (RMS/PEAK) are not moving smoothly.
I use Voxengo SPAN (https://www.voxengo.com/product/span/) 3.21, a free VST3 for all sorts of measurements, and notice the visualization depends on the features of the file being played. E.g. compare the smooth animation of FLAC 7 (https://cdn.muny.us/a/fileBox/7Qa6mE4h48/siren.flac.7.mp4) and the choppy one of WavPack x3 (https://cdn.muny.us/a/fileBox/rMCoWmN851/siren.wavpack.x3m-threads.mp4). Additional DSPs such as a resampler, which may slow down CPU (there is no dedicated GPU on my end), were not used.
Player: Foobar2000 2.1 x64, VST adapter 0.12.
All the VST meters (RMS/PEAK) are not moving smoothly.
I use Voxengo SPAN (https://www.voxengo.com/product/span/) 3.21, a free VST3 for all sorts of measurements...
I know Voxengo, I use it too but the same Voxengo with the same settings moves smoother in any DAW then in Foobar.
There is a nice meter called Blue Cat's DP Meter Pro - just download a VST demo version and a lack of smoothnes in Foobar will be very easy to observe: https://www.bluecataudio.com/Products/Product_DPeakMeterPro/#Download
Every VST meter I put in Foobar do not move smoothly.
There is a nice meter called Blue Cat's DP Meter Pro…
I checked this VST in Audacity and in Ocenaudio (sound editors), then in Foobar2000. In the first case, the animation is the smoothest. In the second case, as I reported above, the degree of smoothness varies depending on the format being played. Roughly like this on my end: WAV > MP3 > FLAC > TAK > APE > WV. Curiously, the animation of WavPack is choppy in any mode, whether lossless or hybrid lossy. There's definitely something wrong here.
Exactly the same situation
@misioI'm using iZotope Insight2.
foobar2000 is an audio player, not a DAW. It's highly unlikely that the internal architecture optimized for fast and efficient audio playback will be broken and changed to make VST plugins able to update their UIs in realtime. The VST support was added for audio effect supports, not for eye candy.
foobar2000 is an audio player, not a DAW. It's highly unlikely that the internal architecture optimized for fast and efficient audio playback will be broken and changed to make VST plugins able to update their UIs in realtime. The VST support was added for audio effect supports, not for eye candy.
Yeah (I think anyone should understand that foobar2000 is not a DAW even though you can use DSPs within converter), but there is "Visualize with VST" that allows you to visualize audio with VST audio analysis plugins with minimal latency (but obviously it would not change audio output at all), which I use with AnSpec analog-style spectrum analyzer VST
Does this VST dsp work with more than stereo?
Should work. Do you know any specific VSTs that fail?
I tested two upmix VSTs and while the gui of the VSTs shows that they work only the left and right channel is in the output.
Hello,
Same here. No signal from rear, center and LFE channels of (at least one) 5.1 upmix VST with no error reported. Upmix VST was working fine with old VST component. (Foobar 1.6.16 and VST component 0.11.7). Thanks for your work BTW.
Cheers.
I gave it a try again but the problem is still the same. With stereo input there is only stereo output.
but there is "Visualize with VST"
What are you refering to?
but there is "Visualize with VST"
What are you refering to?
(https://i.imgur.com/9lyUIER.png)