Please fill in this bug report template:
Lexicon version: 1.9.11
Operating system (remove one): Mac
Bug description:
When importing Serato crates that are nested, tracks can end up in the wrong order
Step by step to reproduce:
In Serato:
- Create a new crate “A”
- Add a bunch of tracks into crate “A”
- Create new crate “B” and “C” and drag them inside of “A”
- Select crate “A”
- Drag tracks that are in “A” into “B” and “C”
- Select crate “B”
- Reorder some of the tracks in crate “B”
- Select crate “C”
- Reorder some of the tracks in crate “C”
- Import Serato library into Lexicon
- Examine the order of tracks in playlists “B” and “C” and they will not match the order they were previously reordered in the Serato crate. Instead, they will match the order that the tracks are in within crate “A”.
Serato allows independent ordering of tracks that are in a parent crate and tracks that are in child crates. Lexicon only allows explicit ordering of tracks in a child/leaf playlist. This is fine (for me). But it seems like Lexicon is looking at the track ordering in crate “A” and associating an index with each track. It then seems to descend into the child crates and reads the track listing in the child, but uses the same index that it recorded within the parent crate.
Screenshot:
Screenshot 1: Parent crate is selected. Environ is before rEvolver
Screenshot 2: Child crate ‘hard’ is selected. Environ has been moved to the end of the list, after rEvolver
Screenshot 3: In Lexicon, playlist ‘hard’ is selected and shows Environ is above rEvolver instead of at the end of the playlist.
I would assert that maintaining the ordering of tracks inside of a child playlist is a much higher priority than maintaining the ordering of tracks in a parent playlist, since Lexicon doesn’t even support independent ordering of a parent crate.
Thanks for looking into this!