crates/veilvoice-video/src/palette.rs

Colours: the site's own tokens, and one per speaker.

One source of colour, cross-checked by a test

The hexes below are Tokyo Night, and they are the same ones website/css/themes.css declares. They are written out here rather than parsed at run time because a crate should not need the website to be on disk to draw a circle, and a test reads that stylesheet and fails if the two ever disagree, which is the same arrangement veilvoice-gui has had since the themes existed.

Ten speaker colours, ordered by measurement rather than by eye

Six of them are palette tokens. The other four are from the wider Tokyo Night set, chosen to sit between the tokens.

The order was first written down by looking at a hue wheel, and it was wrong: a test comparing every pair found a further-apart pair than the one put first. So the order is now computed rather than judged, by distance, the "redmean" approximation, which is the cheap standard stand-in for perceptual difference and weights green most because the eye does.

Slot 0 and slot 1 are the furthest-apart pair in the set, because two speakers is the common case. Every slot after that is the colour whose nearest neighbour among the ones already used is furthest away, which is a maximin order, so the table degrades gracefully: a recording with four people uses four colours chosen to be as separable as four can be, rather than the first four somebody listed.

Ten colours cannot all be far apart. Under this metric the furthest pair scores 507 and the closest pair anywhere in the set scores 63, and the closest pair is only ever reached by a recording with nine or ten people in it.

One colour is deliberately not a hue at all: the near-white foreground token, separated from every saturated colour by lightness, the axis that is still free once the wheel is full.

Colour is never the only signal

Somebody who cannot separate two of these needs the name, and the name is always drawn beside the circle and always in the subtitles. A player that showed only colours would be one about eight per cent of men could not use.

In plain words

The colours, and which one each speaker gets.

They are the same colours the website uses, taken from one place so the application, the website and anything VeilVoice draws cannot drift apart. A test compares them against the site's own stylesheet and fails the build if they do.

Speaker colours are handed out to be as distinct from each other as the number of people allows, so that a glance at the picture tells you who is talking.

WHAT THIS FILE CONTAINS

747 lines defining 9 functions (9 public), 1 type and 8 constants. Everything below is read out of the source, so it cannot disagree with the code.

The types it owns.

• struct Palette line 78 · One complete colour scheme, matching one data-theme block in website/css/themes.css and one entry in veilvoice-gui's theme table.

What happens when it runs. These are the ways in: public, and nothing else in this file calls them, so they are what an outside caller reaches first.

• by_id line 279 · The palette with this identifier.
• default_palette line 285 · The default palette.
• ids line 290 · Every identifier, for an error message or a picker.
• speaker line 333 · The colour for a speaker slot.
• distance line 346 · How far apart two colours look, by the "redmean" approximation.
  reaches rgb
• ink_on line 408 · Black or white, whichever is readable on background.
  reaches contrast, luminance, rgb

WHAT CALLS WHAT

The functions this file defines, and the calls between them. An edge means the callee's name appears, called, inside the caller's body. This is a syntactic reading, not a type-resolved one.

%%{init: {"theme":"base","themeVariables":{"background":"#1a1b26","primaryColor":"#1f2335","primaryTextColor":"#c0caf5","primaryBorderColor":"#7aa2f7","secondaryColor":"#16161e","tertiaryColor":"#16161e","lineColor":"#737aa2","textColor":"#c0caf5","mainBkg":"#1f2335","nodeBorder":"#7aa2f7","clusterBkg":"#16161e","clusterBorder":"#2f3549","fontFamily":"ui-monospace, SFMono-Regular, Consolas, monospace","fontSize":"14px"}}}%%
flowchart TD
    n_by_id(["by_id<br/>line 279"])
    n_default_palette(["default_palette<br/>line 285"])
    n_ids(["ids<br/>line 290"])
    n_speaker(["speaker<br/>line 333"])
    n_distance(["distance<br/>line 346"])
    n_rgb["rgb<br/>line 363"]
    n_luminance["luminance<br/>line 381"]
    n_contrast["contrast<br/>line 397"]
    n_ink_on(["ink_on<br/>line 408"])
    n_contrast --> n_luminance
    n_distance --> n_rgb
    n_ink_on --> n_contrast
    n_luminance --> n_rgb
    click n_by_id href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L279" "open the source"
    click n_default_palette href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L285" "open the source"
    click n_ids href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L290" "open the source"
    click n_speaker href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L333" "open the source"
    click n_distance href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L346" "open the source"
    click n_rgb href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L363" "open the source"
    click n_luminance href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L381" "open the source"
    click n_contrast href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L397" "open the source"
    click n_ink_on href "https://github.com/tilas01/veilvoice/blob/main/crates/veilvoice-video/src/palette.rs#L408" "open the source"
    classDef entry fill:#1f2335,stroke:#7aa2f7,color:#c0caf5
    class n_by_id,n_default_palette,n_ids,n_speaker,n_distance,n_ink_on entry
    classDef api fill:#1f2335,stroke:#7dcfff,color:#c0caf5
    class n_rgb,n_luminance,n_contrast api

ITEMS