63 karma · joined July 18, 2023
It feels backwards ... engineers need to say if things interoperate, customers search for “ONVIF” to check compatibility, yet instead of helping adoption they act like brand cops. Is this normal for “open standards”? Or is ONVIF.org just uniquely hostile here? I don't think they are right here, but having released a completely free product and got a trademark and a demand for 20k a year and being told I cannot use the word ONVIF in any way shape or form seems insane! Thoughts?
Also our take on MoQ https://www.wink.co/documentation/WINK-MoQ-Implementation-An...
GitHub: https://github.com/winkmichael/mediamtx-moq
We implemented both WebTransport (for browsers) and native QUIC (for server-to-server) after discovering browsers block raw QUIC. Works today in Chrome/Edge, integrates with existing RTMP/RTSP streams in MediaMTX.
Do you have a list of what is supported? I've played around with cv2 quite a bit in python for everything from yolo, to loss of signal, to corrupt frame detection and simple things like 'snow blocking camera'
Ultimately, what is supported in your library? is it *.cv2?