Sebb
lvl.4
Flight distance : 498199 ft
Germany
Offline
|
interesting theory, but
- the sensor receives a 2D image. There is no transparency to deal with. it doesnt know the clouds are transparent. it just sees greyer trees.
- there are also examples where it is rendered smoothly.
i dont think algorythm is to blame.
Edit: well, I take that last statement back. algorythm is actually a good candidate for causing this, but transparency doesnt apply I think.
from point of view of algorythm, the image information gets gradually more/less contrasty as clouds move across. But isnt that something that happens all the time anyway in video of landscapes, even without clouds? Why dont we see it more often then?
Edit2: ok, after some reading, I think I understand now. you are right, it makes sense. the algorythm works by taking pixels in motion from A to B without changing them, thereby saving information. But if the pixels change only slightly while moving from A to B, e.g. slightly lighter/darker due to clouds, then this is ignored by algorythm. only when arriving at B they are updated (new keyframe) and for us that causes the visible jump. In other parts of the image where pixels stay same color/saturation/etc., it appears smooth.
This is probably also directly dependent on bitrate. The lower the bitrate, the more these issues appear.
So the reason why it didnt happen in the 2.7K example most likely is
- 2.7K has higher per-pixel bitrate than 4K
- the field under the shadow has much less detail, and drone itself isnt moving = easier for algorythm anyway.
|
|