Ever since updating to Engine DJ Desktop v4.0.0, when updating the metadata within a file, and then choosing to “Re-import track information”, Engine DJ Desktop does not update with the new metadata values.
For example, I mistakenly tag a track “Dum & Bass”, import the file, have Engine DJ Desktop analyze, and then I realize I mess up. So I edit the metadata in the file, select it, and choose “Re-import track information”, yet Engine DJ Desktop fails to reflect the current status of the file and does not update.
This was working in previous versions in this manner.
There could be a number of reasons, but without more info it won’t be obvious since I couldn’t reproduce this.
What drive format are you using where these tracks are stored?
Are you on Mac/Windows?
What file format is affected, mp3, wav, or everything?
What ID3 tag editor are you using? And are you required to save the changes when exiting that app?
Are you editing the tag 1, tag 2, tag 3 field in the ID3 tag editing application?
Which tag field are you editing? Is it always genre?
If you were to go back to a previous engine desktop version (you can find them here, just scroll down a little), does the issue still happen in that version?
What file format is affected, mp3, wav, or everything?
I only import and use .flac files, so I’ve only seen this with .flac files.
This could impact other file formats but I have not tested anything other than .flac.
What ID3 tag editor are you using? And are you required to save the changes when exiting that app?
metaflac
MusicBrainz Picard
Are you editing the tag 1, tag 2, tag 3 field in the ID3 tag editing application?
(I am slightly unclear on this question)
ID3 Tags are not used.
Mutli-value tags are not used as they never seemed to work
(ie: All tags are simple strings, no ; and no multi-value or array-like values)
Which tag field are you editing? Is it always genre?
Primarily Genre, but also Artist/Title fixes.
If you were to go back to a previous engine desktop version does the issue still happen in that version?
I am unable to provide this level of testing right now and have not tested anything downgraded.
I never noticed this issue with 3.x releases
Just to be clear, I have a pretty specific pipeline and workflow that every single file goes through, regardless of the file’s source. Every single file is converted to FLAC, tagged within MusicBrainz Picard, and saved out using the tags. I can import 100 files today, realize I want to change a Genre on one of them, but the update isn’t seen by Engine DJ Desktop. I have tested by changing another of the 100 files and refreshing, Engine DJ Desktop is able to see the updates, so I know there isn’t something inherintely broken with all 100 files or my workflow itself.
Edit: The next time it happens, I’ll dive deeper into the specific file and see if there is anything odd about it that I can find.
Unfortunately, we don’t officially support NAS drives or content stored on servers for use in Engine desktop software, and it’s certainly not something we test for. So the behaviour when using this file storage type could have some unexpected behaviours that we are not aware of. If you find the same issue occurs for locally stored tracks then it’s possible there may be a legitimate bug here.
Appreciate your efforts, and please do let us know if there’s something more you manage to find out when the issue occurs again. We may still be able to advise on a solution. Checking in an older version of Engine desktop will give us some valuable info if this is deemed to be a new issue in the application in version 4.0.0.
A few months later, this is still affecting me and I have not found any commonality between why seemingly random tracks cannot update metadata from an updated file within Engine DJ Desktop.
Can we get some debug logs around this feature and I can try to see if I can discover any details? I’ve yet to see anything that stands out but I’ll check again next time I find a track that refuses to update.
Yes, which is very frustrating when coupled with the fact that:
Double-clicking a file loads the track into the player
Double-clicking a column of a file makes that portion editable.
So, the same action can have two different consequences, and it’s determined by the timing. It’s very clunky and feels very bad when you’re trying to edit more than a single file, having to wait, but not wait to long to waste my time, but if I don’t wait long enough I have to unload the track and start over.
The issue is “Re-import track information” isn’t working. It is compounded by the additional poor UI/UX.
I’ve done plenty of editable grids in my time and getting it all to work the way everyone wants to is extremely difficult. Add to the mouse input, there are keyboard shortcuts and what not.
Build muscle memory in how it works and what you’re able to do/access and you should be fine. =)