Open craigspree opened 4 years ago
3rd screenshot showing the Key information (tonality) in the Rekordbox xml
Hi @craigspree,
I think this could be done, but these points need to be considered:
These are just some initial thoughts!
FWIW here's a mapping :) https://github.com/reducecombine/traktor-keys/blob/cec694cf1db861bf114e0027d62d79d7f295a1e7/src/net/vemv/traktor_keys.clj#L13
I'd love to start using this tool soon. I'll want to keep Rekordbox as my source of truth, generating Traktor dbs from time to time. Including key info would help, I reckon!
I'd love to start using this tool soon. I'll want to keep Rekordbox as my source of truth, generating Traktor dbs from time to time. Including key info would help, I reckon!
Hi @vemv,
Many thanks for the sponsorship! 🙏🙂
I'm currently working on a fix for #33 which is fairly involved and requires me to investigate some unfamiliar stuff, so I can't really say how long that will take. However, when that issue is fixed, I'll try to allocate some time for this one.
Thanks 🙂
@alza-bitz Hey is there any update on this matter?
As a DJ transferring cues and track metatags from RekordBox to Traktor, I would like the KEY information to be copied from the Rekordbox XML (where it is stored as Tonality="" within the track tag) and placed into the collection.nml as KEY="" within the INFO tag.
Attached are 2 screenshots: 1 Existing collection nml file generated from Traktor with the KEY variable showing the location within the file.
1
2