LiveKit Community

why i getting this error even i added the dependencies.:- Cannot access class 'org.webrtc.PeerConnection.RTCConfiguration'. Check your module classpath for missing or conflicting dependencies

did you add jitpack like <https://github.com/livekit/client-sdk-android/#installation|indicated in the README>?

when using the ConnectRoom i am getting the error of "Cannot access class 'org.webrtc.PeerConnection.RTCConfiguration'. Check your module classpath for missing or conflicting dependencies".

where did you add the jitpack dependency?

Have you tried invalidating cache and restart in android studio?

Even after creating new project and adding dependencies still getting the same error.

Does the same occur if you try to build the example app?

could you create a reproducible example project and upload it here or to github?

just tried creating a new project and didn't encounter any issues with the dependency resolution

Can you send me the empty project with successful implemented dependencies, it can be help me <@U01NZKTNE1H>

I don't know why i am getting this error.

<https://github.com/davidliu/LiveKitCompile>

not sure what you mean, do you still have the error?

could you upload a project for me to look at? it'd be quicker that way for me to identify the error if you still have one

Not even any single error after importing your project

Okay i am sending you my project <@U01NZKTNE1H>

test.zip

ah you have dependencyResolutionManagement in your settings.gradle

some of the newer android templates from android studio use that instead

that's from including the protobuf library directly into your app dependencies

if you want to work off of the sample-app-common example, you should copy its dependencies

though you probably shouldn't really need the protobuf library directly unless you're debugging something specific

the simulateScenario is for testing purposes only

Now i'm getting this error....but when i remove the livekit dependency the error gone

When i add the dependencies of firebase and livekit i get this error <@U01NZKTNE1H>

Error is coming after adding either of the two

I figure out that the this error comes because of firestore dependencies

can you please paste the message? screenshots are difficult to read

i am sending you the txt file. i paste the all error in that.

error.txt

Please help me to fix this <@U01NZKTNE1H> <@U01KZ61GV5Z>

<https://github.com/protocolbuffers/protobuf/issues/8104|this> appears to be the issue. <@U01NZKTNE1H> do you think we should depend on lite instead? I think we are using non-lite today. I think it's just adding option "lite"
```  generateProtoTasks {
    all().each { task -&gt;
      task.builtins {
        java {
          option "lite"
        }
      }
    }
  }```

we can't use lite, as it doesn't support some things we need iirc

<@U035CJ1GK0F> follow the solution provided here: <https://github.com/livekit/client-sdk-android/issues/42>

Get another error when connecting with url &amp; token in CallViewModel :- java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/protobuf/TypeRegistry; <@U01NZKTNE1H> <@U01KZ61GV5Z>

Why don't you try livekit with firestore dependency. You will also face this problem.

Okay i fixed the issue by myself. Here is the solution.

just we have to add these lines in build.gradle(module)

`android{`
    configurations {
        implementation.exclude module:'protobuf-javalite'
        implementation.exclude module:'proto-google-common-protos'
        implementation.exclude module:'protolite-well-known-types'
        implementation.exclude module:'protobuf-lite'
    }
}

Now i am getting the error in firestore <@U01NZKTNE1H>

After exclude the protolite-well-known-types i get the error of runtime exception from firestore

Can you please try once with livekit and firestore dependency and check if they both are working or not?

firestoreError.txt

Live Us.zip

i comment out the configuration in build.gradle so you can check all the error. I fixed the duplicate error by it but getting the error of firestore. I implemented the mobile authentication to this project. <@U01NZKTNE1H>

<@U035CJ1GK0F> I would appreciate it if you could avoid tagging people multiple times in the same thread. We are of course happy to help you out, but please mind the fact that there are other things that require our attention. :slightly_smiling_face:

looking into seeing if we can use javalite and avoid this dependency issue, this will take some time to move over if able

<@U01NZKTNE1H> no problem pls take your time and thank you

ok, I've migrated over to using the protobuf-javalite dependency, you can try it on 0.9.1-SNAPSHOT

I don't understand how can i use it? <@U01NZKTNE1H>

You means to change the version from 0.9.0 to 0.9.1-SNAPSHOT ? If yes then i'm getting the warning of failed to resolve: io.livekit:livekit-android:0.9.1-SNAPSHOT

can you send me the project with that? <@U01NZKTNE1H>

