@github-actions[bot] commented on GitHub (Mar 12, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@NickM-27 commented on GitHub (Feb 11, 2024):
because rpi is a fickle device that requires a specific build of ffmpeg to have hwaccel work.
There are multiple times where using standard…
@hawkeye217 commented on GitHub (Feb 10, 2024):
Depending on how you have the camera mounted, left/right might be reversed.
@cyberb commented on GitHub (Feb 11, 2024):
Sorry missed that doc, but it does not explain why would I prefer old ffmpeg on rpi arm64 instead of new ffmpeg from standard-arm64. Would v5 ffmpeg…
@ardenking commented on GitHub (Feb 10, 2024):
Thank you working now just need to figure out why left and right seems to be reversed
@Porencephaly commented on GitHub (Feb 11, 2024):
Thank you. I read through the release notes but for some reason that didn't click for me as I was fixated on this being a GUI problem and not an…
@NickM-27 commented on GitHub (Feb 10, 2024):
This is covered in the release notes. You are not setting the detect resolution for your cameras and now they are used directly where as before it…
@NickM-27 commented on GitHub (Feb 10, 2024):
Please read the docs. The default image uses the raspberry pi specific build when you pull via arm64
There is a separate arm64 specific build that…
@hawkeye217 commented on GitHub (Feb 10, 2024):
You need to specify ffmpeg input parameters like your other cameras do. And then your onvif: section should be under that.
For example:
@NickM-27 commented on GitHub (Feb 12, 2024):
you should create a new issue
@NickM-27 commented on GitHub (Feb 11, 2024):
it's because you made the keys strings when they need to be integers
@kronkinatorix commented on GitHub (Feb 12, 2024):
That scans. Couldn't telll you why I did that. Onwards and upwards to the next error.
I'm losing connection with my cameas some time…