[wdmaudiodev] Re: Naive beginner with only a concept: front filter to use a VST plugin.
- From: Don Gateley <dongateley@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Tue, 7 May 2013 20:34:03 -0700
Thanks, Tim. I understand the need for an integrated, but simple, VST host
that uses the Steinberg API for this. My reason for wanting a
driver/device interface is not to do any low level kernel processing but
simply to give a user a familiar way to direct output to a DSP filter via
the "Windows Sound" control panel and to configure the plugin and real
output device via it. Is there a path to such a driver interface that
doesn't involve kernel mode (other than perhaps as a hidden bridge)? I
clearly misdirected my query. Can you suggest a forum or list more
appropriate?
Even though I am a programmer I am not capable of programming this myself.
I was in real time embedded control, not Windows development. I work at a
different level these days, audio DSP applications, and I want to explore
pulling together the necessary expertise to do something that I and
probably others would find useful both for development and deployment of
audio processing functions on Windows which is much less a kludge than what
is now required.
Thanks again.
On Tue, May 7, 2013 at 3:11 PM, Tim Roberts <timr@xxxxxxxxx> wrote:
> Don Gateley wrote:
> >
> > I would like a WDM front filter that is configurable to the extent of:
> >
> > 1) naming the path to my VST plugins directory,
> > 2) naming a single VST plugin to insert as a filter,
> > 3) naming a real audio device to receive the output and
> > 4) specifying parameters to the VST plugin and opening it's GUI.
> >
> > In my first usage it would name and utilize the PlogueBiduleVST plugin
> > which is an entire framework for building up more complex flows and
> > processes.
>
> VST plugins are user-mode modules. They're just DLLs. There's no
> kernel code involved, so WDM doesn't apply. At the bottom end, the
> hosting application pumps the resulting audio feed into the Audio Engine
> for rendering to a speaker, but there must BE a hosting application.
> They can't run on their own.
>
>
> > I am successfully doing this now via the Virtual Audio Cable and
> > VSTHost applications but would like to considerably simplify the
> > mechanism for use by others with a wish to filter Windows audio in a
> > general and flexible way.
>
> There's really no easier way to do this. You are trying to connect two
> incompatible audio worlds here, so you're always going to need an ugly
> adapter plate. That's what VAC is doing for you. Even if you made your
> own VAC clone, you can't load user-mode DLLs in the kernel, and you
> can't do UI stuff from the kernel. You'd still have to have the VAC
> clone pipe the data to a VST host of some kind.
>
> --
> Tim Roberts, timr@xxxxxxxxx
> Providenza & Boekelheide, Inc.
>
> ******************
>
> WDMAUDIODEV addresses:
> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
> Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
> Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
>
> URL to WDMAUDIODEV page:
> http://www.wdmaudiodev.com/
>
>
Other related posts:
