- Create wav directory like the below example. Each set contains wav files and their file lists for the methods you want to compare. It's easier to understand if you actually browse the wav directory. The number of methods in each set does not have to match.
wav/
|---- set1/
| |-- method1/
| |-- method1.list
|
|---- set2
| |-- method2/
| |-- method3/
| |-- method2.list
| |-- method3.list
|
|---- set3
| |-- method4/
| |-- method5/
| |-- method4.list
| |-- method5.list
|
The command find wav/set1 -name "*.wav" | grep "method1" > wav/set1/method1.list will be helpful to create list files.
-
Rewrite mos.js depending on the structure of the wav directory. You only need to customize the part from line 45.
-
Rewrite index.html as you like. Note that my email address is written as contact info, so you may have to change it to your own one.
-
Use Github Pages to deploy your own test. The test automatically emits a csv file when the test finishes.
If you want to conduct tests other than a MOS test, you need to modify the code significantly depending on the test. You can utilize ABXTest if you want to conduct ABX test.
Please feel free to ask any questions you may have.