ah sorry, add the maven repo for snapshots:
```
maven { url '<https://s01.oss.sonatype.org/content/repositories/snapshots/>' }```


Thanks <@U01NZKTNE1H> you helped me alot. Now firestore and livekit both are working fine.

<@U027EKN77FG> <@U022KB72NFJ> <@U01KZ61GV5Z>

I can get the participant and their tracks by doing `time.Sleep(time.Second * 5)` on my local machine. Not sure if it's a latency problem. But I don't think blocking the thread for 5 seconds is a good idea

Basically what I want to do is recording. When a participant joins the room, I want to start recording that participant (video and/or audio tracks). To do so I need to get the SID of the participant tracks. The event `track_published` could be useful, but it wasn't fired at all

ah ok, I think we are sending the callback a bit too early. before it's done updating the state.

it is, however, expected that no tracks are published when the participant is first joined. we do plan to expose them via webhooks too.

Thanks for your reply <@U01KZ61GV5Z>. I've set up a polling goroutine that checks per tick if the participant is ready for recording. It would be cool to expose the events in an asynchronous fashion (Redis Streams maybe?) so we can do pub-sub. Any potential to go in this direction ?

would webhooks for published tracks work for your needs? we would want to avoid exposing the underlying DB to clients

I see, the webhooks alone will be good enough. I just need the participant tracks to be published already by the time the event gets fired

piggy-backing on this… i’m not getting track_published events to my webhook endpoints. i see them in the docs though

found it <https://docs.livekit.io/client-sdk-js/interfaces/roomoptions.html#videocapturedefaults>

Hey sorry for not getting back to that comment

