- From: White, Jason J <jjwhite@ets.org>
- Date: Tue, 27 Aug 2019 15:37:18 +0000
- To: Joshue O Connor <joconnor@w3.org>, RQTF <public-rqtf@w3.org>
Do we know whether there are any implementations underway for, let's say, Blink, Gecko, or WebKit? -----Original Message----- From: Joshue O Connor <joconnor@w3.org> Sent: Tuesday, August 27, 2019 11:35 AM To: White, Jason J <jjwhite@ets.org>; RQTF <public-rqtf@w3.org> Subject: Re: Accessible RTC Routing use case and Audio Device Client proposal from Web Audio Community Group Just for those who don't watch.. it is mentioned at ~ 9 mins in, that this ADC proposal could be used for browser based DAW (Digital Audio Workstations) and is it is mentioned that already supportive of the API are the likes of Ableton (which is very interesting and a little surprising as it means this more advanced than being a mere proposal). Thanks Josh On 27/08/2019 16:20, Joshue O Connor wrote: > Cool - here is the video (on Vimeo) of Hongchan Choi's presentation > about the Audio Device Client proposal. > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvime > o.com%2F350904743&data=02%7C01%7Cjjwhite%40ets.org%7C25f33f3f7a544 > 41aa90108d72b04269e%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C63702 > 5169157239684&sdata=Mt%2B37obXxSPqA0Is39kEBhLrMY2mPBEC%2BNwDLYURxW > M%3D&reserved=0 > > Thanks > > Josh > > On 27/08/2019 15:43, White, Jason J wrote: >> Thank you, Josh - this is interesting and appears to address some of >> the use cases which RQTF has discussed. I would expect the >> functionality described to be useful for both XR applications and >> real-time communication. >> >> -----Original Message----- >> From: Joshue O Connor <joconnor@w3.org> >> Sent: Tuesday, August 27, 2019 10:21 AM >> To: RQTF <public-rqtf@w3.org> >> Cc: group-apa-chairs@w3.org >> Subject: Accessible RTC Routing use case and Audio Device Client >> proposal from Web Audio Community Group >> >> Hi all, >> >> For anyone tracking some of our discussion about Accessible RTC, and >> the Routing use case [1] - this may be of interest. It from the >> 'Audio and Games' section of the Games Workshop report. [2] >> >> There is an Audio Device Client (ADC) proposal, under incubation in >> the Web Audio Community Group, which aims to provide truly low-level >> audio input and output. Audio Device Client is suggested as middle >> layer between the Web Audio API and the audio device used by the >> browser. >> >> Here is the explainer for the Audio Device Client proposal >> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit >> hub.com%2FWebAudio%2Fweb-audio-cg%2Fblob%2Fmaster%2Faudio-device-clie >> nt%2Fexplainer.md&data=02%7C01%7Cjjwhite%40ets.org%7C25f33f3f7a54 >> 441aa90108d72b04269e%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637 >> 025169157249677&sdata=vd8t1FT8P57B0kc1ITPNR6iUdTO1sPP67Kr6XRjzIZM >> %3D&reserved=0 >> >> >> >> There are different features of the proposal including threading for >> audio, but what is of interest is the suggestion to modify I/O >> buffers, which could help with performance, some AT output does not >> need to be high sample size/bitrate, and especially the ability to >> select audio I/O devices via a MediaTrackConstraints pattern and >> modify the inputDeviceId/outputDeviceId. You can also use suggested >> inputChannelCount/outPutChannelCount properties as constraints on the >> global Audio Object (that my reading anyway). >> >> It is not meant to replace the Web Audio API but to function as a >> customisable middleware and could be a way for people with >> disabilities to manage bespoke/complex routing of multiple audio >> input and output directly in the browser. >> >> Interesting! >> >> Thanks >> >> Josh >> >> [1] >> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >> .w3.org%2F2018%2F12%2Fgames-workshop%2Freport.html%23audio&data=0 >> 2%7C01%7Cjjwhite%40ets.org%7C25f33f3f7a54441aa90108d72b04269e%7C0ba6e >> 9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637025169157249677&sdata=e% >> 2FevgL6AwznyKzXLqEZgKNbmdLgXskNNPZUgmDQMfw8%3D&reserved=0 >> >> [2] >> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >> .w3.org%2FWAI%2FAPA%2Fwiki%2FAccessible_RTC_Use_Cases%23Audio_Routing >> _and_Multi_Channel&data=02%7C01%7Cjjwhite%40ets.org%7C25f33f3f7a5 >> 4441aa90108d72b04269e%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C63 >> 7025169157249677&sdata=iPsb3tFtYCUn0zxPbgXO7QkYKjP09VFUhMLzJF2IvA >> s%3D&reserved=0 >> >> >> >> -- >> Emerging Web Technology Specialist/Accessibility (WAI/W3C) >> >> >> >> ________________________________ >> >> This e-mail and any files transmitted with it may contain privileged >> or confidential information. It is solely for use by the individual >> for whom it is intended, even if addressed incorrectly. If you >> received this e-mail in error, please notify the sender; do not >> disclose, copy, distribute, or take any action in reliance on the >> contents of this information; and delete it from your system. Any >> other use of this e-mail is prohibited. >> >> >> Thank you for your compliance. >> >> ________________________________ > -- Emerging Web Technology Specialist/Accessibility (WAI/W3C) ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Tuesday, 27 August 2019 15:37:45 UTC