10
Ghost in the machine (sh.itjust.works)
submitted 2 days ago by muusemuuse@sh.itjust.works to c/linux@lemmy.ml
6 comments fedilink hide all child comments

I have a rig running frigate that runs all the cameras for a local business. The openvino detectors are suddenly acting up and I’m not sure why just yet. They are slow, even when there’s nothing to figure out. They just seem busy all the fucking time. 

I’m troubleshooting this after hours and aside from a piece of string art being blown around a bit by the heating vents, absolutely nothing is moving. The detectors have no fucking idea what it is which does amuse me on some level but there’s another layer of absurdity to this. 

This is starlight shop that used to be a funeral home. The computer is trying to detect things and seemingly overwhelmed by the attempt even where there is no motion for it to detect objects in. It sees nothing but it doesn’t trust it. 

The computer is trying to comprehend ghosts. 

I should do cocaine about it.

sudo dnf install cocaine

top 6 comments
sorted by: hot top controversial new old
[-] just_another_person@lemmy.world 7 points 2 days ago

So just...turn them off.

If you didn't know, detection runs all the time for anything of this sort unless you have what we call "predetection filters".

If you don't have predetection on video, EVERYTHING gets evaluated. So you pare down what is to be detected by certain, faster events.

Motion detection is probably the most basic because it's done very quickly in software, and almost certainly by ffmpeg, costing very little in system resources.

If your machine is struggling with however many feeds you have, do this:

  1. Reduce the frame rate each camera sends to the minimum acceptable level
  2. Set image compression to the minimum acceptable level, and whatever your hardware is fastest at (read: not RAW anything)
  3. Set a motion filter to only run model detection AFTER motion detection

That should sort you out.

[-] muusemuuse@sh.itjust.works 2 points 2 days ago* (last edited 2 days ago)

So in earlier troubleshooting I set detectors to false and they ran anyway. The detectors were running fine until last week effortlessly. I was evaluating their stability for a future feature.

[-] just_another_person@lemmy.world 1 points 2 days ago

What else is using resources if you stop Frigate for 15m. Give me a general picture of the system resources and CPU as well. It's Intel, obviously, but what's the whole system look like?

[-] muusemuuse@sh.itjust.works 1 points 2 days ago

Nothing is using resources. I only see my 3 ov detectors taking around 60ms in frigate. Htop shows barely a hiccup.

[-] just_another_person@lemmy.world 1 points 1 day ago

Did you perhaps receive an unattended upgrade to Frigate?

[-] muusemuuse@sh.itjust.works 1 points 1 day ago

Nope, frigate is the latest version it was also the same version when it was working fine. Fedora also wasn’t updated right before this started.

this post was submitted on 18 Jan 2026
10 points (81.2% liked)

Linux

57274 readers
1277 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz