- From: klausj via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Aug 2017 14:06:40 +0000
- To: public-media-capture-logs@w3.org
I think the builtin microphone signal on most mobile devices is already preprocessed (noise reduction, dynamic compression, etc.). Maybe already by the hardware or by the driver or operating system. And I am not aware of any audio interface API (DirectSound, CoreAudio, ALSA/PulseAudio,...) which has the capability to somehow guarantee unprocessed audio or could be queried about pre-processing. So, I suggest that a property to disable input processing should only be related to input processing in the browser itself. @burnburn, I do not know any builtin signal processing of video which modifies the video stream, but the property could be preventively meant for video tracks as well. The video might have artifacts caused by lossy compression encoding. But this is probably a different thing and it might be worth to think about another property, for instance "disableLossyCompression". But I don't know if browsers currently do compression encoding of video input at all. I will try to create a pull request in the next days. -- GitHub Notification of comment by klausj Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/457#issuecomment-324645392 using your GitHub account
Received on Thursday, 24 August 2017 14:06:42 UTC