View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019152 | MMW 5 | Playback | public | 2022-06-03 19:14 | 2026-06-03 15:28 |
| Reporter | zvezdan | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | N/A |
| Status | assigned | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 2027 | Fixed in Version | 2027 | ||
| Summary | 0019152: VST plug-in support needed | ||||
| Description | VST plug-ins are very popular in musical applications, available for anything that you could think about. There are 32-bit and 64-bit versions, and there are Windows, Mac and Linux versions of them. Many respected VST authors have all possible variants available (32/64-bit, Win/Mac, VST2/3). There exist VST plug-ins that allow opening Winamp DSP plugins into VST-only host applications. Also, there exist VST plugins/wrappers that allow opening 32-bit VST plugins in 64-bit VST host applications and vice versa. I think VST2 plugins are still more popular than the newer VST3 plugins, but there are also plugins/wrappers that allow opening VST2 plugins in VST3-only host applications and vice versa. Some media players like JRiver Media Center already support VST plugins. Here is the official VST3 SDK, but VST2 SDK could be found on archive.org as well: https://github.com/steinbergmedia/vst3sdk | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3402 | ||||
|
|
Sounds like a good idea to, particularly in case there'd be a working solution to host Winamp DSP plug-ins through VST3 in MM. Did you test any such a solution, so that we know that it really works from Winmp plug-ins? |
|
|
Yes, I tried everything that I described, including VST2 32-bit plugin that could host Winamp DSP plugins. Particularly, I tried Enhancer Winamp plugin with it in more than dozen VST host applications and they all worked fine. Actually, there are two available VST plugins that could host Winamp DSP plugins, which I have found and tried. If I remember correctly, one of them is a little bit problematic because it cannot remember which Winamp DSP plugin was selected after restart of the VST host program, so every time when I restarted the program I needed to select the wanted DSP plugin again (Enhancer). The another one don't have such issue. Well, if user has only one Winamp DSP plugin in the specified folder, even the problematic VST plugin would work fine. I am sure that someone of you who has knowledge of both Winamp plugins and VST plugins wouldn't have any problem to write your own VST wrapper plugin if these two ones that I found are not working as you expect. |
|
|
Ok, thanks, it's definitely encouraging to know that there's a working solution (even if, as you wrote, it'd possibly make sense to implement our own, sometimes). Assigning to Michal to evaluate complexity of an implementation in MM, let's discuss then. |
|
|
Just for your information, one more competitor beat you with this thing - AIMP got recently support for VST2 plugins. |
|
|
Fixed in build 3402. Added support for VST3 audio effects (user can select to use 32b or 64b). Currently not yet compatible with our crossfade/remove silent handling. |
|
|
Great! I just hope that you have implemented VST wrapper for Winamp DSP plugins as well. The available wrappers are VST2, so using another wrapper for VST2-to-VST3 would be needed. That could introduce latency or potential stability and, AFAIK, they are all commercial. |
|
|
Winamp DSP plugins support is not yet implemented, at first I wanted to test standard existing VST3 filters. |
|
|
Can you please add more information as I am not being able to detect/load any VST3 DSP plugins. |
|
|
peke: VST3 must be installed to system to their standard paths, 64b plugins are in C:\Program Files\Common Files\VST3 , 32-bit in: C:\Program Files (x86)\Common Files\VST3 Then go to Options - Player - VST3 Effects and choose architecture (you can use only one, 64b or 32b). |
|
|
Ok, VST plugins needs to have Own Path Configuration, most apps do that. Will open new Bug Also I just found that I have ton of VST2 plugin and 2 VST3 Plugins. |
|
|
VST3 plugins have dedicated install paths, "all VST3 plug-ins must comply with": https://helpcenter.steinberg.de/hc/en-us/articles/115000177084-VST-plug-in-locations-on-Windows It is different from VST2. |
|
|
Well, not all programs are complying with that, many has the ability to specify the additional folders. For example, foobar2000: https://www.foobar2000.org/components/view/foo_dsp_vst3/screenshots Also, such concept with files in C:\Program Files\ is not very nice for a portable mode. Have you implemented the list of plugins located in the said folder(s) with checkboxes (you know, if someone don't want applied all plugins from such folder)? And a possibility to set their order in chain? Sometimes it is not the same if a plugin A is applied before plugin B or vice versa. |
|
|
The VST3 filters should be installed to dedicated folders. What hosting apps allow to scan is different thing. Anyway, it will be needed anyway once we add support also for VST2, where folders are not so strictly defined. Yes list with check-boxes and ability to change order. |
|
|
Oh, problem with VST2 is, that authors of this format actively suppress using old VST2 SDK and do not offer license to use it. So there is problem with legality. Old agreements are ok, but it is not possible to sign new. So it is not possible to completely legally add support for VST2 it seems :-/ https://forums.steinberg.net/t/can-i-create-vst-2-support-for-host-application-vst-3-license/202012/4 "it is not possible to license a VST2 for host too" |
