This message was deleted.
# cloud
s
This message was deleted.
i
(Looking to move this workload from our current setup to LKC)
m
cc @chilly-animal-65189
c
This is not available today. Setting up rtmp to produce a stream compatible with webrtc is really tricky and experience shows that most folks get it wrong (obviously, it can be done, as you're proving it). Without transcoding, there will also be no PLI support, and obviously no simulcast. We are exploring non transcoded ingress, but are likely to tackle that with WHIP first
i
Cool, thanks for the info.
c
To be more specific, in order to support RTMP without transcoding, we'd need to have a solid stream validation logic in ingress, with a very clear feedback mechanism indicating what is wrong with the stream (codec profile, i frame interval, bitrate, dimensions, etc). Even then, my experience is that most folks producing video have difficulties applying these requirements. Transcoding allows streaming to "just work" most of the time.
The latency trade off is real
i
WHIP seems like a sensible route forward. We're only really using RTMP in our stack because it's so easily available in encoders.