Prisma v2.0.0 — unified Windows RGB control

One app for the motherboard, RAM, GPU, fan strips, keyboard and mouse — driven from a
single 25 fps frame loop so everything actually animates in step. No vendor suite, no
cloud, no telemetry, no account.

Which file do I want?

Asset
Prisma.exe	Self-contained, ~162 MB. Nothing to install, no runtime needed — download and run. Start here.
Prisma-2.0.0-win-x64.zip	~0.4 MB. Needs the .NET 8 Desktop Runtime.

Windows SmartScreen will warn on first run — the build is unsigned and has no reputation
yet. More info → Run anyway.

What's in it

12 effects — Static, Rainbow wave, Colour cycle, Breathing, Strobe, Two-colour
gradient, Comet, Twinkle, Fire, Ambient (screen sync), Music (system-audio
reactive with a separate bass band for on-beat punch), Surprise.

Four backends at once, so one falling over does not take the lights with it:

• OpenRGB SDK over TCP for SMBus motherboard and RAM
• a native Sapphire Nitro Glow V3 driver over ADL I2C — no OpenRGB, no admin, which
  is what keeps GPU lighting alive through every boot
• Logitech HID++ 2.0 direct, no G HUB needed
• Gigabyte IT8297 / IT5702 over USB

Per-device control — right-click any device for its own colour or effect. Runs of
identical devices (four RAM sticks, say) collapse under one header with a shared toggle.

Automation — profiles with auto-apply on process launch and restore on exit, a night
schedule (off or dimmed), idle timeout, off on lock/sleep/display-sleep/exit, global
hotkeys (Ctrl+Alt+L / P / R), and a forwarding CLI that makes Stream Deck buttons
trivial.

Reliability, which is where most of the work went. ASUS Aura boards revert their zones
to the firmware rainbow on resume, and a RAM stick that enumerates late on the SMBus will
ignore colour writes until the server is restarted — streaming colours fixes neither, only
re-issuing Direct mode does. Prisma re-asserts after wake and again as the bus settles
post-boot. It also detects other RGB stacks fighting for the lighting bus and names them,
reconnects a dead OpenRGB backend, and orders its writes to avoid wedging the fragile GPU
I2C controller.

Requirements

Windows 10 / 11. Motherboard and RAM lighting need an OpenRGB
server running elevated — SMBus access needs admin. A logon scheduled task with Run
with highest privileges named OpenRGB Server is the cleanest setup; Prisma will start
it for you.

Run exactly one OpenRGB instance. Two servers initialising the same SMBus
controllers will wedge a device — a stuck RAM stick that only a full power-off clears.
Prisma's conflict watchdog exists to catch this.

MIT licensed.