bumpy-shampoo-17100
03/01/2025, 5:13 PMConfig: ${JSON.stringify(config)}
);
console.log('Screen Settings:', config.settings.inputs.screen);
}
}, [config, localParticipant, roomState]);
const agentVideoTrack = tracks.find(
(trackRef) =>
trackRef.publication.kind === Track.Kind.Video &&
trackRef.participant.isAgent
);
const localTracks = tracks.filter(
({ participant }) => participant instanceof LocalParticipant
);
const localVideoTrack = localTracks.find(
({ source }) => source === Track.Source.Camera
);
const localMicTrack = localTracks.find(
({ source }) => source === Track.Source.Microphone
);
const localScreenTrack = localTracks.find(
({ source }) => source === Track.Source.ScreenShare
);
console.log(Local Screen Share tracks: ${localScreenTrack}
);
console.log(Local Tracks: ${JSON.stringify(localTracks)}
)gray-monkey-83525
03/01/2025, 5:13 PMbumpy-shampoo-17100
03/01/2025, 5:15 PMgray-monkey-83525
03/01/2025, 5:15 PMuseEffect
is correctly checking for the Connected
state, but there might be a timing issue or a problem with how roomState
is being updated. Ensure that roomState
is accurately reflecting the connection status by logging it before the if
condition. Additionally, verify that localParticipant
is correctly initialized and associated with the room.
If the roomState
is indeed Connected
, but the error persists, it might be helpful to check if there are any asynchronous operations or state updates that could be affecting the timing of when setScreenShareEnabled(true)
is called. Consider adding more detailed logging to track the sequence of events and confirm that the connection is fully established before attempting to publish the screen share track.
Would you like more detailed guidance on debugging this issue or managing connection states?
Sources:
- https://livekit-users.slack.com/archives/C07FYCB7FRQ/p1728674567.746139 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.bumpy-shampoo-17100
03/01/2025, 8:00 PMgray-monkey-83525
03/01/2025, 8:00 PMTrackEgress
API, which exports tracks in their native format. To ensure that audio is exported as .wav
and video as .mp4
, you may need to explicitly specify the desired output format in your egress request.
According to the Track Egress documentation, the TrackEgress
API exports tracks without transcoding, meaning the output format depends on the track's codec. If you require specific formats like .wav
or .mp4
, consider using TrackCompositeEgress
, which allows transcoding to desired formats. You can specify the output format by setting the fileType
in the EncodedFileOutput
to MP4
for video and ensure the audio is processed to .wav
if necessary.
Would you like more detailed guidance on configuring TrackCompositeEgress
for specific output formats?
Sources:
- Track Composite Egress
- Track Egress documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.bumpy-shampoo-17100
03/01/2025, 8:05 PMgray-monkey-83525
03/01/2025, 8:06 PM