Can HTML5 Player support 96khz 24bit?
-
- KVRer
- 26 posts since 9 Nov, 2012
- KVRAF
- 16861 posts since 8 Mar, 2005 from Utrecht, Holland
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRer
- Topic Starter
- 26 posts since 9 Nov, 2012
- KVRAF
- 16861 posts since 8 Mar, 2005 from Utrecht, Holland
Mind you, if you supply a 96kHz file (I would not know why because it does not sound any better than 44.1 kHz redbook CD) there's a chance that:
a) on the receiving side it gets downsampled to 44.1 kHz with the most crude naieve method available, resulting in appauling quality
b) the receiving side rejects the audio file, resulting in silence.
So as always with web pages, you're totally at the mercy of the user's browser and it's quirks.
As a casual visitor of a web page I would object against megabytes of audio being downloaded without my prior consent. Especially when using a phone my dataplan might not be sufficient.
a) on the receiving side it gets downsampled to 44.1 kHz with the most crude naieve method available, resulting in appauling quality
b) the receiving side rejects the audio file, resulting in silence.
So as always with web pages, you're totally at the mercy of the user's browser and it's quirks.
As a casual visitor of a web page I would object against megabytes of audio being downloaded without my prior consent. Especially when using a phone my dataplan might not be sufficient.
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRer
- Topic Starter
- 26 posts since 9 Nov, 2012
That was my main concern. So better I downsample to 44.1 with quality converter.BertKoor wrote: a) on the receiving side it gets downsampled to 44.1 kHz with the most crude naieve method available, resulting in appauling quality
b) the receiving side rejects the audio file, resulting in silence.