You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example Webcam in Wassen is quite sturdy mechanically and well mounted.
Still, it has moved slightly at least twice since it's install in july 2021.
The result shows, that even a slight shift against ref. images reduces the user experience a lot.
How could this be mitigated?
A pixel-precise re-alignment of the camera will be almost impossible in most cases.
Depending of the Zoom/opening-angle, probably even if the camera would have pan-tilt motors.
So Software might help:
The person responsible for the cam. could regularly compare the images to detect a shift, and then take corrective action by adding a certain x/y offset from the time onwards of the appearance of the shift.
I guess it would make sense to apply the correction permanently to the source files on the server, with ffmpeg or so.
Or should just offsets be stored (eg. in jpeg exif fields or externally to the files), that are then considered on display?
Could the cropping pose a problem?
The text was updated successfully, but these errors were encountered:
The example Webcam in Wassen is quite sturdy mechanically and well mounted.
Still, it has moved slightly at least twice since it's install in july 2021.
The result shows, that even a slight shift against ref. images reduces the user experience a lot.
How could this be mitigated?
A pixel-precise re-alignment of the camera will be almost impossible in most cases.
Depending of the Zoom/opening-angle, probably even if the camera would have pan-tilt motors.
So Software might help:
The person responsible for the cam. could regularly compare the images to detect a shift, and then take corrective action by adding a certain x/y offset from the time onwards of the appearance of the shift.
I guess it would make sense to apply the correction permanently to the source files on the server, with ffmpeg or so.
Or should just offsets be stored (eg. in jpeg exif fields or externally to the files), that are then considered on display?
Could the cropping pose a problem?
The text was updated successfully, but these errors were encountered: