Platform Support
This page summarizes the platforms DearScenario Player is designed, tested, and supported for. Use it when choosing playback hardware for a venue, exhibition, kiosk, or control-system deployment.
DearScenario Player is primarily a local playback endpoint. The most important platform question is not only "can the binary start?", but whether the machine can run stable fullscreen playback, expose the control API, recover unattended, and be supported when something goes wrong on site.
Support Matrix
| Platform | Support status | Supported versions | Notes |
|---|---|---|---|
| Windows | Official | Windows 7 x64 SP1, Windows 10, Windows 11 | Main supported platform for exhibition PCs, Intel NUC-class machines, kiosks, and rack-mounted playback computers. |
| Raspberry Pi | Official, limited | Raspberry Pi 4B / 5 with Raspberry Pi OS 64-bit Lite or Desktop | Supported as a compact playback node. Lite can run as a direct display appliance; Desktop is available when a desktop environment is useful for the deployment. |
| macOS | Not supported | - | macOS is not currently planned. Use Windows or a supported Raspberry Pi target for standard deployments. |
| Other Linux distributions | Custom only | Ubuntu, Debian variants, embedded Linux, and similar targets | Not part of the standard support scope. Platform adaptation may be possible as paid custom work. |
| Other ARM boards | Custom only | Orange Pi, Jetson, industrial ARM boxes, and similar boards | Not part of the standard support scope. Support depends on the exact board, OS image, GPU stack, and deployment environment. |
| 32-bit operating systems | Not supported | - | Always use a 64-bit OS. 32-bit Windows, Raspberry Pi OS, and Linux environments are not supported. |
What Official Support Means
Official support means the platform is part of the expected deployment path for DearScenario Player. Documentation, downloads, support replies, and troubleshooting guidance assume these targets unless a page says otherwise.
For a standard project, choose one of these:
- Windows for exhibition PCs, kiosks, Intel NUC-class machines, and rack-mounted playback computers.
- Raspberry Pi 4B / 5 with Raspberry Pi OS 64-bit Lite or Desktop for compact playback nodes behind screens or inside simple installations.
Official support does not mean every GPU, display adapter, audio interface, driver version, media file, or venue network has been tested. Always test the actual hardware, display chain, media files, and control network before going live.
Windows
Windows is the main production target. It is the safest choice when a project needs broad hardware options, reliable display drivers, common AV interfaces, and the least amount of platform-specific adaptation.
Use Windows when you need:
- standard exhibition or kiosk PCs;
- Intel NUC-class or small-form-factor playback machines;
- rack-mounted players;
- Windows audio device control;
- system tray integration;
- the most straightforward support path.
Windows 7 support exists for legacy industrial PC deployments. For new projects, Windows 10 or Windows 11 is the better default.
Raspberry Pi
Raspberry Pi support is intended for compact playback nodes based on Raspberry Pi 4B or Raspberry Pi 5. Use a 64-bit Raspberry Pi OS Lite or Desktop install, not a 32-bit OS. Lite is suitable when the player should operate as a direct display appliance; Desktop is available when a desktop environment is useful for commissioning or local operation.
hwdec_mode: "v4l2m2m" explicitly enables the Raspberry Pi V4L2 M2M decoder
path for H.264 and HEVC, with software decoding as a fallback. It is not a
zero-copy mpv hwdec path, so performance remains content- and display-dependent.
For best results, test the exact codec, resolution, bitrate, display output,
and thermal setup before deployment.
Custom Linux And ARM Targets
Other Linux distributions and ARM boards are not standard supported platforms. That includes Ubuntu, general Debian variants, non-Raspberry Pi ARM boards, Jetson devices, industrial ARM players, and embedded Linux images.
These targets may still be possible, but they should be treated as custom integration work. Before planning a rollout, confirm:
- board model and CPU architecture;
- OS distribution and version;
- desktop, X11, Wayland, or framebuffer path;
- GPU and OpenGL driver stack;
- expected media codecs, resolution, and bitrate;
- whether the deployment can be validated as paid custom work.
Not Supported
The following are outside the current standard support scope:
- macOS;
- 32-bit operating systems;
- older Raspberry Pi models that cannot meet playback performance needs;
- generic Linux ARM packages;
- unsupported embedded boards without platform validation.
Related Pages
Previous / Next
- Previous: System Tray
- Next: Encoding