Hydrogenaudio Forums

Hosted Forums => foobar2000 => 3rd Party Plugins - (fb2k) => Topic started by: Yegor on 13 November, 2010, 04:07:47 PM

Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 13 November, 2010, 04:07:47 PM

(https://hydrogenaud.io/imgcache.php?id=a1c48fc386c3fd3f6dc62b7e1f5e55df" rel="cached" data-warn="External image, click to view at original size" data-url="http://img257.imageshack.us/img257/5553/vstlogoalphasmall.png)

Foobar2000 VST 2.4 adapter
by Yegor Petrov


How to use it (video) (http://youtu.be/RaFcdAxpaQY)
Description, usage, changelog (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components/VST_adapter) and other info is in Hydrogenaudio Wiki.

Version 0.9.0.3 download: [attachment=6385:foo_vst_0903.zip]
Alternative ZIP of the same DLL: [attachment=7278:foo_vst.zip]
Yegor's latest source (2011-08-31; see p. 13 (http://www.hydrogenaudio.org/forums/index.php?showtopic=84947&st=300)): foo_vst_src.zip (http://www.hydrogenaudio.org/forums/index.php?act=attach&type=post&id=6658) ( 180.35K )


This software is provided 'as-is', without any express or implied warranty.
In no event will the author be held liable for any damages arising from the use of this software.

VST is a trademark of Steinberg Media Technologies GmbH
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 13 November, 2010, 04:55:52 PM
This is a VST adapter component which aims to allow fb2k users to use VST plugins equally with “native” ones, i.e. it supports the following:


Nice, going to try this with the "TT dynamic range meter (http://www.pleasurizemusic.com/)" right away.
Title: foo_vst: VST 2.4 adapter
Post by: ExUser on 13 November, 2010, 04:58:37 PM
Excellent! Finally a VST adapter that feels like foobar2000 itself, rather than the ugly hacks that are the current ones.
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 13 November, 2010, 05:18:46 PM
Looks fine here and great plus for design (settings configurable in foobar preferences)
I added EffectChainer, then restarted foobar (is this necessary?) and VSTs (set inside EffectChainer) are loaded and run as expected
Problem is when trying to load DX effects: this component then crashes foobar, while foo_dsp_vstwrapper does not have this problem
Title: foo_vst: VST 2.4 adapter
Post by: mudlord on 13 November, 2010, 07:13:53 PM
Very nice work.
Makes my stuff redundant but oh well
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 13 November, 2010, 08:34:18 PM
The way VST supposed to be used in foobar. Very nice. I started using it with Isone Pro, so far so good.
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 14 November, 2010, 01:05:34 AM
Fantastaic.
I have a recording studio and own a lot of Plugins (incl Waves) now the use of them is so fantastic........


Thank you very much.

Alex
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 14 November, 2010, 01:19:07 AM
Hi,

what I found out so far.
Smoth integration vor VST Plugins on foobar2000: great.

It did crash with the TLS Maximizer (best freeware maximizer out there)
I get gaps with continuous music (live concrts for example) between tracks.


Chers
Alex
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 November, 2010, 01:36:09 AM
Quote
then restarted foobar (is this necessary?)
Unfortunately, yes. And I don't see any way to get rid of this necessity.

And what is more, it even crashes in basic configs. There must be some fundamental bugs to find out. Gotta work on it.

Quote
I get gaps with continuous music (live concrts for example) between tracks.
That's probably because of re-loading of complex VSTs. I'll optimize this later. Now I'm just keeping things simple. I need to make it stable first
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 14 November, 2010, 05:38:53 AM
It's just crashed on me, I submitted the crash log and dump through foobar service, you can get these information there. I only use one VST (isone pro) and I was tinkering with the VST settings.

EDIT: it seems to only crash when I tinker with the VST GUI.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 November, 2010, 05:53:18 AM
I submitted the crash log and dump through foobar service

Thanks, but please don't do that yet  You know, actually I regret my publication now. I should have posted it later and in a more stable state. Dumps will be useful later.

I'm going to add a notice not to report crashes and contact a moderator to delete the thread.

Sorry guys.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 14 November, 2010, 06:30:53 AM
I think if you set it up then forget about it it's pretty stable, unless you constantly tweaking with the VST GUI then it crashes just as much .
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 November, 2010, 06:34:33 AM
Exactly! And I'm the first kind of user :-D But I'm working hard on making it stable with any usage style.
Title: foo_vst: VST 2.4 adapter
Post by: Zin-Uru on 14 November, 2010, 08:44:20 AM
Thank you! Very actual plugin. Will try.
Title: foo_vst: VST 2.4 adapter
Post by: ExUser on 14 November, 2010, 12:09:14 PM
I'm going to add a notice not to report crashes and contact a moderator to delete the thread.
Not reporting crashes is pretty much never a good idea. foobar2000 only asks because it's impolite to send info without asking. The user doesn't usually know if it's your component causing the crash.

As a developer and as a moderator, I'd encourage you to keep this thread up. I'll delete it if you still insist. Everyone understands that it's a new release and that new releases have some bugs. You're working on it; that's fine. It's such a wonderful development IMO that I'd hate to take a step back in any way.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 November, 2010, 12:12:51 PM
Ok. Let's keep it  I'm just afraid that my component will be added to some kind of black list because of instability.
Title: foo_vst: VST 2.4 adapter
Post by: Zin-Uru on 14 November, 2010, 12:40:53 PM
Ok. Let's keep it  I'm just afraid that my component will be added to some kind of black list because of instability.

You're working on it so there is much reason that it will not be added to black list. Just keep good work as you already do.
Title: foo_vst: VST 2.4 adapter
Post by: lvqcl on 14 November, 2010, 01:21:09 PM
Jusr release stable version with new version number...
Title: foo_vst: VST 2.4 adapter
Post by: Robertina on 14 November, 2010, 08:44:23 PM
Finally a VST adapter that feels like foobar2000 itself, rather than the ugly hacks that are the current ones.

To manage VSTs "outside" foobar2000 as George Yohng's VST wrapper does seems to have the advantage that no application restart is necessary after having added new ones (I leave aside here the possibility to use an universal wrapper like Acon's EffectChainer).

But most important for me: I can play around with VST settings without beeing forced to have foobar's preferences window open so that f2k remains 'untouched' and fully controllable, because the VST configuration is not part of foobar's DSP section.

Or do I fail to see something in my first comparison of these two different concepts of a VST wrapper?

@ Entrase, please continue to develop your VST adapter, there is a lot of interest here and I am looking also for new approaches always.
Title: foo_vst: VST 2.4 adapter
Post by: Steve Forte Rio on 15 November, 2010, 04:16:56 AM
Plugin crashes very often when using iZotope Ozone 3 and switching between tracks

Code: [Select]
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 6FEE9E8Dh
Access violation, operation: write, address: 00000000h

Call path:
playback_process entry=>dsp/run=>dsp_manager::run=>dsp::run

Code bytes (6FEE9E8Dh):
6FEE9E4Dh:  83 C4 0C 33 DB 8B 46 1C 8B 4E 20 89 5C 24 14 3B
6FEE9E5Dh:  C1 72 02 8B C1 3B D8 73 36 8B 07 8B 50 04 8B CF
6FEE9E6Dh:  FF D2 33 C9 39 4E 2C 76 23 8B 56 1C 8B 6E 2C 0F
6FEE9E7Dh:  AF D1 0F AF EB 03 D3 8B 5E 30 03 E9 D9 04 90 41
6FEE9E8Dh:  D9 1C AB 8B 5C 24 14 3B 4E 2C 72 DD 43 EB B6 33
6FEE9E9Dh:  C0 39 46 20 76 18 8B 4E 2C 8B 56 30 0F AF C8 8D
6FEE9EADh:  0C 8A 8B 56 38 89 0C 82 40 3B 46 20 72 E8 33 C0
6FEE9EBDh:  39 46 24 76 18 8B 4E 2C 8B 56 34 0F AF C8 8D 0C

Stack (0CFBF080h):
0CFBF060h:  EA846BAC B3968474 FFFFFD34 000002E4
0CFBF070h:  FFFFFD34 000002CC 00000018 00000000
0CFBF080h:  04C7D83C 0899BAC0 04C7D844 04C7D838
0CFBF090h:  6FEECAE8 00000000 0631088C 3441A7AE
0CFBF0A0h:  737727ED 04C7D838 0CFBF0FC 0CFBF15C
0CFBF0B0h:  00000000 04C7D844 00000000 04C7D83C
0CFBF0C0h:  0CFBF0F0 6FEF14E0 00000001 011E4A63
0CFBF0D0h:  06310B78 06310B08 00000000 0631088C
0CFBF0E0h:  07FB4118 07FB4118 00000031 04C7D838
0CFBF0F0h:  0CFBF190 011F929C 00000002 0CFBF19C
0CFBF100h:  011E5059 07FB4118 06310B78 06310B08
0CFBF110h:  00000000 0631088C 06310B4C 06310B08
0CFBF120h:  06310B78 0CFBF13C 7784201F 0852EA58
0CFBF130h:  00000001 695A4F33 695A4F33 695A4F33
0CFBF140h:  695A4F33 08530DE0 0CFBF1F8 08530DD8
0CFBF150h:  00000000 00000000 00000000 00000000
0CFBF160h:  00000000 0109001F 03000300 0000001F
0CFBF170h:  07FB4118 0CFBF104 00000000 07FB3B18
0CFBF180h:  00000001 00000000 000006E0 0CFBF118
0CFBF190h:  0CFBF1C4 011FE0A2 0000000F 0CFBF1D4

Registers:
EAX: 06331FE8, EBX: 00000000, ECX: 00000001, EDX: 00000000
ESI: 04C7D838, EDI: 0899BAC0, EBP: 00000000, ESP: 0CFBF080

Crash location:
Module: foo_vst
Offset: 9E8Dh

Loaded modules:
foobar2000                      loaded at 010B0000h - 01299000h
ntdll                            loaded at 777F0000h - 7792C000h
kernel32                        loaded at 76020000h - 760F4000h
KERNELBASE                      loaded at 75BF0000h - 75C3A000h
COMCTL32                        loaded at 74890000h - 74A2E000h
msvcrt                          loaded at 773C0000h - 7746C000h
GDI32                            loaded at 77170000h - 771BE000h
USER32                          loaded at 774D0000h - 77599000h
LPK                              loaded at 75C40000h - 75C4A000h
USP10                            loaded at 76100000h - 7619D000h
SHLWAPI                          loaded at 77470000h - 774C7000h
DSOUND                          loaded at 73D10000h - 73D82000h
ADVAPI32                        loaded at 76F10000h - 76FB0000h
sechost                          loaded at 77930000h - 77949000h
RPCRT4                          loaded at 75F70000h - 76011000h
ole32                            loaded at 76FB0000h - 7710C000h
WINMM                            loaded at 73E30000h - 73E62000h
POWRPROF                        loaded at 74E90000h - 74EB5000h
SETUPAPI                        loaded at 75DD0000h - 75F6D000h
CFGMGR32                        loaded at 75A50000h - 75A77000h
OLEAUT32                        loaded at 76230000h - 762BF000h
DEVOBJ                          loaded at 75BD0000h - 75BE2000h
UxTheme                          loaded at 74690000h - 746D0000h
SHELL32                          loaded at 762C0000h - 76F09000h
zlib1                            loaded at 5A4C0000h - 5A4D4000h
shared                          loaded at 73770000h - 7379B000h
imagehlp                        loaded at 779E0000h - 77A0A000h
dbghelp                          loaded at 6F480000h - 6F56B000h
COMDLG32                        loaded at 775A0000h - 7761B000h
Secur32                          loaded at 75700000h - 75708000h
SSPICLI                          loaded at 75850000h - 7586A000h
CRYPT32                          loaded at 75A80000h - 75B9C000h
MSASN1                          loaded at 759B0000h - 759BC000h
gdiplus                          loaded at 74A60000h - 74BF0000h
IMM32                            loaded at 77960000h - 7797F000h
MSCTF                            loaded at 77620000h - 776EC000h
vksaver                          loaded at 10000000h - 10025000h
CRYPTBASE                        loaded at 758C0000h - 758CC000h
pshook                          loaded at 6FEA0000h - 6FEA8000h
RocketDock                      loaded at 00460000h - 00472000h
PSAPI                            loaded at 77980000h - 77985000h
CLBCatQ                          loaded at 761A0000h - 76223000h
MMDevApi                        loaded at 74650000h - 74689000h
PROPSYS                          loaded at 74750000h - 74845000h
dwmapi                          loaded at 74330000h - 74343000h
Amhooker                        loaded at 00AA0000h - 00AA9000h
foo_dsp_crossfader              loaded at 00EA0000h - 00ED2000h
foo_input_ofr                    loaded at 00EE0000h - 00F1D000h
OptimFROG                        loaded at 00F20000h - 00F51000h
foo_dsp_noise                    loaded at 01070000h - 01092000h
foo_bitcompare                  loaded at 01FF0000h - 02018000h
foo_hdcd                        loaded at 02830000h - 02864000h
foo_dsp_xover                    loaded at 02870000h - 028B4000h
foo_burninate                    loaded at 02900000h - 02940000h
foo_convolve                    loaded at 039D0000h - 03A21000h
foo_lastfm_radio                loaded at 03A80000h - 03AC8000h
foo_uie_lyrics2                  loaded at 03C20000h - 03D0E000h
WININET                          loaded at 776F0000h - 777E4000h
Normaliz                        loaded at 77A10000h - 77A13000h
urlmon                          loaded at 75C50000h - 75D85000h
iertutil                        loaded at 771C0000h - 773B9000h
foo_uie_biography                loaded at 69CA0000h - 69CF7000h
foo_dsp_force48kHz              loaded at 73E00000h - 73E1D000h
foo_dsp_soundtouch              loaded at 03AD0000h - 03AF6000h
foo_dsp_resampler_mod2          loaded at 03B00000h - 03B42000h
foo_dsp_std                      loaded at 69C50000h - 69C98000h
foo_out_asio                    loaded at 03B90000h - 03BC6000h
foo_verifier                    loaded at 03D10000h - 03D53000h
foo_input_la                    loaded at 03BD0000h - 03BF5000h
la-core                          loaded at 03F90000h - 04003000h
OLEACC                          loaded at 73F30000h - 73F6C000h
WINSPOOL                        loaded at 73D90000h - 73DE1000h
foo_converter                    loaded at 69BD0000h - 69C4B000h
foo_input_tta                    loaded at 03F10000h - 03F52000h
foo_dumb                        loaded at 04460000h - 044EE000h
foo_run                          loaded at 043F0000h - 0444F000h
foo_input_tak                    loaded at 69B80000h - 69BC4000h
tak_deco_lib                    loaded at 03F60000h - 03F80000h
foo_input_dts                    loaded at 69B10000h - 69B73000h
foo_dsp_span                    loaded at 73740000h - 7376E000h
foo_albumlist                    loaded at 69AB0000h - 69B0D000h
foo_out_ks                      loaded at 042A0000h - 042CA000h
foo_customdb                    loaded at 049D0000h - 04A75000h
foo_channel_mixer                loaded at 04530000h - 0456A000h
foo_playcount                    loaded at 69A70000h - 69AAC000h
foo_ui_std                      loaded at 69950000h - 69A68000h
MSIMG32                          loaded at 6AB10000h - 6AB15000h
foo_masstag                      loaded at 04910000h - 04964000h
foo_vst                          loaded at 6FEE0000h - 6FF04000h
MSVCP90                          loaded at 698C0000h - 6994E000h
MSVCR90                          loaded at 69810000h - 698B3000h
foo_dsp_loudspeakereq            loaded at 045C0000h - 045EC000h
foo_dsp_delta                    loaded at 04990000h - 049AF000h
foo_dsp_ssrcX                    loaded at 04A80000h - 04AC3000h
foo_rgscan                      loaded at 697C0000h - 6980D000h
foo_texttools                    loaded at 69780000h - 697B4000h
foo_out_wasapi                  loaded at 04AE0000h - 04B06000h
foo_input_alac                  loaded at 04B10000h - 04B2D000h
foo_audioscrobbler              loaded at 04DA0000h - 04DD3000h
foo_unpack                      loaded at 6AB20000h - 6AB4E000h
foo_wave_seekbar                loaded at 691D0000h - 6939A000h
WS2_32                          loaded at 75D90000h - 75DC5000h
NSI                              loaded at 77950000h - 77956000h
foo_freedb2                      loaded at 69730000h - 69771000h
foo_dsp_bs2b                    loaded at 04E10000h - 04E37000h
foo_scheduler                    loaded at 68D20000h - 68DFE000h
foo_dsp_dolbyhp                  loaded at 6EDA0000h - 6EDC4000h
VERSION                          loaded at 74E00000h - 74E09000h
foo_runcmd                      loaded at 696F0000h - 69723000h
foo_discogs                      loaded at 69680000h - 696E1000h
foo_input_monkey                loaded at 05010000h - 05058000h
foo_fileops                      loaded at 69510000h - 69557000h
foo_qip_nowplaying_8030          loaded at 05060000h - 05088000h
foo_cdda                        loaded at 69000000h - 6904E000h
foo_vksearch                    loaded at 68B40000h - 68D12000h
WSOCK32                          loaded at 70D50000h - 70D57000h
foo_w7shell                      loaded at 050D0000h - 0510D000h
foo_dsp_resampler                loaded at 051A0000h - 051E2000h
foo_softplaylists                loaded at 68FA0000h - 69000000h
foo_benchmark                    loaded at 05150000h - 0517D000h
foo_input_std                    loaded at 689E0000h - 68B35000h
foo_dsp_resampler_mod            loaded at 053B0000h - 053F2000h
foo_dsp_lowpass                  loaded at 05760000h - 05792000h
foo_dsp_tube                    loaded at 057B0000h - 057D6000h
foo_abx                          loaded at 057E0000h - 05812000h
foo_bpm                          loaded at 68E80000h - 68ECE000h
libfftw                          loaded at 674B0000h - 67636000h
foo_input_dvda                  loaded at 68980000h - 689D7000h
foo_uie_wsh_panel_mod            loaded at 68620000h - 686E2000h
ntmarta                          loaded at 73E70000h - 73E91000h
WLDAP32                          loaded at 77990000h - 779D5000h
apphelp                          loaded at 75870000h - 758BB000h
gameux                          loaded at 727A0000h - 72A18000h
XmlLite                          loaded at 74300000h - 7432F000h
wer                              loaded at 70E60000h - 70EC0000h
shdocvw                          loaded at 72770000h - 7279E000h
profapi                          loaded at 75940000h - 7594B000h
LINKINFO                        loaded at 72E50000h - 72E59000h
ntshrui                          loaded at 72FE0000h - 7304F000h
srvcli                          loaded at 75600000h - 75619000h
cscapi                          loaded at 706C0000h - 706CB000h
slc                              loaded at 73A60000h - 73A6A000h
SXS                              loaded at 758E0000h - 7593F000h
jscript                          loaded at 68400000h - 684B2000h
CRYPTSP                          loaded at 753F0000h - 75406000h
rsaenh                          loaded at 75190000h - 751CB000h
RpcRtRemote                      loaded at 758D0000h - 758DE000h
wshom                            loaded at 68950000h - 68971000h
MPR                              loaded at 71080000h - 71092000h
ScrRun                          loaded at 68920000h - 6894A000h
WindowsCodecs                    loaded at 743B0000h - 744AB000h
explorerframe                    loaded at 72A20000h - 72B8F000h
DUser                            loaded at 74A30000h - 74A5F000h
DUI70                            loaded at 74590000h - 74642000h
sud                              loaded at 68550000h - 6860B000h
ADVPACK                          loaded at 68190000h - 681BE000h
d3d9                            loaded at 68230000h - 683F3000h
d3d8thk                          loaded at 688C0000h - 688C6000h
atiumdag                        loaded at 671B0000h - 674AD000h
atiumdva                        loaded at 66EA0000h - 67174000h
d3dx9_42                        loaded at 66A10000h - 66BF5000h
d3dx10_42                        loaded at 681C0000h - 68230000h
CTASIO                          loaded at 05FD0000h - 05FDF000h
ctosuser                        loaded at 06050000h - 06066000h
mswsock                          loaded at 753B0000h - 753EC000h
wshtcpip                        loaded at 74ED0000h - 74ED5000h
wship6                          loaded at 753A0000h - 753A6000h
DNSAPI                          loaded at 75270000h - 752B4000h
IPHLPAPI                        loaded at 73960000h - 7397C000h
WINNSI                          loaded at 73950000h - 73957000h
rasadhlp                        loaded at 71A10000h - 71A16000h
fwpuclnt                        loaded at 735E0000h - 73618000h
iZotope Ozone 3                  loaded at 63920000h - 63CB4000h
msxml3                          loaded at 68780000h - 688B2000h
RASAPI32                        loaded at 73FB0000h - 74002000h
rasman                          loaded at 73F90000h - 73FA5000h
rtutils                          loaded at 73F70000h - 73F7D000h
dsrole                          loaded at 73A70000h - 73A79000h
peerdist                        loaded at 73B70000h - 73B95000h
USERENV                          loaded at 74F90000h - 74FA7000h
AUTHZ                            loaded at 75560000h - 7557B000h
NLAapi                          loaded at 73B60000h - 73B70000h
mlang                            loaded at 657C0000h - 657EE000h
winrnr                          loaded at 71A60000h - 71A68000h
napinsp                          loaded at 71A50000h - 71A60000h
pnrpnsp                          loaded at 71A30000h - 71A42000h
wshbth                          loaded at 71A20000h - 71A2D000h
sensapi                          loaded at 70160000h - 70166000h
ieframe                          loaded at 6C820000h - 6D29F000h
WINTRUST                        loaded at 75BA0000h - 75BCD000h
avrt                            loaded at 744B0000h - 744B7000h

Stack dump analysis:
Address: 6FEECAE8h (foo_vst+CAE8h)
Address: 737727EDh (shared+27EDh), symbol: "uCallStackTracker::uCallStackTracker" (+0h)
Address: 6FEF14E0h (foo_vst+114E0h), symbol: "foobar2000_get_interface" (+2CD0h)
Address: 011E4A63h (foobar2000+134A63h)
Address: 011F929Ch (foobar2000+14929Ch)
Address: 011E5059h (foobar2000+135059h)
Address: 7784201Fh (ntdll+5201Fh), symbol: "RtlFreeHeap" (+7Eh)
Address: 0109001Fh (foo_dsp_noise+2001Fh), symbol: "foobar2000_get_interface" (+1B66Fh)
Address: 011FE0A2h (foobar2000+14E0A2h)
Address: 0114B77Ch (foobar2000+9B77Ch)
Address: 011FEC69h (foobar2000+14EC69h)
Address: 011FA07Eh (foobar2000+14A07Eh)
Address: 0114B2C4h (foobar2000+9B2C4h)
Address: 0121F928h (foobar2000+16F928h)
Address: 01225998h (foobar2000+175998h)
Address: 01201D32h (foobar2000+151D32h)
Address: 0114DC2Eh (foobar2000+9DC2Eh)
Address: 774E59DFh (USER32+159DFh), symbol: "MsgWaitForMultipleObjects" (+0h)
Address: 7606F292h (kernel32+4F292h), symbol: "SetEvent" (+0h)
Address: 778C72E0h (ntdll+D72E0h), symbol: "NlsAnsiCodePage" (+190h)
Address: 778C72E0h (ntdll+D72E0h), symbol: "NlsAnsiCodePage" (+190h)
Address: 778C72E0h (ntdll+D72E0h), symbol: "NlsAnsiCodePage" (+190h)
Address: 686B45C0h (foo_uie_wsh_panel_mod+945C0h), symbol: "foobar2000_get_interface" (+59060h)
Address: 778C72E0h (ntdll+D72E0h), symbol: "NlsAnsiCodePage" (+190h)
Address: 689B8954h (foo_input_dvda+38954h), symbol: "foobar2000_get_interface" (+24C04h)
Address: 778C72E0h (ntdll+D72E0h), symbol: "NlsAnsiCodePage" (+190h)
Address: 689B8954h (foo_input_dvda+38954h), symbol: "foobar2000_get_interface" (+24C04h)
Address: 778C0000h (ntdll+D0000h), symbol: "EtwTraceEventInstance" (+1FC6h)
Address: 698119C4h (MSVCR90+19C4h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 7784EAB9h (ntdll+5EAB9h), symbol: "LdrGetDllHandleEx" (+272h)
Address: 7784E83Eh (ntdll+5E83Eh), symbol: "LdrGetDllHandle" (+18h)
Address: 75BF7D9Ch (KERNELBASE+7D9Ch), symbol: "GetModuleHandleW" (+51h)
Address: 75BF7DAFh (KERNELBASE+7DAFh), symbol: "GetModuleHandleW" (+64h)
Address: 75BF7D9Ch (KERNELBASE+7D9Ch), symbol: "GetModuleHandleW" (+51h)
Address: 76020000h (kernel32+0h)
Address: 75C0D5F5h (KERNELBASE+1D5F5h), symbol: "OutputDebugStringA" (+100h)
Address: 75BF7DAFh (KERNELBASE+7DAFh), symbol: "GetModuleHandleW" (+64h)
Address: 75BF7BA1h (KERNELBASE+7BA1h), symbol: "GetEnvironmentVariableA" (+20Bh)
Address: 75BF7D0Eh (KERNELBASE+7D0Eh), symbol: "GetEnvironmentVariableA" (+378h)
Address: 0122CCE8h (foobar2000+17CCE8h)
Address: 777F0000h (ntdll+0h)
Address: 7784EE1Eh (ntdll+5EE1Eh), symbol: "LdrGetProcedureAddressEx" (+279h)
Address: 777F00D0h (ntdll+D0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 777F0000h (ntdll+0h)
Address: 777F0000h (ntdll+0h)
Address: 777F00D0h (ntdll+D0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 7784EE1Eh (ntdll+5EE1Eh), symbol: "LdrGetProcedureAddressEx" (+279h)
Address: 7784ECBEh (ntdll+5ECBEh), symbol: "LdrGetProcedureAddressEx" (+119h)
Address: 7784EF67h (ntdll+5EF67h), symbol: "LdrGetProcedureAddress" (+A0h)
Address: 77846D7Eh (ntdll+56D7Eh), symbol: "RtlCompareUnicodeStrings" (+EBh)
Address: 7784ECF0h (ntdll+5ECF0h), symbol: "LdrGetProcedureAddressEx" (+14Bh)
Address: 777F0000h (ntdll+0h)
Address: 77846D7Eh (ntdll+56D7Eh), symbol: "RtlCompareUnicodeStrings" (+EBh)
Address: 7784F0C0h (ntdll+5F0C0h), symbol: "RtlDecodePointer" (+0h)
Address: 7784F0C0h (ntdll+5F0C0h), symbol: "RtlDecodePointer" (+0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 7784ECF0h (ntdll+5ECF0h), symbol: "LdrGetProcedureAddressEx" (+14Bh)
Address: 7784F05Fh (ntdll+5F05Fh), symbol: "LdrGetProcedureAddress" (+198h)
Address: 777F0000h (ntdll+0h)
Address: 7784EE1Eh (ntdll+5EE1Eh), symbol: "LdrGetProcedureAddressEx" (+279h)
Address: 76020000h (kernel32+0h)
Address: 760200E0h (kernel32+E0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 760DEDA8h (kernel32+BEDA8h), symbol: "DecodePointer" (+6h)
Address: 76020000h (kernel32+0h)
Address: 76020000h (kernel32+0h)
Address: 760DEDA2h (kernel32+BEDA2h), symbol: "DecodePointer" (+0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 7784EE1Eh (ntdll+5EE1Eh), symbol: "LdrGetProcedureAddressEx" (+279h)
Address: 7784ECBEh (ntdll+5ECBEh), symbol: "LdrGetProcedureAddressEx" (+119h)
Address: 0122CCE8h (foobar2000+17CCE8h)
Address: 0122CCE8h (foobar2000+17CCE8h)
Address: 7784231Eh (ntdll+5231Eh), symbol: "RtlAllocateHeap" (+211h)
Address: 75BF69B1h (KERNELBASE+69B1h), symbol: "InterlockedIncrement" (+0h)
Address: 77835E6Ch (ntdll+45E6Ch), symbol: "ZwWaitForMultipleObjects" (+Ch)
Address: 75BF6872h (KERNELBASE+6872h), symbol: "GetProcessHeap" (+30h)
Address: 744B0000h (avrt+0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 0122447Ch (foobar2000+17447Ch)
Address: 012080A4h (foobar2000+1580A4h)
Address: 0114CD95h (foobar2000+9CD95h)
Address: 774E59DFh (USER32+159DFh), symbol: "MsgWaitForMultipleObjects" (+0h)
Address: 7606F292h (kernel32+4F292h), symbol: "SetEvent" (+0h)
Address: 774E59FEh (USER32+159FEh), symbol: "MsgWaitForMultipleObjects" (+1Fh)
Address: 012080C0h (foobar2000+1580C0h)
Address: 0114CD33h (foobar2000+9CD33h)
Address: 7377281Eh (shared+281Eh), symbol: "uCallStackTracker::uCallStackTracker" (+31h)
Address: 012080D5h (foobar2000+1580D5h)
Address: 0114CC77h (foobar2000+9CC77h)
Address: 01201D79h (foobar2000+151D79h)
Address: 76071194h (kernel32+51194h), symbol: "BaseThreadInitThunk" (+12h)
Address: 7784B495h (ntdll+5B495h), symbol: "RtlInitializeExceptionChain" (+63h)
Address: 76082B55h (kernel32+62B55h), symbol: "UnhandledExceptionFilter" (+0h)
Address: 76082B55h (kernel32+62B55h), symbol: "UnhandledExceptionFilter" (+0h)
Address: 7780D75Dh (ntdll+1D75Dh), symbol: "RtlAddMandatoryAce" (+5ADh)
Address: 7784B468h (ntdll+5B468h), symbol: "RtlInitializeExceptionChain" (+36h)
Address: 0114CC40h (foobar2000+9CC40h)
Address: 0114CC40h (foobar2000+9CC40h)

Environment:
App: foobar2000 v1.1.1
OS: Windows 6.1.7600 x86
CPU: Intel® Core™ i3 CPU        530  @ 2.93GHz, features: MMX SSE SSE2 SSE3 SSE4.1 SSE4.2
Audio: Динамики (Creative SB X-Fi); Динамики (Realtek High Definition Audio)
UI: Default User Interface 0.9.5

Components:
Core (2010-11-05 10:46:52 UTC)
   foobar2000 core 1.1.1
foo_abx.dll (2009-06-07 12:25:26 UTC)
   ABX Comparator 1.3.4
foo_albumlist.dll (2010-11-05 10:45:06 UTC)
   Album List 4.5
foo_audioscrobbler.dll (2010-06-04 06:27:04 UTC)
   Audioscrobbler 1.4.7
foo_benchmark.dll (2008-12-31 16:23:04 UTC)
   Decoding Speed Test 1.1
foo_bitcompare.dll (2008-12-05 13:08:02 UTC)
   Binary Comparator 1.2
foo_bpm.dll (2010-04-20 12:35:07 UTC)
   BPM Analyser 0.2.4.1
foo_burninate.dll (2010-01-18 20:10:44 UTC)
   Audio CD Writer 3.0.2
foo_cdda.dll (2010-11-05 10:44:56 UTC)
   CD Audio Decoder 3.0
foo_channel_mixer.dll (2008-03-12 09:37:47 UTC)
   Channel Mixer 0.9.6.5
foo_converter.dll (2010-11-05 10:44:36 UTC)
   Converter 1.5
foo_convolve.dll (2006-08-04 19:57:26 UTC)
   Convolver 0.3
foo_customdb.dll (2010-03-04 11:10:54 UTC)
   Custom Database 0.1.0_beta1
foo_discogs.dll (2010-07-19 21:18:22 UTC)
   Discogs Tagger 1.25
foo_dsp_bs2b.dll (2009-06-08 09:30:06 UTC)
   bs2b 3.1.0
foo_dsp_crossfader.dll (2010-01-13 19:46:10 UTC)
   Gapless Crossfader 1.3.4.1
foo_dsp_delta.dll (2008-10-24 12:57:16 UTC)
   Noise Sharpening DSP 1.0.0
foo_dsp_dolbyhp.dll (2010-01-22 11:40:28 UTC)
   Dolby Headphone Wrapper 1.4.1
foo_dsp_force48kHz.dll (2008-08-18 20:54:46 UTC)
   force 48kHz 2008.08.18
foo_dsp_loudspeakereq.dll (2009-07-02 05:52:58 UTC)
   Loudspeaker Equalizer 1.0.1
foo_dsp_lowpass.dll (2010-04-07 15:04:30 UTC)
   SoX Lowpass filter 0.0.2
foo_dsp_noise.dll (2009-06-28 17:28:32 UTC)
   Add Noise DSP 0.0.4
foo_dsp_resampler.dll (2010-09-27 19:55:00 UTC)
   SoX Resampler 0.5.5
foo_dsp_resampler_mod.dll (2010-09-27 19:55:03 UTC)
   SoX Resampler mod 0.5.5 mod
foo_dsp_resampler_mod2.dll (2010-09-27 19:55:05 UTC)
   SoX Resampler mod2 0.5.5 mod2
foo_dsp_soundtouch.dll (2010-01-14 19:08:06 UTC)
   SoundTouch DSP 1.1
foo_dsp_span.dll (2009-04-07 11:35:31 UTC)
   Surround Pan 1.3
foo_dsp_ssrcX.dll (2008-05-11 05:45:16 UTC)
   Resampler DSP (SSRC X) 0.57
foo_dsp_std.dll (2010-11-05 10:45:06 UTC)
   Standard DSP Array 1.0
foo_dsp_tube.dll (2007-02-06 23:17:55 UTC)
   Tube Sound 0.8
foo_dsp_xover.dll (2010-04-07 17:04:58 UTC)
   Crossover 0.42
foo_dumb.dll (2010-10-03 18:54:22 UTC)
   DUMB module decoder 0.9.9.20
foo_fileops.dll (2010-11-05 10:43:42 UTC)
   File Operations 2.1.3
foo_freedb2.dll (2010-11-05 10:43:42 UTC)
   freedb Tagger 0.6.2
foo_hdcd.dll (2010-07-31 09:13:34 UTC)
   HDCD decoder 1.5
foo_input_alac.dll (2010-08-31 19:26:36 UTC)
   ALAC Decoder 1.0.6
foo_input_dts.dll (2010-09-04 19:15:29 UTC)
   DTS decoder 0.3.0
foo_input_dvda.dll (2010-09-08 14:53:23 UTC)
   DVD-Audio Decoder and Watermark Detector 0.3.6
foo_input_la.dll (2010-11-02 14:42:33 UTC)
   Lossless Audio(La) decoder 0.01
foo_input_monkey.dll (2009-05-01 11:40:52 UTC)
   Monkey's Audio Decoder 2.1.4
foo_input_ofr.dll (2008-11-29 11:48:04 UTC)
   OptimFROG Lossless/DualStream Decoder 1.21b
foo_input_std.dll (2010-11-05 10:50:28 UTC)
   Standard Input Array 1.0
foo_input_tak.dll (2010-01-09 17:11:58 UTC)
   TAK Decoder 0.4.4
foo_input_tta.dll (2010-10-30 11:24:31 UTC)
   TTA Audio Decoder 3.2
foo_lastfm_radio.dll (2010-02-17 20:21:28 UTC)
   Last.fm Radio 0.5.7e
foo_masstag.dll (2009-09-18 07:01:36 UTC)
   Masstagger 1.8.4
foo_out_asio.dll (2009-03-22 12:15:46 UTC)
   ASIO support 1.2.7
foo_out_ks.dll (2006-08-04 19:54:58 UTC)
   Kernel Streaming Output 1.2.2
foo_out_wasapi.dll (2010-11-06 14:16:37 UTC)
   WASAPI output support 2.1
foo_playcount.dll (2010-10-15 18:30:42 UTC)
   Playback Statistics 3.0.1
foo_qip_nowplaying_8030.dll (2010-11-10 17:20:03 UTC)
   Foobar2000 Now Playing support for QIP v80xx 0.5.1
foo_rgscan.dll (2010-11-05 10:44:34 UTC)
   ReplayGain Scanner 2.0.9
foo_run.dll (2009-06-07 12:15:18 UTC)
   Run services 0.3.7
foo_runcmd.dll (2010-01-07 17:32:34 UTC)
   Run Command 1.1
foo_scheduler.dll (2010-07-19 19:19:29 UTC)
   Scheduler 4.05
foo_softplaylists.dll (2010-10-21 05:55:48 UTC)
   Soft Playlists 2010-10-21
foo_texttools.dll (2010-09-01 16:45:46 UTC)
   Text Tools 1.0.5
foo_ui_std.dll (2010-11-05 10:45:14 UTC)
   Default User Interface 0.9.5
foo_uie_biography.dll (2010-06-12 18:32:50 UTC)
   Biography View 0.4.2.1
foo_uie_lyrics2.dll (2010-04-12 17:19:24 UTC)
   Lyric Show Panel 2 0.4.6.15
foo_uie_wsh_panel_mod.dll (2010-10-31 16:11:15 UTC)
   WSH Panel Mod 1.4.0 Beta 3
foo_unpack.dll (2010-11-05 10:43:56 UTC)
   ZIP/GZIP/RAR Reader 1.6
foo_verifier.dll (2009-10-05 08:39:20 UTC)
   File Integrity Verifier 1.1
foo_vksearch.dll (2010-08-26 18:48:11 UTC)
   vk.com audio search 0.0.5
foo_vst.dll (2010-11-14 08:20:02 UTC)
   VST adapter 1.0
foo_w7shell.dll (2010-09-01 16:44:50 UTC)
   Windows 7 integration 0.2.9.1
foo_wave_seekbar.dll (2010-07-31 07:41:27 UTC)
   Waveform seekbar 0.2.12

Recent events:
Playcount sync: Last.fm responded 'OK'
Opening track for playback: "D:\Моя музыка\Marco V\Con-Fusion\CD1\03 Marco V - Tolerance.flac"
Audioscrobbler: Submitting track...
foo_qip_nowplaying: QIP is not running! ^(
Audioscrobbler: Submission succeeded.
Playcount sync: Contacting Last.fm....
Audioscrobbler: Submitting track...
Opening track for playback: "D:\Моя музыка\Marco V\Con-Fusion\CD1\07 Marco V - Mascenery.flac"
Playcount sync: Last.fm responded 'OK'
foo_qip_nowplaying: QIP is not running! ^(
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 15 November, 2010, 05:03:16 AM
Quote
Or do I fail to see something in my first comparison of these two different concepts of a VST wrapper?
It seems that you don't know what modal window mode is. It's when you can't access parent window. As I wrote in the first post configuration windows will be accessible in a non-modal mode so that you'll be able to open as many windows as you want.

I'm also going to make an another simple component later. It will put menu items for accessing DSP config windows to both foobar's main menu and notification area icon. Would that be ok then?  At the moment, I'm just focusing on the stability, not on the features. New version is coming. Some serious bugs have been fixed already.

As for no-restart management of VSTs, this will be the only drawback. But hey, don't you restart foobar when adding new components?  It's not some kind of lazyness. I just don't see any way to instantiate DSP services in runtime. GY's VST wrapper approach to switching of VSTs won't work here because of the way Foobar works with multiple dsp services and their names. Sorry.


Quote
Plugin crashes very often when using iZotope Ozone 3 and switching between tracks
Thanks. But please use something like pastebin.com to share long texts. Zaranee spasibo

------>8-------
Currently TT Dynamic Range Meter seems to be one of the most difficult to get working.
Title: foo_vst: VST 2.4 adapter
Post by: Steve Forte Rio on 15 November, 2010, 07:33:04 AM
Quote
Thanks. But please use something like pastebin.com to share long texts


ok, I'll try it. Simply haven't found spoiler tag on this forum
Title: foo_vst: VST 2.4 adapter
Post by: GeSomeone on 15 November, 2010, 09:03:52 AM
ok, I'll try it. Simply haven't found spoiler tag on this forum

You should use [ codebox] ... [/codebox ] instead of quote. (without the extra spaces)
Title: foo_vst: VST 2.4 adapter
Post by: rx32555 on 15 November, 2010, 05:13:11 PM
[a href="http://img541.imageshack.us/i/20101115190420.png/" target="_blank"]


Thanks!
Title: foo_vst: VST 2.4 adapter
Post by: kode54 on 15 November, 2010, 05:27:40 PM
VST + winamp_dsp_bridge (dfx) = Nice sound 

You do know there's a foobar2000 port of DFX, right?
Title: foo_vst: VST 2.4 adapter
Post by: rx32555 on 15 November, 2010, 09:27:54 PM
VST + winamp_dsp_bridge (dfx) = Nice sound 

You do know there's a foobar2000 port of DFX, right?



  Yep, but I use DFX winamp (old version) with ffdshow, DFX foobar gives me serious problems with that version ... ffdshow crash (DFX use the same .dll I guess)
Title: foo_vst: VST 2.4 adapter
Post by: Mr.Duck on 15 November, 2010, 10:23:46 PM
Nice plugin. I'm using it for this crossfeed... http://refinedaudiometrics.com/products-hdphx.shtml (http://refinedaudiometrics.com/products-hdphx.shtml)

It works OK but if I try to configure the VST then foobar crashes.

I will be watching this one though so keep up the good work


EDIT: OK it's a bit less stable than that. Causing a crash sometimes when skip to the next track too. This crossfeed is pretty nice I hope you can give it a try and get it to work one day
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 16 November, 2010, 01:18:30 AM
Here is a new version. It only contains core bugfixes, no changes in UI at all (so yes, plug-ins with no GUI are still crashing if you try to configure it).

LINK REMOVED. Obtain the component in the first thread.

Plug-ins mentioned in this thread:
iZotope Ozone 3: OK
Isone Pro: OK
HDPHX: OK (don't press config, there is no config)
Acon EffectChainer: can't get DX effects listed at all and thus can't test with DX, but generally it seems to be OK.
TT Dynamic Range Meter: crashes on cfg window closing (doesn't crash during step-by-step debugging — the real problem for many developers)
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 16 November, 2010, 01:29:19 AM
Tested it, still crash with http://refinedaudiometrics.com/products-hdphx.shtml (http://refinedaudiometrics.com/products-hdphx.shtml), as far as I know this vst include a fake slider so it does have GUI? Isone Pro is fine. If you need the crash log and dump I can email you.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 16 November, 2010, 02:43:02 AM
At this stage it'll be more useful if you tell me the properties of audio on which you were testing it. What DSPs were in the stack along with the HDPHX if any? What output do you use?

Quote
as far as I know this vst include a fake slider so it does have GUI?
Number of parameters has nothing to do with the GUI  If plug-in lacks its own GUI then it's up to the host to provide some kind of user interface. Usually it's a set of knobs or sliders fit uniformly to the window. That's why you can get “different” editors for the same VST in different hosts. I haven't implented this yet.

(https://hydrogenaud.io/imgcache.php?id=de2509e3863d7040acde6bf07c61447a" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/m2E0U0F8l7WIULZ-Region.png)

(https://hydrogenaud.io/imgcache.php?id=146c1dd4873f96035c6fa7976b9535e8" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/E32KP3iVGRpQ3qg-1hdphxProgram1of.png)
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 16 November, 2010, 03:30:15 AM
Well I only got it crashed with HDPHX and you explained why it crashed in your 2nd passage (it only has a fake parameter not GUI, I don't know the inner working of VST ), so I guess it's not really necessary for me to post the information you required in the 1st passage but I'll provide it to be sure anyway: redbook cd audio, dsps (top down): convert 5.1 to stereo, resampler (sox) (resampling to 44.1KHz), HDPHX, Advanced Limiter.

When I try Isone Pro, I replace HDPHX with it and it's rock stable now.
Title: foo_vst: VST 2.4 adapter
Post by: kode54 on 16 November, 2010, 08:15:24 AM
Maybe that configuration button could be disabled when effFlagsHasEditor is unset? Until such time as you implement support for automation parameters in the absence of an editor dialog.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 16 November, 2010, 09:04:24 AM
If it wasn't about some major changes in the code, I would have done it already. The problem is that VSTs aren't supposed to be loaded when foobar asks if DSP has configuration. Therefore some changes in the scanner need to be made so it will store VST's attributes in the registry. In one's turn some temporary structures need to be introduced for that (otherwise VST list in the preferences will go bloated with unnecessary columns)... And so on. As I said, the UI is to be improved a little bit later

You know, fb2k and VST approaches to instantiation are quite different and it takes time to figure out and implement the glue for linking two worlds together so they run smoothly. I told you (http://www.hydrogenaudio.org/forums/index.php?showtopic=84635) about this before

I've only missed one temporary decision — show “sorry” msg box when the button is pressed.
Title: foo_vst: VST 2.4 adapter
Post by: Mr.Duck on 16 November, 2010, 12:36:02 PM
Here is a new version. It only contains core bugfixes, no changes in UI at all (so yes, plug-ins with no GUI are still crashing if you try to configure it).


Unfortunately it is still exactly the same and crashes when changing tracks while HDPHX is being used. I am using WASAPI output and no other DSPs.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 16 November, 2010, 12:47:03 PM
I can't get it crashing at all. May be you're still using old version for some reason? Try to remove the component completely and then install it again.

The version should be 1.0.01: (https://hydrogenaud.io/imgcache.php?id=e133013f851a2399cded3c239dc4642d" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/8TesScb49MOblzL-Region.png)

Are there any dsp-related plug-ins? May be something is trying to open config window.
Title: foo_vst: VST 2.4 adapter
Post by: Mr.Duck on 16 November, 2010, 02:35:43 PM
I moved the VST file from the foobar root folder into a sub folder. I forgot I did that. So I just removed the VST from the list and added it again and it seems to be working fine  I'll keep an eye on it but its not crashed yet. So thanks very much for this plugin.


- Needs a file not found error message rather than a crash for missing VSTs.
- I use foobar2000 in portable mode. If you could store the paths to the VST as a relative path rather than the full path then that would work much better and still be fine for people that do not use a portable install. Plus store config in a file rather than the registry would be much appreciated.
Title: foo_vst: VST 2.4 adapter
Post by: riboge on 16 November, 2010, 04:57:32 PM
Finally a VST adapter that feels like foobar2000 itself, rather than the ugly hacks that are the current ones.

To manage VSTs "outside" foobar2000 as George Yohng's VST wrapper does seems to have the advantage that no application restart is necessary after having added new ones (I leave aside here the possibility to use an universal wrapper like Acon's EffectChainer).

But most important for me: I can play around with VST settings without beeing forced to have foobar's preferences window open so that f2k remains 'untouched' and fully controllable, because the VST configuration is not part of foobar's DSP section.

Or do I fail to see something in my first comparison of these two different concepts of a VST wrapper?

@ Entrase, please continue to develop your VST adapter, there is a lot of interest here and I am looking also for new approaches always.

I like the same feature of Yohng's wrapper, but I found just today that with newly installed foobar 1.1.1 that Redline monitor plug-in does not appear on startup as it used to with the Wrapper in place using 1.0.  I had to install Redline's dll via VST DSP Entries with a restart to get it to function, so now it only appears with the DSP section open by clicking configuration just like with this new vst adapter.  You seem to imply you can still get the vst settings without needing to do this using Foobar 1.1.  Is that so, and, if so, can you tell me how?
Title: foo_vst: VST 2.4 adapter
Post by: Robertina on 16 November, 2010, 11:26:36 PM
You seem to imply you can still get the vst settings without needing to do this using Foobar 1.1.  Is that so, and, if so, can you tell me how?

Yes, the wrapper's handling as described in the passage "USAGE" here (http://www.hydrogenaudio.org/forums/index.php?showtopic=59206&view=findpost&p=531351) also works with the current foobar2000 v1.1.1, at least with all VSTs I am using on Windows XP Prof. SP3

Please pose possible further questions related to G. Yohng's VST wrapper in the thread I linked to, I don't feel well to discuss this under Entrase's topic.
Title: foo_vst: VST 2.4 adapter
Post by: noiselab on 18 November, 2010, 02:27:58 PM
Will there be support for 64-bit VSTs?
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 18 November, 2010, 03:01:46 PM
Will there be support for 64-bit VSTs?

Why, do you have a 64bit version of foobar nobody else knows about?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 18 November, 2010, 03:09:37 PM
I'm afraid no.
1. Foobar2000 is 32-bit application, hence all its components are 32-bit too.
2. My PC is 32 bit and I have no plans of buying a new one yet.
Title: foo_vst: VST 2.4 adapter
Post by: kode54 on 18 November, 2010, 07:00:10 PM
The only way to support 64-bit VST effects would be to write an external executable proxy to load and execute those effects.
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 18 November, 2010, 08:21:59 PM
Acon EffectChainer: can't get DX effects listed at all and thus can't test with DX, but generally it seems to be OK.
TT Dynamic Range Meter: crashes on cfg window closing (doesn't crash during step-by-step debugging — the real problem for many developers)

If you have some Sony/Cakewalk product they'll install their effects as DX generally and there are perhaps free DX effects somewhere. DX of course can't be processed, but I mentioned them as your component was crashing foobar in the case

Little sad thou, you can't use monitoring VSTs comfortably as we are not in real-time - meaning there is some buffer delay as DSP design is, so what you actually see is delayed response
Can VST component for foobar be made differently, then through this DSP chain?
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 18 November, 2010, 09:26:02 PM
Depends, if you like different implementation get the old vst component. Personally, I prefer tight integration with foobar so I can use it with foobar DSP profile, effect chaining... without resorting to another VST chainer.
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 18 November, 2010, 09:49:07 PM
If you are replying to my post, there is misunderstanding: All foobar VST components (3 of them including this one) are working as DSP components - DSP buffer data is presented in VST before it is actually outputted (sent to playback buffer) or even more intuitive: you see the monitoring data before it is outputed by your sound card's speakers
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 19 November, 2010, 02:15:11 AM
I don't know how to deal with it yet  But surely I'll dedicate a time to find out. Big hosts do synchronize it somehow after all.

As for making it out of chain... Well, I don't know. It could be done as an output service, but the aim of synchronizing isn't worth all the problems one can get while developing that. Speaking in thuan words, you're gonna lose the “tight integration”.

I think it's more about latency measuring and passing the info to VSTs rather than getting rid of the chain. In the end, there will be chain somewhere anyway.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 19 November, 2010, 08:43:54 AM
Bad news. I've spent some time trying to figure out what can I do with the latency and it seems there is no solution. One can only decrease output buffer size to synchronize VST's display with the actual sound.
Title: foo_vst: VST 2.4 adapter
Post by: ExUser on 19 November, 2010, 10:36:36 AM
One possible solution for VST-based visualization would be to write a visualization component that feeds timing-accurate data to a VST. From what I remember from speaking with Peter, foobar2000 provides full PCM data to visualizations.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 19 November, 2010, 11:03:46 AM
Is this time-coded PCM data?
Title: foo_vst: VST 2.4 adapter
Post by: ExUser on 19 November, 2010, 01:09:26 PM
I'm not entirely sure what you mean by "time-coded", but information is given about timing, and pure PCM should be available in the vis subsystem. I'm pretty confident it'll work, based on conversations I've had with Peter. However, I know nothing about the specifics of that subsystem. I'm trying to recruit one of the devs who actually knows something to provide a bit more context.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 19 November, 2010, 02:37:01 PM
I've misunderstood you. Yes, that should be possible. The obvious problem is that such a visualization will only work with already-processed data.

But I think there is a better solution for analyzer-only VSTs. I can make my dsp service to pass data to actual analyzer VST with a delay that is equal to the output buffer size. Delay would be introduced for VST only, not for the whole processing chain. Here is the only problem is to obtain the output buffer size. Is it possible?
Title: foo_vst: VST 2.4 adapter
Post by: mudlord on 20 November, 2010, 06:26:56 AM
I'm not entirely sure what you mean by "time-coded", but information is given about timing, and pure PCM should be available in the vis subsystem. I'm pretty confident it'll work, based on conversations I've had with Peter. However, I know nothing about the specifics of that subsystem. I'm trying to recruit one of the devs who actually knows something to provide a bit more context.


From what I seen in the SDK, it is the case. You can retrieve sample timing along with the pure PCM data. Information is giving regarding sample timing, for A/V sync.

Quote
I can make my dsp service to pass data to actual analyzer VST with a delay that is equal to the output buffer size. Delay would be introduced for VST only, not for the whole processing chain.


So, something circular buffer related.
Title: foo_vst: VST 2.4 adapter
Post by: SevenTwo on 21 November, 2010, 06:46:58 PM
Will there be support for 64-bit VSTs?

I think noiselab means support for x86 VST plugins with 64-bit datapath (double instead float).
Not 64-bit code plugins compiled for x86_64 ...
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 22 November, 2010, 01:28:01 AM
That's pointless. Foobar's DSP chain bit depth is 32 fp and it's sufficient for listening. And I haven't seen any VSTs which only capable of processing with double precision and lack usual single precision mode.

It won't be difficult but I don't see the point. Of course I will introduce double precision support if you tell me why it's necessary.
Title: foo_vst: VST 2.4 adapter
Post by: Marsu42 on 22 November, 2010, 04:44:58 PM
I just tried it and it is very nice to have the ability to use multiple vst plugins at the same time.

However, in comparison to the original vst wrapper the configuration is rather tiresome: as I understand it, whenever one wants to change something, a file->preferences->dsp manager->(plugin)->configure selected is in order? The drawback with this approach is that now the "Preferences: DSP Manager" window clutters the foobar window below and cannot be closed. Furthermore, the vst plugin window cannot be minimized or put below the foobar window (all that was possible with the original vst wrapper). This means that while changing vst settings, the rest of foobar is next to unusable.

Maybe you could implement direct menu shortcuts to the configurations (like View->VST Wrapper->(vst plugin)) ? This would at least remove the locked preferences window while changing settings or using a visual vst plugin.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 22 November, 2010, 09:38:29 PM
That's pointless. Foobar's DSP chain bit depth is 32 fp and it's sufficient for listening. And I haven't seen any VSTs which only capable of processing with double precision and lack usual single precision mode.

It won't be difficult but I don't see the point. Of course I will introduce double precision support if you tell me why it's necessary.

It's not entirely pointless, IMO. Higher bitdepth processing will lower SNR for the particular opertation, and for processing VST that is a plus. However, for playback I doubt one can discern the difference, so not really useful is more correct. IOW, I see some points to it, but find the implementation cost is not worth the results return.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 22 November, 2010, 11:58:12 PM
Quote
Maybe you could implement direct menu shortcuts to the configurations (like View->VST Wrapper->(vst plugin)) ?
Quote
  • Multichannel setup arrangement differences aren't taken into account, nor is VST pin activity status
  • No support for plugins without GUI yet
  • Configuration windows only work in modal mode
  • z3ta_fx and IXL analyzers crashes the application

All of these are to be fixed soon.


Quote
Higher bitdepth processing will lower SNR for the particular opertation
Not in this case, because there is no 64 bit chain in Foobar. One just have to decrease bit depth after increasing it anyway. Hence we get (source → N× [32 → 64 → VST single → 64 → 32] → output) in every active DSP, at every stage. It would only have meaning if there had been pure 64 bit chain in Foobar so we could do it like this: (source → N × [64 → VST double → 64] → output).
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 23 November, 2010, 12:33:33 AM
Higher bitdepth processing will lower SNR for the particular opertation


Emphasize the bold part. I think you meant "source ? N× [32 ? 64 ? VST double ? 64 ? 32] ? output". The "VST double part" will get some benefit here, unless every VST is already using another internal bitdepth (e.g. using double precision regardless of external bitdepth). And say if you have multiple VST stacked consecutively together, it should be better if it can be done like this "source ? 32 ? 64 ? N× [VST double] ? 64 ? 32 ? output". Still I don't think the benefits are worthy of being implemented, I just wanna argue some scientific stuffs about whether this is entirely pointless.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 November, 2010, 12:41:04 AM
Quote
it should be better if it can be done like this "source → 32 → 64 → N× [VST double] → 64 → 32 → output"
Well, it can't be done in Foobar's DSP chain. There is no 64 bit datapath between DSPs in Foobar. It's not entirely pointless generally for sure. But in this particular case, as you said, barely it's worth implementing either at particular stage or in groups using some dirty trickes with storing doubles as two floats %)
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 23 November, 2010, 08:46:39 AM
  • Multichannel setup arrangement differences aren't taken into account, nor is VST pin activity status

To sustain that theory, I did some simple testing for multichannel VSTs not knowing your OP screenshot multichannel VSTs

), but your component I guess tries to output 32 channel and foobar can't handle it
[a href="http://i56.tinypic.com/35ausf7.png" target="_blank"]

[edit] changed 16 to 32 to match screenshot, as there are three bidule VSTs - standard, 16 ch and 32ch
Title: foo_vst: VST 2.4 adapter
Post by: pjofoobar on 23 November, 2010, 08:54:30 AM
Hi Entrase, your VST plug in is great !
It loaded almost all plug ins except iZOzone4.dll although iZotope Ozon4.dll works fine.

I am wondering if you plan to release new version after 2011/Jan/01.

It would be nice to be able to display multiple windows of multiple plug ins.

All the Best

pjofoobar

Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 November, 2010, 01:05:13 PM
Yes, klonuo, I'm going to work on multichannel processing support soon

Quote
- it asks to restart foobar on VST removal - that is really unnecessary

Then restart on adding isn't necessary as well, is it? And restart on installation of new component unnecessary too, right? Wait, it sounds like restarts shouldn't be done at all. Something is wrong here. Let's don't confuse users and let's prevent them from using removed VSTs by restarting. If user doesn't plan to restart after removal, then they shouldn't remove. That's the ideology of Foobar's component and service system as far as I understand it. This is my way of thinking. I may be wrong. Unfortunately, there is no way to add or remove DSP services in runtime.

Quote
It loaded almost all plug ins except iZOzone4.dll although iZotope Ozon4.dll works fine.

I don't remember if previous version checks DLLs but the current one (not published yet though) explains this case clearly:
(https://hydrogenaud.io/imgcache.php?id=e1974348eaa1f5a2b2c8ef284781bda4" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/ZA6CPYRfbZ1Vm2o-Error.png)
iZOzone4.dll isn't VST at all. This is a shared dll which is used by both VST and RTAS wrappers.

Quote
It would be nice to be able to display multiple windows of multiple plug ins.
This is what I'm currently working on. And you know, it's quite difficult to get done because of foobar's decoupling of DSP UI and processing stuff. As I said before VST and Foobar approaches to instantiation and configuration are very different.

By the way, the VST manager is more tidy now:
(https://hydrogenaud.io/imgcache.php?id=b7c421968a8ad37714dc3c208801d95a" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/dUZEntydBGPmTTz-PreferencesVSTpl.png) (http://images.devs-on.net/Image/dUZEntydBGPmTTz-PreferencesVSTpl.png)
And it's not only about UI. Many internals have been changed to be more stable. Strict DLL checking is added.

Thank you guys. Working hard.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 25 November, 2010, 10:39:03 AM
(https://hydrogenaud.io/imgcache.php?id=00069d471073d31a7b03ade296b38e55" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/7yiulmA4zHELsdX-JeanMichelJarreE.png) (http://images.devs-on.net/Image/7yiulmA4zHELsdX-JeanMichelJarreE.png) (https://hydrogenaud.io/imgcache.php?id=537312bcbecbb83d2ac9685c28cf0968" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/i0o8pQOJXfpz4rM-PreferencesKeybo.png) (http://images.devs-on.net/Image/i0o8pQOJXfpz4rM-PreferencesKeybo.png) (https://hydrogenaud.io/imgcache.php?id=1cdbe394c1fde87b763b7380e36b0ad8" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/Ad5frKso7pzwTkZ-Wholescreen.png) (http://images.devs-on.net/Image/Ad5frKso7pzwTkZ-Wholescreen.png)

Coming soon... :)
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 25 November, 2010, 10:52:04 AM
What about no reload track switch, I'm waiting for this .
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 25 November, 2010, 01:23:04 PM
@Entrase: maybe you should leave routing as is, because if i.e. I pass 6ch (5.1) stream and disable LFE then assuming you do the routing by pin activity Ls will be routed to LFE and Rs to Ls, while Rs will be muted. OTOH making some pin matrix setting could be overkill, and most importantly there is easy solution to all this. Add matrix mixer (http://skipyrich.com/wiki/Foobar2000:Matrix_Mixer) after multichannel VST and let user do the routing himself

[a href="http://i51.tinypic.com/2iual9k.png" target="_blank"]
* that's why hosts like Bidule can be very handy (not mentioning it's real powers inside)
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 25 November, 2010, 02:20:06 PM
Quote
What about no reload track switch, I'm waiting for this
Yes, sure. As soon as current UI mess is done.

Quote
maybe you should leave routing as is
Even more! It looks like I'll have to leave it as is since I can't find any VST capable of reporting its output pin activity (though I haven't tested many). Even Bidule doesn't report it. So I don't know what to do with this problem. As for channel configuration, it would not be a problem in the ideal case because along with activity status there should be speaker info as well. But in fact, there is no data at all, quite often.
Quote
Plogue Bidule isn't free but you can run with full capacity for month or so without any annoying popups or similar nonsense.
Its VST wrapper is for registered users only :( I had to ask my friend to help me. I'll ask you next time instead, you'll be more responsive I guess :)

I think it won't be difficult for me to make some channel cutting DSP. Just a dialog box with a slider to set maximum number of channels. May be I'll make it inside of this component.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 27 November, 2010, 02:18:34 PM
Update
Please re-download the archive.

Now you can use multiple DSP config windows with View → DSP menu. That's an experimantal feature and it has some bugs, but it'll take time to fix, so let's leave them till the next release.
You can limit number of outputs to be taken from VST. Default setting is 6 channels (Preferences → Advanced → Playback → “Limit number of outputs for VST effects”). 16 and 32 channel Bidules should work now.
VST manager internals were reworked and I had to change registry values format. Please run this clean_vsts.reg file (http://kostika.net/test/clean_vsts.reg) to remove old entries as they will crash application.

Finally marked as beta now.
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 27 November, 2010, 02:43:16 PM
Please update the first post with changes instead and include the reg file and instructions with the main archive since it looks like it might be needed for every update. Thank you!
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 27 November, 2010, 03:03:49 PM
Please update the first post with changes instead and include the reg file and instructions with the main archive since it looks like it might be needed for every update. Thank you!
I can't.

(https://hydrogenaud.io/imgcache.php?id=259ebb374da1efe51b957d429f29e39e" rel="cached" data-warn="External image, click to view at original size" data-url="http://img819.imageshack.us/img819/9054/screenshot43313053.png)

Should I always provide moderator with updated texts and ask them to update or what? How is it established here?
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 27 November, 2010, 03:51:28 PM
Please update the first post with changes instead and include the reg file and instructions with the main archive since it looks like it might be needed for every update. Thank you!
I can't.


That's weird... how is everybody else doing that? Maybe the release forum has different permissions.
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 27 November, 2010, 04:23:45 PM
16 and 32 channel Bidules should work now.

Thanks Entrase
Having foobar environment with multichannel Bidule processing feels like advanced possibilities can now easily be adopted to any file:

[a href="http://i51.tinypic.com/2vl5n3o.png" target="_blank"]

I can't.

(https://hydrogenaud.io/imgcache.php?id=259ebb374da1efe51b957d429f29e39e" rel="cached" data-warn="External image, click to view at original size" data-url="http://img819.imageshack.us/img819/9054/screenshot43313053.png)

Regular members can edit their posts for 1h from the time they first publish it. You should contact some Mod and ask for promotion I think and become Developer, so that you can edit your own posts after this 1h limit. There is sticky thread in Site Related Discussion forum about this
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 27 November, 2010, 09:49:40 PM
@Entrase: Try to load same VST twice (in VST listing)
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 28 November, 2010, 12:29:32 AM
Yes, I know. Don't do this. It won't be easy to fix and I don't have much time these days. I'm sorry I posted such a bugged version, but hey, it's almost usable ;)

Actually, Foobar doesn't allow multiple config windows to be opened. Since these windows are modal dialogs, there can only be one in a thread. At the same time there should only be one thread—the rule I have to break. There is also no way to control window position without some kind of dirty trick. You know, I'm not sure if I should keep this feature. May be I should cut it so it will only support VST. At least config dialogs are under my control in this case.
Title: foo_vst: VST 2.4 adapter
Post by: foosion on 28 November, 2010, 06:27:20 AM
Actually, Foobar doesn't allow multiple config windows to be opened. Since these windows are modal dialogs, there can only be one in a thread. At the same time there should only be one thread—the rule I have to break.
Just to clarify: The restriction about modal windows is not imposed by foobar2000, it is inherent in Win32 programming. Raymond Chen has written several times about this issue (http://blogs.msdn.com/search/searchresults.aspx?q=modal%20message%20loop&sections=2905) in his blog (http://blogs.msdn.com/b/oldnewthing/).

Nothing stops you from having multiple threads with windows. You "just" have to make sure to properly synchronize communication between different threads and to respect the thread-related restrictions on certain APIs.


Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 28 November, 2010, 07:11:14 AM
I know. But the problem is a little bit deeper. Try to call dsp_entry::g_show_config_popup_v2 for equalizer out of main thread. It outputs “This function can be called only from main thread” to debugger (it does work however). Assuming that it's a blocking function (due to modal dialogs) and there is one main thread, there can be only one such window. If called using main thread callback, this function freezes something and prevents keyboard shortcuts from being used.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 29 November, 2010, 03:36:50 AM
What about no reload track switch, I'm waiting for this :D.
Here you are. The feature introduced in v0.52 ;) But don't forget it's experimental.
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 29 November, 2010, 04:29:21 AM
-deleted-
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 29 November, 2010, 05:08:36 AM
@Entrase: Thanks, but I hear a small click when repeatedly hitting play button, it wasn't there before IIRC.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 29 November, 2010, 03:56:37 PM
Are you sure about it? Try the same with no DSPs. The click happens when there is a difference between the last sample played (before you hit play) and the first one in the song. If it's clear that it's because of DSPs, then tell me which ones I should use to reproduce a click.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 29 November, 2010, 09:55:08 PM
Sure, happened with Isone Pro, my only VST, does not happen without DSPs. You should try a quiet track like some piano and similar to easily hear the click. My output is DirectSound BTW.

EDIT: the click happens everytime I manually change track, too. I guess the reason is like what you said, but normally DirectSound suppresses it with fading.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 November, 2010, 02:46:58 AM
Okay, the problem isn't with sample difference. It's about delay introduced by this plug-in. “Delay” as echo, not as latency. You can more clearly see the effect with some reverb plug-in: one gets the reverb tail at the beginning of the next track (or the current one in the replay case). It seems there is somekind of reset should be done on manual track changes. I put this in the to-do list.
Title: foo_vst: VST 2.4 adapter
Post by: Steve Forte Rio on 30 November, 2010, 01:07:40 PM
What a...??

Quote
Failed to load DLL: foo_vst.dll
Reason: Неверная попытка доступа к адресу памяти.


Looks like corrupted file
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 November, 2010, 01:38:21 PM
Rus: Неверная попытка доступа к адресу памяти = Invalid access to memory location

File is ok. Have you removed old version data as mentioned in the first post? If yes, could you please make a portable installation of fb2k to some folder and test the component there? We need first to find if it's Foobar or the OS problem. Then we will have some starting point at least.
Title: foo_vst: VST 2.4 adapter
Post by: Toggie on 05 December, 2010, 05:51:20 AM
Ignore, I missed the registry key...
Title: foo_vst: VST 2.4 adapter
Post by: Melomane on 05 December, 2010, 01:23:24 PM
thank you , very nice plugin!
Title: foo_vst: VST 2.4 adapter
Post by: Marsu42 on 06 December, 2010, 08:48:00 AM
thank you , very nice plugin!

I second to this: two thumbs up, especially for the nice non-modal configuration via the view->DSP menu entries :-) ... now even the people using traktor as a jukebox might try foobar again!
Title: foo_vst: VST 2.4 adapter
Post by: larryfine on 06 December, 2010, 10:11:50 AM
Thank you.
Works fine with Voxengo TubeAmp, Ruby Tube, Barricade Limiter, TT Dynamic Range and others .
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 13 December, 2010, 03:23:58 PM
There is update to 0.6.0. But please keep old version if it works fine for you. Don't forget it's still not very stable.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 14 December, 2010, 03:46:21 AM
Thanks for the update, the click on track change seems to be fixed, but I have click when I open and close the VST config window. I'm using Isone Pro.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 December, 2010, 05:40:30 AM
This click is caused by the procedure of commiting new configuration to Foobar2000. VST plug-in is requested for configuration data and thus can stutter a little bit. I'll look if it can be fixed. You may try to make the output buffer size greater.

Did you have to increase declicker size to get rid of the click on track change?
Title: foo_vst: VST 2.4 adapter
Post by: servimo on 14 December, 2010, 08:53:33 AM
I now upgrade to v6.0, used the registry cleanup file, and now no vst in the list even VST manager appears. I forget to make a backup of my old foo_vst, where i can find the old one?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 December, 2010, 10:41:10 AM
Unfortunately, you've removed all entries with no chance to get them back. As for old version, I've attached it to this post.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 14 December, 2010, 10:59:31 AM
This click is caused by the procedure of commiting new configuration to Foobar2000. VST plug-in is requested for configuration data and thus can stutter a little bit. I'll look if it can be fixed. You may try to make the output buffer size greater.

Greater output buffer size only delays the click.
Did you have to increase declicker size to get rid of the click on track change?

No, I didn't.
Title: foo_vst: VST 2.4 adapter
Post by: garyldavis on 15 December, 2010, 10:52:49 AM

Fineprint: stuff marked as beta isn't considered to be stable.

(https://hydrogenaud.io/imgcache.php?id=a1c48fc386c3fd3f6dc62b7e1f5e55df" rel="cached" data-warn="External image, click to view at original size" data-url="http://img257.imageshack.us/img257/5553/vstlogoalphasmall.png)

Foobar2000 VST 2.4 adapter
by Yegor Petrov


Details
See article in the Hydrogenaudio Wiki (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components/VST_adapter).

Download
Users of previous betas (1.0 and 1.00.01) must either delete all entries in the old version first or use this reg file to do the same: (Attachment)
Download it here (v0.6.0): (Attachment)
This software is provided 'as-is', without any express or implied warranty.
In no event will the author be held liable for any damages arising from the use of this software.


VST is a trademark of Steinberg Media Technologies GmbH

Yegor,

I love this plugin...but I have a question.  It seems that when I add "any" vst in Foobar 1.1.1 my 5.1 (6 channels) automatically reverts to a (2 channel) system?  I've tried loading 1 vst or multiple it makes no difference.  When I send the VST back to the inactive side of the DSP menu my 6 channels become available again.
(I am using CHANNEL MIXER) to obtain my 6 channels (5.1) but even if I take this off the active side of the DSP menu I still end up with a 2 channel setup.

I don't know a whole lot about this kind of stuff, but my sound is great with just the channel mixer.  It does sound great too when I load my VST's, but I don't get the "spacial" sound that I like when it reverts to the 2 channels.

Does anyone have any suggestions for me or experience the same issues?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 15 December, 2010, 11:28:40 AM
How many inputs/outputs are in VSTs you tried?

(https://hydrogenaud.io/imgcache.php?id=c4076bea0b57dd3d7994158254452c15" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/lj6J72NAZj7hH4z-PreferencesVSTpl.png)
Title: foo_vst: VST 2.4 adapter
Post by: servimo on 16 December, 2010, 09:32:15 AM
Unfortunately, you've removed all entries with no chance to get them back. As for old version, I've attached it to this post.

Thanks for the old version.
Title: foo_vst: VST 2.4 adapter
Post by: garyldavis on 16 December, 2010, 11:45:37 AM
How many inputs/outputs are in VSTs you tried?

(https://hydrogenaud.io/imgcache.php?id=c4076bea0b57dd3d7994158254452c15" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/lj6J72NAZj7hH4z-PreferencesVSTpl.png)

Well you've just given me some help.  I didn't think about I/O.

Thanks!!!  We'll see what happens next.
Title: foo_vst: VST 2.4 adapter
Post by: hidn on 16 December, 2010, 01:26:17 PM
must have
Title: foo_vst: VST 2.4 adapter
Post by: garyldavis on 16 December, 2010, 06:21:38 PM
How many inputs/outputs are in VSTs you tried?

(https://hydrogenaud.io/imgcache.php?id=c4076bea0b57dd3d7994158254452c15" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/lj6J72NAZj7hH4z-PreferencesVSTpl.png)

Well, thanks to you.  It's all awesome now.  Just needed to find VST with 6 or more outputs!!!
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 December, 2010, 12:31:22 PM
0.7.0
Serious bugfixes.
Relative paths in the portable mode.

In general, it's the first version to support the portable mode. It may sound strange because fb2k provides transparent storage for its components, but in this case it's necessary to read configuration at the stage where fb2k services aren't available yet. Depending on the installation, the adapter uses either the registry or a file in the player's directory.
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 24 December, 2010, 01:37:48 AM
Hi

I use portable mode. My Foobar (newest stable Version) crashes an launching with the newest version enabled.


Cheers
Alex
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 December, 2010, 02:22:38 AM
Oops. Sorry. Download the 0.7.1.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 24 December, 2010, 04:25:40 AM
It seems like you did something and the click when closing VST config window rarely happens now.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 December, 2010, 04:53:17 AM
It doesn't click on focus loss anymore, closing procedures all remain the same. But I admit it could affect closing as well.
Title: foo_vst: VST 2.4 adapter
Post by: Marsu42 on 24 December, 2010, 07:28:07 AM
There's a change to the worse from 0.60 to 0.71 with two plugins I tried (Melda Dynamics and Multiband Dynamics): When foobar is playing, the configuration window is blank (i.e. 100% grey), the content only shows when the music is stopped. Other plugins work.

I am using a rather slow laptop, so it might be a task priority problem - but this didn't happen in 0.60. I am using the portable mode. Since I deleted the older dll, I cannot investigate the problem any further.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 December, 2010, 11:52:05 AM
I confirm this with a difference that it randomly occurs in both versions. Got to dedicate time for that later. The performance should not be a problem. v0.6 is attached to the post.
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 24 December, 2010, 12:31:29 PM
Hi
fantastic, it works now and in the meantime it even is gapless.  Great.

Thank you very much.
Title: foo_vst: VST 2.4 adapter
Post by: Marsu42 on 24 December, 2010, 01:22:18 PM
I confirm this with a difference that it randomly occurs in both versions. Got to dedicate time for that later. The performance should not be a problem. v0.6 is attached to the post.


I verified it with the old version, too, and you're correct: There was no regression. In fact another component I forgot I changed was eating the cpu time. No big deal since I spotted it, thx again.

But as the last point on your to-do list there might be a possibility to boost the priority of the VST plugin, for everyting else in the playback chain there seems to be an option under Preferences->Playback->Thread priority.
Title: foo_vst: VST 2.4 adapter
Post by: GeSomeone on 27 December, 2010, 04:51:22 PM
for everyting else in the playback chain there seems to be an option under Preferences->Playback->Thread priority.

This is only done for batch processing (like replaygain scanner and converter), not for DSP components.
Title: foo_vst: VST 2.4 adapter
Post by: Mr.Duck on 30 December, 2010, 07:08:08 PM
I just upgraded from 1.00.01 to 0.71 so thanks for this nice plug and thanks now it looks like its working great in portable mode.

But I also get the problem where the configuration window is blank (i.e. 100% grey). It's like that all the time music playing or not with HDPHX crossfeed... http://refinedaudiometrics.com/products-hdphx.shtml (http://refinedaudiometrics.com/products-hdphx.shtml)
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 30 December, 2010, 09:30:01 PM
HDPHX does not have any configuration so you get that, just close the window.
Title: foo_vst: VST 2.4 adapter
Post by: Melomane on 02 January, 2011, 06:34:51 AM
Failed to load DLL: foo_vst.dll

he asked what library ? no dependency requirer in wiki

thank you

win XP, foobar 1.1.1

edit: Microsoft Visual C++ 2008 Redistributable Package (x86) was the problem , please add in wiki
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 08 January, 2011, 10:20:52 AM
OK.

0.8.0

The adapter has been rewritten from scratch with considerable changes concerning VST plug-in handling.
The [un]loading strategy was completely changed, so now core VST DSPs are always kept active starting with the fb2k at once.
There is no “idle timer” anymore and the corresponding advanced setting has been removed.
FXP loading/saving has been fixed.
Some dirty and unsafe tricks were removed in order to increase stability and reliability, so VST settings won't be saved with a editor left opened on quit.

Important note: To get your VST entries back in the normal (non-portable) mode, you should click Add... button in the preferences holding the Shift key. The registry won't be used to store VSTs anymore.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 08 January, 2011, 11:20:36 AM
FYI, HDPHX crashed again when accessing its configuration. Can you disable configuration for this kind of VST plug-in, one that doesn't have a real configuration?
Title: foo_vst: VST 2.4 adapter
Post by: Hancoque on 08 January, 2011, 11:34:31 AM
HDPHX crashed again
No crashes here.

@Entrase: What are "core VST DSPs"?

There is still the problem of thread safety. When converting more than one file at once and having the converter thread count not limited to 1 the resulting files are garbled.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 08 January, 2011, 11:52:06 AM
Yes, it does not crash normally, unless you try to access its configuration.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 08 January, 2011, 11:53:20 AM
Ok, here is 0.8.0.1
Quote
No crashes here.
It does crash if you try to open HDPHX config in 0.8.0.
Quote
What are "core VST DSPs"?
VSTs in the main DSP chain (as opposed to secondary chains in the “convert” feature). I'm used to name them so after get_core_settings()
Quote
When converting more than one file at once and having the converter thread count not limited to 1 the resulting files are garbled.
Confirmed. I'll investigate this as soon as possible.

UPD Oh my... This seems to be a major problem. I've never tested it that way. If the player recalls same dsp_preset data objects as in case of conversion then all the same vst instances are used to process different audio streams. Damn. I don't even know what to do.

UPD2 Nevermind that pang now. Gotta try a solution later. Hancoque, thank you for pointing that out.
Title: foo_vst: VST 2.4 adapter
Post by: Hancoque on 08 January, 2011, 12:14:19 PM
Yirkha, who took over the development of the Dolby Headphone wrapper some time ago, made it thread-safe which it previously wasn't. Maybe he can help you there.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 08 January, 2011, 12:29:49 PM
It's not really about thread safety (there is all wrong in a one thread as well). It's about coupling back fb2k's decoupled approach to DSP settings setup. I mistakenly assumed that adding some random data to preset objects would allow me to identify different instances of VSTs. But I missed that these randomized presets could be recalled in more than one processing chain. Hence one instance of a VST plug-in can be assigned to more than one DSP processing object, which is way wrong because such VST will process chunks from different streams by turns and that's where garbling goes on.
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 08 January, 2011, 12:37:24 PM
That's fast. Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: notwa on 08 January, 2011, 01:41:40 PM
It seems that every plug from the ReaPlugs (http://www.reaper.fm/reaplugs/index.php) pack works fine, except for ReaComp. After adding it to the VST Plugins list, foobar just crashes. However, it runs fine if you run it in Acon Effectchainer.  crash report (http://pastebin.com/bJEJnPdQ)

EngineersFilter (http://www.kvraudio.com/get/4768.html) has a strange bug in which the right channel gets stuck on a loop after a few seconds of using it. It just repeats the few hundred samples over and over until you take it off.

Both of the plugins are free, so go ahead and try them yourself. I forgot to backup my vst collection a few weeks ago, so I'll keep testing them as I get them.
Thanks a ton for all your effort, this will certainly get some use from me.

Makes my stuff redundant but oh well

Not really, your plugins are native whereas these are not. 'nuff said.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 08 January, 2011, 02:37:00 PM
Quote
except for ReaComp
Confirmed and fixed. It requests UID for null instance and that's strange from my point of view. I didn't expect such behavior.
Quote
EngineersFilter has a strange bug
It sticks on declicking procedure. I'll try to find out why. Now you can disable declicker by setting its size to zero: Preferences > Advanced > VST > Declicker size. Restart is required.

Please let me know if you need the fixed version now. Otherwise the bugfix is due to the next release.
Title: foo_vst: VST 2.4 adapter
Post by: rokk on 11 January, 2011, 09:17:16 PM
Hi!

I found your plugin excellent for using vst-plugins.    Although It doesn't work under "wine". Do you know any procedure to make it work under it. I'm using OSX Snow Leopard, a portable installation of foobar v1.1.1, Isone Pro, some freebie plugins and Reaper for testing (where I can use the plugins normally).

I'm using v0.8.0.1 of your plugin, and after installing it and launching foobar, I get this message:

"
Failed to load DLL: foo_vst.dll
Reason: Unknown error code (317)


and in the terminal the message is:

"
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8)
wine: Call from 0x7b829da2 to unimplemented function msvcr90.dll._set_abort_behavior, abortingfixme:msvcr90:__clean_type_info_names_internal (0x78506644) stub
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 80000100
fixme:win:RegisterShellHookWindow (0x10052): stub
fixme:keyboard:RegisterHotKey (0x100e0,0,0x00000006,46): stub



I tried downloading and registering the "msvcr90.dll", though I'm not sure if it's the correct version, or if I'm putting where is supposed to go (Windows\system32) ? or skipping some important step.

Any help would be very apreciated, as with it I could use my phones and Isone Pro to listen music as it should sound, as I do with my windows and linux PC.

Thanks!


RoKK
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 12 January, 2011, 03:18:24 AM
Is there anything like this to check the version?

(https://hydrogenaud.io/imgcache.php?id=549bb787f3626a31f31e09d6b8f2569a" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/Vd29cdPxJCmrq8r-msvcr90dll.png) (http://images.devs-on.net/Image/Vd29cdPxJCmrq8r-msvcr90dll.png)

I have Ubuntu installed in VirtualBox. I'll try it there but, speaking frankly, I don't know much about other systems, so you may have to wait.


UPD: Fixed.
Title: foo_vst: VST 2.4 adapter
Post by: foofun on 12 January, 2011, 04:20:44 AM
In ubuntu work after install vcrun2008 with winetricks.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 12 January, 2011, 07:31:20 AM
Ok, I have worked this out.  From now on, it'll run on both Windows and Wine without vcredist requirment.

(https://hydrogenaud.io/imgcache.php?id=c473ffd03e044673e781eb4bda594eb1" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/YmQo8SSOPkZlYjS-screenshotpng.png) (http://images.devs-on.net/Image/YmQo8SSOPkZlYjS-screenshotpng.png)

As with the previous bugfix, I'll leave this one for the next release. Feel free to PM if you need the new version now.
Title: foo_vst: VST 2.4 adapter
Post by: mudlord on 13 January, 2011, 03:14:57 AM
Is there any way to adjust the latency for the VST adapter?
Just trying this out with Antares Auto-Tune Evo..and there is quite some delay for some tracks.
Maybe thats just due to the Auto-Tune being so intensive...not sure.

EDIT: NVM, was told elsewhere FB2K's architecture is not designed for such use.
Title: foo_vst: VST 2.4 adapter
Post by: rokk on 13 January, 2011, 04:26:45 PM
Ok, I have worked this out.  From now on, it'll run on both Windows and Wine without vcredist requirment.

(https://hydrogenaud.io/imgcache.php?id=c473ffd03e044673e781eb4bda594eb1" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/YmQo8SSOPkZlYjS-screenshotpng.png) (http://images.devs-on.net/Image/YmQo8SSOPkZlYjS-screenshotpng.png)

As with the previous bugfix, I'll leave this one for the next release. Feel free to PM if you need the new version now.


Thank you so much both to you and to foofun! I can't wait to try it at home!

Cheers
Title: foo_vst: VST 2.4 adapter
Post by: tarsier on 18 January, 2011, 06:53:38 PM
Excellent plugin, I love it!

I'm having a problem with Isone Pro Surround, which is a 6 in/2 out plugin. (looks like it is no longer available. Just the updated stereo version at http://www.toneboosters.com/ (http://www.toneboosters.com/) ) When I switch to a stereo file after playing a 5.1 file, there is stuttering playback. It sounds like the last little bit of the 5.1 file is being constantly repeated after switching to a stereo file.

Steps to reproduce:
Have a stereo file and a 5.1 file in a playlist
Have Isone Pro Surround VST plugin enabled through this VST adapter
Play the 5.1 file and verify that it is playing back correctly with no audio stuttering
While the 5.1 file is playing, double click on the stereo file in your playlist to start it playing back

Results:
The stereo file will play, along with a repeating, stuttering bit of the 5.1 file.

I've tried this on two systems, one on Win7 64 bit and DS playback. The other on XP 32 bit and ASIO playback. Similar results on both machines.

If I insert channel mixer and convert everything to 6 channels before Isone Pro Surround, there is no stuttering.

Please let me know if you need more info to help resolve this stuttering problem.

Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: Hancoque on 18 January, 2011, 08:38:40 PM
Well, if the VST plug-in expects six channels and you feed it only two channels, problems are to be expected. I also use Isone Pro Surround but it never came to my mind to use it with only two channels. I used Channel Mixer right from the start.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 19 January, 2011, 02:47:29 AM
Generally, yes, it's as Hancoque said. But I'll improve internal upmixing. I think it won't be difficult. Thanks for the report.
Title: foo_vst: VST 2.4 adapter
Post by: tarsier on 19 January, 2011, 09:50:37 AM
Well, if the VST plug-in expects six channels and you feed it only two channels, problems are to be expected. I also use Isone Pro Surround but it never came to my mind to use it with only two channels.

It works without problems in all my other two-channel scenarios--including Foobar2000 when I feed it two channels to start with. Its just when I go from a 6 channel file down to a 2 channel file where the problem occurs.

But thanks to Entrase for looking into this, and I've just got to say thanks again for making this plugin.
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 21 January, 2011, 05:54:22 PM
I'm a little late with my update but I think I got similar problem to what tarsier reported maybe.

"Output number limit" is set to 6

I start 16ch bidule with some upmixer - result distortion, statics...

Lets take some other VST - 6ch DTS Neural UpMix VST - at first seems fine, it outputs 7ch instead 6ch and I guess that's because 7th pin in this VST is not a channel but it's pin says "Latency in samples". However it sounds fine. But when I put Channel mixer DSP distortion comes again and even more take a look at this picture:



Even another VST - Voxengo Elephant 8in/8out: Channel mixer after this VST doesn't have effect. OTOH Channel mixer (set to 4ch) before this VST outputs 6ch instead 4ch, where front L/R seem fine, and then sL/sR are outputted on 3rd and 4th and same channels again on 5th and 6th channel

I guess this sounds confusing, but that's what I see happening. I tried to get back on good old 0.5 version (as it's only backup I have) then foobar complains:

Quote
Sorry: You have an outdated beta version of dsp_vst component. Loading will be refused.


PS Maybe it is not such bad idea to offer link to previous component version when it's development is that dynamic. As with drag&drop installation I doubt anyone is making any backup copy before installing

[edit] corrected before and after
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 22 January, 2011, 03:21:53 AM
First set declicker size to zero. The distortion should disappear. I work on getting Bidule working with the declicker.
Quote
Exit foobar, start again with Neural UpMix. Plays fine, then I add Channel mixer DSP (which is set to up/down mix to 4ch) and now I get 1ch output
Does that Neural UpMix work fine alone? How many channels does it have on the output?
Quote
Voxengo Elephant 8in/8out: Channel mixer after this VST doesn't have effect
I've tried the Voxengo Span (which is 8/8 too) and everything seems fine.
Quote
good old 0.5
I wouldn't say so :) Btw, there were no changes in the channel limitation logic. Besides, I didn't keep source codes of versions below 0.7 as I just scratched the surface without organizing the work. So there will be no v0.5 that is enabled to operate after 01/01/2011.

There will be per-instance channel limitation in the next version:
(https://hydrogenaud.io/imgcache.php?id=ad7ae79248e5c46f2b8d5a85e6a1c8fa" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/yr5D7Nq4OI2yP93-MDynamics.png)

May be it'll help :)
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 22 January, 2011, 12:06:20 PM
Hello,
I've just installed this plugin and loaded Voxengo SPAN (volume and frequency metering). When I load it, memory usage of foobar increases from 13MB to 30MB (after loading GUI to 80MB!). It's not a big problem. The main issue is very slow responding of plugin's GUI. CPU usage of foobar is around 1-2% (and whole system around 3%). It is vst plugin case or vst host? Maybe could it be solved?

PROBLEM SOLVED: I had to delete Strip Silence plugin. In any place in chain (pre or post) it was slowing down vst GUI.

But there is another problem. I assigned shortcut to DSP Config #1. It works great only at first use. When I close plugin window (Voxengo SPAN) and use shortcut again, I hear sound (so plugin chain have to work), but plugin looks like it's not receiving signal. When I use View/DSP/PluginName it works great, so I think it's problem of loading plugin by keyboard shortcut. I tried a few shortcuts to make sure that it's issue of loading by shortcut.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 22 January, 2011, 12:34:24 PM
Memory and CPU usage is up to the VST plug-in.
Quote
I assigned shortcut to DSP Config #1. It works great only at first use.
Yes, I was already told about this bug. It'll be fixed in the next version.
Title: foo_vst: VST 2.4 adapter
Post by: klonuo on 22 January, 2011, 07:59:58 PM
Hm, don't know how to explain this, but now everything is fine. In the meantime my PC was restarted (yeah, sounds lame, but hey

[a href="http://i54.tinypic.com/xq9xt5.png" target="_blank"]

Quote
There will be per-instance channel limitation in the next version:

nice idea, thanks
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 22 January, 2011, 08:19:30 PM
Might be good improvement to add shortcut Escape key to close plugin window and then (other improvement) vsthost will switch window to last focused window of all foobar/plugins windows.

By the way, great plugin!
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 23 January, 2011, 05:04:17 PM
(sorry can't edit post)
And other improvement, to remember position of plugin windows. Now plugin window is opened in fixed position depending on foobar window position.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 January, 2011, 12:24:15 AM
I'll add Esc support to VST plug-in windows but suggestion of remembering positions is impossible to implement due to FB2K API limitations (DSP components create and handle their config dialogs themselves and there is no external control over them).
Title: foo_vst: VST 2.4 adapter
Post by: Sylph on 26 January, 2011, 11:04:29 AM
I have tried to load iZotope Ozone 4 and it failed to load: The file doesn't appear to be VST DLL (no entry procedure).
Title: foo_vst: VST 2.4 adapter
Post by: Sylph on 26 January, 2011, 11:23:02 AM
It's also quite messy with Spectralive: with Yohng's one you could choose which preset to load from a dropdown menu, here not and it – turns off one whole headphone and sends bizarre, pulsating signals through it!    It works at first, but when you switch to a different song, it goes bust.
Title: foo_vst: VST 2.4 adapter
Post by: Hancoque on 26 January, 2011, 12:34:42 PM
I have tried to load iZotope Ozone 4 and it failed to load: The file doesn't appear to be VST DLL (no entry procedure).

You are probably loading the wrong file ('iZOzone4.dll'). You must load 'iZotope Ozone 4.dll'.
Title: foo_vst: VST 2.4 adapter
Post by: Sylph on 26 January, 2011, 03:55:59 PM
I did, precisely that one. And it made foobar crash.
Title: foo_vst: VST 2.4 adapter
Post by: foofun on 30 January, 2011, 08:38:46 AM
Congratulations Entrase,

1000 downloads!
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 January, 2011, 09:56:22 AM
Thanks  Unfortunately, I'm too busy at the moment to work on the adapter. A few more weeks I guess.
Quote
It works at first, but when you switch to a different song, it goes bust.
Try setting Delicker size to 0 in the advanced preferences section.
Title: foo_vst: VST 2.4 adapter
Post by: musicreo on 30 January, 2011, 02:01:52 PM
Thanks for this  plugin.

Is it possible to modify the plugin to support 7.1 output ? 

That would be great.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 January, 2011, 02:24:36 PM
Preferences → Advanced → VST → Output ... = 8. Keep in mind that VST must support 7.1 output as well.
Title: foo_vst: VST 2.4 adapter
Post by: Sylph on 30 January, 2011, 03:43:28 PM
Thanks  Unfortunately, I'm too busy at the moment to work on the adapter. A few more weeks I guess.
Quote
It works at first, but when you switch to a different song, it goes bust.
Try setting Delicker size to 0 in the advanced preferences section.


That worked.  Thank you.

Ozone is now saying that it "failed to load", whatever that means, and I was wondering how do I make sure the VST keeps the settings I choose after I open foobar again? As I said, Spectra doesn't offer that dropdown with presets and availability to save a new one. 
Title: foo_vst: VST 2.4 adapter
Post by: musicreo on 30 January, 2011, 06:07:48 PM
Preferences ? Advanced ? VST ? Output ... = 8. Keep in mind that VST must support 7.1 output as well.


Do you mean "Limit number of outputs for VST-Effects"?

When I change the number to 8 and use a 7.1 VST-Effect the error Unsupported stream format: 48000 Hz / 24-bit / 8 channels appears.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 31 January, 2011, 05:42:10 AM
Quote
how do I make sure the VST keeps the settings I choose after I open foobar again?
VST settings are saved when you close editor window. I'm going to add preset manager as soon as some major bugs are fixed.
Quote
When I change the number to 8 and use a 7.1 VST-Effect the error Unsupported stream format: 48000 Hz / 24-bit / 8 channels appears.
This is what output service says, not the adapter. Your sound card (or its particular configuration) doesn't seem to be capable of streaming 8 channel audio. Have you ever played back 7.1 audio without DSPs on your PC?
Title: foo_vst: VST 2.4 adapter
Post by: musicreo on 31 January, 2011, 10:18:29 AM
Quote
how do I make sure the VST keeps the settings I choose after I open foobar again?
VST settings are saved when you close editor window. I'm going to add preset manager as soon as some major bugs are fixed.
Quote
When I change the number to 8 and use a 7.1 VST-Effect the error Unsupported stream format: 48000 Hz / 24-bit / 8 channels appears.
This is what output service says, not the adapter. Your sound card (or its particular configuration) doesn't seem to be capable of streaming 8 channel audio. Have you ever played back 7.1 audio without DSPs on your PC?


No it works.
The problem was the WASAPI output. With direct sound and KernelStreaming I can use  VST-effects with 8ch ouptput.  But I don't understand why WASAPI don't work. With a 7.1 wave-file  or  7.1 upmix with MatrixMixer  WASAPI have no problems.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 31 January, 2011, 10:28:31 AM
The only problem that comes to my mind is speaker configuration inconsistencies. Most VSTs doesn't provide information on pin assignments, so I didn't even bother implementing any queries. What VST do you use?

Also, could you please compare channel configs in the two cases, i.e. with the MatrixMixer and with the VST? Use Foobar's null output to make VST start processing. I need to know resulting channel configs in both cases.

(https://hydrogenaud.io/imgcache.php?id=a25179c99d5e4bb2be2aef3895c7eaf1" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/JiSzwrCZ9frf1ty-VUMeter.png)
Title: foo_vst: VST 2.4 adapter
Post by: musicreo on 31 January, 2011, 01:09:10 PM
The only problem that comes to my mind is speaker configuration inconsistencies. Most VSTs doesn't provide information on pin assignments, so I didn't even bother implementing any queries. What VST do you use?

Also, could you please compare channel configs in the two cases, i.e. with the MatrixMixer and with the VST? Use Foobar's null output to make VST start processing. I need to know resulting channel configs in both cases.

(https://hydrogenaud.io/imgcache.php?id=a25179c99d5e4bb2be2aef3895c7eaf1" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/JiSzwrCZ9frf1ty-VUMeter.png)


You're rigth it is the channel configuration:

The VST is  dts neural upmix 2.0 to 7.1.

Channel configuration with  dts neural upmix 2.0 to 7.1

FL,FR,FC,LFE,RL,RR,FCL,FCR.  This works with kernel streaming and direct sound.


Matrix Mixer:

FL,FR,FC,LFE,RL,RR,Sl,SR      This works with kernel streaming, direct sound and WASAPI.

I have tested the vst with matrix Mixer  and set the FCL, FCR to SL, SR. This works with WASAPI. 






Title: foo_vst: VST 2.4 adapter
Post by: thuan on 02 February, 2011, 10:53:29 PM
FYI, VNoPhone (http://vellocet.com/software/VNoPhones.html) crashed foobar2000 outright when I tried to add it. If it's too old and you don't wanna check, that's fine. I was just trying to find some new crossfeed VST.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 03 February, 2011, 01:34:46 AM
I guess it's just not VST 2.4. I'll look into it though. Thanks.

UPD: It's VST 1.0. I'm not sure if it's worth bothering to make it work. It'd be intersting though. May be I'll try later.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 04 February, 2011, 02:36:36 AM
(https://hydrogenaud.io/imgcache.php?id=73b405cc6f1f303f80d9724a90b68709" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/HONQTFs1lOU7j3D-ElectriQposihfop.png)

:-)
Title: foo_vst: VST 2.4 adapter
Post by: foofun on 04 February, 2011, 02:59:34 AM
Excellent!
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 05 February, 2011, 02:08:25 PM
(https://hydrogenaud.io/imgcache.php?id=73b405cc6f1f303f80d9724a90b68709" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Image/HONQTFs1lOU7j3D-ElectriQposihfop.png)

:-)


Coming soon?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 05 February, 2011, 02:58:59 PM
Yep. I hope so at least
Title: foo_vst: VST 2.4 adapter
Post by: cynric on 07 February, 2011, 11:40:35 AM
Wow, this is one pretty neat VST implementation! I really like the ability of adding multiple instances of DSPs with it.
So far it works great with the majority of my plugins, however I do get some errors with these two (both freeware):

Sonogram SG-1 (http://ag-works.net/plugins.sg1.htm): This one is a real time sonogram, it doesn't actually alter the sound. Foobar crashes when trying to add the VST. George Yohng's wrapper also crashes on startup when this plugin is present in the VST directory. However it does work when added through the EffectChainer (http://www.acondigital.com/us_Downloads.html) VST.

dBlue Glitch (http://illformed.org/plugins/glitch/): A pretty sophisticated Glitcher/Sequencer. Can be added as should, but crashes foobar, once playback starts with this plugin in the chain. Works fine in George Yohng's wrapper, can be loaded and configured when used in the EffectChainer, but does actually change the sound then.

It would be great, if you could have a quick look into these plugins, maybe there is a simple fix for their behaviour. Also it would nice if the user could add mutliple effects at once or have the plugin scan for VSTs inside a specified directory and its subdirs...

Thanks!
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 07 February, 2011, 12:10:02 PM
Quote
Sonogram SG-1 <...> Foobar crashes when trying to add the VST.
Works fine in v0.9 which is coming soon.
Quote
dBlue Glitch: A pretty sophisticated Glitcher/Sequencer. Can be added as should, but crashes foobar, once playback starts with this plugin in the chain.
Confirmed. I'll have a look.
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 08 February, 2011, 05:57:34 PM
Hello,
I changed my OS to Win7 64bit and now I have some problems with Voxengo SPAN. 32bit version of plugin attenuates signal by a fairly large amount, 64bit version can't be loaded in component section. I think they work properly in other hosts, so it is yours plugin issue. Maybe you'll find solution, I hope  There's also another strange thing, when I added freeverb (or sth like that) after SPAN, it was playing ok, but pre SPAN it was attenuated. I also have Convert mono to stereo in chain, but it changes nothing in level (irrespective of position in chain). SPAN has standard stereo routing.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 09 February, 2011, 12:31:53 AM
The adapter itself doesn't change anything in the audio except for the number of channels. I guess you just missed that actually Voxengo plug-ins have more than two outputs and so when downmixing to stereo occurs (somewhere at fb2k output or another DSP service) you get that attenuation. As for other hosts, they can manage the routing themself as they always know how many channels they need. But it's not the case here at all as there is no way to find out if particular VST out pin is active. It's all about multichannel audio support.

In the next version there will be per-instance channel number limitation so it'll be easier to handle such cases as yours. Right now all you can do is to set channel number limit to 2 in the Advanced preferences section or use a Channel Mixer to downmix to stereo.
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 09 February, 2011, 05:35:20 AM
Changing value helped, but previously it was working without it. Anyway thank you
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 09 February, 2011, 05:38:43 AM
I didn't change anything that concerns audio channels. You probably had a 2-output plug-in after the SPAN before, which served the same purpose as the channel number limitation feature ;-)
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 10 February, 2011, 04:21:01 AM
I just started using your VST wrapper, and I must say I'm quite impressed, Entrase. Quite a good job at handling Ozone 4, which seemed to be a problematic VST on older wrapper builds. So far it has handled everything I threw at it like a champ    It's quite nice having direct access to the VST windows as well as any DSPs in the chain.

I've been using Yhong's wrapper for quite some time, specially since the alternatives were quite buggy. Have been using your solution for a few hours and if it continues performing like it is, I won't be returning to Yhong's solution again.

About the 20 VSTs limitation, perhaps users can use a chainer until you increase the total number of VSTs. Haven't tried Acon Effect Chainer yet, but could be a nice solution, as from there the amount of cpu cycles would be the limit.

Congrats on a great job, I hope you improve it even further, and I wish you the best
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 10 February, 2011, 10:01:19 AM
Thank you. Working hard on it.

As for the maximum number of VST entries, I can increase it anytime but I don't see the point. In short, it's not worth it.

More detailed explanation is like this. If one needs more than 20 DSP plug-ins in a player then probably a different tool should be used. I wouldn't introduce the limitation at all and would even make some folder scanning feature as found on Big Hosts, but Foobar2000's API doesn't have an ability to re-use a code for multiple esentially the same DSP services in a one component. I had to abuse a programming language feature to make it possible for one component to provide multiple DSP entries. Basically, the compiler does some copy-paste job for me (c++ templates). So not only will DLL file grow in size, but also compilation and linking times will increase. Of course I could set different limits for internal debug builds and for release builds. But then I would have to support multiple config files or make the component keep entries in memory. That all stuff would be error-prone. The bottom line is, yes, it's not worth it. Feel free to prove the opposite though.
Quote
About the 20 VSTs limitation, perhaps users can use a chainer until you increase the total number of VSTs. Haven't tried Acon Effect Chainer yet, but could be a nice solution, as from there the amount of cpu cycles would be the limit.
I hope you don't mind a little comment. Don't mix up VST entries with their instances. One can still have 100 or, say, 200 Ozones in Foobar's DSP chain, but only 20 different VST plug-ins (not their instances) may be added.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 10 February, 2011, 04:02:03 PM
It's not really a priority for me, as I use just a few VSTs. What I was saying is that inside a single VST chainer, there could be 10 or 20 VSTs loaded inside the chainer, and the wrapper would only consider a single VST as being loaded. I don't think it's that bad of an idea, specially as it would make things cleaner for your wrapper, and the chainer is freeware

Right now I only have 3 VSTs loaded so it's not an issue, and having 20 or more VSTs is not something I'm looking for at this time.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 11 February, 2011, 09:52:35 AM
0.9.0.2 (preview) (http://www.hydrogenaudio.org/forums/index.php?act=attach&type=post&id=6358)
Title: foo_vst: VST 2.4 adapter
Post by: tarsier on 11 February, 2011, 01:20:07 PM
This component is shaping up nicely.

Since it is so great, I wanted to try running a reverb VST on a stereo track and have the reverb come out the rear channels. I tried matrix mixer to upconvert to 4 channels and duplicating the track, but when I run the 2 channel VST, foobar will always output 2 channels.

In a multichannel scenario, it would be nice to be able to run a VST on selected channels and maintain the multichannel configuration.

Or when running a 2/2 VST in a multichannel scenario, have the option to maintain the number of channels but just run the VST on the 1st two channels. I could then use matrix mixer to swap channels around to where I want them.

Thanks for your work on this!
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 11 February, 2011, 01:25:17 PM
Yes, sure, it must be made like this. Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 11 February, 2011, 02:30:08 PM
Do you have a changelog somewhere, Entrase?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 11 February, 2011, 02:31:45 PM
There is brief one in the wiki (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components/VST_adapter).
Title: foo_vst: VST 2.4 adapter
Post by: tarsier on 11 February, 2011, 06:14:00 PM
The UI for Toneboosters Isone: http://www.toneboosters.com/tb-isone/ (http://www.toneboosters.com/tb-isone/) isn't displaying in 0.9.0.2.  All my other VSTs including the old JB Isone are showing up fine.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 11 February, 2011, 07:03:43 PM
My bad. I've been on the wiki and didn't remember.

How stable is 0.9.0.2? 0.8.1.0 is performing quite well, so I might wait for a stable release.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 12 February, 2011, 02:15:16 AM
I think if you don't need features of the new version then it's better for you to wait for a final release.

The UI for Toneboosters Isone: http://www.toneboosters.com/tb-isone/ (http://www.toneboosters.com/tb-isone/) isn't displaying in 0.9.0.2.  All my other VSTs including the old JB Isone are showing up fine.
Well, it works fine for me:
(https://hydrogenaud.io/imgcache.php?id=51383c6fa99f7f6da8c76f7aebbcc6de" rel="cached" data-warn="External image, click to view at original size" data-url="http://images.devs-on.net/Thumb/PUNpx7Cn2GuG4vq-TBIsone.png) (http://images.devs-on.net/Image/PUNpx7Cn2GuG4vq-TBIsone.png)

Could you try any other host just to make sure this plug-in works, please?
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 12 February, 2011, 03:21:55 AM
Well, presets and support for conversion and playback with matched DSP chain presets is nice. But I'll just run things without too much changes and that won't affect me much, for now.
Title: foo_vst: VST 2.4 adapter
Post by: romor on 12 February, 2011, 04:36:42 AM
VST window is not closed when user removes VST from DSP manager

PS I don't know if this is mentioned, thread is rather long
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 12 February, 2011, 04:53:37 AM
It will not I think. There are some technical difficulties which prevent this bug from being fixed. Don't use it this way please.
Title: foo_vst: VST 2.4 adapter
Post by: tarsier on 12 February, 2011, 06:04:06 PM
Quote from: Entrase link=msg=0 date=
Well, it works fine for me:

I just installed the newest tb_Isone 1.5 and it's working. Perhaps it was something odd in my machine, sorry for the false alarm.
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 14 February, 2011, 06:41:42 PM
Hello, I checked 0.9 version and it's not running. Foobar says that some component is damaged. I know it's preview version, but..
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 15 February, 2011, 01:31:04 AM
Did v0.8.0.1 work there before? Or is it clean installation of Foobar2000? Which operating system is that?
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 15 February, 2011, 05:54:03 AM
8.0.1 works. It's not fresh instalation. My OS is Win7 64bit.
Title: foo_vst: VST 2.4 adapter
Post by: tomten on 23 February, 2011, 12:50:50 PM
Amazing!

Bug(?): When I try to configure "George Yohng's W1 Limiter" (the VST that comes with his VST wrapper), I get "This feature isn't implemented for no-GUI plug-ins yet. Sorry." (both 0.8.x and 0.9.0.2). (Same via "configure selected" and "View -> VST -> ...".) It's a GUI plug-in, because using his VST wrapper, it's configurable.

(if someone can recommend an alternative simple limiter/compressor, either vst or dsp...)
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 February, 2011, 01:03:48 PM
Quote
Amazing!
Thanks!

Quote
It's a GUI plug-in, because using his VST wrapper, it's configurable.
In VST, being configurable has nothing to do with having custom GUI. Try a different host and you'll see different appearance of what you take as plug-in's GUI.

(https://hydrogenaud.io/imgcache.php?id=e1bf2088ab56658c3c771bbfafb7f3ab" rel="cached" data-warn="External image, click to view at original size" data-url="http://img832.imageshack.us/img832/9514/clipboard13517283.png)
Title: foo_vst: VST 2.4 adapter
Post by: tomten on 23 February, 2011, 01:43:15 PM
Quote
(Yohng W1 Limiter is) a GUI plug-in, because using his VST wrapper, it's configurable.
In VST, being configurable has nothing to do with having custom GUI. Try a different host and you'll see different appearance of what you take as plug-in's GUI.
Is there an ETA for that feature? Or is there some other way to make it work? Manually entering the values somewhere?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 February, 2011, 02:36:21 PM
Yes, the feature is essential to any VST host and it'll be implemented by 1.0 release. The only way to get it configurable is to use with a VST chainer. Ironically, this is what users were to get rid of in this adapter. And technically, you can edit something manually, but that involves HEX editing and other black magic.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 24 February, 2011, 09:10:40 AM
foobar 1.1.4 disabled foo_vst when installing. Though while 0.8.0.1 was disabled and deleted on install, 0.9.0.2 does work 

...still waiting for an updated midi plugin as well as that was deleted too...
Title: foo_vst: VST 2.4 adapter
Post by: thuan on 24 February, 2011, 10:53:46 AM
? foo_vst 0.8.0.1 is still kicking here after the 1.1.3 and 1.1.4 upgrades. Might be there's something else is wrong with your configuration.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 24 February, 2011, 10:55:42 AM
There's nothing wrong with my config. During the install of 1.1.4 (from a 1.1.2 install) I get a notification that two components are going to be disabled for not being compatible.

If you check the official components list, there are already components being rewritten to be compatible with 1.1.3 and above.
Title: foo_vst: VST 2.4 adapter
Post by: ExUser on 24 February, 2011, 01:28:19 PM
If you check the official components list, there are already components being rewritten to be compatible with 1.1.3 and above.
Just because an official component was modified for a new version does not imply that any other components need alteration. Official components can occasionally use undocumented APIs and various other things. While I don't know for certain, the fact that thuan has no difficulty makes me suspect your configuration rather than a change in foobar2000.

You should buy yourself one of those jump-to-conclusions mats. They have all these different conclusions you can jump to. Maybe that'll help with your burning desire to do so here on the forums.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 24 February, 2011, 04:24:11 PM
Since I said on a previous post that I intended on using the latest stable foo_vst, I'm merely stating what happened with my situation.

If advising for the good of others is frowned upon, don't worry, that won't happen again.

Whatever makes your day shine brighter...
Title: foo_vst: VST 2.4 adapter
Post by: GeSomeone on 25 February, 2011, 06:00:21 AM
? foo_vst 0.8.0.1 is still kicking here after the 1.1.3 and 1.1.4 upgrades.

same here. tribaljet don't play the offended role, there must be something else going on. Why don't you try and add those 2 plugins again?
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 25 February, 2011, 08:04:27 AM
? foo_vst 0.8.0.1 is still kicking here after the 1.1.3 and 1.1.4 upgrades.

same here. tribaljet don't play the offended role, there must be something else going on. Why don't you try and add those 2 plugins again?


I already added the new version of foo_vst, and will wait for an updated version of foo_midi.
Title: foo_vst: VST 2.4 adapter
Post by: Case on 25 February, 2011, 12:28:37 PM
You can just reinstall current version of foo_midi. Installer removed it most likely because you had all the supporting dlls extracted into the components directory where they couldn't be loaded from. Either use the new per-user component installation method or manually move bass.dll and bassmidi.dll into the foobar2000 installation directory.
Title: foo_vst: VST 2.4 adapter
Post by: Yirkha on 25 February, 2011, 01:09:30 PM
Entrase, if you get p_api as NULL in foobar2000_get_interface(), don't do anything and just return the foobar2000_client_impl which can report interface version. The installed does this to check for outdated components, foo_vst currently crashes on the NULL pointer and thus gets deleted.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 25 February, 2011, 01:23:25 PM
Oh! Thanks a lot! There really is a custom foobar2000_get_interface() and I'll fix it. Thanks again.
Title: foo_vst: VST 2.4 adapter
Post by: franky0182 on 28 February, 2011, 01:52:26 AM
Great work! Entrase. It's a nice VST host plugin.

Here may i know where to store the plugin information? I try to download the reg cleaner you attached.But it seems not there any more.

I try to zip foobar working folder to copy whole components instead of installing foobar and other components every time. But if this, foobar can't keep VST plugin configuartion every launch and i need to configure it again. Any suggestion?

Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 28 February, 2011, 02:02:08 AM
You can just reinstall current version of foo_midi. Installer removed it most likely because you had all the supporting dlls extracted into the components directory where they couldn't be loaded from. Either use the new per-user component installation method or manually move bass.dll and bassmidi.dll into the foobar2000 installation directory.


Thanks, Case, moving bass.dll and bassmidi.dll to the main install folder did fix things. Now after updating from 1.1.4 to 1.1.5 there is no longer an issue with foo_midi. On the other hand, foo_vst was once again removed (0.9.0.2), forcing me to copy it again. Would be nice if this didn't happen on future versions.

On a non related note, does anyone know why foobar does some sort of check of all files in the previous install folder? This is only happening since 1.1.3, and I would just like to understand how relevant it is.
Title: foo_vst: VST 2.4 adapter
Post by: tomten on 28 February, 2011, 02:31:30 AM
Here may i know where to store the plugin information?
You mean the stuff in %AppData%\foobar2000\ ?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 28 February, 2011, 11:13:45 AM
The adapter uses the Foobar's profile folder to store the file named vst_entries.bin. In a default standard installation it's in AppData as tomten said. In a portable installation you get everything in one folder in any case. Franky, I guess you're trying to zip normal installation with manually added components. Generally, this is a wrong way. If this is the case then I'd recomment you to use portable installations instead.
Title: foo_vst: VST 2.4 adapter
Post by: franky0182 on 02 March, 2011, 03:02:55 AM
Entrase,

You are right. I should use portable installation instead of standard installation.

Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 04 March, 2011, 10:27:03 PM
Here is version 0.9.0.3. It should not be removed on updates anymore. Please tell me if so.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 04 March, 2011, 10:34:35 PM
Thanks Entrase, as soon as as new foobar version is released, will test and report.
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 08 March, 2011, 06:36:48 AM
Hello Yegor,
I installed 0.9.3 version and it seems to working better, but you said that you'll implement Esc shortcut to close plugin window. Did you do it? It doesn't work on mine computer.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 08 March, 2011, 06:50:52 AM
No, I haven't implemented it yet. I decided not to bother because I need to rewrite the whole plug-in GUI stuff from scratch anyway. So don't worry, I didn't forget.

Actually, 0.9.0.3 wasn't planned at all. It's just to fix that update removal bug. And I'm way too busy these weeks to work on the adapter.
Title: foo_vst: VST 2.4 adapter
Post by: foofun on 08 March, 2011, 07:46:55 AM
An idea for GUI (control button) ...
instead of: (https://hydrogenaud.io/imgcache.php?id=9d97fb172b4cee6d63226646ee7a56e0" rel="cached" data-warn="External image, click to view at original size" data-url="http://img576.imageshack.us/img576/7223/screenshotrjg.png) this (https://hydrogenaud.io/imgcache.php?id=205ff9de201fd1e8594ea734f3348450" rel="cached" data-warn="External image, click to view at original size" data-url="http://img571.imageshack.us/img571/7980/85341007.png)
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 08 March, 2011, 08:02:42 AM
This is how it looked initially  The problem here is that user can't get help message. I know that current solution is weird (especially in Wine) but it is to be changed to something different with introduction of new multichannel support modes (see below). Perhaps there will be a simple button to access a dialog box with different settings.

I'm planning to introduce more flexibility into multichannel config support. One will be able to not only limit the number of channels but also to process surround audio with (for example) stereo plug-ins by means of synchronized instances. It sounds a little bit complicated, I know, but if everything is fine then it'll be transparent to the user.
Title: foo_vst: VST 2.4 adapter
Post by: foofun on 08 March, 2011, 08:24:33 AM
I hope your work will be rewarded with success. Thanks for the reply.
Title: foo_vst: VST 2.4 adapter
Post by: bsw11 on 09 March, 2011, 11:47:52 AM
OK So I am trying out OZ4 right now and have a couple question for you

When I go to play 6 ch tracks, if OZ4 is in the chain I only get 2 channels.
  Note I also have to switch to use the ASIO output due to my HDMI/ASUS setup.  As soon as I pull OZ4 out of the DSP chain I get all 6 chs. 

1 - any way to fix this?

2 - any way to be able to process all 6ch with OZ4?
Title: foo_vst: VST 2.4 adapter
Post by: bsw11 on 09 March, 2011, 01:42:26 PM
One other question - I used to use Ozone MP which had the ability to assign different presets to different tracks - anything like that doable in the VST wrapper?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 09 March, 2011, 02:24:18 PM
Quote
any way to be able to process all 6ch with OZ4?
I'm going to make it possible in the next major release (see my previous post).
Quote
ability to assign different presets to different tracks
Nope. I think it should be the task for a whole different component with a purpose of DSP chain management.
Title: foo_vst: VST 2.4 adapter
Post by: bsw11 on 10 March, 2011, 03:48:51 AM
Quote
any way to be able to process all 6ch with OZ4?
I'm going to make it possible in the next major release (see my previous post).
Quote
ability to assign different presets to different tracks
Nope. I think it should be the task for a whole different component with a purpose of DSP chain management.



Sounds good!  From what I can tell so far you have done a great job on this.

Any eta on that version?  If its going to be awhile, maybe you could slap in the logic to just turn itself off if the channels are > 2 instead of forcing the output down to 2 channels as it does now.

I agree a separate component  might be OK - the only hard part would be to find a way to "tell" the plugin what to load -unless that communication is built into OZ4 - not that familiar with the interface or product.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 10 March, 2011, 04:00:17 AM
Mmm, not sure it's worth implementing now. Just wait a week or two please, ok?
Title: foo_vst: VST 2.4 adapter
Post by: bsw11 on 10 March, 2011, 11:52:24 AM
Mmm, not sure it's worth implementing now. Just wait a week or two please, ok?


No problem - be happy to wait, just was not sure if you were talking months :-).
Title: foo_vst: VST 2.4 adapter
Post by: bsw11 on 10 March, 2011, 10:54:18 PM
I noticed one item you might want to address:

If you have the DSP plugin window open and you go and remove a plugin from the chain, then the plugin window stays open.

I hope this is clear.

Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 11 March, 2011, 07:41:24 AM
As clear as daylight. It's actually a FAQ (yet to be added to the FAQ though). Sorry but this will not be fixed soon. I doubt it's ever going to be fixed. Foobar2000 is not supposed to support modeless DSP config windows at all (which means you're not supposed to be able to remove the DSP when its window is open). The VST [un]loading synchronization is already a hell there and I don't want to completely screw that barely working stuff up. Sorry once again and thank you for the report.
Title: foo_vst: VST 2.4 adapter
Post by: i.12 on 11 March, 2011, 08:39:00 AM
That's a good one! Thanks!
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 11 March, 2011, 09:06:06 AM
Hi,

I have problems with plugins from Waves (I own the Renmaxx bundle and the CLA Compressors). These plugins need about 10-15 sek for loading.
In the newest version I can not configure them: "This feature isn't implemented for non-GUI plug-ins yet. Sorry."
In fact they have guis and oldr versions of the adapter could open the gui.

Cheers
Alex
Title: foo_vst: VST 2.4 adapter
Post by: i.12 on 11 March, 2011, 09:46:30 AM
Can anyone give a link for any free free vst plugins please?
Title: foo_vst: VST 2.4 adapter
Post by: i.12 on 11 March, 2011, 10:09:03 AM
Here is one (http://www.vst4free.com/free_vst.php?plugin=KarmaFX_Equalizer&id=480)
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 11 March, 2011, 11:21:54 AM
http://kvraudio.com/get.php (http://kvraudio.com/get.php)

Quote
In the newest version I can not configure them: "This feature isn't implemented for non-GUI plug-ins yet. Sorry."
In fact they have guis and oldr versions of the adapter could open the gui.
Perhaps these plug-ins report that they have no GUI. Older versions didn't take these reports into account. But may be it's not that simple. I'll try to find out. Do these plug-ins have trial version?
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 11 March, 2011, 11:28:47 AM
Hi,
yes they have, but sadly you need an iLok Dongle to use the demos........
Title: foo_vst: VST 2.4 adapter
Post by: wharfrat73 on 11 March, 2011, 11:47:11 AM
Can anyone give a link for any free free vst plugins please?


There are links from the Audacity site (http://audacity.sourceforge.net/download/plugins) at SourceForge to a bunch of free VST sites.  The links are 3/4 of the way down the page.  I wouldn't be surprised if there were more free VST plug ins on SourceForge too.
Title: foo_vst: VST 2.4 adapter
Post by: almosely on 11 March, 2011, 08:24:34 PM
I tried to add some Waves VSTs (e.g. L3 Ultramaximizer), but without success. These VSTs are using some kind of entry-shell where the actual VST has to be chosen from.

Error Message 1, when I tried the regular entry-dll (works with foo_dsp_vst.dll and foobar 0.9.5.2 or with both AND xlupex vst chainer):

"Could't instantiate a VST effect ... \WaveShell-VST 5.2.dll"

Error Message 2, when I tried the normally not working dll:

"Could not load VST DLL ... \L3.dll"

Of course, I tried YOUR plug-in with foobar 1.x (1.1.1. actually).

Any idea? But it's not urgent.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 12 March, 2011, 12:26:01 AM
Quote
sadly you need an iLok Dongle to use the demos
Way too paranoid. Could you send me your vst_entries.bin? It's in AppData/Foobar2000 if you have a standard installation.
Quote
Could't instantiate a VST effect ... \WaveShell-VST 5.2.dll
But first it says that none of Waves plug-ins could be found, right? I remember that. Does the bundle work in any other VST host? Perhaps, not. So at this stage it's Waves VST shell problem, not the adapter's. But I have to admit that at the next stage the adapter would just show you only one plug-in because of lack of VST shell api support.
Title: foo_vst: VST 2.4 adapter
Post by: almosely on 12 March, 2011, 05:16:58 AM
I could not find the requested vst_entries.bin in the specified folder. There are files like "database.fpl" or "foobar2000.cfg" and a subfolder named "playlists". I don't know if this folder belongs to foobar 0.9.x or foobar 1.x - I have installed both.

And no, the Waves plug-ins does not work with any VST host. Steinberg WaveLab 5 e.g. does not recognize the Waves VST-plug-ins. But they work just fine with foobar 0.9.x and the foo_dsp_vst.dll ... Other VSTs are working fine with your adapter.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 12 March, 2011, 05:46:37 AM
Quote
I could not find the requested vst_entries.bin in the specified folder.
It's ok since the request wasn't addressed to you anyway  And fine, may be I'm gonna get some freewares to improve the adapter's compatibility later. Apparently, you'll have to wait. It'll be much sooner if you find a trial of that old version.
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 12 March, 2011, 02:49:48 PM
Hi,

I have found the file, but don't know how to send it with PM.

Maybe I have to add, that I am not using the Waveshell, but individual Plugins (there is this little utillity shelltovst that splitts the shell into individial vsts. With the shell itself of have many problems in various hosts....
Title: foo_vst: VST 2.4 adapter
Post by: almosely on 13 March, 2011, 01:01:15 AM
So, I stumbled upon XLUTOP's Shell2VST and with this tiny tool Waves' plug-ins work like a charm with your adapter :-) No need to look any further.
Title: foo_vst: VST 2.4 adapter
Post by: Alexander Ostuni on 13 March, 2011, 05:32:37 AM
So, I stumbled upon XLUTOP's Shell2VST and with this tiny tool Waves' plug-ins work like a charm with your adapter :-) No need to look any further.


That may be good for you, but for me they don't work. I can't open the gui....

Title: foo_vst: VST 2.4 adapter
Post by: almosely on 13 March, 2011, 03:33:37 PM
So, I stumbled upon XLUTOP's Shell2VST and with this tiny tool Waves' plug-ins work like a charm with your adapter :-) No need to look any further.


That may be good for you, but for me they don't work. I can't open the gui....


Oh, I only spoke for me an my shell-version. "My personal case is closed" - that was my statement.
Title: foo_vst: VST 2.4 adapter
Post by: Alexa on 14 March, 2011, 11:12:15 AM
Hi

Is anynone else getting short "pop-ups" when the song is starting and fading is enabled?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 March, 2011, 12:15:28 PM
Which fading do you mean exactly and how long is it? Anyway, try adjusting the VST declicker size in the advanced preferences section (the reasonable range is 1 to 1000). Getting rid of clicks and pops was one of the most important goals for me.
Title: foo_vst: VST 2.4 adapter
Post by: Alexa on 14 March, 2011, 05:07:05 PM
I have enabled fade out 6000 ms (it makes really cool transitions). I adjusted the declicker to 1000 like you suggested and the click effect is less noticeable, but it's still there
Title: foo_vst: VST 2.4 adapter
Post by: Squeller on 14 March, 2011, 05:29:35 PM
Am I to stupid to find it? I do not see it in the DSP settings (Win7x64/latest fb2k). It's installed:It was a clear case of RTFM. Thanks for the plugin, well done. Now I can use that useful destroy fx as found on http://smartelectronix.com/ (http://smartelectronix.com/)

Do you have any plans to implement a settings window for vst fx without an own gui?

Can anyone give a link for any free free vst plugins please?
kvraudio.com is undoubtly the centre of the scene for years now. BTW is slsk still existing?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 14 March, 2011, 10:28:59 PM
Quote
Do you have any plans to implement a settings window for vst fx without an own gui?
Quote
Yes, the feature is essential to any VST host and it'll be implemented by 1.0 release.
Title: foo_vst: VST 2.4 adapter
Post by: artyomk3d on 23 March, 2011, 07:34:09 AM
Hi!

1st. Thank You very much for such a great tool.

2nd. Is there any chance to implement some kind of "Always on top" feature for a plugin window? As it couldn't be 'builtin' in the foobar's window, this will help a lot, especially on visualization plugins. They often become obscured by main window during songs navigation.

Best regards.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 March, 2011, 07:36:44 AM
Unfortunately, no. DSPs handle their windows themselves.
Title: foo_vst: VST 2.4 adapter
Post by: artyomk3d on 24 March, 2011, 03:35:28 AM
Unfortunately, no. DSPs handle their windows themselves.


But You somehow added "Load FXP..." and "Save FXP..." to DSP window title. So it might be possible add "Always on top" option, which will set the appropriate window "flag". Right now I can do this with external utility, but it would be great to have this feature "built-in".

Best regards.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 March, 2011, 07:49:35 AM
In this case it'll be on top of everything else, not just the main window. And it will only be aplicable to VST plug-ins.

It's easy to put an item into the window's menu, but with Foobar2000 it's somewhat difficult to get window things working right. As I said before in this thread you are not supposed to have modeless DSP config windows in Foobar2000 at all. Nevertheless, if on-top-of-everything is ok for you, then I'll add that option.
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 30 March, 2011, 02:01:40 AM
something news about version 1.0?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 March, 2011, 07:23:02 AM
Nope. I'm way too busy at the moment.
Title: foo_vst: VST 2.4 adapter
Post by: dyermaker on 04 April, 2011, 07:33:08 PM
thanks alot for this plugin yegor.. ive had some fun messing around with it

i was wondering would it be possible to embed a vst as an element in foobars ui?

id love to have a nice vst scope or parametric equalizer as part of the interface.. (one can only dream)

keep up the good work
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 07 April, 2011, 03:36:02 AM
Yes, it might be cool. But VST plug-ins don't allow to change the editor window size and it's not very easy to keep track of plug-in instances. And in most cases plug-ins GUI isn't supposed to be embeddable.
Title: foo_vst: VST 2.4 adapter
Post by: bsw11 on 09 April, 2011, 01:14:32 PM
Any ETA on the multi-channel update?

If its going to be much longer a simple tweak to just take the plugin out of the chain on multi-channel tracks would be greatly appreciated.

Thanks!
Title: foo_vst: VST 2.4 adapter
Post by: moondragon on 16 April, 2011, 03:29:43 PM
This is a great plugin, thanks. I like the way it integrates with Foobar2000 normal dsp plugins, and appears in the list for tweaking from the view menu. Pretty cool.
I'm running Win 7 with an i7 multicore processor, and got lots of ram etc. and using lots of different vst plugins, including some talked about in posts here. I don't experience any crashes so far. it runs most and is stable. Glitches only seem to occur when other programs in Windows get busy. I would recommend this above any other vst enablers around.
Title: foo_vst: VST 2.4 adapter
Post by: Mr.Duck on 23 April, 2011, 04:40:14 PM
I don't mean to nag for the v1.0 update... I just had the idea that for plugins with no GUI, could just open some cfg file for manual control adjustment. If that helps making the programming a lot easier? Then you don't need to write a GUI system with sliders etc.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 23 April, 2011, 04:55:42 PM
This is a great plugin, thanks. I like the way it integrates with Foobar2000 normal dsp plugins, and appears in the list for tweaking from the view menu. Pretty cool.
I'm running Win 7 with an i7 multicore processor, and got lots of ram etc. and using lots of different vst plugins, including some talked about in posts here. I don't experience any crashes so far. it runs most and is stable. Glitches only seem to occur when other programs in Windows get busy. I would recommend this above any other vst enablers around.


Given that not everyone has an i7 cpu or tons of ram, people have to make compromises. I'm running 4 items on my DSP chain, including a relatively heavy mastering suite, and I have zero issues whatsoever running on a core duo cpu. We are talking about a player, so tweaking buffer settings, optimal DSP ordering and avoiding the cpu to do the audio hardware resampling are all good ways to avoid any glitches.

That being said, I experienced no crashes since day one when using foo_vst, only a slightly slower foobar startup. This VST wrapper is highly recommended over all competing solutions (and I was a fan of George Yohng's wrapper).
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 April, 2011, 12:57:54 AM
Quote
only a slightly slower foobar startup
Yep, this is the way the adapter works. It keeps track of DSP stack from the very application startup as opposed to deferred loading, i.e. when the user starts playback. Either way, there is a delay before you can hear something :)

Further development of the adapter seems somewhat problematic to me because I have no time at all, you know, two jobs and two educations at once (final year both with all the headaches). And when I graduate, I'll have to go to the god damn army (it's obligatory here in Russia). That is I'll return home in summer 2012. Most likely i'll make it open source so you (yes, You, the most experienced and patient developer! :) will be able to finish the job.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 24 April, 2011, 01:03:33 AM
Well, I certainly prefer to have a preload of sorts than slowdowns during foobar's operation

Seems you're quite busy these days, but it's probably a good thing  About going to the army, it's alright when it's a voluntary thing, but being forced is a whole different matter  Is there any way you can avoid going to the army, due to studies or something?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 April, 2011, 01:17:02 AM
Many people avoid this by taking post-graduate courses or by hiding from those who is to take you there or by applying for in-university military education (which I missed for reasons I don't remember) or just by health problems (you can get fake ones for money). Unfortunately, none works for me since I'm a healthy 22 year old student with no extra money to fake anything. The upper age limit is 27 and I wouldn't like to escape for 5 years.
Title: foo_vst: VST 2.4 adapter
Post by: Nowings69 on 24 April, 2011, 03:25:13 AM
When I used your VST adapter for the first time,
I felt what a faithful man as kode54.

In the near future,FB2K should be stable like a military standard(I dont know in RU)
I hope so with your splendid cooperation.

Thank you so much and plz never drink with Hiar Spray
Title: foo_vst: VST 2.4 adapter
Post by: Mr.Duck on 24 April, 2011, 09:30:15 AM
And when I graduate, I'll have to go to the god damn army (it's obligatory here in Russia).

Wow that is bullshit. I would fail in army so bad it's not even funny (24 years old, relatively healthy I guess). I would question everything. I wouldn't sleep well at all. If I am on my feet all day I would need the next day off to recover. On my feet for 2 days and I won't be able to walk the 3rd day (only happened once in my life). When I eventually get a gun I would probably go mad like that guy in Full Metal Jacket.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 24 April, 2011, 10:03:17 AM
I really think that being forced to go to the army isn't really good politics, but it might not be as bad as you expect. Have you talked with someone who's been there recently? And some places are supposed to be better than others.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 April, 2011, 12:52:26 PM
Off-topic posting

Yes, sure. It's one of the most popular topics among young Russian people. My closest friend is there right now. He's mostly ok there because he's tough. Russian army is ruled by “dedovshchina” (“grand-dadness”?) for many years, which is a set of unwritten laws like in a jail. Those who arrived earlier are free to abuse newbies. Try to imagine what the contingent is if everyone is forced to go to the army (except criminals; but who said that everyone is proved not to be a criminal by the go-to-the-army age?).  Speaking of aforementioned Full Metal Jacket, if the movie was made in Russia, there would be not just one unlucky guy but many. Not all of them would end up self-murdered though. And those who self-murder... no, it'd be just murder. The abuse includes stupid meaningless orders, exploitation, ignorance, and so on. You can appeal to army regulations but these will be abused too to show you that “you'd better keep silent”. The common rule to survive there is to be not very smart and not very stupid, not too strong and not too weak, i.e. to be an average person.

As for some places being supposed to be better, well yeah, that's true. The problem is that you don't know and don't choose places. I hope with some education I can spend entire conscription time sitting alone behind a rocket-watching device in a deep forest :D

Guys, I'm glad you think it's all wrong but the topic is wrong for this conversation too, right? :)
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 24 April, 2011, 05:17:56 PM
My bad  I just don't think people should be forced to do it, but there should be incentives to make people who are willing to do it instead.

Again, back on topic. I do think that foo_vst is definitely the upgrade to go from the famous yhong wrapper. Quoting a past post, "it integrates VSTs in foobar the way they were meant to be"

Out of curiosity, your wrapper will be compatible with many foobar versions to come, unless there is a significant core rewrite, like it happened from 0.x to 1.0, right?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 April, 2011, 10:36:59 PM
AFAIR, there are no "hacks", so compatibility should be ok. Still, there are a couple of dirty tricks. Without them it'd be impossible to make this kind of adapter.

More detailed explanation is as follows. First, the adapter has to read its config data earlier than most components do because it needs to decide how many DSP services it needs to instantiate. That is, we have conditionally instantiated service - I didn't see this approach neither in the SDK nor in open-source components. But it must be ok as long as it done at early stage. I tried to avoid version-dependent stuff there, it's a regular non-API code.
The second and the dirtiest trick there is relying on parent window title when showing VST config dialog. It looks if the title contains "Converter" and makes a decision whether new instance of VST is necessary. It will not crash if the title is changed. It just won't work as expected and that conversion stuttering bug will appear again. The reason I do that trick is that there is not enough data to guess whether we're involved in conversion. And it's necessary to guess somehow because DSPs in foobar must provide a decoupled interface (i.e. the player will glue UI and processing routines itself). But it's not the case in VST.
Title: foo_vst: VST 2.4 adapter
Post by: pedroskova on 02 May, 2011, 06:14:53 PM
Hi all,

I can't seem to get this to show as an available VST in fbr2000 ...don't know why.  All other plugins and wrappers have worked as planned.  What am I missing? 
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 02 May, 2011, 10:34:55 PM
Quote
What am I missing?
Usage instructions (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components/VST_adapter#Usage)
Title: foo_vst: VST 2.4 adapter
Post by: pedroskova on 02 May, 2011, 11:27:42 PM
Quote
What am I missing?
Usage instructions (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components/VST_adapter#Usage)


been there, but thanks anyway
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 02 May, 2011, 11:43:08 PM
You must have misread something. You won't see any new entry in the list of DSPs until you add a VST plug-in in the VST manager (Components - VST Manager).
Title: foo_vst: VST 2.4 adapter
Post by: pedroskova on 03 May, 2011, 12:08:06 AM
Hi, yes, I can put a VST dll into components and it shows up in available DSP's --- with the exception of the VST 2.4 adapter.  It shows up under "components", but not under "Available DSP's"

I'm sure I'm having a "senior moment" with this, but what that moment (mistake) is ...I don't know.

Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 03 May, 2011, 01:07:33 AM
This adapter doesn't work the way other wrappers do. It's seamless and you won't see any additional entries in the Available DSP's list until you add something in the VST manager which can be found in the Components branch.

There will be no "Yegor Petrov's VST wrapper" or anything like that in the Available DSP's list. You add your plug-ins in the VST manager and then you get them in the list of Available DSP's with their original names.

Just pay a little bit more attention to screenshots in the wiki.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 03 May, 2011, 04:18:01 AM
This adapter doesn't work the way other wrappers do. It's seamless and you won't see any additional entries in the Available DSP's list until you add something in the VST manager which can be found in the Components branch.

There will be no "Yegor Petrov's VST wrapper" or anything like that in the Available DSP's list. You add your plug-ins in the VST manager and then you get them in the list of Available DSP's with their original names.

Just pay a little bit more attention to screenshots in the wiki.


That's the beauty of Yegor's wrapper. It makes VSTs work the way they were intended on foobar. Install the wrapper, then add VSTs through the VST plug-ins menu on the left side of the options.
Title: foo_vst: VST 2.4 adapter
Post by: pedroskova on 03 May, 2011, 10:21:58 AM
OK, it's a seamless part of fbr2k ... now I just have to figure out how to chain and assign VST instances to the proper outputs, i.e., different EQ settings for different bands in a 3/4 way crossover...uhoh 
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 03 May, 2011, 10:53:04 AM
Quote
now I just have to figure out how to chain and assign VST instances to the proper outputs, i.e., different EQ settings for different bands in a 3/4 way crossover
May be this will help: http://forum.exadevices.com/Forum/tabid/41...ts/Default.aspx (http://forum.exadevices.com/Forum/tabid/41/forumid/3/threadid/3/scope/posts/Default.aspx)
Title: foo_vst: VST 2.4 adapter
Post by: a-phile on 03 May, 2011, 01:18:22 PM
Hello guys!

First of all, I want to thank Yegor for this great plugin! The idea of fully integrated adapter is excellent, and you have done amazing work already.

But there are two things I found not to be working properly and I'm not sure what causes the problem (I'm using foobar v.1.1.5 and Blue Cat's Stereo Parametr'EQ 3)):

1 if I try to play short *.wav clips my right channel is making unusual loud noise, something similar to white noise (I uploaded clips for you) - this problem is not present if I load plugin via Yohng's VST Wrapper;

2 if I'm about to save my custom eq preset, VST plugins freeze, but foobar still continues to play.

Thanks in advance for your answer and congrats for what you have already accomplished!

Hugs N' Kisses

edit: www(dot)mediafire(dot)com/?4xmdoq2kud3s76k
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 03 May, 2011, 01:59:36 PM
I couldn't open this rar under Ubuntu and I don't want to restart for Windows but I think I know what's there. Try setting that particular instance of the EQ to Automatic channel limitation mode - select "Auto" in the upper left corner of the window. The bug is due to improper handling of mono streams. I'll fix it.

As for the second problem, I'll investigate it as soon as I can.
Title: foo_vst: VST 2.4 adapter
Post by: a-phile on 03 May, 2011, 04:59:29 PM
I couldn't open this rar under Ubuntu and I don't want to restart for Windows but I think I know what's there. Try setting that particular instance of the EQ to Automatic channel limitation mode - select "Auto" in the upper left corner of the window. The bug is due to improper handling of mono streams. I'll fix it.


Yes, you are right, in rar you will find a few mono streams!  If this kind of problem only emergeres with mono stream, it is not a big deal for me... I will create a few new stereo freqs - I need them to be able to perfect the EQ settings for testing purposes.

As for the second problem, I'll investigate it as soon as I can.


Thank you very much sir! Also, I noticed that every plugin with the option to write down values freezes right after the beginning of typing. In fact, it seems that every writing inside the adapter/plugin freezes it. I hope it's not a problem localized on my foobar...

Title: foo_vst: VST 2.4 adapter
Post by: dfkt on 05 May, 2011, 10:24:19 AM
Would it be possible to have an active VST plugin permanently displayed in the tabbed bar at the bottom of my Foobar layout (see screenshot (http://img.elektrokrishna.com/images/83210695318387014102.png))?

I tweak the EQ rather often, and instead of opening a free floating additional window, a fixed place in a tab in the main layout would be very convenient for VST plugins.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 05 May, 2011, 11:28:34 AM
I answered this question earlier. It is technically possible but I have no time atm.
Title: foo_vst: VST 2.4 adapter
Post by: a-phile on 07 May, 2011, 07:27:57 PM
Hi!

One more thing you should try to fix... ANWIDA Soft GEQ31V is an graphic EQ with 31 parameters. It seems to me that a huge number of parameters needed to be memorized is causing the problem. After restarting foobar, the last 6 bands always reset, and than you cannot even load your custom presets, not until starting playing the music again. So...

BTW, with this EQ I can write preset names without plugin getting freezed.
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 15 May, 2011, 11:53:48 AM
Hello Yegor,
When I upload first TB EZCompressor and then try to upload TB EBUCompact VST adapter report "This plug-in is already in the list."
(both from ToneBoosters). Vst adapter or plug-ins problem?.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 15 May, 2011, 12:45:54 PM
This is plug-ins problem. Every plug-in must have its own unique ID.
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 15 May, 2011, 01:20:00 PM
Thanks for the reply Yegor

I was informed by Jeroen Breebaart that the problem will be solved.
Title: foo_vst: VST 2.4 adapter
Post by: zmejce on 17 May, 2011, 08:52:37 AM
Hello,
I must say big thanks for this plugin, it does a great job,
but im dissapointed because it cant load the cheap CrySonic Cry-Q vst equalizer,
it displays "Cant load module." pages. Any help on this side please!?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 17 May, 2011, 09:46:31 AM
Although they...
Quote
strongly encourage you to download our free demo versions and test them thoroughly with your setup until satisfied.
... I don't see this particular plug-in listed in their demos. But I'll try to contact them.
Title: foo_vst: VST 2.4 adapter
Post by: gyohng on 18 May, 2011, 03:16:48 PM
Regarding plugin ID, most of other applications actually do not depend on its uniqueness and also hash plugin file name.

@Yegor: By the way, thank you for the other suggestion you posted for my adapter. I will look into it further, when time permits, and if it makes sense.

I still like to know if anybody is preferring my adapter, and whether I should develop it further.

Thanks,
George.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 18 May, 2011, 10:41:19 PM
Quote
Regarding plugin ID, most of other applications actually do not depend on its uniqueness and also hash plugin file name.
Ok, I'll make it this way. Thank you!
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 03 June, 2011, 06:04:17 AM
Yegor, thanks for this component.
Is possible to make autohide toolbar, visible only when mouse is over system menu of editor windows (mouse on the window's titlebar)? Or, maybe better visible while holding down the shift key to show toolbar, like in foobar2000 hide menu item.


(https://hydrogenaud.io/imgcache.php?id=9d26bfebd35ab7e11cc8d28735df0b84" rel="cached" data-warn="External image, click to view at original size" data-url="http://img838.imageshack.us/img838/7223/screenshotrjg.png)
which is good (in my opinion) for clean appearance:
(https://hydrogenaud.io/imgcache.php?id=645789373096c0815928bbf077a8c5c9" rel="cached" data-warn="External image, click to view at original size" data-url="http://img508.imageshack.us/img508/3671/unledwuk.png)

Edit: First screenshoot is from ubuntu but the requirement is for windows.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 03 June, 2011, 06:28:24 AM
Yes and no. I'm agree there should be an option to hide the panel, but switching it on mouse hover doesn't seem a good decision to me. I can add an advanced option for setting the default state and put a show/hide item in the system menu.

As for keyboard-driven solutions, they won't be reliable because plug-ins range from those that do nothing with keyboard to those that intercept just about every stroke.
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 03 June, 2011, 06:38:42 AM
I can add an advanced option for setting the default state and put a show/hide item in the system menu.


Wonderful. Thanks!
PS off topic: I sincerely hope that you had success with graduation paper! 
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 04 June, 2011, 10:55:51 AM
Is it possible to add bypass button in plugins window? I want also to remind about Esc shortcut for closing plugins windows
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 05 June, 2011, 01:25:42 PM
I found the first VST adapter that I couldn't get to work with your plug-in: ambio.one (http://www.weldroid.net/2010/02/ambiophonics-processor-vst-ambioone.html)
Title: foo_vst: VST 2.4 adapter
Post by: lvqcl on 05 June, 2011, 01:36:47 PM
Works here... fb2k 1.1.7, foo_vst 0.9.0.2.

Added: updated foo_vst to 0.9.0.3 and it works too.
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 05 June, 2011, 02:04:11 PM
Strange, my setup is the same. Can't get it to work.

Could not load VST DLL. You may have tried to use x64 DLL or there is an internal error in the plug-in.

C:\Program Files (x86)\audio\Vst\ambio.one.dll
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 05 June, 2011, 02:06:52 PM
It works fine for me as well. What exactly happens / doesn't happen? Ok, it might have something to do with paths, I'll check it later. Though my system is 32 bit and I may not be able to reproduce the bug (64 bit win applies some path substitutions if I am not mistaken).
Quote
Is it possible to add bypass button in plugins window?
Yep.
Quote
I sincerely hope that you had success with graduation paper!
Yeah, thanks, I successfully upheld it three days ago, so I have some free time now. Still, I need to prepare for English exams (a separate course).
Title: foo_vst: VST 2.4 adapter
Post by: Sandrine on 05 June, 2011, 02:21:50 PM
I've put it in a neutral path c:\vst but doesn't work either. Also, even stranger, I had removed the 2 VSTs I had previously installed to avoid conflicts, and now I can't add one of them back either - same error message.

Update: Now I've installed and again removed George Yohng's VST wrapper, and lo and behold, suddenly I can add all DLLs again. Scratch, scratch.
Title: foo_vst: VST 2.4 adapter
Post by: marabundo on 08 June, 2011, 12:46:36 PM
Quote
Could't instantiate a VST effect ... \WaveShell-VST 5.2.dll

But first it says that none of Waves plug-ins could be found, right? I remember that. Does the bundle work in any other VST host? Perhaps, not. So at this stage it's Waves VST shell problem, not the adapter's. But I have to admit that at the next stage the adapter would just show you only one plug-in because of lack of VST shell api support.

I have same problem (WaveShell-VST 5.0.dll+foobar 2000 v.1.1.7+foo_vst v.0.9.0.3)
Error messages:

Could't instantiate a VST effect. This can be caused by an internal error or by the copy protection system of the plug-in.
D:\Program Files\Sound Plugins\Waves\Waveshells\WaveShell-VST 5.0.dll

Could not load VST DLL. The file has no entry procedure and hence doesn't appear to be a VST plug-in. Plug-ins may consist of multiple DLLs. Please try to specify a different one.
D:\Program Files\Sound Plugins\Waves\Plug-Ins\Waves5.0.DLL

Could not load VST DLL. You may have tried to use x64 DLL or there is an internal error in the plug-in.
D:\Program Files\Sound Plugins\Waves\Plug-Ins\C360.dll

But from Acoustica Premium Edition 5.0 this VST`s successfully loaded.
Please, help and thank you for your work.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 08 June, 2011, 01:14:08 PM
I noticed that foobar 1.1.7 has displaying an odd behavior. When playing back online streams, there is a 2-3 seconds input freeze, even though audio is playing back fine.

Any ideas on what might be causing this? I ask because it's kind of a big deal for me, and if I find no solution, I'll have to go back to 1.1.6.
Title: foo_vst: VST 2.4 adapter
Post by: lhaymehr on 28 June, 2011, 11:00:03 AM
Great work, finally! Thanks for this plugin and maybe a suggestion: can you detect player start/stop (ignore crossfades) and clear the plugin stream buffer so that things like reverbs don't have the tail of previous track.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 28 June, 2011, 02:57:58 PM
I noticed that foobar 1.1.7 has displaying an odd behavior. When playing back online streams, there is a 2-3 seconds input freeze, even though audio is playing back fine.

Any ideas on what might be causing this? I ask because it's kind of a big deal for me, and if I find no solution, I'll have to go back to 1.1.6.


Seems completely unrelated to the VST wrapper, it's foobar 1.1.7 version that's faulty. I'm back at 1.1.6, with everything working perfectly.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 June, 2011, 10:22:57 AM
Great work, finally! Thanks for this plugin and maybe a suggestion: can you detect player start/stop (ignore crossfades) and clear the plugin stream buffer so that things like reverbs don't have the tail of previous track.

There is no way to reset a VST plug-in. But I made an imitation of a reset. Whenever a playback event is fired, plug-ins get fed with zeroed data chunks. You can adjust the size of these chunks in the advanced preferences section. The default value works pretty well for non-delay effects. The step size for the declicker is 256 samples.
Title: foo_vst: VST 2.4 adapter
Post by: auditorium on 01 July, 2011, 11:36:17 AM
Hello Yegor
This plugin supports VST synchronization transport (play, pause, stop)? --necessary for VST plugins with play/pause sync button--
Title: foo_vst: VST 2.4 adapter
Post by: tedych on 01 July, 2011, 03:28:12 PM
Hi Yegor. Yet another great plugin I find through my recent migration from Winamp to Foobar2000.

It works great with the VSTs I use currently (some are the same I use in my sound editor).
But I will second the wish I read here somewhere about a Bypass button. Some VSTs are resource intensive and whether I set their parameters to 0 (zero) they don't seem to take it as a private case and turn themselves off, still experiencing high CPU usage. Removing/adding them from the Preferences everytime I want a special effect/preview, is cumbersome.

I'd really like to see a Bypass button to avoid such cases. Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: DDRRE on 02 July, 2011, 02:07:34 PM
Could a feature be implemented that allows certain VSTs to process channels by selection?

I am using a De-esser VST that works in stereo, meaning that giving it 4ch or 6ch files to process outputs stereo, the first 2 channels processed, with the other channels ignored (not passed-through - silenced).

Many other VSTs work in mono/stereo, so could the adapter have a feature to assign channels to a VST? for example, adding 1 stereo VST or 2 mono VSTs to process the front inputs, and all channels not assigned with a VST will be passed-through unprocessed?

P.S. with the exception of the above issue (actually not an issue, merely a workaround request) the plugin works flawlessly. And that's a lot of work. Well done!
Title: foo_vst: VST 2.4 adapter
Post by: puciak on 07 July, 2011, 06:08:16 AM
I don't know if it is good place for this case.
I'm using BootEQ plugin. It works great when I'm playing audio, but when I try to convert files with additional processing (with BootEQ), only EQ section is working (there is also Gain/Output knob which seems to not work - I turned this output section on). Is it case of VST adapter or foobar?
Title: foo_vst: VST 2.4 adapter
Post by: Soviet Commissar on 21 July, 2011, 07:35:49 PM
Argh, the one VST I really wanted to be able to use (iZotope Vinyl) is 64bit.

I fail.

EDIT: I am a moron.  I somehow clicked into the 64-bit "Program Files" twice by mistake somehow, and thereby didn't see the one in the x86 folder.

Stellar component, yegor.  Спасибо!
Title: foo_vst: VST 2.4 adapter
Post by: auditorium on 31 August, 2011, 07:58:29 AM
Quote
only a slightly slower foobar startup
Yep, this is the way the adapter works. It keeps track of DSP stack from the very application startup as opposed to deferred loading, i.e. when the user starts playback. Either way, there is a delay before you can hear something

Further development of the adapter seems somewhat problematic to me because I have no time at all, you know, two jobs and two educations at once (final year both with all the headaches). And when I graduate, I'll have to go to the god damn army (it's obligatory here in Russia). That is I'll return home in summer 2012. Most likely i'll make it open source so you (yes, You, the most experienced and patient developer!  will be able to finish the job.


"Most likely i'll make it open source". Is this possible?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 31 August, 2011, 08:35:47 AM
Yep! It does everything I need and I'm bored with it anyway. Here you are: [attachment=6658:foo_vst_src.zip]
The Simplified BSD License is in license.txt.
Title: foo_vst: VST 2.4 adapter
Post by: compositore on 06 September, 2011, 01:48:03 AM
Thanks for the source.
There's a developer to improve the Foobar2000 VST 2.4 adapter, in particular chapter GUI to look better?
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 06 September, 2011, 09:35:05 AM
Thanks for the source.
There's a developer to improve the Foobar2000 VST 2.4 adapter, in particular chapter GUI to look better?


The UI is fine, what could be improved is VST compatibility and performance to a lesser extent.
Title: foo_vst: VST 2.4 adapter
Post by: zradu on 11 September, 2011, 08:40:42 AM
I noticed they were already 244 number of downloads. There are a developer who has brought or will bring several improvements to the adapter (now or in future)?
Title: foo_vst: VST 2.4 adapter
Post by: Zerox Millienium on 22 September, 2011, 08:41:43 AM
Voxengo SPAN seemed to work but a little retarded when used for a few minutes. The RMS volume statistic doesn't get updated accurately.
Seemed to work fine on most renown DAWs.

Hope some new developer comes along to improve the foo_vst plugin performance.

Regards.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 22 September, 2011, 09:15:34 AM
Quote
Voxengo SPAN seemed to work but a little retarded when used for a few minutes. The RMS volume statistic doesn't get updated accurately.
Seemed to work fine on most renown DAWs.
This is a known issue:
Quote
Display goes ahead of audio by the size of the output buffer.
It can't be fixed due to different buffering approaches between media players and DAWs. The foobar's DSP line isn't supposed to be used for visualization at all.
Title: foo_vst: VST 2.4 adapter
Post by: Rozzo on 22 September, 2011, 12:42:50 PM
It is there some way to integrate de vst adapter as a pannel on Defaul User Interface or Columns UI?

Ys
Rozzo
Title: foo_vst: VST 2.4 adapter
Post by: Oery on 24 September, 2011, 06:36:50 AM
Thank you for making this VST Adapter
working very well
Foobar2k sounds much better now.........
Thank you once again......

Foobar2k v.1.1.8 final
DSP Setting
   - SoX Resampler 2x Best
   - VST VB-FFX4 to load DX FX (RComp, BBE, L2)

(https://hydrogenaud.io/imgcache.php?id=a195d139902f10392d4b956818717eaf" rel="cached" data-warn="External image, click to view at original size" data-url="http://img855.imageshack.us/img855/1764/foobardx.jpg)

Systems:
   - Audiotrak Prodigy HD2 - Wasapi Output 24bit
   - OpAmp 2xLT1364 + AD797-BR (browndog adapter) (http://img600.imageshack.us/img600/7945/audiotrakic.jpg)
        - DIY LM3886 Amp + Philips 6922 Tube Buffer (http://img508.imageshack.us/img508/8825/coversgt.jpg)
        - Wharfedale Diamond 9.1 (anniv) Speakers
        - Yamaha YST-SW325 Sub
Title: foo_vst: VST 2.4 adapter
Post by: m00k0w on 28 September, 2011, 12:52:01 AM
Hey there,

Thanks for developing this amazing component!

Here's a bug for you:

foobar 1.1.8 with current version 2.4 of foo_vst.dll crashes/freezes with Electri-Q 1.8.8 when doing many critical features like loading a preset or setting the ability to resize the window. I think this is related to the VST plugin giving a popup; in Electri-Q, loading a preset asks for a file and setting "allow resize" gives a warning popup that a restart is necessary.

Thing is, whatever version of foo_vst.dll with the "date modified" being 1/8/2011 9:35PM, 170KB in size, works fine with this electri-q plugin. Perhaps it is good if you would post an archive of old versions as problems with some VST plugins may be fixed with an older version of foo_vst.dll!
Title: foo_vst: VST 2.4 adapter
Post by: ElverGun on 06 October, 2011, 06:41:07 AM
Any notable differences between this plug in and the old vst_bridge? Form what i've seen, this plugin is multi vst, and also support waves. Is it worth the hassle of changing?

This is my current setup:
http://img4.imageshack.us/img4/369/myfoobaro.jpg (http://img4.imageshack.us/img4/369/myfoobaro.jpg)
http://imageshack.us/photo/my-images/4/myfoobaro.jpg/ (http://imageshack.us/photo/my-images/4/myfoobaro.jpg/)
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 06 October, 2011, 09:06:57 AM
It's also multichannel to some extent, it supports Foobar's DSP preset subsystem and is able to work within portable installations. OTOH, it lacks support for non-GUI VSTs and isn't very robust due to huge differences between VST and fb2k's APIs.
Title: foo_vst: VST 2.4 adapter
Post by: jdubs on 14 October, 2011, 04:05:07 PM
All

I get this error, when I try to load the Allocator VST:

"Could not load VST DLL. You may have tried to use x64 DLL or there is an internal error in the plug-in.

C:\Program Files (x86)\foobar2000\components\VST Plugins\Allocator1.0.15\Allocator.dll"

Per this link, the combo should work:

http://www.exadevices.com/Blog/tabid/253/a...oobar-2000.aspx (http://www.exadevices.com/Blog/tabid/253/articleType/ArticleView/articleId/20/categoryId/3/Using-Allocator-with-exaU2I-and-Foobar-2000.aspx)

Per the Allocator creator it should work, too:

http://www.thuneau.com/forum/viewtopic.php...b45ca1597bbf4db (http://www.thuneau.com/forum/viewtopic.php?t=222&sid=34259c4af51def719b45ca1597bbf4db)

Any idea what's up?

Thanks!
Jim
Title: foo_vst: VST 2.4 adapter
Post by: jdubs on 14 October, 2011, 04:15:33 PM
Nevermind...did some more research.  I got it working by copying msvcr71.dll to the Windows/SysWOW64 directory.

-Jim
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 30 October, 2011, 12:50:04 AM
Not surprizingly, the thing made its way to the troubleshooter. Well, any bridge like this would be doomed anyway.
Title: foo_vst: VST 2.4 adapter
Post by: Northtech on 04 November, 2011, 03:11:53 PM
foobar2000 1.1.9

--
Online Troubleshooter:
foo_vst.dll : VST 2.4 adapter 0.9.0.3
Reason: Repeated crash reports.
Title: foo_vst: VST 2.4 adapter
Post by: raster43 on 15 November, 2011, 04:29:41 PM
Archive is corrupt in the op and the dll won't extract and can't be repaired.

Please repack/repost.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 15 November, 2011, 04:38:34 PM
Yegor, would it be possible if you posted the previous version of your VST bridge? It was asked previously, and it does make sense as the previous version is your official latest stable version, while 0.9.0.3 is an experimental version. Both versions display different behavior with certain VSTs, so it would increase the VST compatibility range quite a bit.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 15 November, 2011, 10:31:05 PM
It turns out the only previous version on my new PC is 0.9 and its only difference from 0.9.0.3 is correct update handling. Do you still want me to publish it?
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 15 November, 2011, 11:35:16 PM
Oh, I see. The version I was looking for was the previous stable one, 0.8.x.x, which I unfortunately can't remember the exact numbering  But thanks anyway.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 16 November, 2011, 01:00:12 AM
Well, I looked up in my back-ups and found all binaries starting from v0.5. I just thought they weren't backed up.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 16 November, 2011, 01:02:22 AM
Hats off to you sir, with my most sincere thanks *bows down* 
Title: foo_vst: VST 2.4 adapter
Post by: Bob Brines on 16 November, 2011, 10:13:31 AM
Quote the Foobar "Online Help":

foobar2000 troubleshooter
The following components found on your system are known to be problematic and should be either uninstalled or updated to their latest versions:

foo_dynamic_range.dll : Dynamic Range Meter 1.0.0
Reason: Repeated crash reports.

foo_vst.dll : VST 2.4 adapter 0.9.0.3
Reason: Repeated crash reports.

Do you have a fix for this?

Bob
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 16 November, 2011, 11:09:24 AM
The only way to fix it is to sandbox VST DLLs in a separate process. It is possible but it'd be a major rework, not just a fix.
Title: foo_vst: VST 2.4 adapter
Post by: Bob Brines on 16 November, 2011, 11:30:02 AM
The only way to fix it is to sandbox VST DLLs in a separate process. It is possible but it'd be a major rework, not just a fix.


OK. I haven't had any problems, just wanted to make sure you were aware. I would hate to see this plug-in black listed.

Bob
Title: foo_vst: VST 2.4 adapter
Post by: pjgregory on 23 November, 2011, 05:59:03 AM
I have been testing VST 2.4 (0.9.0.3) with the Electri-Q parametric equalizer to correct the low frequency response in my room.  No problems, except that the Electri-Q plugin is dual mono so I cannot create a separate equalization for each speaker.  I have downloaded the demo version of the Blue Cat Stereo Parametric Equalizer.  It loads OK, but as soon as I try to change one of the frequency or gain settings (a small pop-up text box appears), the Equalizer freezes and foobar crashes.  Is this the same general crashing problem that has been reported here?

If there is no fix in sight, does anyone know of a stereo parametric equalizer that does work with VST 2.4

PJG
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 November, 2011, 07:00:44 AM
I know about this problem with Blue Cat plug-ins. New version of the adapter is in development atm. UI stuff is going to have numerous bugfixes.
Title: foo_vst: VST 2.4 adapter
Post by: AlphaWave on 24 November, 2011, 05:07:37 AM
Is there a way to have the running vst start automatically when foobar starts without have to start the dsp manager?  Even better, to have the vst window integrated in foobar rather than in a separate window?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 November, 2011, 05:39:16 AM
What's the point of keeping VST editors visible all the time?
Title: foo_vst: VST 2.4 adapter
Post by: AlphaWave on 24 November, 2011, 06:06:18 AM
Hmmm. I think what I meant to say was having the vst plugin itself visible all the time. I guess I'm asking that in the wrong place aren't I?
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 November, 2011, 06:09:42 AM
It's the same. So why do you want to have them visible?
Title: foo_vst: VST 2.4 adapter
Post by: AlphaWave on 24 November, 2011, 06:50:39 AM
So that I can play around with it as the fancy takes me I.e. when I think the playing track warrants a different eq. At the moment I have to firstly go to view - dsp manger - 'easy eq vst' to see the thing and then I have to switch between the main window and vst window. All this makes it more of a pain to make eq adjustments 'on the fly'. In my view it should be as easy as sliding the foobar volume slider.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 24 November, 2011, 07:38:20 AM
Short answer: I'm sorry but no.

It's View > DSP menu we're talking about, not VST plug-ins, right? Well, not only this feature won't be extended but it will also be disabled by default. It's because Foobar2000 doesn't encourage such behavior, i.e. to leave DSP config windows open. I wish it wasn't so myself. As for integrating VST GUIs into the fb2k's main window, it'll be just ugly because VST doesn't support window sizing.
Title: foo_vst: VST 2.4 adapter
Post by: pjgregory on 24 November, 2011, 11:36:28 AM
I know about this problem with Blue Cat plug-ins. New version of the adapter is in development atm. UI stuff is going to have numerous bugfixes.


Fine. I will wait.

PJG
Title: foo_vst: VST 2.4 adapter
Post by: Sylph on 30 November, 2011, 03:41:26 AM
Does this work with Ozone 5?
Title: foo_vst: VST 2.4 adapter
Post by: marabundo on 04 December, 2011, 02:00:23 PM
Does this work with Ozone 5?

Works fine (foobar2000 v.1.1.10)
Title: foo_vst: VST 2.4 adapter
Post by: oromasdes on 23 December, 2011, 07:29:52 AM
Archive is corrupt in the op and the dll won't extract and can't be repaired.
Please repack/repost.


Got the dll after a few attemtps.  Don't use winzip, but use 7-zip instead.  Steps :
1. Open the downloaded file 'foo_vst_0903.zip' with 7-zip.
2. Extract the 1 file named 'foo_vst_0903' (and close 7-zip)
3. Open the extracted file 'foo_vst_0903' again with 7-zip (as it has no extension, do it with right-click  and 'Open', then select 7-zip as program; or start 7-zip and navigate to the file, then double-click on it)
3. Extract the 1 file named 'foo_vst.dll' - this is the unpacked dll
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 23 December, 2011, 11:45:41 PM
Or just drag'n'drop the zip file to the components list in the preferences dialog box.
Title: foo_vst: VST 2.4 adapter
Post by: pjgregory on 29 December, 2011, 11:08:52 AM
I know about this problem with Blue Cat plug-ins. New version of the adapter is in development atm. UI stuff is going to have numerous bugfixes.


Fine. I will wait.

PJG


Any progress on a fix for the Blue Cat Plugin?
Title: foo_vst: VST 2.4 adapter
Post by: bobbyhu on 14 January, 2012, 08:53:33 AM
Does this work with Ozone 5?

Works fine (foobar2000 v.1.1.10)


Damn, I can't make it to work with foobar2000 v.1.1.10 and ozone advanced 5. (ozone 4 works fine)

Which dll did you add in the VST plugin window? iZotope Ozone 5.dll?

The View/DSP menu is greyed out even after restarting foobar.

Title: foo_vst: VST 2.4 adapter
Post by: ironmine on 20 January, 2012, 12:43:09 AM
I have been testing VST 2.4 (0.9.0.3) with the Electri-Q parametric equalizer to correct the low frequency response in my room.  No problems, except that the Electri-Q plugin is dual mono so I cannot create a separate equalization for each speaker.  I have downloaded the demo version of the Blue Cat Stereo Parametric Equalizer.  It loads OK, but as soon as I try to change one of the frequency or gain settings (a small pop-up text box appears), the Equalizer freezes and foobar crashes.  Is this the same general crashing problem that has been reported here?

If there is no fix in sight, does anyone know of a stereo parametric equalizer that does work with VST 2.4

PJG


Hi PJGREGORY!

I've started experimenting with active equalization for room correction (plus I have some passive self-made acoustic panels & bass traps) quite a long time ago. My final result looks like this:

I use Foobar2000 and its component George Yohng's VST wrapper (http://www.yohng.com/software/foobarvst.html). It is linked to Art-Teknika Console (http://console.jp/en/), it's a very visual and user-friendly Japanese VST-chainer. The main action takes place inside this Art-Teknika. I use two instances of LiquidSonic Reverberate (http://www.liquidsonics.com/software_reverberate.htm) Convolution VST plugins, one for each channel. Each LiquidSonic is loaded with a room correction filter (impulse) made in Room EQ Wizard (http://www.hometheatershack.com/roomeq/), separately for each channel.

Then I add Sonalksis Ultimate-D (http://www.google.ru/url?sa=t&rct=j&q=sonalksis%20ultimate-d&source=web&cd=1&ved=0CCUQFjAA&url=http%3A%2F%2Fwww.sonalksis.com%2Fultimated.htm&ei=r_4YT9AOkKD7Btq_vfUJ&usg=AFQjCNHLRZmv883VCqEP1f-0xG538lfrJg&cad=rja) VST Plugin for dithering to 16 bits and finally I monitor the output with Sonalksis FreeG plugi (http://www.sonalksis.com/freeg.htm)n to make sure the level does not go above zero.

I tried different equalizers, but I prefer the sound of LiquidSonic convolution plugins. However, I should say that Oxford Sonnox EQ (http://www.sonnoxplugins.com/pub/plugins/products/eq.htm) is also very good!

If you need any help with the setup, you can write to me at ironmine@mail.ru

Bye,
Eugene K (Russia)
Title: foo_vst: VST 2.4 adapter
Post by: Presto on 08 February, 2012, 03:31:31 PM
Yegor:

First of all, thank-you SO SO MUCH for creating a multichannel VST wrapper. Do you have a donation page? 

One issue I was wondering if you could help me with. The plugin, whether using kernel streaming or ASIO outputs, seems to do it's channel mapping at a very low level (hardware level? HAL?) for the audio interface. Any attempt to use the Foobar matrix mixer post-plugin, or assign channel mapping in the more recent ASIO output plugin does not make any difference. Is this is a problem? Not really - but for some cards you get unusual or unexpected channel mapping. Examples:

X-Fi (Audio Creation Mode) - Only first 6 of 8 physical channels are available.
M-Audio Revolution 7.1 - Channels 5 and 6 are mirrored onto 7 and 8 (so only six are usable)
C-Media AZ9880 onboard codex - channel mirroring as with M-Audio revolution

Is this wrapper limited to 6 channels? Can one change the mapping?
What audio interface did you use when developing / testing this wrapper?
(Sorry for all the questions - I am SOOOOOOOO close to getting this all working it's maddening!)

I have other cards (and one on the way) to test and maybe that will shine a light on this. It could be goofy channel mapping inherent to the various cards to do "top" channels, which are often combinations of various surround channels. I.e., in X-fi, one top channel maps audio to every other channel. (Not wanted when you're doing audio-creation or Allocator type applications)

Thanks for your time, and thanks for getting us Thuneau Allocator users one step closer to sonic perfection!

Cheers,
Presto
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 08 February, 2012, 04:34:40 PM
ASIO is still a buggy output method, you can get exactly the same bitmatched output through WASAPI. And KS is obviously out of the question.
Title: foo_vst: VST 2.4 adapter
Post by: Presto on 09 February, 2012, 12:19:21 AM
ASIO is still a buggy output method, you can get exactly the same bitmatched output through WASAPI. And KS is obviously out of the question.


Thanks for getting back to me Tribaljet.
UPDATE: It's all working 100% now. I needed to increase the channel limit from 6 to 8. I also no longer needed to do "counter-intuitive" ASIO mapping, so when I just picked the ASIO channels from 1 to 8 in sequence and ignorned the nicknames, it worked just fine.

All I can say is WOW - this sounds amazing. No separate VST host. No Console. No ASIO4ALL - just Foobar and the Allocator and great sound!

This VST adapter is DA BOMB!
Title: foo_vst: VST 2.4 adapter
Post by: grimpr on 20 February, 2012, 07:03:50 AM
I have been testing VST 2.4 (0.9.0.3) with the Electri-Q parametric equalizer to correct the low frequency response in my room.  No problems, except that the Electri-Q plugin is dual mono so I cannot create a separate equalization for each speaker.  I have downloaded the demo version of the Blue Cat Stereo Parametric Equalizer.  It loads OK, but as soon as I try to change one of the frequency or gain settings (a small pop-up text box appears), the Equalizer freezes and foobar crashes.  Is this the same general crashing problem that has been reported here?

If there is no fix in sight, does anyone know of a stereo parametric equalizer that does work with VST 2.4

PJG


Hi PJGREGORY!

I've started experimenting with active equalization for room correction (plus I have some passive self-made acoustic panels & bass traps) quite a long time ago. My final result looks like this:

I use Foobar2000 and its component George Yohng's VST wrapper (http://www.yohng.com/software/foobarvst.html). It is linked to Art-Teknika Console (http://console.jp/en/), it's a very visual and user-friendly Japanese VST-chainer. The main action takes place inside this Art-Teknika. I use two instances of LiquidSonic Reverberate (http://www.liquidsonics.com/software_reverberate.htm) Convolution VST plugins, one for each channel. Each LiquidSonic is loaded with a room correction filter (impulse) made in Room EQ Wizard (http://www.hometheatershack.com/roomeq/), separately for each channel.

Then I add Sonalksis Ultimate-D (http://www.google.ru/url?sa=t&rct=j&q=sonalksis%20ultimate-d&source=web&cd=1&ved=0CCUQFjAA&url=http%3A%2F%2Fwww.sonalksis.com%2Fultimated.htm&ei=r_4YT9AOkKD7Btq_vfUJ&usg=AFQjCNHLRZmv883VCqEP1f-0xG538lfrJg&cad=rja) VST Plugin for dithering to 16 bits and finally I monitor the output with Sonalksis FreeG plugi (http://www.sonalksis.com/freeg.htm)n to make sure the level does not go above zero.

I tried different equalizers, but I prefer the sound of LiquidSonic convolution plugins. However, I should say that Oxford Sonnox EQ (http://www.sonnoxplugins.com/pub/plugins/products/eq.htm) is also very good!

If you need any help with the setup, you can write to me at ironmine@mail.ru

Bye,
Eugene K (Russia)


Amazing post, thanks for letting me know about Console, Foobar + Console + VirtualAudioCable + Continuator is a powerhouse combination.
Title: foo_vst: VST 2.4 adapter
Post by: Alexa on 23 February, 2012, 12:20:58 PM
new foobar fading thingie fixed the clicking noises when you had fading enabled! yey
Title: foo_vst: VST 2.4 adapter
Post by: DJ_DOGGY on 04 March, 2012, 04:48:07 PM
Plugin is very useful
Title: foo_vst: VST 2.4 adapter
Post by: ironmine on 04 March, 2012, 04:53:17 PM
Plugin is very useful


The George Yohng's plugin is better for me because I can keep the interface of the VST plugins on top of the Foobar2000 player while music plays and control the sound "on the fly".
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 04 March, 2012, 08:21:10 PM
The George Yohng's plugin is better for me because I can keep the interface of the VST plugins on top of the Foobar2000 player while music plays and control the sound "on the fly".


You can do the same with foo_vst, I have no idea where you pulled the idea that it can't.
Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 14 March, 2012, 10:04:39 PM
hi,
there's two vst when you enter the parameters manually  (i.e you type number then the enter key) ,
then it crashs. LP10 by DDMF, and VahlalaRoom.
What's weird, is that if I  use the Acon EffectChainer as an intermediary to load vst, it doesn't crash anymore.

Note: By the way, it would be nice , if the vst adapter would allow saving of presets as fxp files (standard way of saving presets introduced by steinberg, but re-used by other programs like soundforge).
Now I'm using Acon EffectChainer just to use fxp presets (and to avoid crash too).
Title: foo_vst: VST 2.4 adapter
Post by: ironmine on 14 March, 2012, 11:35:22 PM
The George Yohng's plugin is better for me because I can keep the interface of the VST plugins on top of the Foobar2000 player while music plays and control the sound "on the fly".


You can do the same with foo_vst, I have no idea where you pulled the idea that it can't.


Yes, you can control the sound "on the fly", but you cannot control the buttons in the Foobar, e.g., start or stop the playback, put it on pause. You gotta close the VST windows first, which is not convinient.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 14 March, 2012, 11:36:43 PM
The George Yohng's plugin is better for me because I can keep the interface of the VST plugins on top of the Foobar2000 player while music plays and control the sound "on the fly".


You can do the same with foo_vst, I have no idea where you pulled the idea that it can't.


Yes, you can control the sound "on the fly", but you cannot control the buttons in the Foobar, e.g., start or stop the playback, put it on pause. You gotta close the VST windows first, which is not convinient.


You don't have to close any VST windows at all. What you might be referring to is window focus, as VST windows can't be pinned at this time.
Title: foo_vst: VST 2.4 adapter
Post by: sbcontt on 16 April, 2012, 05:25:24 PM
May I request multicore support? Currently I can't run more than four VST plug-ins at a time. Multithreading first needs to be implemented in Fb2k before plug-ins can use it so we got a problem. I have seen Fb2K uses 2nd core of CPU most intensively by default. Taking away permission to use 1st CPU core heavily degrades performance, so maybe currently it supports upto dual core, further support of more cores and 64 bit architecture is necessary so that we can run 64 bit versions of VST plugins distributed among all available cores.
Title: foo_vst: VST 2.4 adapter
Post by: sbcontt on 01 May, 2012, 07:33:31 AM
Well I have found a solution: If I take away permission of both first two cores, the process will distribute load among rest of the cores evenly. This both removes the shutters and enables me to perform other tasks while listening music. But I can't do anything with the FB2K UI without causing the audio to shutter.
Title: foo_vst: VST 2.4 adapter
Post by: markanini on 04 May, 2012, 11:23:35 AM
Is there anything that could be done to make visualizing plugins compensate for the playback buffer?
Title: foo_vst: VST 2.4 adapter
Post by: SoNic67 on 06 May, 2012, 10:21:36 AM
I was wondering the same thing... I am using a free VST spectrum analizer (as DSP) and it is "ahead" of music with a full second.
Title: foo_vst: VST 2.4 adapter
Post by: emueyes on 26 June, 2012, 09:21:08 AM
Short answer: I'm sorry but no.

It's View > DSP menu we're talking about, not VST plug-ins, right? Well, not only this feature won't be extended but it will also be disabled by default. It's because Foobar2000 doesn't encourage such behavior, i.e. to leave DSP config windows open. I wish it wasn't so myself. As for integrating VST GUIs into the fb2k's main window, it'll be just ugly because VST doesn't support window sizing.


I've just found this thread, and was wondering the same thing. In my case it's purely ornamental though, I like the effect (visual, that is) of the Blue Cat Frequency Display, and would like to display it in a panel within ColumnsUI. I realise most VST plugins are meant to enhance/alter the sound in some way, and for that I'd think it'd be handy too, more so because the plugin would actually be doing something useful  The phrase 'VST doesn't support window sizing' pretty much says it all though.
Title: foo_vst: VST 2.4 adapter
Post by: midix on 23 July, 2012, 08:09:36 AM
We have developed a VST plugin. There are is one issue on Foobar VST using this VST adapter.

The problem is that this plugin does not call resume() / suspend() on discontinuities in the incoming audio stream and does not return any useful information in
VstTimeInfo *vsti = getTimeInfo(-1);

Because of this issue we cannot detect the situation when users seek song position or switch to another song, and this means we cannot clear inner audio buffers of our plugin to avoid tails and echoes if user is seeking the song or switching between songs. We have tried two approaches:

- detecting when the current buffer has came X times later than the last buffer length but we had problems to adjust the X constant. On some machines for some formats X=4 worked fine but on some other machines or other formats it did not work. Then we tried X=3, but got many false positives on some machines and for some formats.
- then we noticed that after discontinuities the incoming buffer size often changes. But the problem was that it was just "often" and not always, so it's not reliable approach either.

Is there any reliable way to detect audio stream discontinuities in this Foobar VST adapter?
Title: foo_vst: VST 2.4 adapter
Post by: markanini on 23 July, 2012, 09:18:45 AM
You should contact Peter Pawlowski or some official developer, this thread is for a plugin made by a third-party developer.
Title: foo_vst: VST 2.4 adapter
Post by: midix on 23 July, 2012, 09:51:03 AM
Maybe I did not specify it clearly enough. We are loading our VST plugin into Foobar through the Yegor Petrov's VST adapter foo_vst. Generally, it is great adapter except this single issue with not providing any means to determine when the user has changed his song position.

Maybe it is Foobar's problem and there is no any way to get position info from Foobar to foo_vst and then to our plugin? Anyway, it would be great to hear any ideas.
Title: foo_vst: VST 2.4 adapter
Post by: tribaljet on 23 July, 2012, 01:38:43 PM
midix, do you get similar results when using foo_dsp_vstwrap by George Yohng?
Title: foo_vst: VST 2.4 adapter
Post by: midix on 23 July, 2012, 02:38:48 PM
Oh, thanks for the idea, I'll try the foo_dsp_vstwrap. Somehow I forgot that one 
Title: foo_vst: VST 2.4 adapter
Post by: romor on 16 August, 2012, 05:44:32 PM
Yegor, while using Dynamic DSP (http://www.hydrogenaudio.org/forums/index.php?showtopic=96094) component, I noticed issue with your non-modal config dialogs (View > DSP) - if I access Dynamic DSP component through "View > DSP" and then double click on one of available chains inside Dynamic DSP, foobar crashes reproducibly

If I access Dynamic DSP from foobar preferences there is no issue, but then if I try to open actual chain, I have 4 opened windows which mask the player. To be more inappropriate, if I use some VST in Dynamic DSP chain and access VST as described, I get no action - VST doesn't show signal although I can blindly adjust VST and apply the change.

I'm linking this also in Dynamic DSP thread

Thanks for looking into it
Title: foo_vst: VST 2.4 adapter
Post by: Airmann on 20 August, 2012, 05:51:05 PM
Hi guys,

I've a problem with the VST component.

System: Win7 64
foobar: v1.1.14a (newest)

Problem: VST's seem to be loaded, but I see no Plugin-GUI. Tried different 32 bit plugins. I am missing something obvious or is it a foobar-related problem
Title: foo_vst: VST 2.4 adapter
Post by: bison on 13 September, 2012, 08:46:22 PM
just for the record, in order to workaround the lack of support for plugins not providing their own GUI, you can simply use EffectChainer as a middle-man et voilà
Title: foo_vst: VST 2.4 adapter
Post by: Spanky Monkey on 23 September, 2012, 07:44:54 AM
Hi folks,

(first post - so please be kind  )

I think this is a great component.  It's tidy and just allowed a VST plugin to be run as a standard DSP (that's how it appears).  Nice.

However, I have a problem that I don't think I had before.

If a VST plugin is in use, and I leave playing or pause playback, and exit, foobar2000 comes up with an error report.  This doesn't happen if I stop playback first, or unload any VST plugins.

I noticed it happen on the Win7 starter netbook, but it is also happening on WinXP SP3 PC.

The VST wrapper is loaded on the netbook at the moment, that doesn't have this problem, but I don't really like the way it works with the tray icon thing, I like your way of doing things better.

Thanks
Title: foo_vst: VST 2.4 adapter
Post by: Jeroenm on 29 September, 2012, 11:33:57 AM
ASIO is still a buggy output method, you can get exactly the same bitmatched output through WASAPI. And KS is obviously out of the question.


Thanks for getting back to me Tribaljet.
UPDATE: It's all working 100% now. I needed to increase the channel limit from 6 to 8. I also no longer needed to do "counter-intuitive" ASIO mapping, so when I just picked the ASIO channels from 1 to 8 in sequence and ignorned the nicknames, it worked just fine.

All I can say is WOW - this sounds amazing. No separate VST host. No Console. No ASIO4ALL - just Foobar and the Allocator and great sound!

This VST adapter is DA BOMB!


Hello Presto,

First post...

I have also tried the vst wrapper with Thuneau Allocator. It works fine.
Except for one thing. After restarting Foobar I have to activate  the Thuneau Allocator again filling in the licence key.

Am I missing something?

Jeroen.

Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 29 September, 2012, 11:43:49 AM
I have also tried the vst wrapper with Thuneau Allocator. It works fine.
Except for one thing. After restarting Foobar I have to activate  the Thuneau Allocator again filling in the licence key.


Try to launch foobar with admin rights, just for once, while doing activation.
Title: foo_vst: VST 2.4 adapter
Post by: Jeroenm on 30 September, 2012, 02:31:09 AM
I have also tried the vst wrapper with Thuneau Allocator. It works fine.
Except for one thing. After restarting Foobar I have to activate  the Thuneau Allocator again filling in the licence key.


Try to launch foobar with admin rights, just for once, while doing activation.


Yes, this solved the problem. 
Thanks!

Jeroen.
Title: foo_vst: VST 2.4 adapter
Post by: foomark on 01 October, 2012, 05:31:51 AM
Hi everyone, i'm quite new to VST plugins inside foobar2000, so please be kind
I've been able to install and load the plugins i need with no problem, but now i'm wondering one thing:
Is it possible to create a folder for presets in a portable installation of foobar2000??
What i'd like is to keep all of my presets inside the foobar folder, something like \foobar2000\VSTplugins\presets...

Thanks in advance
Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 01 October, 2012, 08:09:13 AM
What i'd like is to keep all of my presets inside the foobar folder, something like \foobar2000\VSTplugins\presets...


You mean preset for all VST ? Each VST is programmed to save preset in a particular path , I bet that's not possible. If you use the VST  "console sound modular studio" (commercial) ,  it allows to save a VST  chain, with preset in every VST , in a single preset. And this works even if you change the installation path of  each VST.

I  think this could be  possible too, with EffectChainer by Acon Digital, or MultiFXVST, although I didn't test well.
Title: foo_vst: VST 2.4 adapter
Post by: Yegor on 01 October, 2012, 09:31:52 AM
Quote
Is it possible to create a folder for presets in a portable installation of foobar2000??
There are 3 kinds of presets: The Presets Pane shows the VST plug-in's own presets. So... what kind of presets are you interested in?

presets presets presets :-D
Title: foo_vst: VST 2.4 adapter
Post by: foomark on 02 October, 2012, 03:16:54 AM
Thank you for the replies 
To be honest i didn't even know of all this kind of presets, i'm a bit confused now 
However i'm studing how to use them, expecially with a portable installation of foobar, tell me if i do some mistake:

1)DSP chain presets: i don't know what they are, i'll keep this way and never use it 

2)the .fxp are the presets i can create inside a VST plugin through the small "Presets pane" button inside the plugin itself, right?
if so, when i create a new presets it is added to a new folder inside foobar2000\vst-presets\nameoftheplugini'musing\....fxp
that's good!!

3)The vst plugin it's own presets: i was talking about this presets in my first message, but tring to use them i found that some of them works other do not.
I have some vst plugins that comes with presets in a .xml formats, and i can load them with no problem.
Other instead comes with strange .spt extension, and also if i open the vst it doesn't allow me to load them. Probably they need an installed "standalone" vst host, idk...

Title: foo_vst: VST 2.4 adapter
Post by: er_or on 05 November, 2012, 02:12:19 PM
It doesn't work on win8.
foo_vst is recognized, but VST are not visible
Title: foo_vst: VST 2.4 adapter
Post by: flipper_gv on 10 December, 2012, 11:41:15 PM
It doesn't work on win8.
foo_vst is recognized, but VST are not visible


Same here. Would love an update.
Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 10 December, 2012, 11:47:14 PM
It doesn't work on win8.
foo_vst is recognized, but VST are not visible


Try to disable windows theme and/or desktop composition.
The issue might be a font displayed in white over a white background.
I  say this , because this remind me an old issue, when I've upgraded to vista, with a particular software.
Title: foo_vst: VST 2.4 adapter
Post by: sdixit3 on 28 December, 2012, 08:55:58 AM
The dowload is not working. It says zip file is invalid.
Could some one upload a working copy ?

thanks
Title: foo_vst: VST 2.4 adapter
Post by: lvqcl on 08 January, 2013, 05:49:00 AM
foo_playlist_attributes.dll 0.5.1 (default settings)
foo_vst.dll 0.9.0.3

Add any VST plugin into the DSP chain, play a file and close foobar2000 while playing or when the playback is paused => fb2k crashes.

However it doesn't crash without foo_playlist_attributes.
Title: foo_vst: VST 2.4 adapter
Post by: db1989 on 08 January, 2013, 06:03:21 AM
The dowload is not working. It says zip file is invalid.
Could some one upload a working copy ?
It works for me using Windows 7 Explorer and the free program 7-Zip, but just in case anyone else has this issue, I’ve added another ZIP that I unarchived and re-compressed using the former.
Title: foo_vst: VST 2.4 adapter
Post by: PJay-Z on 17 January, 2013, 08:38:45 PM
It doesn't work with the latest version?
Title: foo_vst: VST 2.4 adapter
Post by: nine09 on 18 January, 2013, 11:38:49 AM
Hey guys. I just made a very basic tutorial for beginners on how to use this brilliant plugin.

http://youtu.be/RaFcdAxpaQY (http://youtu.be/RaFcdAxpaQY)

Title: foo_vst: VST 2.4 adapter
Post by: Northtech on 14 February, 2013, 12:47:44 PM
Anybody can fix crash in this plugin?
Thanks.
Title: foo_vst: VST 2.4 adapter
Post by: db1989 on 14 February, 2013, 01:05:41 PM
What crash? Are we to assume that you are referring to this report from 15 months ago?

foobar2000 1.1.9

--
Online Troubleshooter:
foo_vst.dll : VST 2.4 adapter 0.9.0.3
Reason: Repeated crash reports.

Either way, did you not think it would be helpful to everyone involved if you posted some actual information? When does it crash, what else was being done in fb2k at that time, what hardware are you using, which other details of your installation/configuration may be relevant to people trying to help you, etc.
Title: foo_vst: VST 2.4 adapter
Post by: Northtech on 17 February, 2013, 01:10:54 PM
db1989
This crash - http://www.hydrogenaudio.org/forums/index....st&p=819766 (http://www.hydrogenaudio.org/forums/index.php?showtopic=84947&view=findpost&p=819766)
My report from 15 months ago is directly related.


Code: [Select]
Windows 7 sp1

Core (2013-02-13 11:26:10 UTC)
   foobar2000 core 1.2.3
foo_albumlist.dll (2013-02-13 11:24:52 UTC)
   Album List 4.5
foo_converter.dll (2013-02-13 11:24:22 UTC)
   Converter 1.5
foo_dsp_eq.dll (2013-02-13 11:24:54 UTC)
   Equalizer 1.0
foo_dsp_std.dll (2013-02-13 11:24:44 UTC)
   Standard DSP Array 1.2
foo_fileops.dll (2013-02-13 11:23:12 UTC)
   File Operations 2.2
foo_hdcd.dll (2012-07-20 20:41:44 UTC)
   HDCD decoder 1.15
foo_input_monkey.dll (2012-06-06 12:48:14 UTC)
   Monkey's Audio Decoder 2.1.6
foo_input_std.dll (2013-02-13 11:23:54 UTC)
   Standard Input Array 1.0
foo_rgscan.dll (2013-02-13 11:24:30 UTC)
   ReplayGain Scanner 2.1.2
foo_simplaylist.dll (2011-08-18 16:01:36 UTC)
   SimPlaylist 1.0
foo_ui_columns.dll (2011-02-27 20:22:58 UTC)
   Columns UI 0.3.8.8
foo_ui_std.dll (2013-02-13 11:23:58 UTC)
   Default User Interface 0.9.5
foo_unpack.dll (2013-02-13 11:24:22 UTC)
   ZIP/GZIP/RAR Reader 1.6
foo_unpack_7z.dll (2011-08-13 14:27:58 UTC)
   7-Zip reader 1.8
foo_vst.dll (2011-03-05 04:19:04 UTC)
   VST 2.4 adapter 0.9.0.3

So far i deleted plugin (Playlist Attributes).
Title: foo_vst: VST 2.4 adapter
Post by: Propheticus on 17 February, 2013, 05:50:21 PM
The latest version of Foobar 1.2.3 does not play when resuming playback on restart while VSTs are loaded in my DSP chain using foo_vst 2.4 (using two VST plugins Electri-Q posihfopit and Headfit). Any playback action (stop, pause, play) won't work and result in 'program not reponding' with 25% cpu usage (1 core 100%). So whatever you do... foobar crashes. This does not happen when there are no VST plugins loaded in the DSP chain (reproducable time after time).
Could this please be fixed? The only workaround for now is disabling 'resume playback after restarting foobar2000' in the playback settings.

plugin report:
Code: [Select]
Core (2013-02-13 11:26:10 UTC)
foobar2000 core 1.2.3
foo_ac3.dll (2012-09-09 19:48:27 UTC)
AC3 decoder 0.9.7
foo_albumlist.dll (2013-02-13 11:24:52 UTC)
Album List 4.5
foo_cdda.dll (2013-02-13 11:24:22 UTC)
CD Audio Decoder 3.0
foo_channel_mixer.dll (2008-03-12 09:37:47 UTC)
Channel Mixer 0.9.6.5
foo_converter.dll (2013-02-13 11:24:22 UTC)
Converter 1.5
foo_cuefilter.dll (2013-02-16 11:18:17 UTC)
CUE Playlist Filter 0.1.7.0
foo_dsp_crossfader.dll (2010-01-13 19:46:10 UTC)
Gapless Crossfader 1.3.4.1
foo_dsp_eq.dll (2013-02-13 11:24:54 UTC)
Equalizer 1.0
foo_dsp_resampler.dll (2012-08-17 18:41:42 UTC)
SoX Resampler 0.8.0
foo_dsp_std.dll (2013-02-13 11:24:44 UTC)
Standard DSP Array 1.2
foo_dsp_xgeq.dll (2012-02-13 12:17:29 UTC)
Graphic Equalizer 0.3.7
foo_fileops.dll (2013-02-13 11:23:12 UTC)
File Operations 2.2
foo_freedb2.dll (2013-02-13 11:22:46 UTC)
Online Tagger 0.7
foo_input_dts.dll (2013-02-10 23:53:10 UTC)
DTS decoder 0.3.1
foo_input_monkey.dll (2012-09-09 19:48:27 UTC)
Monkey's Audio Decoder 2.1.6
foo_input_std.dll (2013-02-13 11:23:54 UTC)
Standard Input Array 1.0
foo_keep_queue.dll (2011-08-03 23:29:28 UTC)
Keep Queue 0.3.5
foo_masstag.dll (2010-07-17 16:50:37 UTC)
Masstagger 1.8.4
foo_out_upnp.dll (2013-02-10 23:53:10 UTC)
UPnP MediaRenderer Output 1.0 beta 4
foo_out_wasapi.dll (2013-02-10 23:53:10 UTC)
WASAPI output support 3.2.1
foo_playcount.dll (2011-08-30 19:57:43 UTC)
Playback Statistics 3.0.2
foo_plorg.dll (2011-09-17 00:23:26 UTC)
Playlist Organizer 2.4
foo_queuecontents.dll (2012-03-20 23:45:53 UTC)
Queue Contents Editor 0.5.1
foo_quicksearch.dll (2012-11-06 01:54:29 UTC)
Quick Search Toolbar 3.4
foo_rgscan.dll (2013-02-13 11:24:30 UTC)
ReplayGain Scanner 2.1.2
foo_scheduler.dll (2013-02-10 23:53:10 UTC)
Scheduler 4.11
foo_softplaylists.dll (2011-03-23 11:29:41 UTC)
Soft Playlists 2011-02-05
foo_texttools.dll (2010-11-07 17:51:39 UTC)
Text Tools 1.0.5
foo_ui_columns.dll (2011-02-27 20:23:00 UTC)
Columns UI 0.3.8.8
foo_ui_std.dll (2013-02-13 11:23:58 UTC)
Default User Interface 0.9.5
foo_uie_albumlist.dll (2009-06-13 22:49:19 UTC)
Album list panel 0.3.5
foo_uie_biography.dll (2010-12-13 20:38:26 UTC)
Biography View 0.4.2.4
foo_uie_elplaylist.dll (2011-01-06 09:07:35 UTC)
ELPlaylist 0.6.9.1.2(beta)
foo_uie_esplaylist.dll (2011-02-19 08:20:42 UTC)
EsPlaylist 0.1.3.7
foo_uie_lyrics3.dll (2012-09-09 19:48:27 UTC)
Lyric Show Panel 3 0.3.5.2
foo_uie_panel_splitter.dll (2010-05-27 11:03:02 UTC)
Panel Stack Splitter 0.3.8.3(alpha)
foo_uie_vis_channel_spectrum.dll (2010-03-07 08:23:55 UTC)
Channel Spectrum panel 0.17.2
foo_uie_vis_peakmeter_spectrum.dll (2010-03-07 08:24:47 UTC)
Peakmeter Spectrum Visualisation 0.2.0.0 beta
foo_uie_wsh_panel_mod.dll (2012-10-16 00:45:19 UTC)
WSH Panel Mod 1.5.6
foo_unpack.dll (2013-02-13 11:24:22 UTC)
ZIP/GZIP/RAR Reader 1.6
foo_vis_shpeck.dll (2009-09-28 10:32:16 UTC)
Shpeck - Winamp vis plugins wrapper 0.3.7
foo_vst.dll (2011-03-05 07:19:04 UTC)
VST 2.4 adapter 0.9.0.3
foo_wave_seekbar.dll (2012-12-18 15:56:12 UTC)
Waveform seekbar 0.2.29
foo_wlm.dll (2011-02-13 13:00:20 UTC)
Windows Live Messenger Notifier 1.1.7
System:
- Win 7 x64
- Q6600 @ 3Ghz, 4GB ram DDR2
- Asus Xonar DG @ 96Khz/24bit with ASUS XONAR Unified Drivers v1.63
- Foobar 1.2.3 with DSP chain: Gapless Crossfader, Convert 5.1 to stereo, Electri-Q posihfopit edition (VST), head-fit-lite (VST), Advanced Limiter | output: Wasapi (event), 24-bit, 2000ms buffer, replaygain enabled
Title: foo_vst: VST 2.4 adapter
Post by: patul on 18 February, 2013, 01:09:27 AM
The latest version of Foobar 1.2.3 does not play when resuming playback on restart while VSTs are loaded in my DSP chain using foo_vst 2.4 (using two VST plugins Electri-Q posihfopit and Headfit).


I got same crashes using this specific vst plugins, Electri-Q posihfopit. In my case, it is reproducible by changing the preset rapidly. I've never got this kind of crashes before, so I suspected it was the vst plugin.
Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 18 February, 2013, 08:05:00 AM
What annoys me , is that foobar crash when I close it directly during playback (when there's a dsp chain using vst).
To avoid crash, I must press first stop , and then only close.
This is especially true with vst with big latency : I guess there's something in cache/buffer, and foobar don't have time time to clean it  when you close it.
I'm wondering why it couldn't be automated  ?  ( a safe stop, when you close).

Title: foo_vst: VST 2.4 adapter
Post by: Propheticus on 18 February, 2013, 10:04:36 AM
The latest version of Foobar 1.2.3 does not play when resuming playback on restart while VSTs are loaded in my DSP chain using foo_vst 2.4 (using two VST plugins Electri-Q posihfopit and Headfit).


I got same crashes using this specific vst plugins, Electri-Q posihfopit. In my case, it is reproducible by changing the preset rapidly. I've never got this kind of crashes before, so I suspected it was the vst plugin.


Never had these crashes in earlier versions of Foobar though... Yet indeed, Electri-Q in this vst wrapper has always been a little buggy when loading/saving presets or opening and closing the configuration UI multiple times (opening too fast after closing).
Title: foo_vst: VST 2.4 adapter
Post by: Propheticus on 08 March, 2013, 04:09:44 PM
This problem still exists. I performed a bit of trial and error and found out the hang/crash* on restart only occurs when I'm using both foo_out_wasapi in EVENT mode AND foo_vst with actual VSTs loaded in the DSP chain.
Foobar does not crash when using either DirectSound or Wasapi PUSH mode output though.

Therefore, my current workaround for this problem is switching to push mode Wasapi output.



*even doing nothing at all and trying to close foobar will result in a 'program is not responding'...

Title: foo_vst: VST 2.4 adapter
Post by: Alexa on 08 March, 2013, 05:54:30 PM
It doesn't work with Ozone 5
Title: foo_vst: VST 2.4 adapter
Post by: DonGateley on 09 March, 2013, 04:32:21 PM
After reading the thread I am still confused about something.  Is it or is it not possible to have the controls of a VST plugin available in a window for tweaking while simultaneously having the controls of the fb2k main window available for controlling it?
Title: foo_vst: VST 2.4 adapter
Post by: Propheticus on 09 March, 2013, 05:46:28 PM
I've just tested this for you. Yes, you can control Foobar's main window while editing VST dsp settings. However, you cannot edit other settings or control the preferences window.
Title: foo_vst: VST 2.4 adapter
Post by: DonGateley on 09 March, 2013, 10:49:01 PM
I've just tested this for you. Yes, you can control Foobar's main window while editing VST dsp settings. However, you cannot edit other settings or control the preferences window.


Thanks for that.  I was doing something wrong.  With "Configure selected" I can get the plug's UI in a window and tweak it while I'm operating the main fb2k window just fine.  The only nag is that the Preferences:DSP Manager window is locked.  I guess that is standard fb2k operation when configuring any plug but it prohibits further manipulation of active plugins or their UI's.  Wish they'd fix that.  :-)

Title: foo_vst: VST 2.4 adapter
Post by: applegate on 26 May, 2013, 04:54:02 AM
VST plugin works great with Foobar200 version 1.26, ASIO on Windows 8 64 bits and GlissEQ (example filter: dynamic equalizer)

Title: foo_vst: VST 2.4 adapter
Post by: foomark on 27 May, 2013, 09:06:54 AM
Great component!! 

I'm just curious to know one thing now...what VST do you use the most? any recommended one?
Title: foo_vst: VST 2.4 adapter
Post by: J.Fleming on 05 June, 2013, 05:56:19 AM
Both zipped DLL attachments are corrupt. All unpackers report corrupted archive, as well as Foobar2000 1.2.4.

Please fix the attachments.
Title: foo_vst: VST 2.4 adapter
Post by: Propheticus on 05 June, 2013, 06:29:01 AM
unpacks without trouble here... I guess your browser/virusscanner is at fault.
Title: foo_vst: VST 2.4 adapter
Post by: Zippy7 on 03 August, 2013, 03:14:07 PM
When I only wanted to use one VST with foobar2000, I used George Yohng's VST Wrapper, which suited my needs.  When I wanted to add a second VST, I tried adding Acon Digital's EffectChainer.  However, I could not find a way to configure it so that the VST chain and all VST settings restore automatically when I run foobar2000.  Has anybody else figured out how to do this?

I replaced them both with Yegor Petrov's VST 2.4 adapter, and it is working fine for me.  I am using the ASIO output on foobar2000 v1.2.9, and I can close foobar2000 while a track is playing without any crash.  I like it that I can insert foobar2000 DSP in between VSTs in the chain.

If someone is having compatibility problems between Yegor's component and some VST, I wanted to offer another option.  You could use George Yohng's component for the problematic VST and use Yegor's component for the other VSTs.

My thanks to Yegor for developing this component!
Title: foo_vst: VST 2.4 adapter
Post by: foomark on 03 August, 2013, 04:30:44 PM
Any way to include a VST plugin inside a panel?
Maybe with WSH panel ??
Just wondering...i know that most of the plugin aren't resizable so i don't think it would be easy
Title: foo_vst: VST 2.4 adapter
Post by: Chodi on 13 January, 2014, 03:39:18 AM
I have this vst plugin working with foobar and TB Isone for use with headphones. It works great for me but I have a question about the channel selection that appears in the upper left corner of the TB Isone window when I use this plugin. I am only using the one dsp. In the upper left corner it lets me choose 1,2 or auto setting for channels. If I choose 1 it is obviously limiting things to something like mono. If I choose 2 it sounds clearly like two channels, but if I choose auto the sound stage expands in width and depth and opens considerably? I thought auto would be the same as "2" since I am only listening to 2 channel flac recordings. I don't understand why selecting 2 and selecting auto do not produce the same results? Further, if I select auto and then later exit the program, when I re-enter foobar it selects "2" rather than remembering I had it set for auto?

Any advice about this setting to be used with 2 channel recordings in foobar would be appreciated? I am particularly interested in why the 2 setting and auto setting sound different when I am only using 2 channel stereo recordings.
Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 13 January, 2014, 06:33:05 AM
I am particularly interested in why the 2 setting and auto setting sound different when I am only using 2 channel stereo recordings.


Might be some placebo. Anyways, just keep the 2 setting.

Title: foo_vst: VST 2.4 adapter
Post by: musicreo on 18 January, 2014, 05:35:29 AM
I have this vst plugin working with foobar and TB Isone for use with headphones. It works great for me but I have a question about the channel selection that appears in the upper left corner of the TB Isone window when I use this plugin. I am only using the one dsp. In the upper left corner it lets me choose 1,2 or auto setting for channels. If I choose 1 it is obviously limiting things to something like mono. If I choose 2 it sounds clearly like two channels, but if I choose auto the sound stage expands in width and depth and opens considerably?


I hear no difference between auto and 2 channels.
Title: foo_vst: VST 2.4 adapter
Post by: DonGateley on 23 February, 2014, 04:13:05 PM
It seems that to get a VST's GUI up I have to do File->Preferences->DSP Manager, click on the plug and select "Configure Selected".  At that point, however, the DSP Manager becomes inactive and immobile (which disallows player interraction if it opens over the player and you don't yet know to move it before opening the plug.) 

Is there a way to go back to the player with only the VST GUI active so that I can interact with it while using the player and not have the DSP Manager window cluttering things up or obscuring the player?

Even better, is there a way to bring up the VST GUI without all the rigamarole through menus and tabs to get there.  As it is the human factors of using VST plugins are horrible and not for the naive.  I understand the rigamarole for installation, but not for subsequent use.

I'd like to create an installable package of Foobar2000 with foo_vst and the VST plug I'm developing already included for users to evaluate but they are unlikely to understand or want to know anything about the rigamarole.  If this plug could add an item to Foobar2000's menu that says "VST" which presents a list of those installed and enabled that a user could just open and select the plugin of interest to bring up its GUI that would be an awesome usability enhancement.
Title: foo_vst: VST 2.4 adapter
Post by: dts350z on 28 February, 2014, 12:09:06 AM
It seems that to get a VST's GUI up I have to do File->Preferences->DSP Manager, click on the plug and select "Configure Selected".  At that point, however, the DSP Manager becomes inactive and immobile (which disallows player interraction if it opens over the player and you don't yet know to move it before opening the plug.) 

Is there a way to go back to the player with only the VST GUI active so that I can interact with it while using the player and not have the DSP Manager window cluttering things up or obscuring the player?

Even better, is there a way to bring up the VST GUI without all the rigamarole through menus and tabs to get there.  As it is the human factors of using VST plugins are horrible and not for the naive.  I understand the rigamarole for installation, but not for subsequent use.

I'd like to create an installable package of Foobar2000 with foo_vst and the VST plug I'm developing already included for users to evaluate but they are unlikely to understand or want to know anything about the rigamarole.  If this plug could add an item to Foobar2000's menu that says "VST" which presents a list of those installed and enabled that a user could just open and select the plugin of interest to bring up its GUI that would be an awesome usability enhancement.


View --> DSP --> VST name
Title: foo_vst: VST 2.4 adapter
Post by: dts350z on 28 February, 2014, 12:15:30 AM
I have a vst working fine for playback, but for conversion half the resulting file is science. The end of the file converts correctly.

Any suggestions?

Title: foo_vst: VST 2.4 adapter
Post by: DonGateley on 28 February, 2014, 12:43:10 AM
View --> DSP --> VST name


Now that's just too easy.  :-)

Thanks a lot.  Solves a big problem for me that you've shown me I didn't have. 

You've given me more motivation to RTFM.
Title: foo_vst: VST 2.4 adapter
Post by: zeremy on 15 April, 2014, 07:07:08 AM
Sharing Info:

If anyone is looking for a multichannel chainer (8 input - 8 output)
try Blue Cat's PatchWork

http://www.bluecataudio.com/Products/Product_PatchWork/ (http://www.bluecataudio.com/Products/Product_PatchWork/)

All vst loaded  in one interface ( pre,sided/parallel and post filters) and no 20 vst limit.



Title: foo_vst: VST 2.4 adapter
Post by: Sparktank on 15 April, 2014, 11:54:32 PM
Sharing Info:

If anyone is looking for a multichannel chainer (8 input - 8 output)
try Blue Cat's PatchWork

http://www.bluecataudio.com/Products/Product_PatchWork/ (http://www.bluecataudio.com/Products/Product_PatchWork/)

All vst loaded  in one interface ( pre,sided/parallel and post filters) and no 20 vst limit.


You mean: "anyone with money" ... Price: 59 EUR or $79 (excl. VAT

</h2>
Quote
<h2>Demo Limitations[/b]
  • One single instance of the plug-in per session.
  • The plug-in is regularly bypassed for a few seconds.
Title: foo_vst: VST 2.4 adapter
Post by: extrabigmehdi on 16 April, 2014, 08:10:13 AM
Quote
You mean: "anyone with money" ... Price: 59 EUR or $79 (excl. VAT


Yeah, not all vst are free. But frankly I  don't see why a foobar user would be interested by a "8 input/output chainer".

I find at least a modular vst host more interesting, you can do all kind of complicated mixing , with different dsp.
The console art teknika works well inside foobar with the vst adapter.
But most people are just interested to run an eq.
Title: foo_vst: VST 2.4 adapter
Post by: zeremy on 16 April, 2014, 03:22:19 PM
Quote
You mean: "anyone with money" ... Price: 59 EUR or $79 (excl. VAT


Yeah, not all vst are free. But frankly I  don't see why a foobar user would be interested by a "8 input/output chainer".

I find at least a modular vst host more interesting, you can do all kind of complicated mixing , with different dsp.
The console art teknika works well inside foobar with the vst adapter.
But most people are just interested to run an eq.


Yes.  most vst cost money, but as I said you could try the demo and do as you wish. I found it useful because it was the only chainer I found with multichannel support.
My interest is in multichannel music files (quad, surround)  and I can process each channel with vst in real-time playback to my surround system.
eg Boost the center channel (which usually has only vocals)  or the lfe channel for extra bass.

Listening to music recorded in true surround, is a must for the audio enthusiast.

ps.  console art techika is not free.
Title: foo_vst: VST 2.4 adapter
Post by: TranceAndAcid on 17 April, 2014, 01:04:45 PM
Hi,

great plugin, most things work for me. But I have one issue. When I use T-Racks Metering VST Plugin and close the plugin window and shut down Foobar, foo_vst.dll crashes everytime on startup when i want to restart Foobar and i have to delete foo_vst.dll to be able to launch Foobar.

When I use another (T-Racks) Plugin, that doesn't happen. It also doesn't crash on startup when I DO NOT close T-Racks Metering Window and only shut down Foobar.

Finally, as "workaround" I use to MINIMIZE Plugin Windows when not needed. Then everything is ok.
Title: foo_vst: VST 2.4 adapter
Post by: milavla on 28 November, 2014, 09:57:54 AM
Works someone MaxxBass from Waves ?
Title: foo_vst: VST 2.4 adapter
Post by: CedricM on 31 May, 2015, 01:08:43 PM
Something isn't working.

When I add ARC 2 from IK Multimedia (room correction), I have to choose a measurement in a list.

Clicking on an item of the list should let the plugin load a data file and make some calculations.

In foobar, I'm not sure an item is selected. If it is it does nothing so the addon doesn't work.

Having tried the blue cat's patchwork demo mentionend above, the ARC plugin does work there, I can select an item in the list and the plugin does work.

Can you fix the vst adapter pls?
Title: foo_vst: VST 2.4 adapter
Post by: Juha on 21 August, 2015, 10:09:27 AM
Sharing Info:  If anyone is looking for a multichannel chainer (8 input - 8 output)  try Blue Cat's PatchWork  http://www.bluecataudio.com/Products/Product_PatchWork/ (http://www.bluecataudio.com/Products/Product_PatchWork/)  All vst loaded  in one interface ( pre,sided/parallel and post filters) and no 20 vst limit.


Or maybe one of these:

Mutools MUX - http://www.mutools.com/mux-product.html (http://www.mutools.com/mux-product.html) (19€)

DDMF Metaplugin - http://www.ddmf.eu/product.php?id=3 (http://www.ddmf.eu/product.php?id=3) (49$)

Image-Line Minihost Modular - http://forum.image-line.com/viewtopic.php?...19&t=123031 (http://forum.image-line.com/viewtopic.php?f=1919&t=123031) (registering)

Here's MUX in action (stereo to 7.1 surround by FreeSurround component --> MUX VST (each mono channel monitored by SPAN) ... (just load EQ, Delay, what ever VST's you like to MUX ... ) -->):

(https://hydrogenaud.io/imgcache.php?id=e88dcd865de63962e6bcf4f71c8b3ce6" rel="cached" data-warn="External image, click to view at original size" data-url="http://i58.tinypic.com/11rpqh0.png)

Title: foo_vst: VST 2.4 adapter
Post by: friscom on 23 October, 2015, 04:35:49 AM
would it be possible to upload the original video (mentione din the inital post) explaining the installation process, or an updated one?
it is no more available.

thanks
Title: Re: foo_vst: VST 2.4 adapter
Post by: Möhre on 19 October, 2016, 09:41:51 AM
Doens't work anymore under Win 10 Pro x64. Crashes always =(
Title: Re: foo_vst: VST 2.4 adapter
Post by: Möhre on 19 October, 2016, 10:54:32 AM
Oh, I found a solution for the Melda Production VSTs with foobar2k v1.3.12!
- Get the latest version of Melda VSTs
- While in setup select only VST (no VST3, no AVX-whatever)
- Install it to the default path ("C:\Programs (x86)\vstPlugins\MeldaProduction")
- Create a "vst" folder within your foobar2k directory
- Go to the default path and copy the whole "MeldaProduction" folder into your "foobar2k/vst"
- Launch foobar2k
- In the menu select "Preferences/Components/VST-plugins" and add/update the paths for your VST plugins
- In the menu select "Preferences/Playback/DSP Manager" and there you go

Hope that helps someone!

Cheers!
Title: Re: foo_vst: VST 2.4 adapter
Post by: Ancipital on 30 December, 2016, 07:57:15 AM
I am finding that trying to make a preset in the presets panel causes the UI to go nuts. It becomes unresponsive, with the close button on the text entry popup flickering madly. In order to get the VST's UI under control, I have to kill Foobar and restart it. This happens with all the VSTs that I've tried, including EasyQ, Sonarworks and TDR Nova.

I also find that the host is pretty unstable in general, sometimes bringing up the UI of VSTs will just cause Foobar to crash to desktop.

I'm using up to date Win 10 x64, Foobar 1.3.14 (though the same happened with earlier versions) and foo_vst 0.9.0.3. I have let Foobar send a few crash longs, I don't know how helpful this is for you, though.

Edit: I notice that Foobar's "online troubleshooter" calls this plugin out too, so I guess the problems are a known thing- I assume it's abandoned?
Title: Re: foo_vst: VST 2.4 adapter
Post by: dekatch on 29 September, 2017, 01:00:56 PM
any vst users still out there? vst was an pretty neat feature. i specially always preferred that one tda 32 band geq which is just different to the 31band xgeq offered here in the components section.

ofc. the tda has its downsides.. however. it always worked like a charm with that vst 0903..


later i had that other vst plugin installed. one that you had to control via taskbar menu. didnt work for me at all.

but now i am stuck. my fb2k app crashes when trying to save new tda 32band geq presets. i recently wiped my drive and lost all my presets. now i can only use it on the fly. meaning i can not save any presets, but i can use it ...

and its still more convinient imo, since i can still use / navigate in the fb2k audio player while having an vst plugn opened and displayed. cant do that with the other 31 band xgeq from the components section one for example

please help me getting vst pluging fully working again. appreciate any help

(https://picload.org/infonail/dgowgirr/2017-09-298.jpg) (https://picload.org/view/dgowgirr/2017-09-298.png.html)
Title: Re: foo_vst: VST 2.4 adapter
Post by: darkflame23 on 29 September, 2017, 03:35:03 PM
It's always been like this, massive bug, whenever you try to do text/keyboard entry it hangs. Not been updated/fixed in forever, not likely to be, I imagine. Only workaround is to never use text entry, just use the knobs instead.

I for one would LOVE to see native VST support in FB2K.
Title: Re: foo_vst: VST 2.4 adapter
Post by: dekatch on 29 September, 2017, 09:11:35 PM
Only workaround is to never use text entry, just use the knobs instead.

yea that works. i control the knobs and save it as is. it saves the preset as "default" but later i can jusr rename the saved file within the presets folder of my plugin.

gosh that works as a workaround.

only need to re create like 10 profiles, then i am fine

(https://picload.org/thumbnail/dgowcpdw/2017-09-30.jpg) (https://picload.org/view/dgowcpdw/2017-09-30.png.html)

thanks darkflame23 :P