Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

locallibrary: hardware test day for every writer and the player features on real players

Abierto
  • ¿Algo no está bien?
#175 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend, testing-qa

Línea de trabajo

Start with the hardware test checklist in apps/locallibrary/TODO.md#L93-L116 and the referenced createdDate code in crates/locallibrary/src/onelibrary/mod.rs#L480. Work through the listed writers and player behaviors on the specified real players, recording results for each item. Done means the checklist has measured results, including file writes, format and cue behavior, sessions, and the createdDate comparison.

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

Descripción

locallibrary: core tests
Problem

No OneLibrary write, collection export, transcoded copy or track upgrade has been loaded on a real player. Everything so far ran against fixtures and the rekordbox export format. What CDJs do with MP3 encoder delay or the new FLAC and AIFF format codes cannot be measured from files.

What you'd like

Run these on a spare drive with an export.pdb player and the CDJ-3000X, taking a snapshot first and using undo after each writer:

  • Every writer, then undo, each loaded on both players: playlist and track edits, tags, cues, merge (include a source with no exportLibrary.db; analysedBits and contentLink are guessed from the target's tracks), clean, art set, convert, pack, refresh, prep, drive player, settings apply, drive firmware, edits replay.
  • Whether OneLibrary-only players read My Settings from *SETTING.DAT (one settings apply).
  • Which files each player writes during a set and whether it checkpoints exportLibrary.db (snapshot, plug in, play, eject, locallibrary diff --summary).
  • Whether players show OneLibrary's deviceName, what colour codes 1 to 8 look like, and where export.pdb players get the Device Name.
  • The TUI Drives actions (pull, sync group, pack, restore, eject), the : palette and footer hints on real drives in a real terminal.
  • My Tags from exportExt.pdb on a real tagged drive.
  • Sessions: a track on deck 1's stick played from deck 2 is logged on deck 1's stick; plugging in a stick and playing nothing leaves no empty history list; a player power-cycled with the stick in starts a new list; a b2b with two sticks leaves each stick only its own tracks.
  • collection export to a stick, loaded on both players.
  • pack --transcode WAV copies (written as plain PCM) and the FLAC and AIFF format codes.
  • Cue timing after track upgrade, including an AAC track (its delay is not measured against rekordbox yet).
  • OneLibrary's createdDate is the local date (https://github.com/cutenode/localnetwork/blob/24d3176/crates/locallibrary/src/onelibrary/mod.rs#L480): compare it with what a rekordbox export writes.
Where
Lenguaje dominante
Rust
Estrellas
0
Forks
0
Merge medio
9 h 14 min
PR fusionados (30 d)
99

Preparar el entorno

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 cutenode/localnetwork

Todos los issues de cutenode/localnetwork

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.