README: describe the output outside the refiner band precisely
Browse files
README.md
CHANGED
|
@@ -60,8 +60,9 @@ Its receptive field is ±9 pixels. Per native pixel it receives:
|
|
| 60 |
| 10 | `a_gf`: alpha of a colour guided filter driven by CorridorKey's low-resolution alpha |
|
| 61 |
|
| 62 |
It outputs residuals on top of `a_gf` (alpha) and `F` (foreground). The result is used only inside an
|
| 63 |
-
uncertainty band around CorridorKey's edges
|
| 64 |
-
|
|
|
|
| 65 |
|
| 66 |
In the real-time engine the refiner only runs on 32×32 tiles that intersect the band, with a fixed tile budget
|
| 67 |
(most uncertain tiles first). In fp16 that costs about 5–6 ms per frame with 256 tiles and 10–11 ms with 512 tiles
|
|
|
|
| 60 |
| 10 | `a_gf`: alpha of a colour guided filter driven by CorridorKey's low-resolution alpha |
|
| 61 |
|
| 62 |
It outputs residuals on top of `a_gf` (alpha) and `F` (foreground). The result is used only inside an
|
| 63 |
+
uncertainty band around CorridorKey's edges. Outside the band the output is the colour-guided upsampling of
|
| 64 |
+
CorridorKey's matte, which in solid foreground and clean background is CorridorKey's own 0 or 1. The band is weighted
|
| 65 |
+
by nearby foreground, which keeps the refiner out of dark or noisy screen areas.
|
| 66 |
|
| 67 |
In the real-time engine the refiner only runs on 32×32 tiles that intersect the band, with a fixed tile budget
|
| 68 |
(most uncertain tiles first). In fp16 that costs about 5–6 ms per frame with 256 tiles and 10–11 ms with 512 tiles
|