Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#175 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
backend, testing-qa

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Rust
Stelle
0
Fork
0
Merge medio
9h 14m
PR unite (30g)
99

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cutenode/localnetwork

Tutte le issue di cutenode/localnetwork

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.