WebRTC is has encryption enabled by default (and they removed that variable in m97 so it can't be turned off without rebuilding the library)

You can check here: <https://github.com/livekit/client-sdk-js#example-listing-and-selecting-a-camera-device>

image.png

I've got speech to text working using just the golang livekit sdk and gcp speech-to-text api. There is a room.Callback.OnTrackSubscribed that I'm calling to get access to the audio files. You'll need to decode the track.ReadRTP() using an opus decoder.
This example is using pion, but is pretty similar: <https://github.com/daniel-d-truong/whohacks/blob/329d3054f18b307d1b1ce2864f59800ba54d65e0/pkg/stream/stream.go>

hey <@U02G87YSENA>, it depends on your time frame for this. If the need is immediate, what <@U02Q4J8KS85> suggested is the way to go. But I would add that you should use a samplebuilder as seen in <https://github.com/livekit/server-sdk-go/blob/main/examples/filesaver/main.go|this example> to ensure you are reading packets in order (since it's UDP, it may be transmitted out of order or received multiple times)

We are working on a simpler solution for this (universal egress), that would instruct LiveKit to post specified tracks to an external server via websocket. The ETA is about ~2 months before it'll be released.

Sorry a bit late to the party, but I'm the author of the PR mentioned. There are a few improvements to be made but I was busy with a separate recorder service (<https://github.com/CloudGroundControl/livekit-recorder>). I'll update the PR a bit later today or tomorrow.

Thank you guys, I’m going to try these out.

&gt; L’ll update the PR a bit later today or tomorrow.
Thanks mate

&gt; separate recorder service (<https://github.com/CloudGroundControl/livekit-recorder>).
~What’s features are you adding here?~ Nevermind I see these have been mentioned in the repo

Hi <@U02G87YSENA>, here's the updated PR: <https://github.com/livekit/server-sdk-go/pull/51> . I closed the previous one as it was too outdated

Thanks <@U02SGSET1RT>, I will check this out

Screen Recording 2022-03-19 at 7.42.20 PM.mov

Got it to work, super buggy code on my end right now, but good proof of concept

Hi <@U02RJP33ZQX>! Thanks for all the kind words you shared. I’m excited to hear you’ve been making progress with LiveKit.

At the moment, participant metadata can only be updated from the backend using one of our server SDKs (<https://github.com/livekit?q=server-sdk&amp;type=all&amp;language=&amp;sort=>)

You can create an API endpoint and use the server SDK within that endpoint to perform the required metadata updates. Those updates will be flushed to all other participants in the room.

We may, and have discussed, being able to make updates to participant metadata directly from the client but we haven’t designed how that will work yet.

here's the issue explaining the reasons for not enabling participants from performing these updates: <https://github.com/livekit/client-sdk-js/issues/148>

Okay, I see now. I think it is time to go deeper on API endpoint part on Go. Thanks for your help. :pray:

Hello guys, I'm interested in developing Mattermost plugin for LiveKit, and trying to get going with VM installation. Generated init_script.sh was runned, but redis container refuses to start: with

# Warning: Could not create server TCP listening socket ::1:6379: bind: Address not available

You may have to install docker compose as well

<https://docs.docker.com/compose/install/>

init_script.sh installs it, saying that docker itself seems already installed

hey <@U036FGT00TT>, does it have docker compose 2 available? The bind failure sounds like you already have Redis running on the machine. LiveKit could use an existing Redis install instead of trying to bundle it

<https://github.com/livekit/livekit-server/releases/tag/v0.15.4>

<@U01KZ61GV5Z> or <@U01KZ0SCDKL> Do you have a sec to help me with this?

Disclosure: I don’t know Dart and I’m not intimately familiar with our Flutter SDK, but I poked around in `local.dart` and doesn’t seem like the equivalent is currently there.

I’ll defer to <@U02MAJLGN65> on this one.

<@U02MAJLGN65> Do you have a sec to help with this? I'm looking to get a list of available video and audio sources for the user to choose. Thanks in advance.

What platform are you mainly interested in ?

Windows, Mac, Linux and web. IOS and Android will use the camera swap that's in the example code. and thanks for helping!

I tried `room.localparticipant.videoTracks` but that is only the currently used tracks.

I'm looking at the following right now, does `CameraPosition` work on all platforms?
<https://github.com/livekit/client-sdk-flutter/blob/main/example/lib/widgets/controls.dart>

At the moment we don’t have great support for device enumeration &amp; selection, but we are working on it :slightly_smiling_face:

For the meantime you can try the method described in this thread :
<https://livekit-users.slack.com/archives/C01KVTJH6BX/p1646187208133309>

Is the above mentioned also going to apply to audio streams as well?

For context. Attempting to add the ability for users to change audio and camera devices.

Is there a way to change this on the fly or only when initiating the room?

Thanks for the context, I will need to check `flutter_webrtc` ’s code, but I think audio might not work for native platforms at the moment.

This is something I will work on in the future.

I assume currently it won’t work on-the-fly, you will probably need to re-create the track.

Device management (Hardware access) is pretty tricky with Flutter (each platform is pretty different here) But it’s definitely something I want to improve over time.

That sounds great! I'm using Flutter for the obvious reasons, one codebase, all platforms. This project is great and exactly what I was looking for.

Hello can I have more information with the error? `VideoView` should be public.

I've copied code from GitHub <https://github.com/livekit/client-sdk-swift>

And here is my error
```'VideoView' initializer is inaccessible due to 'internal' protection level```

Thanks for finding this, the UIKit version’s *init* wasn’t marked `public` and defaults to internal…

Can you try using this branch ?
<https://github.com/livekit/client-sdk-swift/tree/fix-access-level>

let me know if you have any other issues :slightly_smiling_face:

Thank you so much :slightly_smiling_face:

hey juan,
that’s a good point.
Alternatively to your suggestion of not firing for screen share audio, we could think about including the source(s) of audio in the event handler or fire a separate event for screenshare audio (not sure how realistic that is).
I’m trying to think about occasions where people would _want_ to know that the screenshare is producing audio.

I think here’s a good place to voice suggestions, maybe even better in <#C025KM0S1CK|dev> .

I can see the case that "speaking" events are for mic tracks. if we had an event for audio activity.. that'd make more sense on the screen share track

Screenshot 2022-03-11 at 14.36.41.png

In our case we do not really need to know that a screen share is producing audio. It is more so that we want to know when a user is ‘speaking’, to show a speaking indicator around the user his camera element.

In the image below, the indicator of user A would almost constantly show because his screen share is producing audio. I think this might be confusing to a user watching the stream. Minor thing though.

I agree with you that "speaking" events should be limited to tracks with a Mic source. we'll make a change on our side

sorry, our library uses coroutines extensively, we don't have any sample code without it

I just answered my own question. No. :sweat_smile:

The commit I'm trying to grab is <https://github.com/livekit/client-sdk-flutter/commit/288bd99dca4604cf04be0db5e6daf49abb99f535>

Do I just need to wait for the next release?

You can use the same method described here (for now)  :point_right:
<https://github.com/livekit/client-sdk-flutter/issues/76#issuecomment-1022898436>

<@U02MAJLGN65> I'm getting a `malformed constraints` on the webrtc side.

`could not publish video: Unable to getUserMedia: TypeError: Failed to execute 'getUserMedia' on 'MediaDevices': Malformed constraint: Cannot use both optional/mandatory and specific or advanced constraints.`

Is the Flutter/Web ?
I’ll take a look when I have time

damn, that's annoying, will have to detect platform when supplying the device id

hmmm, running into issues with deviceId not being respected for flutter web, this is a little problematic

ah, my usb devices aren't being detected by chrome...

k, fixed my usb detection issues, pr is up at <https://github.com/livekit/client-sdk-flutter/pull/91>

Hello, I got this log in server side and user unable to join when this happen. Can anyone help ?

which version of the server are you using? and can you recall any usage that could help reproduce the issue?

I'm using latest docker image 0.15.5 with multi region setup. I use keydb multi master setup to replace redis. The server error only have 2 rooms with total 6 participants.

this is strange.. we've seen this previously due to actual bugs. and this is indicative of a deadlock somewhere.

v0.15.5 had been put under heavy load tests prior to release. We have not been able to reproduce this (even while handling 1000s of simultaneous users)

if you can share any repro steps for this (OS, environment, client platform/version, any tracks that are published, and what they are doing).. that'd be helpful in tracking it down further.

Do you think it relate to keydb replica issue ? I setup keydb on Singapore and US and those instance replica to each other.

<https://docs.keydb.dev/docs/multi-master/>

what's the latency between livekit to your redis instance?

Oh sorry, i mean 175ms is the latency between 2 redis instances. The livekit server at each region connects to the redis in the same region in the same LAN network so the latency is very short.

I see, and can you provide any details on what the clients are doing?

Sorry, i don't know what client did. In server side i found this error before problem happened.

2022-03-10T05:40:29.687Z    *ERROR*   livekit.mux mux/mux.go:122  mux: ending readLoop dispatch error packetio.Buffer is full, discarding write
    {"room": "open-frt", "roomID": "RM_vvoSty3z9MjF", "participant": "6907506175224012800|David Huang|wke7pusv", "pID": "PA_pEs3R4jaCMrP"}
<http://github.com/pion/webrtc/v3/internal/mux.(*Mux).readLoop|github.com/pion/webrtc/v3/internal/mux.(*Mux).readLoop>
    /go/pkg/mod/github.com/pion/webrtc/v3@v3.1.23/internal/mux/mux.go:122
redis: 2022/03/10 05:49:34 pubsub.go:599: redis: &amp;{%!s(*redis.PubSub=&amp;{0xc0003ce1c0 0x700600 0x702ca0 {0 0} 0xc0001341e0 map[rtc_channel:ND_OXHwd2d1:{} signal_channel:ND_OXHwd2d1:{}] map[] false 0xc00023c4e0 0xc000df62a0 {1 {0 0}} 0xc00046c080 &lt;nil&gt;}) %!s(chan *redis.Message=0xc000df61e0) %!s(chan interface {}=&lt;nil&gt;) %!s(chan struct {}=0xc0000d0a80) %!s(int=100) %!s(time.Duration=60000000000) %!s(time.Duration=3000000000)} channel is full for 1m0s (message is dropped)
redis: 2022/03/10 05:50:34 pubsub.go:599: redis: &amp;{%!s(*redis.PubSub=&amp;{0xc0003ce1c0 0x700600 0x702ca0 {0 0} 0xc0001341e0 map[rtc_channel:ND_OXHwd2d1:{} signal_channel:ND_OXHwd2d1:{}] map[] false 0xc00023c4e0 0xc000df62a0 {1 {0 0}} 0xc00046c080 &lt;nil&gt;}) %!s(chan *redis.Message=0xc000df61e0) %!s(chan interface {}=&lt;nil&gt;) %!s(chan struct {}=0xc0000d0a80) %!s(int=100) %!s(time.Duration=60000000000) %!s(time.Duration=3000000000)} channel is full for 1m0s (message is dropped)
redis: 2022/03/10 05:51:34 pubsub.go:599: redis: &amp;{%!s(*redis.PubSub=&amp;{0xc0003ce1c0 0x700600 0x702ca0 {0 0} 0xc0001341e0 map[rtc_channel:ND_OXHwd2d1:{} signal_channel:ND_OXHwd2d1:{}] map[] false 0xc00023c4e0 0xc000df62a0 {1 {0 0}} 0xc00046c080 &lt;nil&gt;}) %!s(chan *redis.Message=0xc000df61e0) %!s(chan interface {}=&lt;nil&gt;) %!s(chan struct {}=0xc0000d0a80) %!s(int=100) %!s(time.Duration=60000000000) %!s(time.Duration=3000000000)} channel is full for 1m0s (message is dropped)
redis: 2022/03/10 05:52:34 pubsub.go:599: redis: &amp;{%!s(*redis.PubSub=&amp;{0xc0003ce1c0 0x700600 0x702ca0 {0 0} 0xc0001341e0 map[rtc_channel:ND_OXHwd2d1:{} signal_channel:ND_OXHwd2d1:{}] map[] false 0xc00023c4e0 0xc000df62a0 {1 {0 0}} 0xc00046c080 &lt;nil&gt;}) %!s(chan *redis.Message=0xc000df61e0) %!s(chan interface {}=&lt;nil&gt;) %!s(chan struct {}=0xc0000d0a80) %!s(int=100) %!s(time.Duration=60000000000) %!s(time.Duration=3000000000)} channel is full for 1m0s (message is dropped)

Mar 04 20:42:54 w1 livekit-server[1766386]: 2022-03-04T20:42:54.420+0300    INFO    livekit    service/rtcservice.go:203    new client WS connected    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "connID": "CO_aZhZkMMxcsUi", "roomID": "RM_FnL9YGAJwyS9"}
Mar 04 20:42:54 w1 livekit-server[1766386]: 2022-03-04T20:42:54.421+0300    INFO    livekit    rtc/room.go:225    new participant joined    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "roomID": "RM_FnL9YGAJwyS9", "pID": "PA_JRUz6UK32XUh", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "protocol": 5, "options": {"AutoSubscribe":true}}
Mar 04 20:43:02 w1 livekit-server[1766386]: 2022-03-04T20:43:02.641+0300    INFO    livekit    sfu/streamallocator.go:680    channel congestion detected, updating channel capacity    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "roomID": "RM_FnL9YGAJwyS9", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "pID": "PA_JRUz6UK32XUh", "old(bps)": 0, "new(bps)": 226474, "lastReceived(bps)": 226474, "nackRatio": 0}
Mar 04 20:43:09 w1 livekit-server[1766386]: 2022-03-04T20:43:09.373+0300    INFO    livekit    sfu/streamallocator.go:680    channel congestion detected, updating channel capacity    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "roomID": "RM_FnL9YGAJwyS9", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "pID": "PA_JRUz6UK32XUh", "old(bps)": 226474, "new(bps)": 71074, "lastReceived(bps)": 71074, "nackRatio": 0}
Mar 04 20:47:07 w1 livekit-server[1766386]: 2022-03-04T20:47:07.848+0300    INFO    livekit    service/rtcservice.go:184    server closing WS connection    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "connID": "CO_aZhZkMMxcsUi"}
Mar 04 20:47:14 w1 livekit-server[1766386]: 2022-03-04T20:47:14.062+0300    INFO    livekit    service/rtcservice.go:203    new client WS connected    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "connID": "CO_4Eq9UHcRY6K5", "roomID": "RM_FnL9YGAJwyS9"}
Mar 04 20:47:16 w1 livekit-server[1766386]: 2022-03-04T20:47:16.863+0300    INFO    livekit    service/rtcservice.go:203    new client WS connected    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "connID": "CO_4wqgkHtZ22DP", "roomID": "RM_FnL9YGAJwyS9"}
Mar 04 20:47:24 w1 livekit-server[1766386]: 2022-03-04T20:47:24.357+0300    INFO    livekit    service/rtcservice.go:184    server closing WS connection    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "connID": "CO_4Eq9UHcRY6K5"}
Mar 04 20:47:26 w1 livekit-server[1766386]: 2022-03-04T20:47:26.969+0300    INFO    livekit    service/rtcservice.go:184    server closing WS connection    {"room": "conference_93967e09-c76d-4388-93e5-7e425f04129d", "participant": "968558db-77bf-45f7-bd0d-6c6632fabe68", "connID": "CO_4wqgkHtZ22DP"}

