Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

1,428

Downloads of v 2.13.0:

33

Last Update:

31 Oct 2024

Package Maintainer(s):

Software Author(s):

  • Voxengo

Tags:

voxengo beeper noise beep vst aax audio mixing mastering recording free

Voxengo Beeper

  • 1
  • 2
  • 3

2.13.0 | Updated: 31 Oct 2024

Downloads:

1,428

Downloads of v 2.13.0:

33

Maintainer(s):

Software Author(s):

  • Voxengo

Voxengo Beeper 2.13.0

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Voxengo. The inclusion of Voxengo trademark(s), if any, upon this webpage is solely to identify Voxengo goods or services and not for commercial purposes.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Exemption for this package version only:

Package Scanner thinks there should be more files to scan than there actually are, this is an issue with the service and not this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

To uninstall Voxengo Beeper, 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 https://community.chocolatey.org/api/v2/)


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 https://community.chocolatey.org/api/v2/. 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 voxengo-beeper -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 voxengo-beeper -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install voxengo-beeper
  win_chocolatey:
    name: voxengo-beeper
    version: '2.13.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'voxengo-beeper' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.13.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller voxengo-beeper
{
    Name     = "voxengo-beeper"
    Version  = "2.13.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'voxengo-beeper':
  ensure   => '2.13.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator Windos on 12 Nov 2024.

Description

Beeper is an auxiliary audio processing AAX, AudioUnit and VST plugin which you can use to insert short beep, noise burst or silence signals to any sound material. This plugin may help you protect your work from unauthorized use. It is safe to apply this plugin to any mission-critical material because plugin does not perform any processing on the audio between the inserted signals.

You may specify signal’s duration, beep frequency, signal’s loudness, period between signals and the amount of random variation of all parameters.

Package Specific

Package Parameters

The following package parameters can be set:

  • /NoVst2x86 - Do not install the x86 VST2 version
  • /NoVst2x64 - Do not install the x64 VST2 version
  • /NoVst3x86 - Do not install the x86 VST3 version
  • /NoVst3x64 - Do not install the x64 VST3 version
  • /NoAaxx86 - Do not install the x86 AAX version
  • /NoAaxx64 - Do not install the x64 AAX version
  • /NoShortcuts - Do not install shortcuts to manuals and uninstaller into start menu or onto desktop
  • /Vst2Path: - Installation path of the VST2 version
  • /Vst2x86Path: - Installation path of the x86 VST2 version on x64 CPU architecture
  • /InstallerPath: - Do not download the installer from the official Voxengo website and use the one passed with this argument instead. Use it, if you don't have an internet connection at your studio computer.
  • /CompanyPath: - Path of the company to put all program files in. Override if you want to have the program files at a custom location.

You must pass the package parameters like this:

$VST2x86 = [System.Environment]::GetEnvironmentVariable('CommonProgramFiles(x86)') + "\VST2\Voxengo"
choco install voxengo-beeper --package-parameters "'/NoVst2x64 /Vst2x86Path:$VST2x86 '"

tools\.skipAutoUninstall
 
tools\chocolateyfunctions.ps1
# Installer Functions

<#
.SYNOPSIS
Checks for default installer values
#>
function GetDefaultValues () {
  $newDefaultPath = GetDefaultVst2Directory(64)
  If (![string]::IsNullOrWhiteSpace($newDefaultPath)) {
    Write-Debug("Default VST2 64 Path found: " + $newDefaultPath)
    $global:vst2DefaultPath = $newDefaultPath
  }
  $newDefaultPath = GetDefaultVst2Directory(32)
  If (![string]::IsNullOrWhiteSpace($newDefaultPath)) {
    Write-Debug("Default VST2 32 Path found: " + $newDefaultPath)
    $global:vst2x86_64DefaultPath = $newDefaultPath
  }
}
<#
.SYNOPSIS
If default values were found (for instance in the registry) and no overrides have been given, set default installer settings

.DESCRIPTION
If default values were found (for instance in the registry) and no overrides have been given, set default installer settings

#>
function PickDefaultValuesFromSystem () {
  If ([string]::IsNullOrWhiteSpace($pp["Vst2Path"])) {
    If (![string]::IsNullOrWhiteSpace($global:vst2DefaultPath)) {
      Write-Debug("Overwriting VST2 path with value found in registry: " + $vst2DefaultPath)
      $global:vst2Path = $global:vst2DefaultPath
    }
  }

  If ([string]::IsNullOrWhiteSpace($pp["Vst2x86Path"])) {
    If (![string]::IsNullOrWhiteSpace($global:vst2x86_64DefaultPath)) {
      Write-Debug("Overwriting VST2x86 path with value found in registry: " + $global:vst2x86_64DefaultPath)
      $global:vst2x86_64Path = $global:vst2x86_64DefaultPath
    }
  }

  If ($pp["CompanyPath"] -eq $false) {
    # Some installers have an automatic detection mechanism for this path next to a default
    Write-Debug "Checking if automatic install path detection is implemented ..."
    if (Get-Command InstallerCompanyPathAutomaticDetection -errorAction SilentlyContinue) {
      Write-Debug "Method has been implemented!"

      InstallerCompanyPathAutomaticDetection
      If ($autoInstDetectionCompanyPath) {
        Write-Debug("AutoInstDetectionCompanyPath: " + $autoInstDetectionCompanyPath)
        $global:companyPath = $autoInstDetectionCompanyPath
      }
    }
  }
}

<#
.SYNOPSIS
Checks if a given path is a kind of link and returns its value resolved

.DESCRIPTION
Checks if a given path is a kind of link and returns its value resolved. Also returns the path if it's a directory or a file. Returns $null if it doesn't exist.

.NOTES
Comment added because reviewer asked to do so.
#>
function ResolvePath($target) {
  $targetpath = $null

  If (!(Test-Path $target)) {
    Write-Debug ("Ended prematurely")
    Write-Debug ("$targetpath")
    return $targetpath
  }

  if($target.EndsWith(".lnk")) {
    $sh = new-object -com wscript.shell
    $fullpath = resolve-path $target
    $targetpath = $sh.CreateShortcut($fullpath).TargetPath
    Write-Debug ("Target ended with lnk and is " + "$targetpath")
    return $targetpath
  }

  If ((Get-ItemPropertyValue -Path $target -Name LinkType) -eq "SymbolicLink") {
    return $targetpath = Get-ItemPropertyValue -Path $target -Name Target
  } ElseIf (Test-Path $target -pathType leaf) {
    return $targetpath = (Get-Item $target).DirectoryName
  } ElseIf (Test-Path $target -pathType container) {
    return $targetpath = $target
  }

  Write-Debug ($targetpath)
  return $targetpath
}

<#
.SYNOPSIS
Checks if given an array of paths has an entry with a kind of link and returns the first value resolved

.DESCRIPTION
Checks if a given an array of paths it checks for link and returns the first value resolved. Also returns the first path if it's a directory or a file. Returns $null if nothing exists.

.NOTES
Comment added because reviewer asked to do so.
#>
function ResolvePaths([String[]] $Paths) {
  Foreach ($path in $Paths) {
    If (ResolvePath($path)) {
      Write-Debug ("Successfully resolved path " + "$path")
      return ResolvePath($path)
      break
    }
  }
  Write-Debug ("Returning NULL path ")
  return $null
}

<#
.SYNOPSIS
Returns a given registry key/name's value

.DESCRIPTION
Returns a given registry key/name's value

.NOTES
Comment added because reviewer asked to do so.
#>
function ResolveRegPath($reg) {
  If (!(Test-Path -Path $reg.key)) {
    Write-Debug ("Given key is NULL")
    return $null
  }
  $value = Get-ItemProperty -Path $reg.key -ErrorAction SilentlyContinue | Select-Object -ExpandProperty $reg.name -ErrorAction SilentlyContinue
  If ([string]::IsNullOrWhiteSpace($value)) {
    Write-Debug ("Given key's name is NULL")
    return $null
  }

  Write-Debug ("Value found: " + $value)
  return $value
}

<#
.SYNOPSIS
Try to find the default VST2 directory

.DESCRIPTION
Try to find the default VST2 directory

.PARAMETER bitToCheck
Wether to find the default 32 bit or 64 bit directory

.NOTES
Comment added because reviewer asked to do so.
#>
function GetDefaultVst2Directory ($bitToCheck) {
  If ($bitToCheck -eq 32) {
    $defaultRegBasePath = "HKLM:\\SOFTWARE\WOW6432Node\VST"
    $installerDefaultRegPath = $vst2x86_64PathReg
  } ElseIf ($bitToCheck -eq 64) {
    $defaultRegBasePath = "HKLM:\\SOFTWARE\VST"
    $installerDefaultRegPath = $vst2PathReg
  }

  $returnVst2Path = $null

  If (Test-Path -Path $defaultRegBasePath) {
    $newVst2Path = Get-ItemProperty -Path $defaultRegBasePath -ErrorAction SilentlyContinue | Select-Object -ExpandProperty VstPluginsPath -ErrorAction SilentlyContinue
    If (![string]::IsNullOrWhiteSpace($newVst2Path)) {
      If ($vst2AddSubfolder) {
        $newVst2Path += "\$companyPath"
      }
      $returnVst2Path = $newVst2Path
    }
  }

  If (![string]::IsNullOrWhiteSpace($installerDefaultRegPath.key)) {
    $newVst2Path = Get-ItemProperty -Path $installerDefaultRegPath.key -ErrorAction SilentlyContinue | Select-Object -ExpandProperty $installerDefaultRegPath.name -ErrorAction SilentlyContinue
    If (![string]::IsNullOrWhiteSpace($newVst2Path)) {
      $returnVst2Path = $newVst2Path
    }
  }

  return $returnVst2Path
}

# Creates/Overwrites bit-aware variables, so x86 files can use the same path-var on both platforms
function CreateBitAwareVariables () {
  if($osBitness -eq 64) {
    $global:vst2x86BitAware = "$vst2x86_64Path"
    $global:vst3x86BitAware = "$vst3x86_64Path"
    $global:aaxx86BitAware  = "$aaxx86_64Path"
    $global:vst2x86PathRegBitAware = "$vst2x86_64PathReg"
    $global:rtasBitaware = "${env:COMMONPROGRAMFILES(x86)}\Digidesign\DAE\Plug-Ins"
  }
  if($osBitness -eq 32) {
    $global:vst2x86BitAware = "$vst2Path"
    $global:vst3x86BitAware = "$vst3Path"
    $global:aaxx86BitAware  = "$aaxPath"
    $global:vst2x86PathRegBitAware = "$vst2PathReg"
    $global:rtasBitaware = "${env:COMMONPROGRAMFILES}\Digidesign\DAE\Plug-Ins"
  }
}

<#
.SYNOPSIS
Which installation steps are actually necessary for the given OS and package parameters?

.DESCRIPTION
Checks the current OS bitness and the given package parameters and marks all steps from the chocolateyvariables file to be actually executed by setting their 'execute' bit.

.PARAMETER objectsList
A list of objects with a 'validpp' key and a 'bit' key from the chocolateyvariables.ps1 file.

.NOTES
#>

function DetermineExecutionOfAllObjects ($objectsList) {
  Foreach ($object in $objectsList) {
      $object.Add('execute', $false)
      $bitStatus = ($object.bit -eq $null) -Or ($object.bit -Contains $osBitness)
      $ppIndependent = (($object.validpp -eq $null) -Or ($object.validpp -Like "Always"))
      Write-Debug ("ppindependent: " + $ppIndependent)
      Write-Debug ("bitStatus: " + $bitStatus)

      Foreach ($packageParameter in $object.validpp) {
          Write-Debug ("Status of evaluated package parameter:" + $packageParameter)
          if ((Test-Path variable:pp.packageParameter) -eq $true) {
              Write-Debug $pp[$packageParameter]
              Write-Debug ($pp[$packageParameter] -eq $false)
          }
          if (($pp[$packageParameter] -eq $false) -And $bitStatus) {
              $object.execute = $true
          }
      }

      if ($ppIndependent -And $bitStatus) {
          $object.execute = $true
      }

      If ($object.ContainsKey("dropIfNull")) {
          Write-Debug ("Object $object contains a dropIfNull!")

          Foreach ($variableToCheck in $object.dropIfNull) {
              If ([string]::IsNullOrWhiteSpace($variableToCheck)) {
                  Write-Debug ("Dependent variable is NULL")
                  $object.execute = $false
              }
              else {
                  Write-Debug ("Dependent variable is $variableToCheck")
              }
          }
      }
  }
}
tools\chocolateyinstall.ps1
# Comments to this script have been added upon request by the chocolatey community reviewer
$ErrorActionPreference = 'Stop';

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$unzPath = "${env:TEMP}"
$chocolateyPackageFolder = ($(Get-ChocolateyPath -PathType 'PackagePath'))
$osBitness = Get-ProcessorBits

if((Test-Path $chocolateyPackageFolder) -And (Test-Path $chocolateyPackageFolder\tools\chocolateyfunctions.ps1)) {
  . $chocolateyPackageFolder\tools\chocolateyfunctions.ps1
  . $chocolateyPackageFolder\tools\chocolateyvariables.ps1
} else {
  . ((Get-Item -Path ".\" -Verbose).FullName + "\tools\chocolateyfunctions.ps1")
  . ((Get-Item -Path ".\" -Verbose).FullName + "\tools\chocolateyvariables.ps1")
}

Remove-Variable chocolateyPackageFolder

# Get default values that may or may not be already on the machine
GetDefaultValues

$pp = Get-PackageParameters
# Audio plugins can come in various formats for multiple platforms, all contained in one single installer with different control schemes at the CLI (if available).
# With the package parameters below it is possible for the user to have a single unified interface for all audio plugin packages I create.
# If the package parameter is set here and an equivalent installation action is found in the chocovariables.ps1 with the 'validpp' key being equal to the
# package parameter, the default behaviour of the package/installer can be changed.
# Not all possible package parameters here actually do something as this depends on the specific package/software vendor. If a package parameter either does
# not exist below or does not exist in a 'validpp'-key in the chocolateyvariables.ps1, it will be ignored and have no effect.
if ($pp["NoClapx64"]      -eq $null -or $pp["NoClapx64"] -eq '')     { if($osBitness -eq 64) { $pp["NoClapx64"] = $false }}
if ($pp["NoVst2x86"]      -eq $null -or $pp["NoVst2x86"] -eq '')     { $pp["NoVst2x86"] = $false }
if ($pp["NoVst2x64"]      -eq $null -or $pp["NoVst2x64"] -eq '')     { if($osBitness -eq 64) { $pp["NoVst2x64"] = $false }}
if ($pp["NoVst3x86"]      -eq $null -or $pp["NoVst3x86"] -eq '')     { $pp["NoVst3x86"] = $false }
if ($pp["NoVst3x64"]      -eq $null -or $pp["NoVst3x64"] -eq '')     { if($osBitness -eq 64) { $pp["NoVst3x64"] = $false }}
if ($pp["NoAaxx86"]       -eq $null -or $pp["NoAaxx86"] -eq '')      { $pp["NoAaxx86"] = $false }
if ($pp["NoAaxx64"]       -eq $null -or $pp["NoAaxx64"] -eq '')      { if($osBitness -eq 64) { $pp["NoAaxx64"] = $false }}
if ($pp["NoRtas"]         -eq $null -or $pp["NoRtas"] -eq '')        { $pp["NoRtas"] = $false }
if ($pp["NoPresets"]      -eq $null -or $pp["NoPresets"] -eq '')     { $pp["NoPresets"] = $false }
if ($pp["NoNks"]          -eq $null -or $pp["NoNks"] -eq '')         { $pp["NoNks"] = $false }
if ($pp["NoUserFolder"]   -eq $null -or $pp["NoUserFolder"] -eq '')  { $pp["NoUserFolder"] = $false }
if ($pp["NoShortcuts"]    -eq $null -or $pp["NoShortcuts"] -eq '')   { $pp["NoShortcuts"] = $false }
if ($pp["NoStandalone"]   -eq $null -or $pp["NoStandalone"] -eq '')  { $pp["NoStandalone"] = $false }
if ($pp["InstallerPath"]  -eq $null -or $pp["InstallerPath"] -eq '') { $fileLocation = "$unzPath\$unzInstPath"; $pp["InstallerPath"]=$false } else { $fileLocation = $pp["InstallerPath"] }
if ($pp["CompanyPath"]    -eq $null -or $pp["CompanyPath"] -eq '')   { $pp["CompanyPath"] = $false }                                          else { $standardCompanyPath=$global:companyPath; $global:companyPath = $pp["CompanyPath"] }
if ($pp["LibraryPath"]    -eq $null -or $pp["LibraryPath"] -eq '')   { $pp["LibraryPath"] = $false }                                          else { $libraryPath = $pp["LibraryPath"] }
if ($pp["UserFolderPath"] -eq $null -or $pp["UserFolderPath"] -eq ''){ }                                                                      else { $userFolderPath = $pp["UserFolderPath"]}
if ($pp["Vst2Path"]       -eq $null -or $pp["Vst2Path"] -eq '')      { }                                                                      else { $global:vst2Path = $pp["Vst2Path"] }
if ($pp["Vst2x86Path"]    -eq $null -or $pp["Vst2x86Path"] -eq '')   { }                                                                      else { $global:vst2x86_64Path = $pp["Vst2x86Path"] }
if ($pp["Vst3Path"]       -eq $null -or $pp["Vst3Path"] -eq '')      { }                                                                      else { $vst3Path = $pp["Vst3Path"] }
if ($pp["Vst3x86Path"]    -eq $null -or $pp["Vst3x86Path"] -eq '')   { }                                                                      else { $vst3x86_64Path = $pp["Vst3x86Path"] }

# Create/Overwrite bit-aware variables. These variables are used to access different paths across different OS bitnesses in a uniform way.
CreateBitAwareVariables

# Create all the necessary information for the setup after package parameters changed the packages default values.
# This includes registry keys to write, shortcuts to create or additional installer parameters to parse.

# Begin with handling the components of the installer so the settings can be written to registry afterwards
if (Get-Command 'CreatePackageParametersObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreatePackageParametersObjects defined, so dot sourcing $PSScriptRoot\helpers-installer.ps1"
  . $PSScriptRoot\helpers-installer.ps1

  # Handle installer components first
  if (Get-Command 'CreateInstallerObjects' -ErrorAction SilentlyContinue) { 
    Write-Debug "CreateInstallerObjects defined"
    CreateInstallerObjects
  
    DetermineExecutionOfAllObjects($installerComponentsList)
    Foreach ($item in $installerComponentsList)  { CreateInstallerParameters($item) }
  }

  ## Now handle installer
  Write-Debug "CreatePackageParametersObjects defined"
  CreatePackageParametersObjects

  # Decision to use previous values or package parameters have been made. Whatever it is, finalize and append to installer call.
  Foreach ($item in $packageParametersObjectsList) { HandlePackageArgs($item) }
}

# Now that the package parameters (from possibly previous installations) have been evaluated
# as well as the installer components, we pick default values for any settings without overrides
PickDefaultValuesFromSystem

# Installer components are now fully evaluated and can be written to registry in case some installers don't save these settings on their own (needed for upgrades)
$objectsLists

if (Get-Command 'CreateRegistryObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreateRegistryObjects defined, so dot sourcing $PSScriptRoot\helpers-regkey.ps1"
  . $PSScriptRoot\helpers-regkey.ps1
  CreateRegistryObjects 
  $objectsLists += $regKeys
}

if (Get-Command 'CreateRegistryFileObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreateRegistryFileObjects defined, so dot sourcing $PSScriptRoot\helpers-regkey.ps1"
  . $PSScriptRoot\helpers-regkey.ps1
  CreateRegistryFileObjects 
  $objectsLists += $regKeyFileObjects
}

if (Get-Command 'CreateShortcutObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreateRegistryFileObjects defined, so dot sourcing $PSScriptRoot\helpers-links.ps1"
  . $PSScriptRoot\helpers-links.ps1
  CreateShortcutObjects
  $objectsLists += $shortcuts
}

if (Get-Command 'CreateSymlinkObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreateSymlinkObjects defined, so dot sourcing $PSScriptRoot\helpers-links.ps1"
  . $PSScriptRoot\helpers-links.ps1
  CreateSymlinkObjects
  $objectsLists += $symlinks
}

if (Get-Command 'CreatePackageRessourcePathObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreateSymlinkObjects defined, so dot sourcing $PSScriptRoot\helpers-packageressources.ps1"
  . $PSScriptRoot\helpers-packageressources.ps1
  CreatePackageRessourcePathObjects
  $objectsLists += $PackageRessourcePathList
}

if (Get-Command 'CreateTxtFileObjects' -ErrorAction SilentlyContinue) { 
  Write-Debug "CreateSymlinkObjects defined, so dot sourcing $PSScriptRoot\helpers-textfiles.ps1"
  . $PSScriptRoot\helpers-textfiles.ps1
  CreateTxtFileObjects
  $objectsLists += $PackageNewFiles
}

if (Get-Command 'CreatePackageRessourcePathObjects' -ErrorAction SilentlyContinue) { 
  # These functions are necessary for embedded installer and other embedded files, only. Nothing actually happens if
  # this package doesn't include something in the 'bin' folder.
  ReducePackageSize
  CreateUninstallFile
}

# For each possible install action defined in chocolateyvariables.ps1 that can be customized via package parameter or depends on the OS bitness,
# it is determined if it is ultimately executed or not. Up until here including all DetermineExecutionOfAllObjects calls, nothing has actually
# happened on the system.
Foreach($objectsList in $objectsLists) { DetermineExecutionOfAllObjects($objectsList) }

# Each possible install action defined in chocolateyvariables.ps1 with the execute-bit set to true is being executed by each corresponding function.
Foreach ($item in $regKeys)                  { CreateRegKey($item)              }
Foreach ($item in $regKeyFileObjects)        { CreateRegKeyFromFile($item)      }
Foreach ($item in $shortcuts)                { CreateShortcut($item)         }
Foreach ($item in $symlinks)                 { CreateSymlink ($item)         }
Foreach ($item in $PackageRessourcePathList) { CopyPackageRessources($item)     }
Foreach ($item in $PackageRessourcePathList) { WriteUninstallData($item)        }
Foreach ($item in $PackageRessourcePathList) { RemoveTemporaryFiles($item)      }
Foreach ($item in $PackageNewFiles)          { CreateTxtFiles($item)            }
Foreach ($item in $packageParametersObjectsList) { RunInstallerWithPackageParametersObject($item) }
Foreach ($item in $packageParametersObjectsList) { RemoveInstallerObjects($item) }
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'

$chocolateyPackageFolder = ($(Get-ChocolateyPath -PathType 'PackagePath'))
. $chocolateyPackageFolder\tools\chocolateyfunctions.ps1
. $chocolateyPackageFolder\tools\chocolateyvariables.ps1

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Voxengo Beeper*'
  fileType      = 'EXE'
  validExitCodes= @(0)
  silentArgs   = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
}

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % {
    $packageArgs['file'] = "$($_.UninstallString)"
    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}
}

CreateRegistryObjects
Foreach ($item in $regKeys) { DeleteRegKeyFromObjects($item) }
tools\chocolateyvariables.ps1
$packageName    = 'Beeper'
$company        = 'Voxengo'
$softwareName   = "$company $packageName"
$checksum       = 'd8d1bc9cbdaeffa0e41df038e39bd371a7dbe3c0dcc6d7e7722629f87c817879'
$url            = 'https://www.voxengo.com/files/VoxengoBeeper_213_Win32_64_VST_VST3_AAX_setup.exe'

function CreateRegistryObjects () {
  # The installer does not have an option for custom paths so we need to create the registry entry before
  $global:regKeys

  if (![string]::IsNullOrWhiteSpace($global:vst2Path)) {
    $global:regKeys += @{'path' = "HKLM:\Software\Voxengo\AudioPluginsInstall"; 'key' = "DirVST2_64"; 'value' = "$global:vst2Path"; 'bit' = 64; 'validpp' = "NoVst2x64" }
  }

  if (![string]::IsNullOrWhiteSpace($global:vst2x86BitAware)) {
    $global:regKeys += @{'path' = "HKLM:\Software\Voxengo\AudioPluginsInstall"; 'key' = "DirVST2_32"; 'value' = "$global:vst2x86BitAware"; 'bit' = 64, 32; 'validpp' = "NoVst2x86" }
  }
}

function CreateInstallerObjects () {
  $global:installerComponentsList =
  @{'value'="shortcuts"; 'bit'=64,32; 'validpp'="NoShortcuts"},
  @{'value'="guides";    'bit'=64,32; 'validpp'="NoVst2x64", "NoVst2x86", "NoVst3x64", "NoVst3x86", "NoAaxx86", "NoAaxx64"},
  @{'value'="vst2_32";   'bit'=64,32; 'validpp'="NoVst2x86"},
  @{'value'="vst2_64";   'bit'=64;    'validpp'="NoVst2x64"},
  @{'value'="vst3_32";   'bit'=64,32; 'validpp'="NoVst3x86"},
  @{'value'="vst3_64";   'bit'=64;    'validpp'="NoVst3x64"},
  @{'value'="aax_32";    'bit'=64,32; 'validpp'="NoAaxx86"},
  @{'value'="aax_64";    'bit'=64;    'validpp'="NoAaxx64"}
}

function CreatePackageParametersObjects () {
  $global:packageArgs = @{
    packageName   = $packageName
    unzipLocation = $unzPath
    fileType      = 'exe'
    url           = $url
    softwareName  = $softwareName
    checksum      = $checksum
    checksumType  = 'sha256' #default is md5, can also be sha1, sha256 or sha512
    silentArgs    = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup
  }

  if ((Test-Path variable:global:companyPath) -and ($global:companyPath -is [string]) -and ($global:companyPath.Length -gt 0)) {
    $global:packageArgs.silentArgs += " /Dir=`"${global:companyPath}`""
  }

  $global:packageParametersObjectsList = $packageArgs
}
tools\helpers-installer.ps1
# Helper functions for managing installer

<#
.SYNOPSIS
Create the component list that will be parsed to the installer.

.DESCRIPTION
Create the component list that will be parsed to the installer. A component is a tickable box in an installer.
The resulting component list depends on the 'execute' bool that should be set before handing the installer
component into this function.

.PARAMETER instParamObject
An installer parameter object/action defined in the chocolateyvariables.ps1.
.NOTES
#>
function CreateInstallerParameters ($instParamObject) {
    if ($instParamObject.execute -eq $true) {
        Write-Debug "Checking Installer Components for: "; Write-Debug $instParamObject.value
        $global:installerComponents += $instParamObject.value
        $global:installerComponents += ","
        Write-Debug ("These are the current installerComponents: " + $global:installerComponents + ".")
    }
}


# This name is too generic, it actually handles the components argument of installers
function HandlePackageArgs ($packageParameterObject) {
    if ($global:installerComponents) {
        If ($global:installerComponents.EndsWith(',')) {
            Write-Debug ("Components list ends with , - removing.")
            $global:installerComponents = $global:installerComponents.Substring(0, $global:installerComponents.Length - 1)
        }
        $packageParameterObject["silentArgs"] += " /Components=$global:installerComponents"
    }
    Write-Debug "These are the silentArgs"; Write-Debug $packageParameterObject["silentArgs"]
}

function RunInstallerWithPackageParametersObject ($packageParameterObject) {
    $installerPathViaPP = (Test-Path $pp["InstallerPath"])
    $chocolateyPackageFolder = ($(Get-ChocolateyPath -PathType 'PackagePath'))
    ## Does the following check work for 32 bit installers??
    $installerEmbedded = ((Test-Path ($chocolateyPackageFolder + "\" + $packageParameterObject.file)) -And ($packageParameterObject.file64 -ne $null) -And (Test-Path ($chocolateyPackageFolder + "\" + $packageParameterObject.file64)))
    $installerDownload = (($packageParameterObject.url -ne $null) -Or ($packageParameterObject.url64 -ne $null))
    $installerDownloadExe = (($packageParameterObject.url -ne $null) -And ($packageParameterObject.url).EndsWith(".exe"))
    Write-Debug ("This is the InstallerPath Variable: " + $pp["InstallerPath"])
  
    if ($installerPathViaPP -eq $true) {
        Write-Debug "Installer overridden via package parameter"
        $packageParameterObject["file"] = $fileLocation
        Install-ChocolateyInstallPackage @packageParameterObject # https://chocolatey.org/docs/helpers-install-chocolatey-install-package
        return
    }
  
    if ($installerEmbedded -eq $true) {
        Write-Debug "Installer is embedded"
        $packageParameterObject.file = ($chocolateyPackageFolder + "\" + $packageParameterObject.file)
        $packageParameterObject.file64 = ($chocolateyPackageFolder + "\" + $packageParameterObject.file64)
        Write-Debug ("Installer (32 bit referenced) embedded path: " + $packageParameterObject.file)
        Write-Debug ("Installer (64 bit referenced) embedded path: " + $packageParameterObject.file64)
        Install-ChocolateyInstallPackage @packageParameterObject
        return
    }
  
    if ($installerDownload -eq $true -And $installerPathViaPP -eq $false) {
        Write-Debug ("Installer needs to be downloaded from " + $packageParameterObject.url)
        if ($installerDownloadExe -eq $true) { 
            Write-Debug "Installer is exe, running now..."
            Install-ChocolateyPackage @packageParameterObject # https://chocolatey.org/docs/helpers-install-chocolatey-package
        }
        else { 
            Write-Debug "Installer inside zip"
            Write-Debug ("UnzipLocation is: " + $packageParameterObject.unzipLocation)
            $packageParameterObject["file"] = $fileLocation
            Install-ChocolateyZipPackage @packageParameterObject
            Install-ChocolateyInstallPackage @packageParameterObject
        }
        return
    }
  
    Write-Warning ("No installer found!");
}

function RemoveInstallerObjects ($packageParameterObject) {
    Write-Debug "Starting cleanup of installer files"
  
    if ($packageParameterObject.removePostInstall) {
      ("Entries to remove: " + ($packageParameterObject.removePostInstall | Out-String -stream)) | Write-Debug
  
        foreach ($entry in $packageParameterObject.removePostInstall) {
            $chocolateyPackageFolder = ($(Get-ChocolateyPath -PathType 'PackagePath'))
            $pathToRemove = $chocolateyPackageFolder + "\" + $entry
            Write-Debug "Trying to delete $pathToRemove"
            Write-Debug (Test-Path ($pathToRemove) -ErrorAction Ignore)
  
            if (Test-Path ($pathToRemove) -ErrorAction Ignore) {
                Write-Debug "Deleting $pathToRemove"
                if (Test-Path $pathToRemove -pathType leaf) {
                    $directoryName = (Get-Item $pathToRemove).DirectoryName
                    Write-Debug "$pathToRemove will be deleted."
                    Remove-Item "$pathToRemove" -Force
                }
                if (Test-Path $pathToRemove -pathType container) {
                    $parentDirectory = (Get-ItemProperty $pathToRemove).Parent.FullName
                    Write-Debug "$pathToRemove will be deleted."
                    #Remove-Item "$pathToRemove" -Recurse -Force #fails if folder contains a symlink -.-
                    [System.IO.Directory]::Delete("$pathToRemove", $true)
                }
            }
        }
    }
    else {
        # ATM, keep old behaviour when no removePostInstall variable has been defined
        if ($packageParameterObject.file) {
            if (Test-Path ($packageParameterObject.file) -ErrorAction Ignore) {
                Remove-Item $packageParameterObject.file -Force -ErrorAction SilentlyContinue
            }
        }
        if ($packageParameterObject.file64) {
            if (Test-Path ($packageParameterObject.file64) -ErrorAction Ignore) {
                Remove-Item $packageParameterObject.file64 -Force -ErrorAction SilentlyContinue
            }
        }
    }
}
tools\helpers-regkey.ps1
# Helper functions for managing registry keys

function CreateRegKey ($regKeyObject) {
    If ([string]::IsNullOrWhiteSpace($regKeyObject.path)) {
        Write-Warning ("Given Registry Object Path is NULL.")
        return
    }
  
    if ($regKeyObject.execute -eq $true) {
        # Determine value type
        if (${regKeyObject}.value -is [String]) {
            $registryValueType = "String"
            Write-Debug("Registry value type is String.")
        }
        elseif (${regKeyObject}.value -is [Int32]) {
            $registryValueType = "DWORD"
            Write-Debug("Registry value type is DWORD.")
        }
        else {
            $registryValueType = "String"
            Write-Warning("Registry value type unknown. Using String as type.")
        }
  
        # Write reg key
        if ($regKeyObject.key -eq '') {
            New-Item -Path ${regKeyObject}.path -Value ${regKeyObject}.value -Force
        }
        else {
            if (Test-Path ${regKeyObject}.path) { } else { New-Item ${regKeyObject}.path -force }
            New-ItemProperty -PropertyType $registryValueType -Path ${regKeyObject}.path -Name ${regKeyObject}.key -Value ${regKeyObject}.value -force
        }
    }
}
  
function CreateRegKeyFromFile ($regKeyFileObject) {
    if ($regKeyFileObject.execute -eq $true) {
        $chocolateyPackageFolder = ($(Get-ChocolateyPath -PathType 'PackagePath'))
        Write-Debug ("Creating registry entry from file " + $chocolateyPackageFolder + "\" + $regKeyFileObject.path)
        regedit.exe /S ($chocolateyPackageFolder + "\" + $regKeyFileObject.path)
    }
}
  
# Removes all registry entires in a given registry file from the registry
function DeleteRegKeysFromFile ($file) {
    if (Test-Path $file) {
      (Get-Content $file) -replace "^\[", "[-" | out-file $file
        regedit.exe /S ($file)
    }
}
  
# Deletes a registry key or property, if it exists and is not marked as delete=$false
function DeleteRegKeyFromObjects ($regKey) {
    Write-Debug ("About to delete Registry Entry: " + $regKey.path + $regKey.key)
    if ($regKey.ContainsKey("delete")) {
        return
    }
    If ([string]::IsNullOrWhiteSpace($regKey.path)) {
        Write-Debug("Given Registry Path is null or empty.")
        return
    }
    if ((Test-Path -Path $regKey.path) -eq $false) {
        Write-Debug ("Registry Entry does not exist anymore.")
        return
    }
    if (($regKey.key -eq "")) {
        Write-Debug ("Deleting " + $regKey.path)
        Remove-Item -Path $regKey.path -Force
        return
    }
    if ($regKey.key -ne "") {
        Write-Debug ("Deleting Key " + $regKey.key + " at Path " + $regKey.path)
        Remove-ItemProperty -Path $regKey.path -Name $regKey.key -Force -ErrorAction SilentlyContinue
        return
    }

    If (([string]::IsNullOrWhiteSpace((Get-Item -Path $regKey.path | Get-ItemProperty))) -And ([string]::IsNullOrWhiteSpace((Get-ChildItem -Path $regKey.path)))) {
        Write-Debug ("Deleting orphaned key " + $regKey.path)
        Remove-Item -Path $regKey.path
        return
    }
}

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
Voxengo Beeper (Install) 2.12 150 Monday, April 24, 2023 Approved
Voxengo Beeper (Install) 2.11 93 Sunday, October 9, 2022 Approved
Voxengo Beeper (Install) 2.10 385 Wednesday, July 28, 2021 Approved
Voxengo Beeper (Install) 2.9 200 Wednesday, July 22, 2020 Approved
Voxengo Beeper (Install) 2.8 344 Sunday, April 28, 2019 Approved
Voxengo Beeper (Install) 2.7 223 Tuesday, January 8, 2019 Approved
Discussion for the Voxengo Beeper Package

Ground Rules:

  • This discussion is only about Voxengo Beeper and the Voxengo Beeper 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 Voxengo Beeper, 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