Bug fix | Race on initial publishing causing mute state to be desync

[BillCarsonFr]

No description provided.

[toger5]

I think this is the main place we need to use mute/unmute?

**
   * Observe changes in the mute states and update the LiveKit room accordingly.
   * @param scope
   * @private
   */
  private observeMuteStates(scope: ObservableScope): void {
    const lkRoom = this.connection.livekitRoom;
    this.muteStates.audio.setHandler(async (desired) => {
      try {
        await lkRoom.localParticipant.setMicrophoneEnabled(desired);
      } catch (e) {
        this.logger.error("Failed to update LiveKit audio input mute state", e);
      }
      return lkRoom.localParticipant.isMicrophoneEnabled;
    });
    this.muteStates.video.setHandler(async (desired) => {
      try {
        await lkRoom.localParticipant.setCameraEnabled(desired);
      } catch (e) {
        this.logger.error("Failed to update LiveKit video input mute state", e);
      }
      return lkRoom.localParticipant.isCameraEnabled;
    });
  }

[robintown]

You might also find the testScope utility to be convenient

[BillCarsonFr]

I think this is the main place we need to use mute/unmute?

I wonder if I don't prefer that we always use the high level API, it is doing quite a bunch of things.
But given the current high level API we cannot create without publishing. How much of a performance gain it is?