This is the case in engine dj as well as my sc6000’s.
1 Like
Yes. It’s a known bug.
1 Like
How to fix it?
You wait until team Denon commits code and releases a fix for it. The data is in the database.
Well, I think this makes sense, though…
The History is just a log of what you played. This log should reflect what was played, and has no ties to your Collection at all. For example, maybe you play a track a few times and then decide to remove it from your Collection. In this case, your History should still reflect the track was played, but tying it to Collection or other information could make things unnecessarily complicated, and would mean solutions need to be in place to handle the fact that items in Collection can be removed and altered, etc.
If Denon users were given a proper Play Count, we could use this to view our Collection with all the metadata. In my mind, a proper Play Count implementation would also give us “Last Played” field.
Anyways, I don’t say this to argue with you, just to voice some of my own opinions. I am curious though, what is your goal or need for album art to be available in the History? When I Export any of my sets as a CSV file, I am given the “File name” as a field. I am able to then iterate these values and pull album art from the files if needed. It’s just not clear to me what benefit you get from seeing album art in your History. Is it simply to be able to better-find specific tracks within the History because you are familiar with the art?
I’m missing the cover in history as well
That’s the fact and I will remember the matching combinations; seeing the covers is assisting me to remember
I often make preparitons for a GIG. The course is documented in the history. In the history is shown what I have trained and prepared. When I’m at the GIG, I will remeber by viewing the covers of the matching tracks and can reload them. And seeing the cover is the benefit. Imo it’s of the essence.
1 Like
I often like to go back and look at the history and build playlists from it. Most people recognise tracks visually. For me it doesn’t make sense to show tracks differently just because it’s in history.
As others have said this seems to be a bug
2 Likes
Looking at it purely from a DB perspective. Isn’t the answer as simple as trying not to bloat the drive.
Your library db is fairly static, only expanding when you add new music, and rarely having any kind of performance issues unless you carry a huge library.
On the other hand your history db is an evolving beast, kind of like a transaction log in my day job world. Every single time you use the device it’s writing new data to the history db. Would it be sensible for it to write this image file to that db every time you play a track, or is it better to keep that data as slimline a possible due to it growing every time you load a track?
Could it reference the library db to pull the file, is the indexing and connections efficient enough to do this? Is the cost of doing this worth the end result?
3 Likes
The history feature copies the album art and all pertinent track data to the history database for each “session” playlist. This is what makes all of the databases so big, they store PNG files as blobs.
this is why it’s purely a bug. The data is there (in two places actually).
Engine DJ used to have this exact issue when you browsed history sessions with music that originally resided in an external drive.
3 Likes
Ahhh ok, that’s a bit ridiculous then isn’t it. My Serato history goes back about 16yrs or so, imagine 16yrs of Engine history data. I dread to think what yours looks like.
You are always smart, this forum is full of your s*** like this one.
Have you been saving those good vibes for a year?
2 Likes
Why did you reply like this? I could not see any sarcasm / malicious intent in Stu’s message.
1 Like
I’m guessing it’s from prior interactions, best not to get involved man. I’m sure they mean well lol.
If you don’t feed the trolls, they tend to go back under the bridge they came from.
1 Like
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.