WebRTC - Help for Understanding
Ben93kie opened this issue · 4 comments
Hi!
Recently stumbled across your repo, looks impressive!
However, I'm a bit unsure whether it serves my goal. I'd like to have a live-feed fed into Deepstream, primary inference, and then send out the video stream and the synchronized metadata (bboxes) via WebRTC to a browser (single client would be fine).
I've seen the WebRTC sink
and
but I'm not sure if that's doing what I'd like to have. Could you point me in the right direction?
Thank you!
I apologize for the late response @Ben93kie... just back from a short holiday.
re: "send out the video stream and the synchronized metadata (bboxes) via WebRTC"
Are you wanting to send the metadata as message data through the WebRTC data channel? Or do you just which to add the bboxes and labels to the video for visualization with the On-Screen-Display and send the augmented video to the client via WebRTC?
Just FYI, the WebRTC implementation is based on what little information and examples I could find... and currently supports encoded video only. The data channel is unused.
Thanks for your response!
I'd like to send the boxes separately for downstream custom visualizations in the browser.
I know there is a data channel, but I'm not sure how I would feed it the metadata. Especially, in view of needed tight synchronization.
Currently, I'm using the appsink example (python example imagedata-multistream) and adapted it to do a python-based websocket server to send out mjpeg video. But, I'm not happy with the performance.
Could you point me in the right direction maybe?
Thanks!
I believe some users are streaming the video using an RTMP sink and the Metadata using a Message Sink ... streaming both to something like a media server. If you can do your visualization work in the media server, then clients can connect to the server using WebRTC or other protocols.
Using the WebRTC Sink and data channel to send the metadata is something I would need to research and develop.
Nice thx!
I was looking at this and got it to run. Apparently, this runs kind of natively within a Gstreamer pipeline. I wondered whether this works also with Deepstream. The main question is how to ingest the metadata (bboxes) in the data channel in a synchronized fashion.
One could do with appsink, but I worry about performance..