https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
d
which platform are you building for?
b
ARM platform
d
running Linux?
b
yep , ARM iot platform running Linux
only have 256MB memory
d
that should be fine.. you could try running either the Go SDK or Python/Rust
b
Could Go sdk or Rust SDK support device only have 256M memory Linux IOT platform? I only concern the performance
I mean the livekit client sdk running on IOT device
d
yeah it should be ok. wanna give it a try?
you should be able to run the examples on there (and for Go, you could run livekit-cli, which is built using it)
b
OK, I'll give it a try , I saw the go server sdk included publish and write examples
👍 1
hello， thanks for guide on IoT device， The go client sdk audio and video are not sync， any parameters to set ？
d
how are you publishing?
b
using audio file and video file ， I'll try to use c video capture stream and audio record stream currently, if go sdk can handle network adaptive like android and ios native sdk ?
d
if it's not encoding the video, it will not be able to adapt to network conditions. Since the adaptation requires control of the encoder to produce at different resolution/bitrates
b
it's encode the video and audio, but video using hardware processing
d
right, but because we/webrtc isn't doing the encode.. we cannot control the encoder when the network becomes congested
b
Have any event or call back to issue hardware encoding bitrate etc , or rust sdk is the better than go sdk ?
d
Right, that would be ideal, something we are thinking about. CC: @flat-raincoat-62120 @big-market-42155, I'm curious on what your use case is? I assume your device will publish video? is it a security camera of some sort?
b
@dry-elephant-14928 Yes， it‘s home security camera supported video call scenario device, the device will publish video and audio also subscribe video and audio, in consideration of cost the device only have 256M system memory and have video encode and decode hardware supported.
f
That is super cool! I am working on something to make that easier right now @big-market-42155!
256M is pretty tight budget. I have been looking at using https://github.com/sepfy/libpeer
b
good work ， but it's not include packet loss and delay frame processing ， it's a simple webrtc libray on iot device
If the go sdk or rust sdk can do the work? i mean the 256M device, we can add adaptive network control to go sdk or rust sdk
d
The Go SDK should work. the memory footprint is fairly small (~13MB of memory when tested with our CLI)
b
Ok， thanks very much
hello, david , i 'm running rust-sdk on apple m1 , cpu usage 70%, this is horrible .
d
70% of the entire system? or of a single core? it's hard to imagine that it would consume 70% of the entire system.
b
single core
I think go client sdk would be better than rust sdk
d
that depends.. they are performing different tasks.. so it's not apples to apples. Rust SDK is doing what Chrome would: encoding and decoding video. Go SDK isn't doing that.. and will def be less resource-heavy
if you were to encode using CPU within Go.. it'll likely perform the same as Rust.
b
I'm running rust client wgpu_room on apple m1
How can I use the hardware encoding and decode on rust sdk?
Does rust sdk still using webrtc library?
d
yes it is.
Open in Slack
PreviousNext
Powered by