This message was deleted.
# helpdesks
steep-balloon-41261
10/28/2023, 8:19 PMThis message was deleted.
👋 1
m
magnificent-art-43333
10/28/2023, 9:21 PMHey @narrow-raincoat-54988, how are you publishing your camera tracks?
Edit: Oh, I just saw same source. May I ask what your use case is for publishing the track twice — versus simply rendering it twice on the receiving end?
n
narrow-raincoat-54988
10/29/2023, 12:18 AMhey!! sure thing, my use case is a publisher showing multiple cameras, so each track is actually a different camera feed
narrow-raincoat-54988
10/29/2023, 12:20 AMmaybe my comment is confusing, the actual physical source of each track is a different camera. But in the code, the SDK is tagging them with the source
cameranarrow-raincoat-54988
10/29/2023, 12:21 AMfrom what I can see, the error is generated here: https://github.com/livekit/client-sdk-js/blob/main/src/room/participant/LocalParticipant.ts#L292
narrow-raincoat-54988
10/29/2023, 12:21 AMi followed the logic of how it gets there, and that's where i see the source being set as
camerab
brief-refrigerator-69901
10/29/2023, 12:42 AMI could be wrong, but i think you could publish multiple tracks for 1 participant with a track souce "unknown" for camera 2,3, etc. This said you'd need to add some custom handling on the client side. Someone from the LK team might be able to confirm or correct me about this.
m
magnificent-art-43333
10/29/2023, 12:43 AMYou can definitely publish multiple camera tracks. How are you publishing the camera now? Can you paste code pls?
n
narrow-raincoat-54988
10/29/2023, 12:54 AMso, the most basic code i'm using (after a lot of trial and error, and more
console.log Copy code
await LivekitClient.Room.getLocalDevices().then((devices) => {
devices.forEach((device) => {
if(device.kind == "videoinput"){
room.localParticipant.setCameraEnabled(true, {deviceId: device.deviceId}).then((trackPub => {
console.log(trackPub);
document.getElementById("video1").appendChild(trackPub.track.attach());
}));
}
});narrow-raincoat-54988
10/29/2023, 12:55 AMthis approach throws an error saying `trackPub`is undefined
narrow-raincoat-54988
10/29/2023, 12:57 AMhowever, I also tried an approach where I would enable and attach each camera through different actions:
Copy code
document.getElementById("cam1").addEventListener("click", function() {
room.localParticipant.setCameraEnabled(true, {name: "Cam1", deviceId: "ylAVQ0tA4yyzQYPw/GOGgLClpGxgFoGVSo9M84zzNM0="}, {stream: "Test1"}).then(a => {
document.getElementById("video1").appendChild(a.track.attach());
});
})
document.getElementById("cam2").addEventListener("click", function() {
room.localParticipant.setCameraEnabled(true, {name: "Cam2", deviceId: "qBRsmmiarD5rm/0XD/9MLky1kAGnMBEH6lkoJCPrWU0="}, {stream: "Test2"}).then(a => {
document.getElementById("video1").appendChild(a.track.attach());
});
})narrow-raincoat-54988
10/29/2023, 12:57 AMand with that, the behaviour is different, it republishes the track with whatever camera I enable last
d
dry-elephant-14928
10/29/2023, 1:15 AMsetCameraEnabled is a shortcut and that only supports a single track.
to publish multiple tracks of the same source, you should use LocalParticipant.publishTrack like documented here.
n
narrow-raincoat-54988
10/29/2023, 1:26 AMI've must have looked at the docs 200 times, yet it was right there
narrow-raincoat-54988
10/29/2023, 1:26 AMI got it running 🙂
narrow-raincoat-54988
10/29/2023, 1:26 AMthank you very much for the swift response!!
d
dry-elephant-14928
10/29/2023, 1:27 AMawesome!! we should make that section more clear then! especially regarding the limitations of the shortcuts
n
narrow-raincoat-54988
10/29/2023, 1:28 AMthat would help for sure, but I could've payed more attention and not get nearsighted on my approach
narrow-raincoat-54988
10/29/2023, 1:29 AMmuch obliged folks! I'm loving the platform so far!
❤️ 2
m
magnificent-art-43333
10/29/2023, 1:40 AMcc @acoustic-engineer-41666 for visibility
n
narrow-raincoat-54988
10/29/2023, 2:06 AMan extra note on this, everything works as expected, however a warning pops up on the browser debug console:
Copy code
"trace": "Error: publishing a second track with the same source: camera\n at Co.<anonymous> (<https://cdn.jsdelivr.net/npm/livekit-client/dist/livekit-client.umd.min.js:7:280160>)\n at Generator.next (<anonymous>)\n at <https://cdn.jsdelivr.net/npm/livekit-client/dist/livekit-client.umd.min.js:7:58176>\n at new Promise (<anonymous>)\n at gt (<https://cdn.jsdelivr.net/npm/livekit-client/dist/livekit-client.umd.min.js:7:57921>)\n at Co.publish (<https://cdn.jsdelivr.net/npm/livekit-client/dist/livekit-client.umd.min.js:7:279991>)\n at Co.<anonymous> (<https://cdn.jsdelivr.net/npm/livekit-client/dist/livekit-client.umd.min.js:7:279799>)\n at Generator.next (<anonymous>)\n at o (<https://cdn.jsdelivr.net/npm/livekit-client/dist/livekit-client.umd.min.js:7:57978>)"narrow-raincoat-54988
10/29/2023, 2:06 AMit still works, and it's not an error, despite the actual message, but it seems confusing
m
magnificent-art-43333
10/29/2023, 3:05 PMcc @polite-kilobyte-67570
🙏 1
p
polite-kilobyte-67570
11/01/2023, 9:55 AMthe wording of that warning is unfortunate (or rather wrong). We probably want to demote that to an info log and strip the “Error” mention from that message.
2 Views