Re: [mediacapture-main] Specification to capture unmodified audio

@fluffy 

I am a bit confused by your comment above:

_**Just as FYI on this ... currently there is no way for the browser to get unprocessed audio on IOS devices. I still think adding this is a good idea because there are many situations where you really want unprocessed audio and hopefully this will change in future IOS releases.**_

If I can write native apps and have access to raw audio natively (and I can AFAIK,..at least my high frequency audio signalling above even 20KHz at 44100 sample rate is working which should be the first thing to get disrupted with almost any audio filter), then why is in not possible for a natively written IOS browser to deliver raw (aka unprocessed) audio and pass that on thru its webRTC block? In fact, I believe it should be possible for the webRTC block in the Chrome browser on IOS to deliver not only raw audio full analyzer nodes with FFT sizes == 32768 in IOS 11 even though Safari 11 does not allow fft sizes above 2048. Any native app (including a browser running on top of Safari 11) should have access to native audio as well as IOS core FFT.

Safari 11 will move at Apples whim to comply with webRTC, but what is restricting Chrome or Firefox or any other browser running natively on an iphone from building a webRTC compliant block including raw audio and full fft analyser nodes. (and dare I say, on a personal note, I believe windowing (i.e. hamming, gaussian) as well as raising the fftsize limit to 65536 should be added to webRTC across the board but that is a different discussion)

-- 
GitHub Notification of comment by kdavis45
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/457#issuecomment-355453300 using your GitHub account

Received on Friday, 5 January 2018 02:02:39 UTC