https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
d
bandwidth consumption depends on the specific resolution & bitrates that you are publishing. load tester uses a specific bitrate (it's actually a pre-recorded video played on loop).
also, screen share uses dynamic bitrate, and typically it's not high due to the nature of the screen being mostly static
d
a participant sends the video & audio data to the livekit-server and livekit-server sends other participants video & audio data to the participant. So if the total receive bandwidth is higher on the server side, shouldn’t be the transmit bandwidth also higher?
d
what parameters did you use with the load tester?
d
Copy code
livekit-cli join-room --url wss://${url} --api-key ${key} --api-secret ${secret} --room room:123 --identity 1 --publish ~/file1.ivf --publish ~/file1.ogg --fps 23.98
Copy code
livekit-cli join-room --url wss://${url} --api-key ${key} --api-secret ${secret} --room room:123 --identity 2 --publish ~/file2.ivf --publish ~/file2.ogg --fps 23.98
Copy code
livekit-cli join-room --url wss://${url} --api-key ${key} --api-secret ${secret} --room room:123 --identity 3 --publish ~/file3.ivf --publish ~/file3.ogg --fps 23.98
Copy code
livekit-cli load-test --url https://${url} --api-key  ${key} --api-secret ${secret} --room room:123 --publishers 13
d
what are you trying to do? the commands you've ran simulated 16 publishers and 3 subscribers.
to simulate 13 participants that are all subscribing, you would want to do:
Copy code
livekit-cli load-test --url https://${url} --api-key  ${key} --api-secret ${secret} --room room:123 --video-publishers 13 --subscribers 13
d
Thanks for the feedback david, I missed subscriber part. I’ll try with this command
b
Hi, I would ask... (I have tested all before manually.. server side, client side ... Sharing screen .. even wss, and all it's ok) but I would ask, Trying this part https://github.com/livekit/livekit-cli#publish-media-files in my side as a real user I only see a gray screen, not the video that I'm publishing as file... What I'm missing? Thank a lot
d
your media files are probably not encoded correctly. did you re-encode them into the correct formats?
b
Umm in theory it's ok... I can see it with VLC... Bu I'll try later with a few other example... I'll comment later, thx
d
VLC plays just about anything.. WebRTC is very particular about supported formats
b
Hi, I codec as IVF (vp8) and no luck... The command livekit-cli join-room --room yourroom --identity publisher --publish-demo should show a sample video too? The gray screen in client it's because no video html tag... Maybe I miss something in the default react client?
d
yeah, --publish-demo would send a valid sample video to the room. It sounds like your client isn't rendering it correctly? can you try https://example.livekit.io
b
I think this url is the react client (the same/ersion that mine)
Using my server... That with my front the results are the same (using --publish-demo attribute
If works for you... Maybe something wrong in my server side? Some port or something else?
d
hmm that seems odd. does it behave this way on a desktop browser too?
I just tested it with the latest server, and it's working well here.
b
Ummm ok I'll review with latest server
Don't remember the version now
Well ... i did some progress, upgrade to 1.3.1 from 1.2.3 and with a few research more... i think my big problem with my configuration was rtc.use_external_ip: true for some reason if change to false it works (to see configuration check this https://equilibristofgo.github.io/blog/posts/livekit_telegram/) and... if use standard if use --publish-demo with firefox 102.4.0esr in debian ... "errorVerbose": "unable to start track, *codec is not supported by remote*\nsetting remote description failed) but now with my ivf video ... it's work... i'll keep diggin in it 😅 thanks for now
Open in Slack
PreviousNext
Powered by