I am in this Teams performance event, apparently the version we downloaded is a leaked version and is not supposed to be used, and they mentioned they will have something soon (but they wouldn't share roadmap, so don't know how soon is soon)
I think they said they will give the timeline at the end of this week? If I heard correctly?I am in this Teams performance event, apparently the version we downloaded is a leaked version and is not supposed to be used, and they mentioned they will have something soon (but they wouldn't share roadmap, so don't know how soon is soon)
Didn't hear that, I feel all the questions regards roadmaps are a bit vague.I think they said they will give the timeline at the end of this week? If I heard correctly?
Yeah definitely. Very sad though hearing that it's just an internal build that got leaked. It probably means it'll take so much more time before it gets released in stableDidn't hear that, I feel all the questions regards roadmaps are a bit vague.
I think there are still bugs on meeting. Like your cam looking awful on others and also you can't share screen I think. It just doesn't do it properly or somethingI heard that too. He said that they'd share news of a native Apple Silicon optimized version REAL soon...
At this point, I'm not sure if I'll revert to the release build or stay on this Universal Build that was leaked. I'll give it some more time right now.
This, I reckon there must be some API that's required in x86 Core Audio that's not ported to M1 yet
View attachment 1996476
You can use Activity Monitor to get information about the process. I don't have the CoreAudioDriver process when I run the x86-64 version of Teams but when I click on "CarbonComponentScannerXPC" and Open Files and Ports tab, I can see that it is a Rosetta process.Honest question for anyone who wants to answer: How does macOS on an M1 machine deal with a driver situation like this? Does Rosetta 2 handle it somehow?
/usr/libexec/rosetta/runtime
No issues except for the video quality artifacts and me appearing in black and white. It's a leaked beta so I'm ok with that. Memory footprint is much lower and it also launches _A_LOT_ faster. One bounce then maybe a second of the "Loading Microsoft Teams" splash screen?Guys how’s the performance in a call on the optimized version
I've tested it for less than 5 minutes. But the thing I really noticed was how much faster it is to load stuff up when switching between channelsNo issues except for the video quality artifacts and me appearing in black and white. It's a leaked beta so I'm ok with that. Memory footprint is much lower and it also launches _A_LOT_ faster. One bounce then maybe a second of the "Loading Microsoft Teams" splash screen?
Yes I agree! Everything is snappy and responsive now. I haven't run into any issues with screen sharing yet so I am going to stay on this beta for the time being.I've tested it for less than 5 minutes. But the thing I really noticed was how much faster it is to load stuff up when switching between channels
I'm having the same video problems. I look a pale green and pink to others on video calls!No issues except for the video quality artifacts and me appearing in black and white. It's a leaked beta so I'm ok with that. Memory footprint is much lower and it also launches _A_LOT_ faster. One bounce then maybe a second of the "Loading Microsoft Teams" splash screen?
Was told today that my screen sharing was also black and white with a tinge of green so at least that's consistentI'm having the same video problems. I look a pale green and pink to others on video calls!![]()
A Microsoft engineer has commented that it's actually called "exploration" in which makes sense because I have been using these versions back in 2019 and it has been getting lots of major Electron updates (from Electron 5 to Electron 7 to Electron 10 to Electron 13 to Electron 16) which is sort of similar to the way the VS Code nightly exploration channel works (https://github.com/microsoft/vscode/issues/143587).Was told today that my screen sharing was also black and white with a tinge of green so at least that's consistent
Still not complaining! This isn't even a public beta (was told the E in the version number was Experimental) but it's so snappy that I don't hate using Teams as much as I did last week
In fact in my personal experience, it's so much better on the Mac than on Windows. Which kinda makes no sense to me.FWIW, Teams runs like absolute crap on Windows too, so...yay?
This one is new - 1.5.00.11713 (osx-x64 + osx-arm64) - published on Wednesday, April 27, 2022 at 3:15 PM with 203 MB: https://statics.teams.cdn.office.net/production-osx/1.5.00.11713/Teams_osx.pkgA Microsoft engineer has commented that it's actually called "exploration" in which makes sense because I have been using these versions back in 2019 and it has been getting lots of major Electron updates (from Electron 5 to Electron 7 to Electron 10 to Electron 13 to Electron 16) which is sort of similar to the way the VS Code nightly exploration channel works (https://github.com/microsoft/vscode/issues/143587).
They also posted a source of where you can keep yourself up-to-date on Apple M1 (osx-arm64) builds: https://raw.githubusercontent.com/ItzLevvie/MicrosoftTeams-msinternal/master/defconfig
Is the new one better? Any bug fixes regarding the important meeting issues?This one is new - 1.5.00.11713 (osx-x64 + osx-arm64) - published on Wednesday, April 27, 2022 at 3:15 PM with 203 MB: https://statics.teams.cdn.office.net/production-osx/1.5.00.11713/Teams_osx.pkg
The one I have the ARM Build from Tuesday - You have Microsoft Teams Version 1.5.00.11505-E
My camera is working both the internal and external ones, and I don't see the green lines on my colleague's webcam feed so it seems to be fixing those.Is the new one better? Any bug fixes regarding the important meeting issues?
I see. So your camera on other people is fine now? How's screen sharing? Tbh if it's all working fine. It's probably worth it to move now lol even though it's not even a public beta ?My camera is working both the internal and external ones, and I don't see the green lines on my colleague's webcam feed so it seems to be fixing those.
Plus it's only using 961MB outside of calls! Vast improvement for me went down from 1.2GB on the previous build.
Everything is working for me thankfully! I have a external microphone and camera when connected to my Thunderbolt dock and thus far no issues.I see. So your camera on other people is fine now? How's screen sharing? Tbh if it's all working fine. It's probably worth it to move now lol even though it's not even a public beta ?
The pros of using Apple Silicon version is so crazy. The ram usage too is crazy little compared to using Rosetta
Yep . I noticed that the first few minutes of using it. If all is well I might as well move to it lol. Considering Microsoft is probably gonna take more months and months to release it to the public. As long as all the main features work fine. I'm fine ?Everything is working for me thankfully! I have a external microphone and camera when connected to my Thunderbolt dock and thus far no issues.
Only thing I'm real curious is the battery life, but I'll have to go on the go to test it out! (Thankfully tomorrow got a business trip so can look into it)
The biggest improvement for me is the way it's much faster to navigate thorough the UI especially the Channels section.
We just gotta keep looking at this page and see when the Experimental builds come out and update manually as we go.Yep . I noticed that the first few minutes of using it. If all is well I might as well move to it lol. Considering Microsoft is probably gonna take more months and months to release it to the public. As long as all the main features work fine. I'm fine ?
There is a link AFAIK that updates when a new release is out. You probably just need to do web monitoring and it should be fineWe just gotta keep looking at this page and see when the Experimental builds come out and update manually as we go.
From the older version to the Wednesday build it's already a vast improvement!