Replies: 1 comment
-
So I have made a bit of progress by figuring out that I can pass the -strict -1 argument through to ffmpeg from the main proxy command line by adding --ffmpeg-args='-strict -1' at the end. So my entire command-line now looks like this:
I now am able to see static images in UI Protect and every now and then they also appear to be moving. And it tells me that it is connected via 15 fps and receiving 2800Kbps bandwidth of data. But whenever I try to access the live view via UI Protect, I just get 3 marching dots in the bottom left corner of the video feed. The console log seems to indicate some broken pipe issue:
|
Beta Was this translation helpful? Give feedback.
-
I have four older video cameras connected to an Axis Video Server and am trying to integrate them into UniFi Protect. Through a lot of digging I have figured out the correct rtsp string to get to the cameras: rtsp://:554/mpeg4/1/media.amp. But when I start my docker container, I get the following error periodically: Codec mpeg4 is not supported in the official FLV specification
And it is suggesting to do this: use vstrict=-1 / -strict -1 to use it anyway
But that doesn't seem to be a command-line argument I can simply pass into unifi-cam-proxy?
Is there a way to work around this issue? Maybe use motion-jpeg instead of mp4?
Beta Was this translation helpful? Give feedback.
All reactions