Closed RUHavingFun closed 3 years ago
Are you using a Raspberry Pi Zero by any chance?
You can try setting vcodec to copy and seeing if that helps.
That did it! I had actually removed that from old config for older cams. I thought Copy was the default. Not sure what Copy truly means - other than use what is sent.
I am using a Pi Zero. You think I need to move to a more powerful Pi with more memory?
The Zero is pretty underpowered for handling video, but if it’s working for you, no real reason to switch.
The reason I thought it was a Zero was the SIGILL error is something I see rarely, but only on that model of Pi. I’ve never been able to reproduce it myself though, so I really have no idea what causes it. Copy typically still works when it happens.
As for why copy isn’t default, it’s less compatible, as certain cameras send streams that HomeKit apparently can’t handle. I try to keep the defaults as likely to work out of the box as possible.
Thanks for the info and super quick help. I may move to a better Pi, I was not doing much video for a while. I am seeing spikes to 100% more now.
Yea, video (even with the copy codec) takes a bit of grunt.
Describe The Problem:
I have an RTSP feed from [docker-wyze-bridge]. I can view feed in VLC and LiveCams Pro on iPhone. FFmpeg seems to connect and get info, it can even get a snapshot. But the video feed does not display. Only issue I clearly see in logs is:
"[warning] attempted to set receive buffer to size 393216 but it only ended up set as 360448
To Reproduce:
You would have to setup a Wyze camera and connect [docker-wyze-bridge] to create a feed. The feed is currently in SD to try and make sure it was not a size or dimensions problem.
Logs:
Homebridge Config:
Screenshots:
Environment: