search

tfaehse / DashcamCleaner

Censor identifiable information in videos, in particular dashcam recordings in Germany.
GNU Affero General Public License v3.0
130 stars 27 forks source link

Where is the feature of bluring previous frames in case of missed detections implemented? #79

Open aaronpohle opened 11 months ago

aaronpohle commented 11 months ago

According to the readme, the dashcamcleaner has a nice feature: "Sometimes, a license plate might be missed for just one frame. This one frame, usually 1/30th of a second long, still means the license plate or face could easily be identified - a computationally very cheap (as opposed to increasing the inference scale) way to fix such false negatives can be the frame memory option. In essence, it blurs not only the detected boxes in the current frame, it also blurs regions that were detected in n frames before."

Where is it implemented and how can i influence the number of previous blurred frames?

RegularTom91 commented 11 months ago

Hast du ein 60fps Video genommen zum probieren?

Did you took a 60 frames per second video?

joshinils commented 11 months ago

@tfaehse removed it in favor of faster batch processing

graebec commented 11 months ago

Would be nice to have it back, just to avoid flashing license plate within scenes.

aaronpohle commented 11 months ago

Thanks you for the answer, i found the commit: https://github.com/tfaehse/DashcamCleaner/commit/d5e792e0719bcf4b2d5140208444a9f4ec0c87aa

Now I can look how I can enable the feature again, probably by losing performance. But I have cases in which this feature would help and is more important than speed.

graebec commented 11 months ago

Thanks you for the answer, i found the commit: d5e792e

Now I can look how I can enable the feature again, probably by losing performance. But I have cases in which this feature would help and is more important than speed.

Could you please share with us in case you find a way ?

joshinils commented 11 months ago

also, this issue is now a duplicate of #68, both are asking the same thing

nils8107 commented 11 months ago

I also would like it back :-)

Counterdoc commented 10 months ago

Same here, this feature would help a lot. I have a lot of flickering between some frames unfortunately.

tfaehse commented 9 months ago

I'll try to address this over the holidays, I didn't know it was actually popular :)

Mauzifus commented 8 months ago

I would really like to have the feature back - it doesn't matter if it takes longer - it's still faster than correcting the errors by hand.

JZ4142 commented 7 months ago

Hi, is there any news on this topic? Would be great to have the feature back.

thkukuk commented 7 months ago

I also would like to have this feature back :) Speed is no issue, as I "clean" the videos in batch mode on a server in the background, but fixing all this "flickering" manual is a huge amount of work. Flickering always means, the face or plate is visible for one or two pictures.

tfaehse commented 6 months ago

This PR should fix this, hopefully: https://github.com/tfaehse/DashcamCleaner/pull/87

Basically, the pipeline was (pretty massively) changed to

  1. Read frames, run detection for all frames
  2. Run forward/backward tracking
  3. Read frames, write blurred frames for all frames

Internally, this tracker (https://github.com/tryolabs/norfair, love it) uses kalman filters to estimate movement of boxes it can track. In the best case, this works better than a frame memory, because the position is not the same as in the previous frames but a better estimation. Worst case it's the same as before, because no real motion can be estimated. I hope this works well for you! :)

Next up, the detector has to be improved.