These pages use javascript to play the audio files, so if you have a script blocker, enable javascript for this domain.
Also Chrome browser seems to work better - some Firefox browser versions get stuck at the 'Downloading...' part.
Test 1
Test 2
Test 3
Test 4
Test 5
Test 6 - binaural
Test 7 - binaural
The online version of this webpage is available at:
http://www.stereomatch.com/apk/hires_doubleblind_test1/doubleblind_index_intro.html tinyurl version of above url: http://tinyurl.com/y9drac9v
You can also download this webpage and the test files (including audio samples) as a zip file (for better responsiveness):
http://www.stereomatch.com/apk/hires_doubleblind_test1.zip tinyurl version of above url: http://tinyurl.com/y7cyp62q
To build your own testbed (where you supply the pair of audio files that need to be compared), see the instructions below.
To understand how the samples are randomized for every trial, check out the demo below.
For examples of Hi-Res Audio, check out this website directory:
http://www.findhdmusic.com/high-res-audio/free-music/
For each of the tests above, you can Listen to Sample 0 or Sample 1 (randomized - one will be Low-Res, while the other will be Hi-Res or vice-versa).
Then Vote which of the Sample 0 or Sample 1 was the Hi-Res version.
Every time you Vote, results will be shown, and a new trial will start (the Listen: Sample 0/1 samples will be randomized, so you can Listen and Vote again).
Your results (success rate) will be shown below.
A 100% success rate implies your equipment is outputting high quality audio, and you are able to hear the difference. If your success rate is around 50%, that means you are doing no better than chance - you should make sure your equipment is capable of outputting 24-bit/96kHz, or 32-bit/192kHz, and that you are using speakers or high-quality headphones.
NOTE: reload the webpage to reset the trial count.
Taking inspiration from the double-blind test on this webpage: The 16-bit v/s 8-bit Blind Listening Test, Part 2., we have devised a similar double-blind test for distinguishing Hi-Res 24-bit/32-bit or 96kHz/192kHz audio samples from their downsampled versions (16-bit/44.1kHz).
This is a double-blind test (a double-blind test removes user and administrator bias from the experiment).
In order to make the Hi-Res and Low-Res versions indistinguishable in content, we will create the Low-Res version by just downsampling the Hi-Res version using Audacity program.
However, when testing Android devices, and the advantages of recording in 32-bit/192kHz, it maybe better to use two identical devices and record the same real-world event, with one device recording at 32-bit/192kHz, and the other at 16-bit/44.1kHz. Android Marshmallow and above versions support 32-bit/192kHz audio recording. However, you will get best results with a Hi-Res Audio certified android device, like LG V20, or Samsung S8. These devices can record at 24-bit/96kHz and higher resolutions.
Starting Trial (1/10):
Downloading...
Listen on speakers, or high-quality headphones. You will NOT notice a difference on low quality earbud earphones
Make sure your device isn't downsampling to some default sample rate.
Here is a discussion about the capabilities of the HTML 'new Audio("0.wav").play()' that we are using to play audio files - whether HTML audio is capable of using the max capabilities of the hardware, or whether HTML audio resamples to some safe default like 44.1kHz:
X-post: [Question] Does HTML audio support full resolution of device ? (32-bit/192kHz playback) - r/webaudio
In Chrome browser, you can check the sample rate that is being used, by viewing the url in one tab: chrome://media-internals/ and clicking the Audio tab, and then the Component button. The Component buttons will only appear if audio is playing, so play in one tab and then switch to the other tab to click the Component button while audio is playing.
For Mac laptops, run 'Audio MIDI Setup' to change from 24-bit/44.1kHz to 32-bit/96kHz output (earphone jack), or use optical output and use 'Audio MIDI Setup' to change to 32-bit/192kHz output.
You have to be sure that the device is outputting 32-bit float at 192kHz output (or the highest it can support). Macs by default will do 24-bit/44.1kHz only on earphones, but by going into "Audio MIDI Setup" you can increase this from "24-bit Integer 44.1kHz" to "32-bit float 96kHz" as outlined here:
How to find and play high-resolution audio on the Mac
And for higher sample rates of 192kHz on Macs, you have to use the optical output as outlined here:
Play high sample rate digital audio on Mac computers (optical)
For Windows machines, set your sound interface as the default interface, and set the bit-depth/sample-rate for the device.
On Android, use Hi-Res Audio certified Android devices like the LG V20, Samsung S8 to test. The Neutron player on android plays 32-bit WAV - this app has a free trial, but is usable after you dismiss the nag screen:
Neutron Music Player (Eval) by Neutron Code Limited
Hi-Res Audio certified Android devices will output 24-bit/96kHz, and some may do 192kHz or higher.
You can use our app to record 32-bit/192kHz WAV on Android Marshmallow and above devices. Hi-Res Audio certified devices like the LG V20 and Samsung S8 will give better results:
Amazing MP3 Recorder
If users are going to be choosing between two samples, they should not be distinguishable by their content. Otherwise the user may learn which content is the Hi-Res version (esp. since during the test, we are giving immediate feedback if their guess was Correct/Wrong). So users may learn which content is associated with the Hi-Res version. Thus it is important that Hi-Res and Low-Res should sound similar in content.
For this reason, when testing for differences between Hi-Res and Low-Res versions, it is best to either use the Hi-Res version and downsample it to get the Low-Res version (using Audacity program), or use two identical hardware devices to record the same live performance. You can eliminate bias from device variations, by doing another test, but with devices switched.
You can easily build your own testing setup. You just need to copy the Hi-Res sample as '0.wav' and the Low-Res sample as '1.wav' into the same folder on your computer, or web server. Also copy the files 'doubleblind_index.html' and 'doubleblind_javascript.js' into the same folder. To begin testing, have your users view 'doubleblind_index.html' in a browser like Firefox or Chrome. On a computer, you can just drag it into an empty Firefox window, or type in the location of this file into the url window of the web browser.
doubleblind_index.html (view this in a web browser) doubleblind_javascript.js 0.wav 1.wav
To setup multiple tests (for different audio samples), just create separate folders for each test.
test1/ doubleblind_index.html (view this in a web browser) doubleblind_javascript.js 0.wav 1.wav test2/ doubleblind_index.html (view this in a web browser) doubleblind_javascript.js 0.wav 1.wav test3/ doubleblind_index.html (view this in a web browser) doubleblind_javascript.js 0.wav 1.wav
You can download an example of this by downloading and then unzipping the zip file mentioned above.