Replies: 1 comment
-
Is the player a native player, not a browser? What I don't understand is how to get client sync by putting a unique id in the sei. You can send a stream with the sei inserted from the RTMP encoder to OME. Since OME doesn't truncate the sei, you can just take it out of the player and use it. It's very hard to get frame-by-frame client sync. Even if you do it in absolute time, the wall clock of each device is slightly different, in the hundreds of ms range. If you do webrtc ultra-low latency streaming with a latency of 4-6 frames, you can roughly get client sync. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, my OME server is receiving an RTMP video stream and publishing it normally via WebRTC at ws://OME_SERVER_IP:3333/app/stream. I'd like to add a unique ID to each frame of the WebRTC stream to synchronize multiple clients. I considered using the WebRTC Data Channel if the synchronization with the video is accurate enough (not sure), or embedding SEI messages in the H.264 stream. Are there any ways to use the WebRTC Data Channel or integrate custom SEI messages with OME?
Beta Was this translation helpful? Give feedback.
All reactions