Mar 04 20:51:11 w1 livekit-server[1766386]: redis: 2022/03/04 20:51:11 pubsub.go:599: redis: &amp;{%!s(*redis.PubSub=&amp;{0xc0000e20e0 0x705a40 0x7080e0 {0 0} 0xc0002ad4a0 map[rtc_channel:ND_mhMpuz4o:{} signal_channel:ND_mhMpuz4o:{}] map[] false 0xc00010e2a0 0xc000130a80 {1 {0 0}} 0xc00116a200 &lt;nil&gt;}) %!s(chan *redis.Message=0xc0001309c0) %!s(chan interface {}=&lt;nil&gt;) %!s(chan struct {}=0xc00010e420) %!s(int=100) %!s(time.Duration=60000000000) %!s(time.Duration=3000000000)} channel is full for 1m0s (message is dropped)

<@U02F289FVTK> is your redis single or cluster ?

<@U02F289FVTK> are you able to repro with deadlock finder applied?

<@U01KZ61GV5Z> it was I who threw off the sequence before the fall on March 4. After being replaced with deadlock, there has not been a single error since March 5

that's really interesting. I've been trying to repro this one for awhile with no luck.. but this is helpful information. <@U02F289FVTK> when you saw the error, was it with a docker image? or just running the binary?

