This message was deleted.

Yeah, you can call

publishTrack

multiple times with the same kind of input. some caveats though: • consumers tend to use

participant.getTrack(source)

to get the

RemoteTrackPublication

. if you are tagging both tracks with

Track.Source.Microphone

, it would lead to a bit of unpredictability there which one it returns. • alternatively you can give Tracks a name and use that to distinguish between different microphones.

Thanks @dry-elephant-14928, we just tried it but got an error: publishing a second track with the same source: microphone {oldTrack: LocalTrackPublication, newTrack: LocalAudioTrack, trace: 'Error: publishing a second track with the same.. shows up as a warning on console, but seems there's an underlying error being thrown

it's a warning as it could have been unintentional.. are you seeing the underlying track to not be published?

we got 2 tracks published, trying to get an understanding on whether they actually have 2 different mic inputs

I don't believe there are any limitations here..

It looks like it's publishing both tracks but we may have faced some of the caveats mentioned above