This message was deleted.

Hi @boundless-jackal-7234, does this happen for all participants or only for the ones that are not currently visible in the GridLayout (maybe on page two of the GridLayout). The GridLayout has some built-in paging logic that returns only the tracks for the currently visible page and participants. However, the easiest way is to use the RoomAudioRendere and let it handle the audio for you.

<LiveKitRoom>
  <RoomAudioRenderer />
</LiveKitRoom>

It will automatically subscribe to all audio tracks and make sure that the audio just works. When you use

RoomAudioRendere

you can remove the

AudioTrack

in your

ParticipantTile

For now this happened to everyone, and thank you I will try using RoomAudioRendere

Hi @boundless-jackal-7234, setting audio to

true

publishes the local tracks immediately after joining the room: docs The reason why you don’t here audio is possible because of autoplay policy. We created the

useStartAudio

(Source) hook and the

<StartAudio/>

(Docs | Source) component to deal with that.

/**

* In many browsers to start audio playback, the user must perform a user-initiated event such as clicking a button.

* The

useStatAudio

hook returns an object with a boolean

canPlayAudio

flag

* that indicates whether audio playback is allowed in the current context,

* as well as a

startAudio

function that can be called in a button

onClick

callback to start audio playback in the current context.

*

Let me know if this fixes your problem. 🤞

Thanx @eager-zoo-16408, worked fine with us