Re: [mediacapture-main] Redefine groupId to be more narrow and useful (#899)

> Use cases are similar to screen capture, and so there is overlap with `getDisplayMedia()`.

> @karlt that comment was a little too terse for me to understand it.

I just meant that someone may wish to record or share the output of a particular speaker device in the same way that they might that of a tab or application.  It wasn't a comment for or against monitors being in the same group as their output device.

> If I have a list of input devices and a list of output devices, I'd like to know what I/O pairs together. Common devices where this is useful include USB headsets, USB microphones with integrated headphone jacks, and DJ mixers/decks.

I assume everyone's agreeing that microphones and speakers on the same headset should be in the same group.

The DJ mixer/deck and stereo-to-stereo effects unit, for example, are interesting cases because their inputs and outputs are useful when used together, though not really in the sense usually considered for a video call.

If the input and output of an effects unit should be in the same group, then its hard to argue that those of a pass-through effects unit, like an output and its monitor, should not be in the same group.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 28 October 2022 02:14:15 UTC