Incorrect Metadata for Year Displayed
Answered
Hi
I have several albums where the album date is shown incorrectly. If I look at the metadata for the album using (for example) Mp3tag, the data for each track on a an album is displayed correctly, However, in the Bluesound player a different date is shown. Where is this date coming from and how do I change it? It is very annoying to have albums listed in the wrong order.
-
Official comment
Hello all,
I was almost certain I made a response on this a while back...? Apologies for the mix-up on my part!
In any case, please send two sample songs (from the same album, one where the year metadata is shown correctly and one where it isn't) to support@bluesound.com so our support crew may test and investigate further.
Regards,
Sam R. -
Hi Rob
BlueOS will only display what's in your tag. Check if all dates are equal for the same album using Mp3Tag.
If you do any changes you have to do a full rebuild.
(Or rename the folder and do a reindex to see if there is any difference.)0 -
I'm also seeing this on certain albums, and so far I've only noticed it when I have multiple albums with the same name, but different artists. When I'm browsing by Library -> Artists -> (Artist) and sort by Release Date, the album is in the wrong place chronologically. Checking the tags in the files shows them to be correct, and Logitech Media Server is showing the correct years, as does foobar2000, Plex and everything else I test them with.
An example:
Logitech Media Server correclty shows 1988 for both versions:
dbPowerAmp tags for standard edition:
dbPowerAmp tags for Deluxe Edition (Disc 1 - see post further down for Disc 2):
Here's what the Bluesound controller shows me: 1988 for one version, and 2019 for the other!
I'm seeing it with other albums too, such as Def Leppard's Hysteria.
I'm an OCD freak when it comes to fixing any errors in my tags, and this definitely seems to be a Bluesound issue as every other bit of software I use is handling it correctly. I've also checked several times that all files for that album have the same year, so it isn't because a few songs have a different year.
However, if you browse by Library -> Albums and sort by Release Date, the information for the problematic albums is correct!
0 -
Why the difference in total tracks between dbPowerAmp and BlueOS?
Are there any option in dbPowerAmp to view what kind of tag it's writing? (ID3v1x/2x, APE, FLAC, ALAC)0 -
Funnily enough I was just about to edit my post as I'd also spotted the discrepency in the total tracks for the version that has the wrong year! As you've noticed, the header shows 12 tracks, but browsing into the album in Bluesound does show all 14 tracks correctly.
Don't worry about the Deluxe Version showing 37 tracks in the header, but only 17 in my screenshot - the physical files are split into Disc 1 and Disc 2 and I only showed the screenshot for Disc 1 in my original post. Here's Disc 2 to show that all 37 tracks (17 Disc 1, 20 Disc 2) are present and being displayed as expected in Bluesound. This Deluxe Version seems to be in order - it's the standard version above that's messed up.
Regarding tag type, I can't see how to view this on dbPowerAmp on my Mac. I'll try to work it out on my Windows Virtual Machine tomorrow and update this post - it's almost 1am and I need to get to bed!
I've taken a quick look at my Def Leppard Hysteria albums and the version with the incorrect year is also showing the wrong track count in the header, but the correct tracks in the main listing. Surely no coincidence!
0 -
Bjørn, when I first noticed this problem a few days ago I trawled through the forums and found the following similar post:
https://support1.bluesound.com/hc/en-us/community/posts/360048764494-Bug-in-displaying-indexed-data-
I've just realised it was yourself who'd reported it - I assume you still have the problem at your end too?
Edit: Aha! You're right. My issue does seem to match yours!
I've just seen that my dodgy Def Leppard Hysteria entry is clashing with a Muse Hysteria CD Single, and my All About Eve album is clashing with PJ Harvey's All About Eve soundtrack. So it isn't consistent behaviour (my dozens of Greatest Hits albums seem to be okay) but I can now concur with you that it seems related to albums with the same name by different artists.
This only seems to display incorrectly when viewing the album from the Artists section. When I browse via the top-level Albums section, the correct information is shown. Here's what I see when vewing the All About Eve album via Albums instead of Artist - it's correct now. Same with my Def Leppard album!
Over to you guys, Bluesound :-) If you need any more examples, let me know.
To the original poster (Rob Smith) - sorry for taking over your thread, but can you check if your problem is the same? If you view the problematic albums from the top level Albums section, does the correct year show up?
0 -
One more example to back up this theory. It doesn't happen for every album that shares a name with one by another artist, but when it does happen it consistently shows the wrong information, even after closing/re-opening the controller.
Behaviour is the same on both Mac and iOS controllers. I haven't tested on Windows or Android.
I have two albums called "At the BBC" (seen here via the Albums view)
Viewing each via the top-level Albums section shows correct info for both albums:
But when I view the Siouxsie album from her own Artist page, I see the track count and year for the Sleeper album instead. The running time and tracklisting is correct however!
0 -
Hi Pete.
You are absolutely right about your findings.
It also affects some of my "Greatest Hits" but not all.0 -
I have checked that my meta tags are all correct. Any comment from Bluesound on this problem?
0 -
Sam, it's easy to replicate the issue.
Library - Albums - Sort by A -> Z
Metadata (foobar)
Library - Artists - Artist name - Albums, show all - Sort by A -> Z
0 -
Ah, I thought that originally which made me think of this post: https://support1.bluesound.com/hc/en-us/community/posts/360048764494-Bug-in-displaying-indexed-data-
What I thought Rob was seeing was that some songs of the same album showed different years. So I suppose it is somewhat similar to the other post. I will forward this to our QA team to look into further.
0 -
Sorry, my bad. Looks like Pete and I hijacked the tread!
Rob's issue is probably something else, so he should send you some files ;-)0 -
Sorry for the possible hijacking! I genuinely thought Rob's problem was the same thing I was seeing.
From reading Rob's original post, there's still a chance we are all talking about the same issue, but it would be handy if Rob could confirm whether he only sees this issue when browsing albums via the Artist page? As shown by our examples, both Bjørn and myself have noticed that the metadata only appears to be wrong when browsing via Artists, but viewing the same album directly via Library -> Albums actually shows the correct metadata.
Rob - when you get chance could you try viewing the album via Library -> Albums instead and see if it's displayed correctly this time?
It's kinda irrelevant for me now because I returned my Node 2i after a week, but I'd be happy for others if this issue gets resolved :-)
0 -
I realise this thread is now two years old, but did the problem ever get resolved? Basically if you had two different albums by two different artists, but the album name was the same for both, then the Bluesound controller would often show the Year and Track Count for the wrong album when browsing to the album via Library -> Artist -> Album (yet showed the correct information when bypassing the Artist screen and viewing the album from Library -> Albums instead.)
There's a bit of back-and-forth above whilst a few of us were trying to prove it wasn't a tagging issue and identify the root cause - see this particular post for a clearer explanation and example:
https://support1.bluesound.com/hc/en-us/community/posts/360052167233/comments/360014726173
Anyway, it's now been two years and I don't currently have any Bluesound gear to check if it's been fixed.
Thanks!
0 -
I can confirm that the (annoying) bug is still present :-)
1 -
Thanks for confirming it's still occurring, Bjørn.
I've been considering getting back into the Bluesound ecosystem recently (either the new PowerNode or the NAD C 700) and was interested to see if there'd been any resolution to a couple of issues mentioned by myself and others. Unfortunately it doesn't look like anything has changed in the intervening years :-)
0 -
Why is this still a bug some 2 years later (although it was long before that it was first reported)? It makes the user experience very poor. Any chance that this can be looked at again? I never did get a response to the files I sent in before as requested.
1 -
Echoing Rob's comment above, it's a pretty poor show by Bluesound that they appear to have made no effort to resolve this over the last couple of years. I decided to get back into the Bluesound ecosystem last week and have already been hit by this bug multiple times in a matter of days. As somebody who tends to browse an artist's discography in chronological order, it's really annoying when certain albums appear in the completely wrong place.
It doesn't matter how good the hardware is when the software controller (a critical part of any music system) has such fundamental and reproducible bugs, and when the company doesn't seem to care about their users' UI experience. I'd expect the company to take some kind of professional pride in what they're releasing, and it's extremely disappointing to see the complete lack of effort to resolve this.
0 -
Unbelievable. Version 4.0 has been released and this 3+ year old bug still remains? Great customer support, guys.
0 -
Could we have an official statement regarding this issue?
0 -
Just letting you know I've now raised an official support ticket about this, and the other related thread we've been commenting on over the last 3+ years. I'm completely fed-up with Bluesound's utter lack of action on this bug, but I don't know if anyone has ever raised a proper support ticket about it, or if we'd assumed that it was already on their "to-do" list (as both threads imply that it had been passed on to the development team).
Hopefully this will spur them on a bit? Or maybe they'll just continue to ignore it for another 3 years...
0
Please sign in to leave a comment.
Comments
21 comments