<@U01KZ61GV5Z> on bare hardware AMD Risen 9 5950X 16-Core Processor without docker. redis is installed locally.

<@U01KZ61GV5Z> having investigated all the errors leading to a hang on redis, there is always a double connection of one user, most likely due to the loss of packets of the first connection and manifests itself about 2 minutes after that.

I rolled back to version 0.15.2 from 3 days ago and it's been working fine ever since. Maybe it will help the investigation.

thank you both for the additional details. We'll take a look at the delta between 0.15.2 and current.

<@U02F289FVTK> or <@U0362G7R3HR> are you still able to reproduce this? If so, can you try the following?
1. run livekit-server with `--dev` flag
2. when it gets stuck, visit `/debug/goroutine` on your server to dump all of the goroutines
3. save that as a text file and DM me
Since I'm still not able to reproduce this, it'd help greatly to see what's going on when this happens.

<@U01KZ61GV5Z>  there have been no such errors lately. Now I will transfer the server to dev. and if there is, I will send

<@U01KZ61GV5Z> Sorry, i'm using it for production environment so can not use newest version because it is unstable. I will try to run it in dev environment with steps you provided above and let you know info when it happen.

<@U01KZ61GV5Z> <https://pastebin.com/raw/s9Wmb2f7>

livekit_error.log

