Difference between revisions of "Foobar2000:Components/VST 2.4 adapter (foo vst)"
From Hydrogenaudio Knowledgebase
| Line 40: | Line 40: | ||
This component has only advanced settings placed in the corresponding section of Foobar2000 preferences. Depending on the component version they can be found either in the Playback or VST category (the latter is true for v0.6+). Al the problems that mentioned here are caused by the differences between Foobar2000 and VST approaches. | This component has only advanced settings placed in the corresponding section of Foobar2000 preferences. Depending on the component version they can be found either in the Playback or VST category (the latter is true for v0.6+). Al the problems that mentioned here are caused by the differences between Foobar2000 and VST approaches. | ||
* ''VST declicker size (256*n samples, 4 by default)''<br/>Number of zero samples to be passed through VST on transport switches to suppress plug-in's output data that can produce click at the beginning of the next track, i.e. ringing of filters or delay effect tail. The latter requires this number to be increased. | * ''VST declicker size (256*n samples, 4 by default)''<br/>Number of zero samples to be passed through VST on transport switches to suppress plug-in's output data that can produce click at the beginning of the next track, i.e. ringing of filters or delay effect tail. The latter requires this number to be increased. | ||
| − | * ''VST idle time to unload DLL (0-10,000 ms)'' | + | * ''VST idle time to unload DLL (0-10,000 ms)''<br/>The delay is needed to suppress excessive unload-load cycles between tracks, i.e. to keep VST plug-ins loaded as it is supposed to be for them. |
| − | The delay is needed to suppress excessive unload-load cycles between tracks, i.e. to keep VST plug-ins loaded as it is supposed to be for them. | + | * ''Limit number of outputs for VST effects''<br/>In contrast to DAW, audio players don't manage outputs of their DSPs. Besides, many VST plug-ins don't report activity of their outputs. Hence the only way to output data from 16-channel VST is to drop some of the channels according to the setting. |
| − | * ''Limit number of outputs for VST effects'' | + | |
| − | In contrast to DAW, audio players don't manage outputs of their DSPs. Besides, many VST plug-ins don't report activity of their outputs. Hence the only way to output data from 16-channel VST is to drop some of the channels according to the setting. | + | |
Revision as of 17:02, 12 December 2010
| foo_vst | |
|---|---|
 VST 2.4 adapter | |
| Developer(s) | Yegor Petrov |
| Release information | |
| Stable release | 0.5.2.0 |
| Preview release | 0.6.0.0 |
| foobar2000 compatibility | |
| Minimum version | 1.0+ |
| UI module(s) | N/A |
| Additional information | |
| Use | VST plug-ins as native Foobar2000 DSPs |
| License | Proprietary |
| Discussion thread | Discussion and download page |
| View all components | |
VST 2.4 adapter is a component which aims to allow Foobar2000 users to use VST 2.4 plug-ins equally with “native” ones.
Usage
First, add VST plug-ins you would like to use in the VST manager: Preferences → Components → VST plug-ins. Restart is required for the changes to take effect. After the restart open the DSP Manager or some conversion dialog box to try the plug-ins you've added.
→ 
Use View → DSP menu to access DSP configuration windows. Bind commands by their number to keyboard shortcuts if necessary.
Features
The component has support for the following feature set:
- Multiple instances
- Multiple channels (including asymmetric configs like 2.0 → 5.1)
- Chain presets and secondary DSP chains (“convert” feature)
- Modeless DSP configuration windows with keyboard shortcut binding
- FXP import/export
Limitations and known issues
- Supports only up to 20 VST entries due to API limitations (not to be confused with particular instances in a chain).
- No support for VSTs without custom editors yet (to be implemented in the near future).
- Doesn't support x64 VST plug-ins: Foobar2000 is 32-bit application.
- Smooth track switching must be disabled for some plug-ins to work (so they will be unloaded in the same thread as the one they were loaded in).
- Modeless DSP configuration functionality isn't well synchronized with the DSP manager in the Preferences window.
Settings
This component has only advanced settings placed in the corresponding section of Foobar2000 preferences. Depending on the component version they can be found either in the Playback or VST category (the latter is true for v0.6+). Al the problems that mentioned here are caused by the differences between Foobar2000 and VST approaches.
- VST declicker size (256*n samples, 4 by default)
Number of zero samples to be passed through VST on transport switches to suppress plug-in's output data that can produce click at the beginning of the next track, i.e. ringing of filters or delay effect tail. The latter requires this number to be increased. - VST idle time to unload DLL (0-10,000 ms)
The delay is needed to suppress excessive unload-load cycles between tracks, i.e. to keep VST plug-ins loaded as it is supposed to be for them. - Limit number of outputs for VST effects
In contrast to DAW, audio players don't manage outputs of their DSPs. Besides, many VST plug-ins don't report activity of their outputs. Hence the only way to output data from 16-channel VST is to drop some of the channels according to the setting.
