Troubleshooting

If the tool is not working as expected or desired, going over this list may help:

• Make sure you are using the last version from the master branch, as little fixes can be implemented along the way. Pull using git, or download as a ZIP file.
• The tool should be fully functional in Firefox and Chrome. The least stable browsers are old Safari (v8) and Edge (least amount of testing) but both should be functional, with some little GUI glitches that are hard to track down.
• Make sure to use the same test creator as in your package, which will say which version it is built for (v1.2.1, v1.2.2 or v1.2.3), on the bottom of all the interface pages is a footer which says which test engine is currently running. If these don’t match, validation issues can occur.
• If you’re still having issues, check the “vnext” branch (download here) to see if that fixes the problem.
• As a sanity test, you should be able to load any of the included xml examples without any issues. Likewise you should be able to import them into the Test Creator, export them and run the newly made files.

The Web Audio Evaluation Tool is constantly being updated, with bugs being fixed regularly by authors and the community of users. The introduction of new features and removal of errors sometimes creates new problems. We're grateful for your patience while we improve the tool, and even more grateful if you can

• log issues or desired features on the Issues page: be specific, and make note of any errors that pop up in the browser's console;
• create a patch that will fix a problem or introduce a new feature as a Pull Request: if it fits the scope and standards of the tool we will incorporate it.

We also always like to hear about ways in which you have used the tool and how you liked it, and are usually happy to put links to your online tests on our Examples page.