4 ms·

> I think the explanation is quite mundane > There’ll be plots of various stats, including CPU utilization. I think meet will also helpfully suggest closing ta

> I think the explanation is quite mundane > There’ll be plots of various stats, including CPU utilization. I think meet will also helpfully suggest closing tabs if your machine is overloaded This is not mundane at all, it's a perfect example of giving your product an unfair competitive advantage. If Meet users are told why their meeting isn't working correctly but Zoom, Teams and Slack, Meet users are going to have a better experience that Zoom, Teams or Slack has no way of replicating. No wonder every other meeting provider pushes you aggressively into using their desktop app, Google Meet's desktop app is just Chrome!

trealira 2y ago
> If Meet users are told why their meeting isn't working correctly but Zoom, Teams and Slack, Meet users are going to have a better experience that Zoom, Teams or Slack has no way of replicating. I had to re-read this a few times; did you accidentally omit a word? > If Meet users are told why their meeting isn't working correctly but Zoom, Teams and Slack aren't, Meet users are going to have a better experience that Zoom, Teams or Slack has no way of replicating. I fully agree with you, though; it's anticompetitive for them to use Chrome to give their other products an advantage.
- lupire 2y ago
  Insert "aren't" after the first "Slack".
  - trealira 2y ago
    That makes sense; that's how I interpreted it.
hot_gril 2y ago
At least other video conferencing tools don't lag like Meet, so users don't need to debug ;) I think this has to do with all of them using H.264 while Meet uses VP8/9.
- ddalex 2y ago
  Achtually its AV1 which is even worse. but saves a bunch of bandwidth
- fayalalebrun 2y ago
  As a result of a flaw in the protocol itself or in its implementation?
  - hot_gril 2y ago
    The implementation is what I was thinking of. I've also heard claims that VP9 is inherently slower to encode than H.264, but no idea if that's accurate. AVC/H.264 has very broad hardware support. For example, the 2019 MBP I'm using right now can't do hardware-accelerated VP9 encoding, but even 2011-ish MBPs can do H.264 acceleration in both directions. Intel's support matrix: https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video For PCs with dedicated GPUs, Nvidia's matrix doesn't even mention VP8/9 encoding, and for decode there are a lot of VP8/9 "no"s for GPUs that have "yes" for H.264: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new https://developer.nvidia.com/video-encode-and-decode-gpu-sup... AV1 looks like it's getting broader support, but it's still new. Zoom's release notes mention they'll use AV1 if the participants support it, and I don't see a similar note about VP8/9.
    - ddalex 2y ago
      there are very few CPUs supporting AV1 hw encoding now, all is on the CPU
      - hot_gril 2y ago
        It's only in newer chips, but it's broader than VP8/9 was. Intel and Nvidia's newest chips support hardware en/decoding of AV1, while Nvidia never supported VP8/9.
- deleted 2y ago
  [deleted]
flanqueue 2y ago
Example of why this is not mundane https://x.com/fedekauffman/status/1811019707165856259 https://x.com/fedekauffman/status/1811019707165856259

trealira 2y ago

> If Meet users are told why their meeting isn't working correctly but Zoom, Teams and Slack, Meet users are going to have a better experience that Zoom, Teams or Slack has no way of replicating. I had to re-read this a few times; did you accidentally omit a word? > If Meet users are told why their meeting isn't working correctly but Zoom, Teams and Slack aren't, Meet users are going to have a better experience that Zoom, Teams or Slack has no way of replicating. I fully agree with you, though; it's anticompetitive for them to use Chrome to give their other products an advantage.

lupire 2y ago
Insert "aren't" after the first "Slack".
- trealira 2y ago
  That makes sense; that's how I interpreted it.

hot_gril 2y ago

At least other video conferencing tools don't lag like Meet, so users don't need to debug ;) I think this has to do with all of them using H.264 while Meet uses VP8/9.

ddalex 2y ago
Achtually its AV1 which is even worse. but saves a bunch of bandwidth
fayalalebrun 2y ago
As a result of a flaw in the protocol itself or in its implementation?
- hot_gril 2y ago
  The implementation is what I was thinking of. I've also heard claims that VP9 is inherently slower to encode than H.264, but no idea if that's accurate. AVC/H.264 has very broad hardware support. For example, the 2019 MBP I'm using right now can't do hardware-accelerated VP9 encoding, but even 2011-ish MBPs can do H.264 acceleration in both directions. Intel's support matrix: https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video For PCs with dedicated GPUs, Nvidia's matrix doesn't even mention VP8/9 encoding, and for decode there are a lot of VP8/9 "no"s for GPUs that have "yes" for H.264: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new https://developer.nvidia.com/video-encode-and-decode-gpu-sup... AV1 looks like it's getting broader support, but it's still new. Zoom's release notes mention they'll use AV1 if the participants support it, and I don't see a similar note about VP8/9.
  - ddalex 2y ago
    there are very few CPUs supporting AV1 hw encoding now, all is on the CPU
    - hot_gril 2y ago
      It's only in newer chips, but it's broader than VP8/9 was. Intel and Nvidia's newest chips support hardware en/decoding of AV1, while Nvidia never supported VP8/9.
deleted 2y ago
[deleted]

flanqueue 2y ago

Example of why this is not mundane https://x.com/fedekauffman/status/1811019707165856259 https://x.com/fedekauffman/status/1811019707165856259