This message was deleted.
# helpdesk
s
This message was deleted.
🤩 1
a
Hi Antonio, looking forward to your next video! I’m going to cc @brainy-oxygen-72823 for this one
šŸ’Ŗ 1
šŸ™ 1
b
Hi Antonio, sorry you're running into trouble! what I'm hearing is that you can successfully publish to LiveKit from OBS, but playback isn't working in the web browser?
n
That seems to be correct! At least from the logs I could gather. No errors whilst creating ingress, no errors whilst creating viewer token, but when It comes to actually using the
useConnectionState
and
useTracks
, the results differ from the
livestream
repo by livekit.
I can prepare a minimum reproduction repo tomorrow for you to look at if it helps, also please dont feel like this is urgent or something, I know some of you are on holidays with your close ones and I do not want to disturb!! Great product
b
yes, that would be super helpful! don't worry about bothering us šŸ˜„ it's useful feedback and I want to make sure you're able to build with LK successfully
ā¤ļø 1
āž• 1
m
cc @eager-zoo-16408 for visibility as it relates to components
n
Oooh I think I got it! This is part of my code for creating ingress. For my current example the person that created the ingress is: (username is unique)
Copy code
const options: CreateIngressOptions = {
    name: self.username, // "antonio"
    roomName: self.username,  // "antonio"
    participantName: self.username, // "antonio"
    participantIdentity: self.username, // "antonio"
  };
And then, when i go about creating the viewer token I am using the identity of ingress creator, to create a viewer token using the same identity. As in the screenshot. Basically I am the only user trying to watch my own stream. For some reason, when I keep the same viewerToken identity and ingress participant identity (I assume?) the stream gets disconnected. But when I change my viewer token identity to anything else even like
{self.username}-viewer
it seems to work fine! Should I be using streamerToken instead of viewerToken if the streamer itself is trying to watch their video? On the livestream repo there is no issue like this because it uses faker to generate the identity.
p
generally speaking, if you try to connect with the same identity to the same room twice, the older connection of that identity will get disconnected and the newer connection will establish successfully.
in order to have the same display-name for both you could populate the
name
field in the token instead.
identity
is unique within a single room (thus the older one gets disconnected)
n
That makes sense, thank you! I was mostly confused because right now I am testing as the only user on my app, only streamer on my app and only viewer of that stream, and all over the place I have the same identity, roomName and participantIdentity "antonio". So it seems like when I create an ingress with "antonio" and then create a viewer token with "antonio" I get disconnected. What I do for now is create ingress with "antonio" and create a viewer token with my userID instead, but also pass "name" to be "username" so it can be displayed where needed. I will continue like this for now since it seems to be working fine, thank you all for your help! ā¤ļø
šŸ™Œ 2