Get Virtual Acoustics (VA) for Windows
Full VA package for Windows¶
Build name: VA_full.v2022a.win64.vc14
Includes VAServer, VC14 C++ programming libraries, all bindings and Unity scripts.
Quick user guide:
A quick guide can be found in the documentation section.
Binary package license / sharing:
GNU General Public License
+ VABase, VANet and VACore* C++ developer packages for Visual C++ Compiler Version 14 (Visual Studio 2019)
+ VAMatlab and VAC# bindings
+ VAPython bindings for Python 3.8, 3.9 and 3.10
+ VAServer command line interface application
- Redstart VA GUI application [DEPRECATED]
*includes FFTW3 (GNU GPL)
Important changes in 2022¶
In 2022, we introduced major changes in our build system. This allows us to use compilers newer than VC12 for all VA components. Generally, this lead to the following changes for newly deployed VA versions:
- VAPython is now part of the
VA_bindingsbuild is not shipped anymore.
- VAPython is now included as wheels which makes installing much easier
- We stopped developing the Redstart GUI and removed it from the packages
VACore - Rendering system rework
- Now distinguishs between FIR-based and sound-path-based renderers
- Sound-path-based renderers are not restricted to binaural output anymore but can choose from binaural / Ambisonics / VBAP
- Tracking now works with AR-Tracking (in addition to OptiTrack)
- Is now installed using wheels
- Now shipped with version 3.8 to 3.10
- Undesired default receiver position (
[0 0 0]) removed
- Fixed performance issues of Windows timer used in VAMatlab
- Fixed CTC crash that could occur if utilized HRTF did not cover a full sphere
- Fixed bug in ITASimulationScheduler where mainly a single source-receiver pair was simulated disregarding other sound sources
- Now a receiver becomes active as soon as it has a valid position. The
set_active_listenerfunction should not be used anymore was removed from all bindings.
VAServer / VACore
- Now comes with
VACore.recording.inifile for offline rendering. Use
run_VAServer_recording.batto start VAServer with this configuration.
VACore - AirtraficNoiseRenderer
- Now can switch between homogeneous and inhomogeneous medium
- Homogeneous medium: straight sound paths calculated within VA
- Inhomogeneous medium: curved sound paths simulated with Atmospheric Ray Tracing framework
- Previously only working for Python 3.6, now only works with Python 3.7 and higher
- Now shipped with version 3.7 to 3.9
|VA_full.v2022a_dev.win64.vc14||GPL||[CURRENTLY NO DEV VERSION AVAILABLE] Continuously updated developer branch distribution (includes hotfixes and recent feature requests)|
|VA_bindings.v2021a.win32-x64.vc14_static||Apache License, Version 2.0||v2021a bindings (static)|
|VA_bindings.v2020a.win32-x64.vc14_static||Apache License, Version 2.0||v2020a bindings (static)|
|VA_bindings.v2019a.win32-x64.vc14_static||Apache License, Version 2.0||v2019a bindings (static)|
|VA_bindings.v2018b.win32-x64.vc14_static||Apache License, Version 2.0||v2018b bindings (static)|
|VA_bindings.v2018a.win32-x64.vc14_static||Apache License, Version 2.0||v2018a bindings (static)|
Linux, Mac OSX and other¶
From the very beginning, Virtual Acoustics has been developed and used under Windows platforms. If you do not have a Windows system, you can still use VA. Unfortunately, we are not experienced in building binary packages for other platforms than Windows, hence you will have to build it from the source code. However, we can't guarantee smooth performance on those systems. For more information, read the developer section.
A common alternative way is to run the VA server application on a dedicated remote Windows PC with a proper ASIO interface, and control it from any other platform. This way, you can use the Windows download package and you only have to build the remote control part of VA (the C++ interface libraries and/or bindings). You will require no further third-party libraries except for the binding interface you choose (usually Matlab or Python). You can also run a Jupyter notebook along with VA on the Windows machine and remotely control everything using a web browser on any mobile device connected to the same network.
Some hints on VA packages¶
VA is always in development and we constantly add new features or components. Therefore, we chose the version identifier to reflect the release year and added an ascending alphabetic character, like
v2018a. This makes it easier to determine the release time, just like in Matlab and other applications.
We cannot guarantee compatibility among VA versions! The reason is, that we still update the interface for new powerful features. This is unfortunate, but can not be achieved with the resources we can afford. If you are interested in new features, you will have to pay the price and update everything, including the bindings you use.
We adopt naming conventions for platforms and compiler versions from ViSTA VR Toolkit. This way, one can easily extract the target platform, such as
win32-x64 for a Windows operating system using a mixed 32 bit and 64 bit environment, or
vc12 to indicate that the binary package was built using the Microsoft Visual C++ Compiler Version 12. If you are missing redistributable libraries you can identify the required Microsoft installer by this suffix.
The build environment of VA provides configuration of the underlying components. This may or may not result in a binary package that links against GNU GPL licensed libraries. For this reason, VA is either licenses under the favored Apache License, Version 2.0 or under the GNU General Public License, as required by the copyleft nature.