I’m rebuilding my database & I’ve found that none of the music files YEARS data has been imported, what have I done wrong?
I had the same issue.
Same here. And that is 6 months later… So Engine is not importing the year tag???
So it’s January 2022 & this is still an issue, not a major one but still a bug which should have been sorted a long long time ago. Easily fixed by rescanning every new file added but that’s not the point!
Now it’s January 2023 and it’s still an issue 
29 April 2023 and still an issue in v3.0.1.
Please fix the minor issues in Engine Dj before adding more functionality like the Kaoss Pad touch screen effect. Half of the issues should be easy fixes for low end programmers on staff while you work on other features.
1 Like
Never seen this issue, but I have engine set to re-analyse all my music as it’s imported. Been using the Serato import since day one of using Engine.
Hey Steve, was this ever resolved for you? I am relatively new to Engine and I am importing over from Serato with the same issue.
This has never been resolved, I just do a quick tag scan on anything without the year in & I’m golden 
1 Like
Oh nice one, I’ll give it a crack myself. Cheers!
It doesn’t sound like this was resolved… I’ve done an import of my entire library and found that all my files were imported without a year. I’m assuming the year is not imported from the id3tag. Is there a way to at least make an edit to read the year? What field in the mp3 should I update to import the year correctly? Any help would be appreciated. Thanks.
Ok… I did some research and found that Engine DJ is reading the year from ID3v1 and not ID3v2.
1 Like
Long standing unresolved issue
Do a re-import track info after updating engine DJ with Serato library