31–40 of 353 posts
Earlier quoted context omitted.
Couldn’t this be done by using some ML on the video stream?
Probably the user experience would not be as good, though, since it'd be an audio-only feature that only works if you've enabled video.
:-)
I feel like they're trying to make an insidious suggestion about the usage of these. IMO, there's likely a good reason - user experience. At a hardware level, grabbing the microphone can take time. Even worse that timing is inconsistent across devices, workloads, etc. That leads to a bad experience when unmuting and needing to delay your commentary. The solution to this is to keep the microphone on, but mute at a sof…
Earlier quoted context omitted.
Most MacBooks are also designed so the camera “on” light is impossible to disable in software.
Some hardware up there must be active and sending data even when the light's not on. It's how they make the (excellent, can hardly live without it now that I'm used to it) automatic monitor color temp adjustment work, AFAIK. Though maybe that's a separate sensor from the camera proper.
I feel like they're trying to make an insidious suggestion about the usage of these. IMO, there's likely a good reason - user experience. At a hardware level, grabbing the microphone can take time. Even worse that timing is inconsistent across devices, workloads, etc. That leads to a bad experience when unmuting and needing to delay your commentary. The solution to this is to keep the microphone on, but mute at a sof…
As seems to be pretty common, for the sake of privacy we do stop sending audio to the media server. That's a tradeoff, since we're still susceptible to losing a little bit while the audio connection resumes.
Edit: as others have mentioned, also useful to keep bluetooth headsets in two-way audio mode rather than reverting to audio output mode, since that's really disruptive.
I feel like they're trying to make an insidious suggestion about the usage of these. IMO, there's likely a good reason - user experience. At a hardware level, grabbing the microphone can take time. Even worse that timing is inconsistent across devices, workloads, etc. That leads to a bad experience when unmuting and needing to delay your commentary. The solution to this is to keep the microphone on, but mute at a sof…
My team and I built some of the world's most decentralized videoconferencing software, using WebRTC. You can try it on https://yang2020.app/meeting for example ... but it's available in all of our apps, including for teachers, etc. Since a major point of our platform (qbix.com/platform) is to avoid relying on external third parties, that meant we built a version of livestreaming that is completely peer-to-peer. Imagi…
I feel like they're trying to make an insidious suggestion about the usage of these. IMO, there's likely a good reason - user experience. At a hardware level, grabbing the microphone can take time. Even worse that timing is inconsistent across devices, workloads, etc. That leads to a bad experience when unmuting and needing to delay your commentary. The solution to this is to keep the microphone on, but mute at a sof…
On Linux at least, Teams continue to grab the microphone even after the meeting has ended. You can see this by looking at apps registered for "recording". I'm not sure how that can be justified. Besides privacy, the issue is that this prevents the sound card from going to sleep, which may be an issue on laptops. But I guess this is insignificant compared to the rest of Teams' power consumption.
Earlier quoted context omitted.
Probably the user experience would not be as good, though, since it'd be an audio-only feature that only works if you've enabled video.
The solution is obvious: have the camera watch you even when it's "off". :-)