Live data from Hacker News

Google Meet rolls out multi-device adaptive audio merging

workspaceupdates.googleblog.com

141–150 of 279 posts

Re: Google Meet rolls out multi-device adaptive audio merging

#141

Earlier quoted context omitted.

This does not complicate matters.

It does in ways you likely don't understand. At large enterprises with satellite offices, most of us don't want to sit at our desks and annoy our coworkers who are also in-office by taking calls at our desks. That leaves meeting rooms, which are at a premium. Full single device for everyone would mean either everyone loudly shouting at their desks from within their noise canceling headphones or the company giving eve…

Why is anyone shouting at their desk in this scenario?

Re: Google Meet rolls out multi-device adaptive audio merging

#142
post #29

Earlier quoted context omitted.

I'm not that deep into Google latest rebrand activity... how is Google Meet related to LLM model? or do they call many unrelated things Gemini?

It's not related to Gemini. I suspect they're putting non-LLM stuff behind the Gemini paywall to make Gemini look more profitable than it is. Like most LLM rollouts, it could maybe become cashflow-positive, but it will likely never be profitable because of the many billions it takes to compete with OpenAI and Meta.

Bundling could also be a strategy to get people to try LLM products. You want X, you have to buy a package with both X and Y to get X. Many people will think, "I'm paying for Y, might as well try getting something out of it."

Re: Google Meet rolls out multi-device adaptive audio merging

#145
post #5

Meet, to me, is the perfect balance of functionality and simplicity (as an end user). And features like this only make that more apparent. Zoom and Teams always frustrate me, even though they're what I use far more often. It's too bad that video conferencing is largely a game of who has the most boxes checked - IT admins and A/V folk are the ones that need to be convinced, and Meet just doesn't ...meet... their needs

[dead]

Re: Google Meet rolls out multi-device adaptive audio merging

#146

Earlier quoted context omitted.

> As far as Teams vs. Meet, it seems like Teams is great when you are working with people that have climbed it's learning curve. Can you give one example?

I can give several. Most of them are not Meet specific but how Meets integrates with rest of Google Products. This is actually overall massive problem with Google Workspaces in general IMO. 1) You can call someone in Teams. Sure, Google Chat has "Start Meeting now" but it's very passive. I know some will see this as negative but ringing has massive advantages around UX. 2) Chat, Teams will persist chat after meeting…

> The fact so many Google Workspaces companies have Slack is just frustrating

True, but Teams is so buggy and had in many areas has no UX per se.

I'd take for 2 great products (Slack + Meet) with bad integration vs great integration of shitty products.

Re: Google Meet rolls out multi-device adaptive audio merging

#147

I just want to say that this is really actually kind of mind-blowing from an audio engineering perspective. Outputting audio from multiple laptops in the same room is easy. Perfectly syncing it is harder. Implementing echo cancellation across all of that is quite a bit trickier than regular single-device echo cancellation. But then treating all the laptop microphones as a kind of microphone array, having to deal with…

I think this is much simpler than what you're suggesting. Careful microphone level management can handle this. No need for audio sync. I know they use the word "sync" but that's a very broad term.

Re: Google Meet rolls out multi-device adaptive audio merging

#148
post #26

GitLab offers a nice course about transitioning to remote work. One of the items in their guidelines about online meeting is not having hybrid meetings. This is, all those attending must attend from their own device rather than the meeting room one (see Jabra) precisely for the reasons this feature tries to address.

It gets complicated when half a team is in the office taking the same call from their desks, easier for Gitlab because they are full remote

Only if you don't have a reasonable amount of offices (one per person)...

Re: Google Meet rolls out multi-device adaptive audio merging

#149

I just want to say that this is really actually kind of mind-blowing from an audio engineering perspective. Outputting audio from multiple laptops in the same room is easy. Perfectly syncing it is harder. Implementing echo cancellation across all of that is quite a bit trickier than regular single-device echo cancellation. But then treating all the laptop microphones as a kind of microphone array, having to deal with…

If you were doing this kind of multipath and array signal processing on RF signals, it would be covered by ITAR. And yet Google can ship it anywhere on the planet via HTTPS and webasm... Things that make you go hmm.

It would be....surprising if this was done client side and not serverside.

Re: Google Meet rolls out multi-device adaptive audio merging

#150

Earlier quoted context omitted.

It very rarely matters which product is "better" in any objective sense. If you are team that work with Teams, your meetings will be on teams. Teams could be much worse than Zoom or Meet, you wouldn't move your group from Teams for one meeting anyway.

We work with a lot of external customers. Teams, GotoMeeting, GotoWebinar, Skype, Google Meet, Zoom. And honestly, they all suck. Getting logged in is always a problem. Setting my name permanently is literally always a problem (I have zero idea why). Viewing someone elses screen always stinks because the scaling is just not good. On top of that you can't compare Teams to Google Meet because literally every organizati…

I used to use a lot of random services while at work, and then I found Jitsi (browser based) and honestly I’m astounded it hasn’t taken over because of its simplicity or ability to just handle anything thrown at it.
Post reply on HN