Add Rekordbox XML export#251
Open
Peter7896 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a first XML export path for device exports, built on the existing
xmlmodel rather than formatting XML by hand.The export currently includes track metadata from
export.pdb, beatgrid-derivedTEMPOentries fromANLZ0000.DAT, cue and loopPOSITION_MARKentries fromANLZ0000.EXT/ANLZ0000.2EX, and playlist folders/playlists when the device export contains playlist tree rows.I also fixed the generated test templates to use raw path literals so the existing generated tests compile with Windows paths.
Checks run locally:
cargo fmt --all -- --checkcargo clippy --all-targets -- -D warningscargo testcargo run --quiet -- export-xml data/complete_export/demo_tracks _tmp_demo.xmlcargo run --quiet -- dump-xml _tmp_demo.xmlThe bundled demo export has track metadata and beatgrids, but no playlist tree rows or cue entries, so the demo regression covers XML generation plus BPM/beatgrid output. Cue/hot-cue and playlist ordering are covered with focused unit tests. I do not have CDJ hardware available for the physical import check requested in the issue thread.
Refs #127