Jesper

Good spot, will fix in an upcoming version

Will fix in #306 when its released

1. Detection runs only on one frame, so if you have a camera with 30 fps and ```interval: 1```, every 30th frame will be scanned. 2. If either ```timeout``` or...

Only one frame is scanned, they are not bunched up. ```interval``` is a value in **seconds**, and its not tied to the fps in any way. ```interval: 10``` will run...

Yes this wont be a problem to implement now that a basic web api is implemented, will add in a future release

You can probably solve this by adding a `codec` like `h264` to your recorder config.

That is coming in the next release. I am working on a huge rewrite of Viseron entirely, thats why there has not been any releases in a while. It focuses...

You can kinda do this already by using `require_motion` on the tracked label. By using that, stationary objects, like parked cars, wont keep the recorder going forever. You can also...

Kind of odd, will see if i can fix it in #306

Tried this on the current release of V2 (roflcoopter/viseron:modularize) and it works as expected for me with this config: ```yaml ffmpeg: camera: camera_1: name: Camera 1 ...... recorder: codec: h264...