Error "Silence detected on local audio track" when running locally

[gsogol]

Self hosted livekit , running on 127.0.0.1:7880
Have .env.local with key/secret and pointing to ws://127.0.0.1:7880

Clicking start conversations, says publishing to room and then automatically get: "Silence detected on local audio track {room: 'oxwsws', roomID: 'RM_wWRwZSJ7kjtA', participant: 'human', pID: 'PA_oUqjWqHGxt2J', trackID: 'TR_AMiW4EZunbEvDw', …}".

No code changes besides .env.local

Browser permissions all say allow for localhost:3000 that is running the frontend

What am I doing wrong?

[bcherry]

@gsogol it's possible this is related to the krisp filter which isn't available for local/OSS livekit instances. you can comment it out in the project or switch to livekit cloud. let me know if that doesn't resolve the issue.

[gsogol]

@bcherry I commented out below but no change. Please see the attached image. It happens when I click Start Conversation and start speaking.

//const { isNoiseFilterEnabled, isNoiseFilterPending, setNoiseFilterEnabled } = useKrispNoiseFilter();
/*
useEffect(() => {
setNoiseFilterEnabled(true);
}, [setNoiseFilterEnabled]);
*/

[davidzhao]

if you went to https://meet.livekit.io, which microphone is selected by default?

[gsogol]

@davidzhao @bcherry works fine on meet.livekit.io. Seems like a regular mac microphone.

[davidzhao]

click on the drop down and ensure the mic is the default one that you'd expect..

do you get similar errors on meet.livekit.io?

[gsogol]

@davidzhao no errors at all on meet.livekit.io. Works fine. Default mic was selected on meet.

In my cloned Gemini playground, there is no option that I see to select any mic. I initially allowed access to mic and then all I see is just Start A Conversation button. There is no UI on my page for mic selection like in meet. See the the initial image I uploaded. Just a single blue button that gives an error as soon as I speak up.