Skip to content

Latest commit

 

History

History
53 lines (29 loc) · 2.34 KB

File metadata and controls

53 lines (29 loc) · 2.34 KB

FAQ

Common questions about platforms, playback, and workflows.

Why is HDR Wayland‑only today?

Ferrex’s native zero‑copy HDR path depends on Wayland subsurfaces and recent HDR metadata handling in GStreamer. This combination enables passing HDR surfaces to the compositor without expensive copies. Other platforms currently lack an equivalent path in this project.

Will HDR come to Windows/macOS?

That’s a goal. A cross‑platform native HDR path will require platform‑specific work and maturing dependencies. Until then, Windows/macOS can use the cross‑platform backend or the “Open with MPV” hand‑off.

How does MPV hand‑off preserve position and status?

The player communicates with mpv via IPC (Unix) or a named pipe (Windows) and keeps watch state synchronized with the server. You can override the mpv path on Windows using FERREX_MPV_PATH if auto‑detection fails.

What’s the default server port?

3000 (HTTP). Configure via SERVER_PORT (and SERVER_HOST) in .env. See docs/configuration.md for more.

Where do I configure environment variables?

.env. Generate or refresh it with just config or just start. A reference lives at .env.example.

Why is compilation failing with hundreds of sqlx errors?

As the errors describe, sqlx needs a database connection during compilation in order to validate queries. To bypass this requirement using cached queries, include SQLX_OFFLINE in your environment. For example, run export SQLX_OFFLINE=true to add to your current session or ensure the variable is set in .env.

Note: SQLX_OFFLINE=true is automatically included in .env during initial configuration.

How do I adjust server logging verbosity?

Use --rust-log when starting the stack, e.g.:

just start --rust-log 'sqlx=trace,ferrex=debug'

Or set RUST_LOG in .env.

Is there a quick way to try Ferrex without real media?

Yes. Use the feature‑gated Demo Mode to seed a disposable library. See docs/demo-mode.md for enabling flags and env.

How do I record and run UI tests?

The player ships with a tester overlay and a headless emulator. See docs/ui-testing-workflow.md for the full workflow.

Where can I report issues or check known issues?

Use GitHub Issues. For transient caveats and ongoing problems, check open issues with relevant labels (e.g., bug, known-issues).