@alucryd commented on GitHub (Jan 17, 2024):
Intel has documentation on how to run it on ARM 64 devices (https://www.intel.com/content/www/us/en/developer/articles/technical/arm64-sbc-and-ncs2.htm…
@NickM-27 commented on GitHub (Jan 18, 2024):
what is the use case though? why are you running these exports? is it just to quickly review different periods of time?
@SpangleLabs commented on GitHub (Jan 18, 2024):
it is currently in rc, release is likely coming soon
Awesome, thank you!
yeah, having a GPU would make a lot of this simpler
For…
@NickM-27 commented on GitHub (Jan 17, 2024):
it does ship with it, there were users testing it on raspberry pis https://github.com/blakeblackshear/frigate/discussions/3797
@NickM-27 commented on GitHub (Jan 17, 2024):
ah I see, interesting
@mabed-fr commented on GitHub (Jan 18, 2024):
pouvez-vous expliquer votre cas d'utilisation et pourquoi vous voudriez choisir différents taux de time lapse à différents moments ?
I would…
@NickM-27 commented on GitHub (Jan 18, 2024):
I guess that means this will be fixed once 1.13.0 is released fully! (Is there any rough timeline on that?) Or maybe I should just update to the…
@alucryd commented on GitHub (Jan 17, 2024):
I'm quite sure it should be a volume, it works as a volume on my server, doesn't work when passed as a device. But I can give it a try.
Official…
@Plawasan commented on GitHub (Jan 18, 2024):
Gets a +1 from me, it would be great if you're e.g. exporting a timelapse covering the whole day then you typically want a higher factor than if…
@SpangleLabs commented on GitHub (Jan 18, 2024):
They cause issues when trying to sum the cpu usage across all processes as that MiB PID entry says it's using 10273.9 CPU, and using avail…
@NickM-27 commented on GitHub (Jan 18, 2024):
can you explain your use case as to why you would want to choose different rates of time lapses at different times?
@NickM-27 commented on GitHub (Jan 18, 2024):
I don't think these values are "invalid" in that they cause any issues, many of the processes wouldn't be necessary to check anyway. There is also an…
@NickM-27 commented on GitHub (Jan 17, 2024):
/dev/bus/usb should be passed as a device not volume
@Morphy99 commented on GitHub (Jan 17, 2024):
Yep, I hadn't put the "ffmpeg: at the start of the URL for the substreams. Seems to be working ok now. Thanks for the help!