[Feature]: Desktop app: music and Listen Together

Abierto
#91 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust, typescript

Línea de trabajo

Read epic #80 and prerequisite issues #82 and #83 first, then compare the web player in web/src/music/, especially decoder.worker.ts, engine.ts, and listen.ts, with the shared queue logic in packages/shared/src/music.ts and its music.test.ts tests. The issue calls for a native desktop audio engine, player UI, queue synchronization, and Listen Together integration across several subsystems. Done means gapless playback, matching crossfade and ReplayGain behavior, shared queue continuity, and Listen Together compatibility with web members.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a planning session with @PhrolovaMoe. Part of #80, builds on #82 and #83. Read the epic first.

Area

Desktop app

Problem

Music on the web is a fully custom, hi-fi player: untranscoded playback, sample-accurate gapless, crossfade and ReplayGain, a server-side queue shared with Subsonic clients, and Listen Together. The app needs the same thing natively, not through mpv.

Proposed solution
Engine
  • Decode with decoder/core (symphonia, gapless sequence, resampling to the output rate), exactly as the web worker does (web/src/music/decoder.worker.ts, engine.ts).
  • Read files through a Read + Seek adapter over HTTP Range requests on /api/music/tracks/{id}/file, with the same fallback the web uses (…/flac for lossless formats the decoder can't read, …/stream only when the user asks for lossy).
  • Output with cpal. On Linux that's the ALSA host, which reaches PipeWire/PulseAudio through their ALSA plugins. Use the device's default rate and follow the default device when it changes.
  • A lock-free ring between the decode thread and the cpal callback, like the web's ring.ts/worklet.ts. The position comes from frames actually played, as on web.
  • ReplayGain Off/Track/Album/Auto (default Auto), crossfade (off by default, never between consecutive tracks of the same album), and volume, all as on web.
Player logic
  • Port packages/shared/src/music.ts (queue, repeat/shuffle, keeping the server's play queue in step) to Rust, with its tests (music.test.ts) ported too. Behaviour must match, because web, Android and Subsonic clients share the server's queue. Send the client argument on nowPlaying/savePlayQueue as the other apps do.
  • Starting a video, clip or room pauses music and hides the pill; leaving it brings the pill back paused. The pill can only be closed while paused. The queue persists. All as on web.
UI

The web is the spec (web/src/music/):

  • Library (Albums / Artists / Songs / Playlists) in the sidebar's music library, routes/album.$id.tsx, artist.$id.tsx, playlist.$id.tsx.
  • The bottom-centre pill → floating card → full-screen Now Playing (Lyrics / Queue / Info) with synced lyrics, tinted from the artwork (Pill.tsx, NowPlaying.tsx, controls.tsx, components.tsx).
  • Stars, ratings, playlists, history: the same mutations.
Listen Together

Port web/src/music/listen.ts and routes/listen.$code.tsx: the listen WebSocket (/api/listen/{code}/ws), the room's routes for files/covers/avatars, guests without sign-in, and joining from tinystream://<host>/listen/<code> and web URLs (the entry point is called by #92).

MPRIS for music is wired in #92. Expose the player state it needs (metadata, art URL, position, rate, controls).

Done when

An album with gapless transitions plays without a gap or click. Crossfade and ReplayGain sound the same as on web. The queue picked up on web continues in the app and the other way round. Listen Together works with web members. CPU use while playing is low (well under a browser tab playing the same).

Lenguaje dominante
TypeScript
Estrellas
4
Forks
1
Merge medio
4 h 49 min
PR fusionados (30 d)
5

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de tinystream-dev/tinystream

Todos los issues de tinystream-dev/tinystream

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.