I have a 4k camera continously recording the sub stream with "continous + alerts", using deepstack. This works well, but I have a very small part of the picture I would like to use the full 4k resolution for.
I have set up a clone of the camera and defined an area of interest, hoping that I would be able to trigger a recording on this area. But the substream has to low resolution for this to work. The area of interest is about 50x30 pixels on the sub stream, using the main 4k stream for this area would make the detection much easier.
Can anyone give me any hints for running the motion detection on the main stream in the area of interest and/or running continous recording of the main 4k stream, but only in the small area of interest?
Record area of interest
Re: Record area of interest
I don't have an answer, but I'll be watching to find out...
- "Whenever I take something apart to fix it and put it back together again, I end up with like six really important looking pieces left over" -Tim Allen
- If you know what your after, you'll recognize it when you see it.
Re: Record area of interest
I was hesitant to try this as I expected the decoding of the full 4k stream and encoding of the area of interest recording would be resource intensive. It is, but going from 8-12% on the three cores of the i3-10100 made available to the VM, to 18% is better then expected.IAmATeaf wrote: ↑Sat Sep 11, 2021 9:34 am Don’t know of another way but you’ll have to disable the substream on the clone and then it will no longer be a clone and will be pulling its own stream, you can then define your area of interest etc and the triggering and recording will all use the main stream.
When the original camera instance detects motion and starts a recording (this is configured for direct to disc) the other camera instance splits it's recording and starts on a new file (This does not use direct to disc as I only want to record part of the stream).