• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Jaded-Encoding-Thaumaturgy / vs-jetpack / 14865979608
66%

Build:
DEFAULT BRANCH: main
Ran 06 May 2025 05:33PM UTC
Jobs 2
Files 67
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

06 May 2025 05:30PM UTC coverage: 61.563%. Remained the same
14865979608

push

github

web-flow
FixInterlacedFades: universal "match field closer to target color" mode (#90)

The target color may be something other than pure black or white, such
that pixel brightness may not only consistently fall or consistently
rise during the fade.

Even when a fade does have monotonically changing average brightness,
near the target end of the fade, compression noise may cause a field’s
average to overshoot the target (as in
https://github.com/Jaded-Encoding-Thaumaturgy/vs-deinterlace/issues/41).
In this case, current `Darken`/`Brighten` modes treat this overshot
field as the source of truth and modify the other field, even if in
reality it exactly matches the target color.

Furthermore, some pixels may be darker and some brighter than the
target: in the extreme case, if a bright-and-dark checkerboard pattern
fades to gray, the average brightness of the entire frame stays
constant. The individual pixels’ absolute differences from the target,
however, are larger on one end of the fade and approach zero on the
other end.

Finally, even on black/white targets, the target chroma is a mid-range
value (float 0 on a scale from −0.5 to +0.5). Since
https://github.com/Jaded-Encoding-Thaumaturgy/vs-deinterlace/issues/34,
`Darken` handles this by keeping the field whose absolute chroma is
closer to zero and adjusting the other field, which is correct, but
`Brighten` does the opposite, moving the more-neutral chroma *away* from
zero, thus amplifying random color fluctuations near the target end of
the fade.

This can all be fixed at once by taking the individual pixels’ absolute
differences from the target color and simply adjusting the values
towards the target color, no matter what color it is. This additionally
removes any need for a human to decide whether to “darken” or “brighten”
the fade, thus making `FixInterlacedFades` somewhat easier to use.

When the target color is pure black or pure white, the new behaviour for
luma is the same as the current `Darken`/`Brig... (continued)

3711 of 6028 relevant lines covered (61.56%)

1.23 hits per line

Jobs
ID Job ID Ran Files Coverage
1 67 - 3.12 - 14865979608.1 06 May 2025 05:34PM UTC 67
61.56
GitHub Action Run
2 67 - 3.10 - 14865979608.2 06 May 2025 05:33PM UTC 67
61.56
GitHub Action Run
Source Files on build 14865979608
  • Tree
  • List 67
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #14865979608
  • 478b78a8 on github
  • Prev Build on main (#14848615922)
  • Next Build on main (#14868724130)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc