Frequently Asked Questions (FAQ)
- If you load a file from hard drive, it has to be placed on the computer where the VA server is running - not necessarily on the client side, if you are using a remote connection. Use relative paths for loading files only, avoid absolute paths. Add search paths (folders where your files can be found) to help VA find the files. You can do this in the configuration file of the VA server, or you can interactively add the search path over the VA interface.
- It is very likely, that your firewall has blocked the program due to insufficient privileges. This happens a lot in managed networks like universities, where you are not allowed to open a TCP/IP port. Please contact your network administration or check, if your firewall settings are blocking VA.
Also, check if the versions are matching and you are not mixing different VA binary packages of different compiler versions. Especially if dynamic linking to ViSTA and VA libraries is used, this can lead to unpredictable behavior, because the DLLs will have the same name - but are incompatible. It is strongly recommended to use static linking for bindings like Python or Matlab for this reason.
- Check your sampling rates and buffer sizes.
Do not overload your computer. There are limits on how much sound sources and sound receivers can be processed depending on the number of rendering and reproduction modules you've instantiated.
Use ASIO drivers.
- You are missing a dependent shared library (dll on Windows). Make sure to include the dependencies if you copy libraries. If you are a developer, the Dependency Walker is an excellent supporter for solving these problems on Windows platforms. Otherwise consider switching to static linking to avoid this problem with the VA bindings.
SOFAHRTFs in VA?
- Not directly, but you can convert
SOFAHRTF files into
OpenDAFFusing the ITA-Toolbox for Matlab. Create an
itaHRTFand load the
SOFAfile, then export using
Issue trackerIssues are very likely to appear. VA is a prototyping software, and the usage can hardly be foreseen by the developers. However, it is important to identify if the issues you have are usage-related or require a bug fix in the code. If you are insecure, go through the FAQ and discuss with the community first.
If you have trouble configuring and using VA, there is a whole section about that in the documentation page, which should be thoroughly read first.
If you are sure it is a bug that should be fixed, then
- does it affect the interface? File it here: VABase issues
- does it affect the Python binding? File it here: VAPython issues
- does it affect the Matlab binding? File it here: VAMatlab issues
- does it affect the Redstart application: Redstart issues
- does it affect the functionality* of VA? File it here: VACore issues
The developers of VA can not answer every question due to limited resources. The solution approach is to establish a community of users that help each other to a) minimize the workload for the dev team and b) handle potentially easy-to-solve questions quicker.
Right now, questions can be asked at stack exchange's sound design group. If there are enough VA questions, a tag
va can be created that should be assigned with every question.
VA has no official support team
We are very sorry to inform you, that there is no official support team in place. We, the developers of VA, are scientists and are paid for research, not commercial or private support activity. However, if you are willing to start a research alliance or fund a joint project that gives us opportunities to spend time on your ideas, we will be open to discuss your proposal. Please contact the administration of the Institute for Hearing Technology and Acoustics (IHTA), RWTH Aachen University, in this case.