Hi Melowin, Thanks for getting back to me :)
Perhaps I wasn't clear enough on the steps I have already taken, apologies.
Troubleshooter was our first port of call, didn't fix it, have run a number of times.
Went to Device Manager & uninstalled Intel SST Audio Device & it disappears from list, reboot & it just comes back in device manager list again with exclamation mark.
Uninstalled driver & tried to re-installed manually as automatic install option said latest driver was already installed - states Windows cannot verify the digital signature for the drivers required, recent hardware or software change might have installed a file that is signed incorrectly or damaged or that might be malicious software etc (code 52).
Performed virus scan - nothing comes up.
Sorry typo on Windows version - should have been Windows 8 and the version 6.3 (build 9600).
Zoo tycoon 2: Marine Mania introduce you into a new water world you will love for sure. And if you think that's all, try going for a swim accompained by your beloved animals. Now it's time for the feisty rockhopper penguin, the fun-loving sea otter, and the fearsome white shark. Zoo tycoon 2 marine download completo.
When I googled the issue, another thread came up on this site talking about the registry file being missing, but looks like the discussion then went off to PM, so no resolution was posted.
Any other suggestions?
-->A Microsoft Windows Driver Model (WDM) audio driver provides the following functionality:
- The driver exposes all the types of input and output streams, and the number of instances of each stream type that it can support. The driver provides this information in the form of a set of pin factories and the number of pins that each factory can instantiate. For example, a simple audio device might input a single PCM audio stream and output a single PCM audio stream. The filter for this device contains two pin factories--one for the input stream an one for the output stream--and each pin factory supports only a single pin instance. If the adapter card contains only one of these devices, the adapter driver provides a filter factory containing only a single instance of a filter with these capabilities.
- The driver supports one or more property sets. For example, all audio drivers should support KSPROPSETID_Audio, but some audio drivers might support additional property sets as well. Clients of the driver use property requests both to discover a filter's capabilities and to change the filter's configurable settings.
- The driver optionally supports a hardware clock. This clock should be readable and writable so that streams can synchronize with other streams on the same or different hardware. For additional information, see KSPROPSETID_Clock.
- The driver optionally supports other media interfaces, such as KSINTERFACE_STANDARD_STREAMING, KSINTERFACE_MEDIA_WAVE_QUEUED, or KSINTERFACE_STANDARD_LOOPED_STREAMING.
ASIO logo
Audio Stream Input/Output (ASIO) is a computer sound card driver protocol for digital audio specified by Steinberg, providing a low-latency and high fidelity interface between a software application and a computer's sound card. Whereas Microsoft's DirectSound is commonly used as an intermediary signal path for non-professional users, ASIO allows musicians and sound engineers to access external hardware directly.
- 1Overview
Overview[edit]
ASIO bypasses the normal audio path from a user application through layers of intermediary Windows operating system software so that an application connects directly to the sound card hardware. Each layer that is bypassed means a reduction in latency (the delay between an application sending audio information and it being reproduced by the sound card, or input signals from the sound card being available to the application). In this way ASIO offers a relatively simple way of accessing multiple audio inputs and outputs independently.
What Is Wdm Audio Drivers
Operating systems[edit]
Interface support is normally restricted to Microsoft Windows. Starting with Windows Vista, KMixer has been removed and replaced by WASAPI and a new WaveRT port driver.
As of 2007 there is also an experimental ASIO driver for Wine, a Windows compatibility layer for Linux. This wineasio driver uses the JACK sound server as its audio back-end and allows many ASIO-aware applications to run with low latency under WINE.
Usage limitation[edit]
Being a proprietary protocol, compatibility with Windows-based DAW and other recording software is not universal. For example, the user manual of the Audacity audio editor states: 'Licensing restrictions prevent us including ASIO support in released versions of Audacity, but Audacity can be compiled with ASIO support for private, non-distributable use.'[1]
A popular alternative is to use the ASIO4All driver by German programmer Michael Tippach, which can often deliver low latency on soundcards that have not been designed with music production in mind.[citation needed][2]
See also[edit]
Wdm Ks
- JUCE – an open-source C++ toolkit that includes support for ASIO audio devices.
References[edit]
- ^'ASIO Audio Interface'. 2008. Retrieved 16 February 2014.
- ^http://www.asio4all.com/
External links[edit]
- ASIO4ALL, hardware-independent ASIO driver for WDM audio devices
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Audio_Stream_Input/Output&oldid=875715255'
In computing, the Windows Driver Model (WDM) – also known at one point as the Win32 Driver Model – is a framework for device drivers that was introduced with Windows 98 and Windows 2000 to replace VxD, which was used on older versions of Windows such as Windows 95 and Windows 3.1, as well as the Windows NT Driver Model.
- 1Overview
Overview[edit]
WDM drivers are layered in a stack and communicate with each other via I/O request packets (IRPs). The Microsoft Windows Driver Model unified driver models for the Windows 9x and Windows NT product lines by standardizing requirements and reducing the amount of code that needed to be written. WDM drivers will not run on operating systems earlier than Windows 98 or Windows 2000, such as Windows 95, Windows NT 4.0 and Windows 3.1. By conforming to WDM, drivers can be binary compatible and source-compatible across Windows 98, Windows 98 Second Edition, Windows Me, Windows 2000, Windows XP, Windows Server 2003 and Windows Vista (for backwards compatibility) on x86-based computers. WDM drivers are designed to be forward-compatible so that a WDM driver can run on a version of Windows newer than what the driver was initially written for, but doing that would mean that the driver cannot take advantage of any new features introduced with the new version. WDM is generally not backward-compatible, that is, a WDM driver is not guaranteed to run on any older version of Windows. For example, Windows XP can use a driver written for Windows 2000 but will not make use of any of the new WDM features that were introduced in Windows XP. However, a driver written for Windows XP may or may not load on Windows 2000.
WDM exists in the intermediary layer of Windows 2000 kernel-mode drivers and was introduced to increase the functionality and ease of writing drivers for Windows. Although WDM was mainly designed to be binary and source compatible between Windows 98 and Windows 2000, this may not always be desired and so specific drivers can be developed for either operating system.
Device kernel-mode drivers[edit]
With the Windows Drivers Model (WDM) for devices Microsoft implements an approach to kernel mode drivers that is unique to Windows operating systems. WDM implements a layered architecture for device drivers, and every device of a computer is served by a stack of drivers. However, every driver in that stack can chain isolate hardware independent features from the driver above and beneath it. So drivers in the stack do not need to interact directly with one another. WDM defines architecture and device procedures for a range of devices, such as display and the network card, known as Network Driver Interface Specification (NDIS). In the NDIS architecture the layered network drivers include lower-level drivers that manage the hardware and upper-level drivers that implement network data transport, such as the Transmission Control Protocol (TCP).[1]
All known locations on the map World Map / Bohemia Ancient Treasure IA grave. DLC is NOT required to find and pick up these treasures! Kingdom come deliverance world map. Dig it up.Required equipment: SpadeRewards: Decorated riding boots (647), German bascinet (790), Groschen (217.8), Lucky playing die (50), Recipe for poison (650), Silver Ring (184), Stinger (1.8k), Warhorse pauldrons (1), Warhorse waffenrock (1). You can head straight to the treasure location and pick it up without the map.Ancient Treasure Maps are included in a DLC pack called Treasures of the Past, and will automatically appear in your inventory when that DLC is installed. Ancient Treasure IIA sack inside a collapsed mine.Required equipment: -Rewards: Ash Longbow (497.2), Decorated German bascinet (1k), Fashionable slippers (463.5), Groschen (308.2), Heavenly Kingdom die (100), Marathon IV (1.3k), Plate jack dyed (925.2), Recipe for Artemisia potion (520), Warhorse gambeson chausses (1), Warhorse gauntlets (1).Ancient Treasure IIIA grave.
While WDM defines three types of device drivers, not all driver stacks for a given device contain all types of device drivers. The three WDM device driver types are:[2]
Bus driver: For every bus on the mainboard there is a one bus driver, with the primary responsibility for the identification of all devices connected to that bus and responding to plug and play events. Microsoft will provide bus drivers as part of the operating system,[3] such as PCI, PnPISA, SCSI, USB and FireWire.
Function driver: this is the principal driver for a device and it provides the operational interface for a device by handling read and write operations. Function drivers are written by the device vendors, and for their interaction with the hardware they depend on a specific bus driver being present in the Windows operating system.[4]
Filter driver: This driver is optional, and can modify the behaviour of a device, such as input and output requests. These drivers can be implemented as lower-level and upper-level filter drivers.[5]
Object orientated driver stack[edit]
Function drivers and bus drivers are often implemented as driver/minidriver pairs, which in practice is either a class/miniclass or a port/miniport pair.[6]
Bus drivers for devices attached to a bus are implemented as class drivers and are hardware-agnostic. They will support the operations of a certain type of device. Windows operating systems include a number of class drivers, such as the kbdclass.sys driver for keyboards. Miniclass drivers on the other hand are supplied by the vendor of a device, and only support device specific operations, for a particular device of a given class.[7]
Port drivers support general input/output (I/O) operations for a peripheral hardware interface. The core functionality of port drivers is mandated by the operating system, and Windows operating systems integrate a variety of port drivers. For example, the i8042prt.sys port driver for the 8042 microcontroller connects PS/2 keyboards to the mainboard peripheral bus. The miniport drivers, like the miniclass drivers, are supplied by the hardware vendors and support only device specific operations of peripheral hardware that is connected to a port on the mainboard.[8]
Each driver that processes an I/O request for a device has a corresponding object, which is loaded into main memory. A device object is created by the Windows operating system from the associated device class. Device objects contain structures of type DEVICE_OBJECT, which store pointers to their driver. At run time these pointers are used to locate a driver's dispatch routine and member functions. In the WDM driver stack, the filter driver device object, known as the upper filter, will receive an I/O request packet (IRP) for a device from the I/O manager. If the upper filter driver can not serve the request, it will locate the object of the driver one step down in the driver stack. The IRP is passed down the driver stack by calling the function IoCallDrive(), and processed by the function driver device object, also known as functional device object. The function driver device object in turn may pass the IRP to the lower filter, another filter device object. Then the IRP may be passed down to the bus driver, which operates as the physical device object. The bus driver object is at the bottom of the driver stack, and interacts with the hardware abstraction layer, which is part of the Windows operating system kernel and allows Windows operating systems to run on a variety of processors, different memory management unit architectures, and a variety of computer systems with different I/O bus architectures.[9] The execution of an IRP is finished when any of the driver objects in the stack returns the request back to the I/O manager, with the result and a status flag.[10]
Device drivers for different Windows operating systems[edit]
The WDM framework was developed by Microsoft to simplify the communication between the operating system and drivers inside the kernel. In Windows operating systems, drivers are implemented as Dynamic Link Libraries .DLL or .SYS files. WDM compliant drivers must follow rules of design, initialisation, plug-and-play, power management and memory allocation. In practice WDM driver programmers reuse large pieces of code when building new object orientated drivers. This means that drivers in the WDM stack may contain residual functionality, which is not documented in specifications.[11] Drivers that have passed the Microsoft quality test are digitally signed by Microsoft. The Microsoft Hardware Compatibility Tests and the Driver Development Kit include reliability and stress tests.[12]
A device driver that is not designed for a specific hardware component may allow another device to function. This is because the basic functionality of a hardware device class is similar. The functionality of the video card class, for example, allows the Microsoft Basic Display Adapter driver to work with a wide variety of video cards. However, installing the wrong driver for a device will mean that the full functionality of the device can not be used, and may result in poor performance and the destabilization of the Windows operating system. Hardware device vendors may release updated device drivers for particular Windows operating systems, to improve performance, add functionality or fix bugs. If a device is not working as expected the latest device drivers should be downloaded from the vendor website and installed.[13]
Device drivers are designed for particular Windows operating system versions, and device drivers for a previous version of Windows may not work correctly or at all with other versions. Because many device drivers run in kernel mode installing drivers for a previous operating system version may destabilise the Windows operating system. Migrating a computer to a higher version of a Windows operating system therefore requires that new device drivers are installed for all hardware components. Finding up to date device drivers and installing them for Windows 10 has introduced complications into the migration process.[14]
Common device driver compatibility issues include: a 32-bit device driver is required for a 32-bit Windows operating system, and a 64-bit device driver is required for a 64-bit Windows operating system. 64-bit device drivers must be signed by Microsoft, because they run in kernel mode and have unrestricted access to the computer hardware. For operating systems prior to Windows 10 Microsoft allowed vendors to sign their 64-bit drivers themselves, assuming vendors had undertaken compatibility tests. However, Windows 10 64-bit drivers now need to be signed by Microsoft. Therefore device vendors have to submit their drivers to Microsoft for testing and approval. The driver installation package includes all files in the .inf directory, and all files in the package need to be installed, otherwise the installation of the device driver may fail. For operating system versions before Windows 10 not all files necessary for the driver installation were included in the package, as this requirement was not consistently enforced. Some device driver installers have a user interface GUI, often requiring user configuration input. The absence of a user interface does not mean that the installation of the device driver is not successful. Besides, Windows 10 device drivers are not allowed to include a user interface. The Network Driver Interface Specification (NDIS) 10.x is used for network devices by the Windows 10 operating system. Network device drivers for Windows XP use NDIS 5.x and may work with subsequent Windows operating systems, but for performance reasons network device drivers should implement NDIS 6.0 or higher.[15] Similarly, WDDM is the driver model for Windows Vista and up, which replaces XPDM used in graphics drivers.
Device Manager[edit]
The Device Manager is a Control Panel applet in Microsoft Windows operating systems. It allows users to view and control the hardware attached to the computer. It allows users to view and modify hardware device properties, and is also the primary tool to manager device drivers.[16]
Criticism[edit]
The Windows Driver Model, while a significant improvement over the VxD and Windows NT Driver Model used before it, has been criticised by driver software developers,[17] most significantly for the following:
- Interactions with power management events and plug and play are difficult. This can lead to situations where Windows machines cannot enter or exit sleep modes correctly due to bugs in driver code.
- I/O cancellation is difficult to get right.[18]
- Complex boilerplate support code is required for every driver.
- No support for writing pure user-mode drivers.
There were also a number of concerns about the quality of documentation and samples that Microsoft provided.
Because of these issues, Microsoft has released a new set of frameworks on top of WDM, called the Windows Driver Frameworks (WDF; formerly Windows Driver Foundation), which includes Kernel-Mode Driver Framework (KMDF) and User-Mode Driver Framework (UMDF). Windows Vista supports both pure WDM and the newer WDF. KMDF is also available for download for Windows XP and even Windows 2000, while UMDF is available for Windows XP and above.
See also[edit]
- Windows Driver Frameworks (WDF)
- Kernel-Mode Driver Framework (KMDF)
- User-Mode Driver Framework (UMDF)
- Windows Display Driver Model (WDDM)
References[edit]
- ^Marco Vieira & Joao Carlos Cunha, eds. (2013). Dependable Computing: 14th European Workshop, EWDC 2013, Coimbra, Portugal, May 15-16, 2013, Proceedings. Springer. p. 64. ISBN9783642387890.CS1 maint: Uses editors parameter (link)
- ^Marco Vieira & Joao Carlos Cunha, eds. (2013). Dependable Computing: 14th European Workshop, EWDC 2013, Coimbra, Portugal, May 15-16, 2013, Proceedings. Springer. p. 64. ISBN9783642387890.CS1 maint: Uses editors parameter (link)
- ^Marco Vieira & Joao Carlos Cunha, eds. (2013). Dependable Computing: 14th European Workshop, EWDC 2013, Coimbra, Portugal, May 15-16, 2013, Proceedings. Springer. p. 64. ISBN9783642387890.CS1 maint: Uses editors parameter (link)
- ^Marco Vieira & Joao Carlos Cunha, eds. (2013). Dependable Computing: 14th European Workshop, EWDC 2013, Coimbra, Portugal, May 15-16, 2013, Proceedings. Springer. p. 64. ISBN9783642387890.CS1 maint: Uses editors parameter (link)
- ^Marco Vieira & Joao Carlos Cunha, eds. (2013). Dependable Computing: 14th European Workshop, EWDC 2013, Coimbra, Portugal, May 15-16, 2013, Proceedings. Springer. p. 64. ISBN9783642387890.CS1 maint: Uses editors parameter (link)
- ^Bill Blunden (2009). The Rootkit Arsenal: Escape and Evasion. Jones & Bartlett Publishers. p. 460. ISBN9781449661229.
- ^Bill Blunden (2009). The Rootkit Arsenal: Escape and Evasion. Jones & Bartlett Publishers. p. 460. ISBN9781449661229.
- ^Bill Blunden (2009). The Rootkit Arsenal: Escape and Evasion. Jones & Bartlett Publishers. p. 460. ISBN9781449661229.
- ^Bill Blunden (2009). The Rootkit Arsenal: Escape and Evasion. Jones & Bartlett Publishers. pp. 460–461. ISBN9781449661229.
- ^Dave Penkler, Manfred Reitenspiess & Francis Tam, eds. (2006). Service Availability: Third International Service Availability Symposium, ISAS 2006, Helsinki, Finland, May 15-16, 2006, Revised Selected Papers. Springer Science & Business Media. p. 124. ISBN9783540687245.CS1 maint: Uses editors parameter (link)
- ^Dave Penkler, Manfred Reitenspiess & Francis Tam, eds. (2006). Service Availability: Third International Service Availability Symposium, ISAS 2006, Helsinki, Finland, May 15-16, 2006, Revised Selected Papers. Springer Science & Business Media. p. 124. ISBN9783540687245.CS1 maint: Uses editors parameter (link)
- ^Dave Penkler, Manfred Reitenspiess & Francis Tam, eds. (2006). Service Availability: Third International Service Availability Symposium, ISAS 2006, Helsinki, Finland, May 15-16, 2006, Revised Selected Papers. Springer Science & Business Media. p. 132. ISBN9783540687245.CS1 maint: Uses editors parameter (link)
- ^Byron Wright & Leon Plesniarski (2016). Microsoft Specialist Guide to Microsoft Windows 10 (Exam 70-697, Configuring Windows Devices). Cengage Learning. p. 96. ISBN9781285868578.CS1 maint: Uses authors parameter (link)
- ^Byron Wright & Leon Plesniarski (2016). Microsoft Specialist Guide to Microsoft Windows 10 (Exam 70-697, Configuring Windows Devices). Cengage Learning. p. 96. ISBN9781285868578.CS1 maint: Uses authors parameter (link)
- ^Byron Wright & Leon Plesniarski (2016). Microsoft Specialist Guide to Microsoft Windows 10 (Exam 70-697, Configuring Windows Devices). Cengage Learning. p. 96. ISBN9781285868578.CS1 maint: Uses authors parameter (link)
- ^Byron Wright & Leon Plesniarski (2016). Microsoft Specialist Guide to Microsoft Windows 10 (Exam 70-697, Configuring Windows Devices). Cengage Learning. p. 96. ISBN9781285868578.CS1 maint: Uses authors parameter (link)
- ^Oney, Walter (May 6, 2003). 'Introducing Windows Driver Framework'. Windows Driver Developer's Digest. Vol. 1 no. 3. Archived from the original on 2016-01-25.
- ^'I/O Completion/Cancellation Guidelines'. MSDN. Microsoft. May 5, 2003. Retrieved 2018-02-08.
- Finnel, Lynn (2000). MCSE Exam 70-215, Microsoft Windows 2000 Server. Microsoft Press. ISBN1-57231-903-8.
- Oney, Walter (2003). Programming the Windows Driver Model, Microsoft Press, ISBN0-7356-1803-8.
External links[edit]
- WDM Input Output Concepts - This article gives a high level overview of the I/O concepts as defined in the Windows Driver Model.
- Windows driver API basics - This article informs you about the basics behind soundcard drivers such as WDM, ASIO, MME, DirectX, etc.
- Channel 9 Video - Interview with the Device Management and Installation team at Microsoft, primarily covering Plug-and-play.
- Lecture Notes on Windows Kernel Programming at the Wayback Machine (archived 2016-03-03) - Free lecture notes book fragment detailing basic creation of Windows Drivers, Kernel Mode programming, and Memory management
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Windows_Driver_Model&oldid=878077115'
Is there any (possibly free or open-source) virtual WDM audio driver for Windows, with additional processing plugins, which would add one more layer between windows applications and actual sound card's audio driver, allowing to:
- Add software DSPs to general audio output. I would like to be able to use custom effects, like compressor, or stereophonic-to-binaural converter for listening online streaming media on headphones, etc.
- Connect its output to some custom buffer instead of the sound card. For example, to be able to record audio, or to send audio via wireless connection to some other wireless source?
I know only about VAC driver, but don't know how I would use it to do any of these tasks. And unfortunately it is not free.
Also, audio driver was just my idea how to solve these issues - if you know other way, please share your knowledge.
I need this for Windows 7 and/or Windows XP.
Ognjen
OgnjenOgnjen29411 gold badge44 silver badges1212 bronze badges
closed as off-topic by Nifle, bwDraco, mdpc, fixer1234, DavidPostill♦Feb 6 '15 at 6:20
Windows Wdm Ks
This question appears to be off-topic. The users who voted to close gave this specific reason:
- 'Questions seeking product, service, or learning material recommendations are off-topic because they become outdated quickly and attract opinion-based answers. Instead, describe your situation and the specific problem you're trying to solve. Share your research. Here are a few suggestions on how to properly ask this type of question.' – Nifle, bwDraco, mdpc, fixer1234, DavidPostill
6 Answers
There is now a free (donationware) alternative to VAC Virtual Audio Cable. Check out VB-Audio Virtual Cable.
There are 32 bit and 64 bit drivers available to support one virtual cable. This cable appears to support 8 channels (7.1 surround) can handle 96kHz sample rate, and has an adjustable buffer size.
BradBrad3,52344 gold badges3434 silver badges6363 bronze badges
Then there are several drivers working even without any physical sound card present:
- e2eSoft VSC - Virtual Sound Card http://www.e2esoft.cn/vsc/
- ShiningMorning's Virtual Audio Streaming http://www.virtualaudiostreaming.net/
but these two have no ability to apply effects, AFAIK.
saulius2saulius2
Tf2 upgrade to premium free download. I've found a free open source API called Jack that appears to allow for both of what you've requested.
There are a number of applications that make use of Jack that offer what you've requested.
From their site:
JACK is system for handling real-time, low latency audio (and MIDI). It runs on GNU/Linux, Solaris, FreeBSD, OS X and Windows (and can be ported to other POSIX-conformant platforms). It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a 'plugin'). JACK also has support for distributing audio processing across a network, both fast & reliable LANs as well as slower, less reliable WANs.
I'm interested to know if this works for what you are doing.
slhck167k4848 gold badges466466 silver badges482482 bronze badges
nathanm412nathanm412
If you can deal with support for Windows Vista and later only, you can program in custom effects to the audio stack (the audio device graph, hosted by
audiodg.exe
)directly for applications using the following APIs:- WinMM (the oldest and most compatible sound API on Windows)
- DirectSound
- WASAPI in Shared mode
The following are unsupported:
- Kernel Streaming (KS)
- WASAPI in Exclusive mode
- ASIO
The feature that allows you to program your own filters is called
Audio Processing Objects
and more info is available from Microsoft here (should be a stable link) with more detail here.Note that all of this is laughably easy with Gstreamer and Pulseaudio on Linux; if you can get a similar stack to become the backend for all Windows audio, you won't have to do all the ugly machinations of a sAPO implementation.
allquixoticallquixotic31k66 gold badges9797 silver badges130130 bronze badges
Non-free but maybe useful for effects -- DMMF Virtual Audio Stream. Also, there is Dante Virtual Sound Card. Have you found anything useful by this time?
Linger2,8261010 gold badges2828 silver badges4040 bronze badges
saulius2saulius2
One way to accomplish the same thing; although it is not technically what you are asking for, is to use a virtual audio loopback device such as Virtual Audio Cable. Such software creates new virtual send and receive devices that can be used to take e.g. the default Windows sound device output, set to a virtual device, and send it to an audio processing application. Thus, the plug-in is not in the driver, but you can still get yer fx by sending sound to the default sound device. You then should use an ASIO driver for low latency. If your sound-card is not an audiophile device, then it probably doesn't come with an ASIO driver; although I suggest you check anyway. If it does not, use ASIO4ALL, which provides an ASIO driver for almost all audio devices. You will then need a platform that speaks ASIO, and as such, probably uses VST effects. Protools can als probably be used, but is overkill for this application. Reaper is one inexpensive possibility; and it has a non-expiring demo. There are free ones, as well. What is crucial here, is that it can do real-time audio effects, since e.g. not all wave file editors can. You then start the application, create a track, select your loopback device for the input and yer sound-card's ASIO driver for the output, plug in your VST effect (Reaper comes with a nice assortment of simple fx), and enable monitoring on the track (check the help for info on doing this). It sounds involved, but can actually be started pretty quickly. Reaper even reloads the last used project by default.
CodeLurkerCodeLurker