@NickM-27 commented on GitHub (Feb 11, 2024):
what GPU do you have again?
@CodeWithBryan commented on GitHub (Feb 11, 2024):
I'm experiencing the same thing, usually happens after ~24 hours of uptime for me. I've got 5 cameras, and 2-3 tend to "die out" Clicking into…
@NickM-27 commented on GitHub (Feb 11, 2024):
You should use the tree view
@mike2307 commented on GitHub (Feb 11, 2024):
Not much luck there either:
:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@mike2307 commented on GitHub (Feb 12, 2024):
Documentation has been updated. Closing issue.
@mike2307 commented on GitHub (Feb 11, 2024):
htop doesn't seem to provide lots of details in that case: :
It looks like only the "-qp" parameter is having a good effect here. I tried with "-qp 38" and the file size looks very good already; probably I…
@NickM-27 commented on GitHub (Feb 11, 2024):
I'm not sure what options the vaapi encoder supports, seems like that isn't one of them. The hardware encoders don't necessarily support all the…
@NickM-27 commented on GitHub (Feb 11, 2024):
Htop can provide thread info, I'll have to run one and see if I see the same thing
@NickM-27 commented on GitHub (Feb 11, 2024):
Multiple things could be going on here. I'd like to see where you're seeing this data, htop for example will show the usage under the python process…
@Tomlap123 commented on GitHub (Feb 11, 2024):
Now it works like a charm.
Thank you :)
It would be great if you could add this information to the doc. I think a lot of people will have the…
@mike2307 commented on GitHub (Feb 11, 2024):
I already tried adding "-b:v 4M" to timelapse_args. But that causes an error in ffmpeg:
@mike2307 commented on GitHub (Feb 11, 2024):
I looked at the output of 'top' after noticing suspiciously high CPU and RAM usage. When switching to the thread view, I saw that just 1 out of 18…