foo_vst: VST 2.4 adapter Reply #300 – 2011-08-31 12:58:29 Quote from: Yegor on 2011-04-24 05:57:54Quoteonly a slightly slower foobar startupYep, 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? Last Edit: 2011-08-31 12:59:53 by auditorium
foo_vst: VST 2.4 adapter Reply #301 – 2011-08-31 13:35:47 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.
foo_vst: VST 2.4 adapter Reply #302 – 2011-09-06 06:48:03 Thanks for the source.There's a developer to improve the Foobar2000 VST 2.4 adapter, in particular chapter GUI to look better? Last Edit: 2011-09-06 07:03:26 by compositore
foo_vst: VST 2.4 adapter Reply #303 – 2011-09-06 14:35:05 Quote from: compositore on 2011-09-06 06:48:03Thanks 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.
foo_vst: VST 2.4 adapter Reply #304 – 2011-09-11 13:40:42 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)?
foo_vst: VST 2.4 adapter Reply #305 – 2011-09-22 13:41:43 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.
foo_vst: VST 2.4 adapter Reply #306 – 2011-09-22 14:15:34 QuoteVoxengo 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:QuoteDisplay 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.
foo_vst: VST 2.4 adapter Reply #307 – 2011-09-22 17:42:50 It is there some way to integrate de vst adapter as a pannel on Defaul User Interface or Columns UI?YsRozzo
foo_vst: VST 2.4 adapter Reply #308 – 2011-09-24 11:36:50 Thank you for making this VST Adapterworking very well Foobar2k sounds much better now.........Thank you once again......Foobar2k v.1.1.8 finalDSP Setting - SoX Resampler 2x Best - VST VB-FFX4 to load DX FX (RComp, BBE, L2)Systems: - Audiotrak Prodigy HD2 - Wasapi Output 24bit - OpAmp 2xLT1364 + AD797-BR (browndog adapter) - DIY LM3886 Amp + Philips 6922 Tube Buffer - Wharfedale Diamond 9.1 (anniv) Speakers - Yamaha YST-SW325 Sub Last Edit: 2011-09-24 11:53:22 by Oery
foo_vst: VST 2.4 adapter Reply #309 – 2011-09-28 05:52:01 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!
foo_vst: VST 2.4 adapter Reply #310 – 2011-10-06 11:41:07 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.jpghttp://imageshack.us/photo/my-images/4/myfoobaro.jpg/
foo_vst: VST 2.4 adapter Reply #311 – 2011-10-06 14:06:57 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. Last Edit: 2011-10-06 14:07:42 by Yegor
foo_vst: VST 2.4 adapter Reply #312 – 2011-10-14 21:05:07 AllI 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.aspxPer the Allocator creator it should work, too:http://www.thuneau.com/forum/viewtopic.php...b45ca1597bbf4dbAny idea what's up?Thanks!Jim Last Edit: 2011-10-14 21:07:39 by jdubs
foo_vst: VST 2.4 adapter Reply #313 – 2011-10-14 21:15:33 Nevermind...did some more research. I got it working by copying msvcr71.dll to the Windows/SysWOW64 directory.-Jim Last Edit: 2011-11-21 16:53:18 by db1989
foo_vst: VST 2.4 adapter Reply #314 – 2011-10-30 04:50:04 Not surprizingly, the thing made its way to the troubleshooter. Well, any bridge like this would be doomed anyway.
foo_vst: VST 2.4 adapter Reply #315 – 2011-11-04 19:11:53 foobar2000 1.1.9--Online Troubleshooter:foo_vst.dll : VST 2.4 adapter 0.9.0.3Reason: Repeated crash reports. Last Edit: 2011-11-04 19:13:33 by Northtech
foo_vst: VST 2.4 adapter Reply #316 – 2011-11-15 21:29:41 Archive is corrupt in the op and the dll won't extract and can't be repaired.Please repack/repost. Last Edit: 2011-11-15 21:40:03 by raster43
foo_vst: VST 2.4 adapter Reply #317 – 2011-11-15 21:38:34 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.
foo_vst: VST 2.4 adapter Reply #318 – 2011-11-16 03:31:05 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?
foo_vst: VST 2.4 adapter Reply #319 – 2011-11-16 04:35:16 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.
foo_vst: VST 2.4 adapter Reply #320 – 2011-11-16 06:00:12 Well, I looked up in my back-ups and found all binaries starting from v0.5. I just thought they weren't backed up. Last Edit: 2011-11-16 06:01:09 by Yegor
foo_vst: VST 2.4 adapter Reply #321 – 2011-11-16 06:02:22 Hats off to you sir, with my most sincere thanks *bows down*
foo_vst: VST 2.4 adapter Reply #322 – 2011-11-16 15:13:31 Quote the Foobar "Online Help":foobar2000 troubleshooterThe 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.0Reason: Repeated crash reports.foo_vst.dll : VST 2.4 adapter 0.9.0.3Reason: Repeated crash reports.Do you have a fix for this?Bob
foo_vst: VST 2.4 adapter Reply #323 – 2011-11-16 16:09:24 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.
foo_vst: VST 2.4 adapter Reply #324 – 2011-11-16 16:30:02 Quote from: Yegor on 2011-11-16 16:09:24The 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