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 expectedProblem is when trying to load DX effects: this component then crashes foobar, while foo_dsp_vstwrapper does not have this problem

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.

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.

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.