Chroma Immersive Platform
The Chroma Immersive Platform brings together three on-device AI features that analyze what a player's PC is already producing, the system audio output and the on-screen image, and translate it into lighting and haptics in real time. All inference runs locally on the player's machine.
The platform is available in Razer Chroma for Windows (V4.0.63.2608041508). Players enable the individual features from the Chroma dashboard and configure them per device, app and game.
These features consume system-level audio and video output. Your title does not call an API, emit events, or register effects to benefit from them. A game that has already shipped is supported without a patch.
Because there is no integration surface, what you control is the input. These pages document the signal characteristics of each feature so you can reason about how your title's audio mix and visual design will be interpreted.
Feature summary
| Feature | Session identifier | Input | Output | Content type |
|---|---|---|---|---|
| Razer Resonance | SessionAudioToHaptics | System audio output | Sensa HD Haptics intensity | Games, video |
| Screen Sync | SessionAmbientAwareness | Foreground window image | Chroma lighting | Games, video |
| Mood Analyzer | SessionMoodAnalyzer | System audio output | Chroma lighting | Music |
The two lighting features are alternative paths, selected by content type. Screen Sync handles content with a picture worth reading. Mood Analyzer handles music, where there is no meaningful frame to sample. Only one of them drives the devices at a time.
Razer Resonance is independent of that choice and may run alongside either, since it drives haptics rather than lighting.
Signal characteristics
All timing values that affect how your content is interpreted, in one place.
| Feature | Analysis | Rate | Smoothing |
|---|---|---|---|
| Razer Resonance | Audio event classification | ~8 Hz | Asymmetric envelope on a ~20 ms loop |
| Screen Sync | Dominant color extraction | ~5 Hz | None documented |
| Screen Sync | Pattern classification | ~0.33 Hz | None documented |
| Screen Sync | Active region detection | ~0.33 Hz | None documented |
| Mood Analyzer | Mood classification | ~20 Hz capture | 2 s dominant-mood window |
Requirements
| Component | Requirement | Applies to |
|---|---|---|
| Razer Synapse | Installed and running | Razer Resonance |
| RzChromatic | 2.3.2.0 or newer | Screen Sync |
| Razer Experience Service | Installed, user logged in | All features |
| Haptics-capable device | Required for haptic output | Razer Resonance |
Screen Sync communicates with RzChromatic over a WebSocket interface introduced in 2.3.2.0. On earlier versions the connection does not establish and no ambient lighting appears.
Data handling
All analysis is performed locally on the player's machine. No audio and no frames are transmitted off the device, and nothing is sent to the cloud.
All three features read the system audio output. None of them access the microphone.
Runtime model
All three features run as sessions inside the Razer Experience Service, a Windows background service. The service hosts a worker process in the logged-in user's context, because the features require access to the user's audio endpoint, screen, Chroma and Synapse instances.
Three properties are relevant when evaluating behavior on a test machine:
Sessions activate at user logon. After a boot with no user logged in, the service runs but no analysis occurs.
Session state persists across restarts. Enabled sessions are restored automatically after reboot, logon, or service restart. A session enabled during earlier testing will still be active later.
No session is enabled by default. The built-in default session list is empty, so features are inactive until enabled by Synapse or restored from a previous state.
Model precompilation
At install time the service can precompile the AI models (precompileModels) in the logged-in user's context, so that the first feature activation is fast rather than pausing to compile. Uninstall clears this cache (clearPrecompiledModels).
Choosing between the platform and the WYVRN SDK
The platform and explicit SDK integration solve different problems and are commonly used together.
| Use the Chroma Immersive Platform when | Use the WYVRN SDK when |
|---|---|
| You want broad coverage with no engineering cost | You need a specific effect at a specific moment |
| Moments are emergent or procedural, and cannot be authored ahead of time | The moment is scripted and you know when it happens |
| The title has already shipped | You are in active development and can add integration |
| Approximate, content-derived response is sufficient | You need exact control over color, timing, or haptic waveform |
| Music-driven or rhythmic haptics are not required | Music-driven or rhythmic haptics are core to the design |
A common pattern is to rely on the inference path for general coverage and author explicit effects through the SDK for signature moments.
Evaluating your title
Practical checks when assessing how your game behaves with these features enabled.
| Check | Expected result |
|---|---|
| Combat or impact-heavy sequence | Distinct haptic response on impacts, with immediate onset and a smooth decay |
| Dialogue sequence with no other audio | No haptic response |
| Music-only sequence | No haptic response through Resonance |
| Scene with a strong dominant color | Device lighting reflects that color within roughly 200 ms |
| Letterboxed cinematic | Colors derived from the picture, not the bars |
| Borderless, exclusive fullscreen, and overlay focus | Capture continues to follow the intended window |
| Pause audio for several seconds | Haptics stop and reset after approximately 5 seconds |
Diagnostics
Verbose service logging can be enabled by creating an empty file named debug.flag next to the service executable, typically:
C:\Program Files (x86)\RazerExperienceService\RazerExperienceService\debug.flag
Directory permissions may require creating the file elsewhere and moving it in. Restart the service. Logs are written to:
%LOCALAPPDATA%\Razer\RazerExperienceService\Logs\dllLog.log
If nothing responds
| Symptom | First check |
|---|---|
| No ambient lighting at all | RzChromatic version is 2.3.2.0 or newer |
| No haptic response | Synapse is running, and the device supports haptics |
| No response from any feature | The relevant session is enabled, and a user is logged in |
Feature reference
- Razer Resonance: audio-classified haptic intensity
- Screen Sync: screen-derived Chroma lighting
- Mood Analyzer: music mood lighting
- Performance: device selection and measured resource cost
Related
- WYVRN SDK for explicitly authored haptics and lighting
- WYVRN Haptics Configuration
- Chroma RGB SDK
- Razer Indie Lab