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.
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.
Will there be support for 64-bit VSTs?
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.
Maybe you could implement direct menu shortcuts to the configurations (like View->VST Wrapper->(vst plugin)) ?
Multichannel setup arrangement differences aren't taken into account, nor is VST pin activity statusNo support for plugins without GUI yetConfiguration windows only work in modal modez3ta_fx and IXL analyzers crashes the applicationAll of these are to be fixed soon.
Higher bitdepth processing will lower SNR for the particular opertation
it should be better if it can be done like this "source → 32 → 64 → N× [VST double] → 64 → 32 → output"
Multichannel setup arrangement differences aren't taken into account, nor is VST pin activity status
- it asks to restart foobar on VST removal - that is really unnecessary
It loaded almost all plug ins except iZOzone4.dll although iZotope Ozon4.dll works fine.
It would be nice to be able to display multiple windows of multiple plug ins.
What about no reload track switch, I'm waiting for this
maybe you should leave routing as is
Plogue Bidule isn't free but you can run with full capacity for month or so without any annoying popups or similar nonsense.
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!
Quote from: Sandrine on 27 November, 2010, 02:43:16 PMPlease 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.
16 and 32 channel Bidules should work now.
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.