feat: spatial settings end-to-end + core-web wasm built in-tree #1

Merged
wbadmin merged 14 commits from feat/net-whiteblossom-stremio into main 2026-11-11 19:14:17 +00:00
Owner
No description provided.
- New 'omniphony' module: extracts mpv-omniphony v0.7.0 AppImage to
  /app/lib/omniphony/player and harletty-bridge v0.9.0 .so files to
  /app/lib/omniphony/bridges (sha256-pinned).
- Launcher prefers the embedded player; falls back to flatpak-spawn --host
  /usr/bin/mpv-omniphony (whiteblossom-os image) when absent.
- Bundled default config /app/etc/omniphony/config.yaml (binaural + embedded
  bridge_paths) applied via OMNIPHONY_CONFIG_DIR only when the user has no
  ~/.config/omniphony/config.yaml yet.
- Verified: TrueHD probe inside sandbox renders through harletty-dolby
  bridge 0.9.0; UI boots with zero auth errors.
- server.js: prepend /app/bin/mpv to the external-player probe list so the
  MPV device appears on every install (verified via /casting/ API).
- Launcher injects --ad=orender,lavc for spatial rendering (ad_orender is
  opt-in in mpv); gsettings key spatial-audio gates it; explicit --ad in
  spawn args wins (last --ad wins in mpv).
- New gschema key spatial-audio (default on) + AdwSwitchRow in the
  preferences dialog (MPV group).
- Verified live: MPV device listed, toggle on -> harletty-dolby bridge +
  VBAP 12-speaker renderer on TrueHD; toggle off -> native decoder.
Invalid signal in the spatial-audio row template made PreferencesDialog
construction panic (app abort on opening Preferences). Matches the signal
pattern of the other switch rows.
Internal player (in-window playback):
- libmpv module now builds the mpv fork (mgth/mpv orender-v0.7.0.1, same
  upstream v0.41.0 base) with -Dorender=enabled -Dgpl=true (shell is
  GPL-3.0-only: compatible).
- video init sets ORENDER_LIBRARY + OMNIPHONY_CONFIG_DIR (bundled engine)
  and ad=orender,lavc when the spatial-audio gsettings key is on.

OSD overlay:
- New spatial-osd key + 'Object overlay (OSD)' switch; off spawns with
  OMNIPHONY_OVERLAY=off (startup Lua disables the overlay; rendering
  unaffected). Ctrl+o works during playback via shipped input.conf
  (Ctrl+o master, Ctrl+l labels, Ctrl+k objects, Ctrl+j heatmap).
- Object overlay now defaults OFF (spatial-osd default false; launcher and
  shell video init invert the env logic accordingly).
- Ctrl+o/Ctrl+l/Ctrl+k/Ctrl+j work during in-window playback: GTK owns
  keyboard input for the embedded player, so the bindings are captured on
  the Video widget (ObjectImpl::constructed) and forwarded as
  script-message omniphony-overlay <msg> — rendering unaffected.
- MPRIS: grant org.mpris.MediaPlayer2.Stremio (the name the shell requests;
  the Devel-suffix grant caused ServiceUnknown panic at playback start).
Root cause of 'overlay still shows': the overlay enabled state is
hard-coded true in orender_engine (overlay.rs AtomicBool) — no env var
or config key exists, and OMNIPHONY_OVERLAY was fictional. The startup
Lua 'disable' also raced the overlay client thread's subscription.

- Internal player: send script-message omniphony-overlay disable on
  StartFile (overlay client subscribed by then) when spatial-osd is off.
- External player: Lua now re-sends disable on every start-file at
  0/300/800/1500/2500ms until the client picks it up (idempotent).
Single disable at StartFile could still race the overlay client init in
the embedded (libmpv-in-GTK) case. The command itself is proven against
a live session (IPC enable/disable screenshots); retrying makes the
default application robust. Also switch to glib::timeout_future(Duration)
(timeout_future_seconds takes whole seconds).
- IpcEvent::Settings (settings-update {spatialAudio, spatialOsd}) from the
  web UI; handler persists both into the gschema (existing GTK dialog and
  the external mpv launcher keep reading it) and calls
  Video::set_spatial_enabled.
- Video: Rc<Cell<bool>> pending toggle + last-applied value; StartFile
  switches mpv 'ad' (orender,lavc <-> lavc,orender) when changed - mpv
  applies ad at decoder init, so switching is next-track by design.
- webui: static server for /app/webui on 127.0.0.1:11471 (path-traversal
  guarded, correct content-types, no-cache html); startup URL falls back
  to the deployed web URL when no bundle is present (dev runs).
- Init capability property omniphonySpatialAudio=true.
- Manifest: webui module builds the pinned streamio-web commit with the
  module-installed node.
The web fork (upstream/development) uses pnpm with pnpm-lock.yaml - npm ci
fails without package-lock.json. Ship the node dist's lib (npm modules)
and drive the build through corepack-managed pnpm.
- Settings IPC arm now calls Video::set_overlay_enabled: overlay
  enable/disable applies to the playing file immediately (script-message
  with the 0/500/1500ms retry guard, idempotent via overlay_applied).
- StartFile handler re-reads spatial-osd from the gschema instead of the
  realize-time snapshot, and sends 'enable' too - replaying a video
  always reflects the latest toggle state.
feat(flatpak): build core-web wasm in-tree from upstream/stremio-core
Some checks reported errors
compliance/security-scan Security scan passed (0 leaks)
compliance/build-verification Build pre-flight & lockfile verification passed
compliance/catalog-governance catalog-info.yaml is missing
compliance/chart-governance Compliance run terminated before this check reported: failed at step 'governance'
compliance/consensus-registry Compliance run terminated before this check reported: failed at step 'governance'
Build Flatpak / build-flatpak (pull_request) Failing after 8m16s
Build Flatpak / build-flatpak (push) Failing after 8m2s
7f0f700370
- new core-web module: rustup pinned 1.95 + wasm32 (pinned rustup-init
  sha256), wasm-pack 0.13.1 (pinned sha256), builds the wasm bundle and
  npm-packs it to /app/run/core-web.tgz
- webui module consumes the fresh tarball: copies it to vendor/, refreshes
  the volatile file-dep integrity hashes with --lockfile-only, then installs
  with --frozen-lockfile
- everything the flatpak needs now builds from pinned git commits in CI

fix(flatpak): resolve wasm-pack via PATH, not broken relative path

fix(flatpak): consolidate core-web build commands (per-command shell isolation)

fix(flatpak): use npx --package for @babel/cli bin resolution

fix(flatpak): npm install core-web devDeps for babel plugins
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
upstream/stremio-linux-shell!1
No description provided.