<@U01KZ61GV5Z> It happened today with v0.15.6. Please take a look.

fixed! <https://github.com/livekit/livekit-server/pull/614>

So will this bug be fixed in next version ?

Hi David, I build docker image from master branch. Today other error happened. Please help to check the log bellow

:wave:
you can find examples of Go server SDK <https://github.com/livekit/livekit-cli|here>. the CLI is built on top of Go SDK.

For web client, there's a <https://github.com/livekit/client-sdk-js/tree/main/example|sample app> linked off of the repo, or react <https://github.com/livekit/livekit-react/tree/master/example|here>

The error I'm receiving when using the `livekitserver:6789/metrics` endpoint as a Prometheus data source in Grafana.
`Error reading Prometheus: bad_response: readObjectStart: expect { or n, but found #, error found in #1 byte of ...|# HELP go_g|..., bigger context ...|# HELP go_gc_duration_seconds A summary of the paus|...`

Do I need to install and run a Prometheus instance then point Grafana at it?

<@U01KZ0SCDKL> You know how this is supposed to work? :sweat_smile:

<@U02SFES0N9Y> do you mind to share how you resolved the issue? I'm facing similar problem.

Hi <@U02LCP104CQ>! Have you spun up a Prometheus instance to ingest the metrics from LiveKit?

Essentially the flow is LiveKit/metrics -&gt; Prometheus -&gt; Grafana.

Aha! thanks <@U02SFES0N9Y>. That was the problem.

hey <@U028HADVD5K> just apply a transform scale(-1,1)  to the video element, see  line #447 of <https://github.com/livekit/client-sdk-js/blob/main/example/sample.ts>

<@U0351E7KCTT>, are you running the latest from the repo?

latency should be computed for audio tracks, do you see if they show up in the per sub report? i.e.

