Downloads of v


Last Update:

22 Aug 2016

Package Maintainer(s):

Software Author(s):

  • Euphy Wong
  • Jasper Loo


viper sound card audio volume compressor equalizer bass reverb reverberation surround convolver


  • 1
  • 2
  • 3 | Updated: 22 Aug 2016



Downloads of v



Software Author(s):

  • Euphy Wong
  • Jasper Loo

  • 1
  • 2
  • 3

  • 1
  • 2
  • 3

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Installs drivers


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install ViPER4Windows, run the following command from the command line or from PowerShell:


To upgrade ViPER4Windows, run the following command from the command line or from PowerShell:


To uninstall ViPER4Windows, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade viper4windows -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade viper4windows -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install viper4windows
    name: viper4windows
    version: ''
    state: present

See docs at

chocolatey_package 'viper4windows' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller viper4windows
    Name     = "viper4windows"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'viper4windows':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 23 Aug 2016.


ViPER4Windows is an “APO”. APO stands for “Audio Processing Object”. APO is designed by Microsoft. It is an audio processing framework that can be loaded onto any sound card.
ViPER4Windows ViPER’s Audio audio driver for Windows PC OS.
It comes with many audio effects such as Gain Control, Equalizer, Convolver, Surround, Reverb, Compressor and Limiter.

$packageName = 'viper4windows'
$fileType = 'exe'
$url = ''
$scriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$ahkFile = "$scriptPath\viper4windowsinstall.ahk"

new-item "${env:temp}\viper4windows" -itemtype directory
$unpackfile = "${env:temp}\viper4windows\"
$unpackdir = "${env:temp}\viper4windows"
Get-ChocolateyWebFile $packageName $unpackfile $url -Checksum 642fe0c89e25792b9551b4b8d89f4aa091b1f081be94bee66d4dbdf526d9b949 -ChecksumType 'sha256'
Get-ChocolateyUnzip $unpackfile $unpackdir
$file = "${env:temp}\viper4windows\V4W_Setup_x86.exe"
$osBitness = Get-ProcessorBits
if ($osBitness -eq 64) {
  $file = "${env:temp}\viper4windows\V4W_Setup_x64.exe"
Start-Process 'AutoHotkey' $ahkFile	
Install-ChocolateyInstallPackage $packageName $fileType $silentArgs $file

Remove-Item $unpackdir -Recurse -Force

WinWait, ahk_class #32770, , 500
ControlClick, Button2, ahk_class #32770

WinWait, ahk_class #32770, , 500
ControlClick, Button1, ahk_class #32770

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
ViPER4Windows 1.0.5 666 Monday, May 18, 2015 Approved
Discussion for the ViPER4Windows Package

Ground Rules:

  • This discussion is only about ViPER4Windows and the ViPER4Windows package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or ViPER4Windows, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus