Skip to content
Snippets Groups Projects
Select Git revision
  • phhw
  • captouch-threshold
  • t
  • dos
  • test2
  • test
  • slewtest
  • simtest
  • view-think
  • vm-pending
  • media-buf
  • scope
  • passthrough
  • wave
  • vsync
  • dos-main-patch-50543
  • json-error
  • rahix/big-flow3r
  • main default protected
  • pippin/media_framework
  • v1.3.0
  • v1.2.0
  • v1.2.0+rc1
  • v1.1.1
  • v1.1.0
  • v1.1.0+rc1
  • v1.0.0
  • v1.0.0+rc6
  • v1.0.0+rc5
  • v1.0.0+rc4
  • v1.0.0+rc3
  • v1.0.0+rc2
  • v1.0.0+rc1
33 results

flow3r-firmware

  • Clone with SSH
  • Clone with HTTPS
  • Forked from flow3r / flow3r firmware
    Source project has a limited visibility.
    Sebastian Krzyszkowiak's avatar
    dos authored
    The reason why this is needed is pretty easy to observe when
    taking a color like (1.0, 0.75, 0.0), which appears yellow,
    and transitioning it to (0.0, 0.0, 0.0). Without this,
    all the channel values get reduced at constant rate, meaning
    that the green channel will reach zero much earlier than
    the red one, so in the middle of transition the yellow color
    will turn into red.
    
    To prevent that and preserve the hue, desaturate only the channel
    with the greatest difference from target at full rate and scale
    the rest in relation to that one. This way the transition still
    takes the exact same time, but doesn't go through unexpected
    color hues during it.
    03762590
    History
    Name Last commit Last update