Feature #1498
Add bit depth warning to test creator
| Status: | Resolved | Start date: | 2015-12-16 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
Have the test creator inform the user that, when they use a file with a bit depth above 16-bit, that Firefox may not work (and in the future that Firefox will quantise the information).
History
#1
Updated by Nicholas Jillings over 8 years ago
- Status changed from New to Resolved
Not needed now as by default all WAV files pass through our WAVE decoder first then through the browser decoders if failed.
#2
Updated by Brecht De Man over 8 years ago
Sorry, I'm not sure I understand. My thinking was that if a researcher is conducting a test with 32 bit wave files (let's say he's trying to establish whether some people can hear the difference between 32 bit recordings and 16 bit recordings) he gets a warning about his files being requantised if he's using Firefox.
You are saying that this requantising now happens, without the user being made aware, no? I would say a warning about this when using Firefox is still useful. Perhaps I misunderstood.
#3
Updated by Nicholas Jillings over 8 years ago
The web audio API has its data stored as 32-bit normalised floats, all input data must go up to that. However the 'decoder' is browser based and Firefox does not like performing the conversion if the WAVE is a 32-bit float as well. The WAVE.js module simply takes the incoming binary level data and converts it into the float32array that the web audio API needs. No quantising at all.
#4
Updated by Brecht De Man over 8 years ago
Got it, thanks. That's really good then.