```Sub 2 | Track              | Kind  | Pkts | Bitrate   | Latency    | Dropped
      | 0A TR_iMAmBs6342fu | audio | 574  | 9.8kbps   | 6.102862ms | 0 (0%)
      | 0V TR_AT4UJLdHDxTg | video | 413  | 131.9kbps |  -         | 0 (0%)
      | 1A TR_cRU48iNxyXmL | audio | 574  | 9.8kbps   | 6.484193ms | 0 (0%)
      | 1V TR_LRAxwnVmzQky | video | 422  | 131.9kbps |  -         | 0 (0%)
      | 2A TR_tFCSDPeAyCcp | audio | 574  | 9.8kbps   | 6.518686ms | 0 (0%)
      | 2V TR_FkT5bQ2fv4JL | video | 869  | 333.0kbps |  -         | 0 (0%)
      | 3A TR_mopSbHJhepPa | audio | 574  | 9.8kbps   | 6.002954ms | 0 (0%)
      | 3V TR_qEdVAG4L7Js3 | video | 418  | 131.7kbps |  -         | 0 (0%)
      | 4A TR_eYTqPFAHsdgJ | audio | 574  | 9.8kbps   | 6.403965ms | 0 (0%)
      | 4V TR_5kLSf85YesyQ | video | 416  | 131.8kbps |  -         | 0 (0%)```

Yeah I installed the latest release available from go on Friday.

```Sub 0 | Track              | Kind  | Pkts  | Bitrate   | Latency | Dropped
      | 0A TR_Ly3y4PeTMwSw | audio | 1795  | 9.8kbps   |  -      | 0 (0%)
      | 0V TR_Nu25DAFUofuL | video | 12051 | 1.8mbps   |  -      | 0 (0%)
      | 1A TR_Jyf7uj2VrTRu | audio | 1765  | 9.8kbps   |  -      | 0 (0%)
      | 1V TR_DL22PuDNcTtK | video | 1425  | 152.0kbps |  -      | 0 (0%)
      | 2A TR_JdW49DAcempW | audio | 1766  | 9.8kbps   |  -      | 0 (0%)
      | 2V TR_ZZ3xVM9sU6mQ | video | 1430  | 153.2kbps |  -      | 0 (0%)

Sub 1 | Track              | Kind  | Pkts  | Bitrate   | Latency | Dropped
      | 0A TR_Ly3y4PeTMwSw | audio | 1795  | 9.8kbps   |  -      | 0 (0%)
      | 0V TR_Nu25DAFUofuL | video | 12051 | 1.8mbps   |  -      | 0 (0%)
      | 1A TR_Jyf7uj2VrTRu | audio | 1765  | 9.8kbps   |  -      | 0 (0%)
      | 1V TR_DL22PuDNcTtK | video | 1425  | 152.0kbps |  -      | 0 (0%)
      | 2A TR_JdW49DAcempW | audio | 1766  | 9.8kbps   |  -      | 0 (0%)
      | 2V TR_ZZ3xVM9sU6mQ | video | 1430  | 153.2kbps |  -      | 0 (0%)

Sub 2 | Track              | Kind  | Pkts  | Bitrate   | Latency | Dropped
      | 0A TR_Ly3y4PeTMwSw | audio | 1795  | 9.8kbps   |  -      | 0 (0%)
      | 0V TR_Nu25DAFUofuL | video | 12051 | 1.8mbps   |  -      | 0 (0%)
      | 1A TR_Jyf7uj2VrTRu | audio | 1765  | 9.8kbps   |  -      | 0 (0%)
      | 1V TR_DL22PuDNcTtK | video | 1425  | 152.0kbps |  -      | 0 (0%)
      | 2A TR_JdW49DAcempW | audio | 1766  | 9.8kbps   |  -      | 0 (0%)
      | 2V TR_ZZ3xVM9sU6mQ | video | 1430  | 153.2kbps |  -      | 0 (0%)

Sub 3 | Track              | Kind  | Pkts  | Bitrate   | Latency | Dropped
      | 0A TR_Ly3y4PeTMwSw | audio | 1775  | 9.8kbps   |  -      | 0 (0%)
      | 0V TR_Nu25DAFUofuL | video | 1409  | 152.1kbps |  -      | 0 (0%)
      | 1A TR_Jyf7uj2VrTRu | audio | 1766  | 9.8kbps   |  -      | 0 (0%)
      | 1V TR_DL22PuDNcTtK | video | 11930 | 1.8mbps   |  -      | 0 (0%)
      | 2A TR_JdW49DAcempW | audio | 1766  | 9.8kbps   |  -      | 0 (0%)
      | 2V TR_ZZ3xVM9sU6mQ | video | 1430  | 153.2kbps |  -      | 0 (0%)

Sub 4 | Track              | Kind  | Pkts  | Bitrate   | Latency | Dropped
      | 0A TR_Ly3y4PeTMwSw | audio | 1776  | 9.8kbps   |  -      | 0 (0%)
      | 0V TR_Nu25DAFUofuL | video | 1208  | 120.1kbps |  -      | 0 (0%)
      | 1A TR_Jyf7uj2VrTRu | audio | 1765  | 9.8kbps   |  -      | 0 (0%)
      | 1V TR_DL22PuDNcTtK | video | 11930 | 1.8mbps   |  -      | 0 (0%)
      | 2A TR_JdW49DAcempW | audio | 1766  | 9.8kbps   |  -      | 0 (0%)
      | 2V TR_ZZ3xVM9sU6mQ | video | 1430  | 153.2kbps |  -      | 0 (0%)

Summary | Tester | Tracks | Bitrate                | Latency | Total Dropped
        | Sub 0  | 6/6    | 2.1mbps                |  -      | 0 (0%)
        | Sub 1  | 6/6    | 2.1mbps                |  -      | 0 (0%)
        | Sub 2  | 6/6    | 2.1mbps                |  -      | 0 (0%)
        | Sub 3  | 6/6    | 2.1mbps                |  -      | 0 (0%)
        | Sub 4  | 6/6    | 2.1mbps                |  -      | 0 (0%)
        | Total  | 30/30  | 10.4mbps (2.1mbps avg) |  -      | 0 (0%)```

