This message was deleted.
# announcements
s
This message was deleted.
d
Hey Jesse, Which platform are you building for? muting a video track should turn off the camera indicator. Though unpublish/republish should be supported too. Do you mind filing an issue for this under the repo where you are seeing this?
p
Hi @colossal-engine-37907, to add to this, one thing to be aware of is that js client will assume that in case you provide mediastreamtracks yourself (via getMedia and
new LocalTrack
) you are in charge of releasing and reacquiring media streams. In contrast, if you create the track via
createLocalTracks
, the device release will be managed within the sdk for you. This means on the other hand that muting a track will not release the device if you created a
LocalTrack
by yourself by default. One workaround would be to explicitly signal to the client sdk that you still want that track to be managed by the sdk, by passing in an optional constructor parameter
new LocalVideoTrack(mediastreamtrack, constraints, false)
that last parameter (which is true by default) will indicate whether the track will be treated as userProvided (i.e. unmanaged) within the sdk.
c
This is using the Web SDK. Thanks, setting userProvided = false did solve the problem with camera indicator getting turned on and off properly. I'll put together a bug report about publish / unpublish / publish not appearing to work for cams.
Probably would be good to have some details in the SDK docs added to the LocalVideoTrack / LocalAudioTrack constructor explaining what userProvidedTrack does. I wouldn't have guessed this changes the mute / unmute behavior. On that note, it's a little unintuitive to call mute on a video track rather than enable / disable or something.
d
appreciate the feedback. we'll add a note about this in the docs. you are totally right it's non-obvious to use mute on video tracks. We ultimately went with the same interfaces as audio tracks to be consistent