1) Set the BPM in mix to 129,83333333 for a mp3 (in Right Click » Properties ...)
2) Right Click » Metadata » Export To File Tags
3) Exit mixxx
4) Start mixxx
5) Find that mp3 » Right Click » Properties » Re-Import Metadata from File » Apply/OK
6) Now the rounded integer BPM imported to mixxx library.
(My workflow: I get my music » tag it with foobar2000 and mp3tag » load and analyze in mixxx » do an Export To File Tags in mixxx. This writes the BPM in file tags and will show up in foobar2000 – I play and pre-select music for my sets using foobar2000.)
[Can’t there be a workaround for this problem using APE tag or a custom field?
If I have an mp3 with APEv2 tag only, mixxx will write BPM with thousandth precision (and will add an ID3v2.4 tag part) and it will show up this way in the Mp3tag software (thousandth precision), but mixxx will see/import integer rounded value.]
1) Set the BPM in mix to 129,83333333 for a mp3 (in Right Click » Properties ...)
2) Right Click » Metadata » Export To File Tags
3) Exit mixxx
4) Start mixxx
5) Find that mp3 » Right Click » Properties » Re-Import Metadata from File » Apply/OK
6) Now the rounded integer BPM imported to mixxx library.
(My workflow: I get my music » tag it with foobar2000 and mp3tag » load and analyze in mixxx » do an Export To File Tags in mixxx. This writes the BPM in file tags and will show up in foobar2000 – I play and pre-select music for my sets using foobar2000.)
[Can’t there be a workaround for this problem using APE tag or a custom field?
If I have an mp3 with APEv2 tag only, mixxx will write BPM with thousandth precision (and will add an ID3v2.4 tag part) and it will show up this way in the Mp3tag software (thousandth precision), but mixxx will see/import integer rounded value.]