I don’t have latency values for any of the tracks

Yeah I second this, no latency shown for audio/video tracks

I have opened an issue on Github <https://github.com/livekit/livekit-cli/issues/15> I might look into it if I have time

Thanks for filing the issue Alex! We'll get to it soon. Can you include the commit that you've built for the load tester?

Got it, and which OS are you running this on?

I added those two pieces of info to the issue on github

The Server SDK would be required to generate the token, and which would define the room also. That is correct.

For the “template engine”, I think the easiest way is to use the React built-in UI <https://github.com/livekit/livekit-react> … you’ll need to set up React in your Rails project, either using <https://github.com/shakacode/react_on_rails> or <https://github.com/reactjs/react-rails>

hi, can you pull the latest generate script with:
`docker pull livekit/generate` ?

then generate a new set of scripts. Firefox is a bit annoying with its TURN server setup. We've updated our setup to be compatible with FF in the latest version

you should have an `update_ip.sh` script in `/opt/livekit`

Hi <@U036B4BJH55>,  I'm facing the exactly same issue, did you manage to solve it ? :pray:

<@U03KCMG3GPL> How are you deploying the server? is it using the generated deploy script?

Hi <@U01KZ61GV5Z>, The Livekit server is setup using the docker image <https://hub.docker.com/r/livekit/livekit-server> v1.1.0 using the following configuration
Tried locally with and without the "turn" section

```# ===================== PORTS ===================== #

port: ${LIVEKIT_PORT}

rtc:
  port_range_start: 50000
  port_range_end: 60000
  tcp_port: 7881
  udp_port: 7882
  use_external_ip: false

# ===================== SECURITY ===================== #

keys:
  ${LIVEKIT_API_KEY}: ${LIVEKIT_API_SECRET}

# ===================== LOGS ===================== #

logging:
  json: false
  level: ${LIVEKIT_LOG_LEVEL}
  pion_level: ${LIVEKIT_LOG_LEVEL}

# ===================== REDIS ===================== #

redis:
  address: ${REDIS_URL}
  db: 1
  password: ${REDIS_PASSWORD}
  username: ${REDIS_USERNAME}

turn:
  enabled: true
  udp_port: 3478```


docker set up is tricky, but most importantly is you are not using `use_external_ip`, that'll cause the server to advertise a private address that clients would not know how to address

Hello David, switching `use_external_ip`  to true seems to have no effect :confused:

On chrome on the other hand, it was okay.

they're just kotlin flows that emit event objects

<https://developer.android.com/kotlin/flow#collect>

That documentation will need to be fixed.. it was true in an early version of livekit, but that behavior had been changed awhile ago