How to separate two different equal named albums ?

[Ron Olsen]

i agree, i do that myself.

but what concerns me is why is he seeing what he is seeing if the GH logic applies the way i described? either i'm wrong, (very possible), or something else is amiss here.

The OP's albums are named "No Stress", not "Greatest Hits".

[Mnyb]

are you looking under home -> albums?

my understanding of the "greatest hits logic" is that albums with the same name by the same artist (or AA) will NOT be merged IF the albums are in different folders.

There may be no AA ? Or some uses varius artists as AA would that be a reason ?

I would try another folder scheme:

No stress (a) /cd 1 , cd2
No stress (b) /cd 1 , cd2


Having the CD's as subfolders to the no stress folder that's how I store a multi disc album a main folder for the album and sub folders for the discs .

What about actually give a folder a slightly different name ? It is the tags that are important .

The group multiple disc together setting ? What does that do ? Ideally it should only group a with cd1,2 and b with it's cd1,2 is it broken for a situation like this ?

[MrSinatra]

The OP's albums are named "No Stress", not "Greatest Hits".

indeed, but the "greatest hits logic" applies to any albums sharing the same name, not just "greatest hits"

[Ron Olsen]

indeed, but the "greatest hits logic" applies to any albums sharing the same name, not just "greatest hits"

See the first post in this thread. The OP has two albums with different artists and the same album name, and they are merged in the LMS display.

The OP is looking for a solution that does not require changing the album names, but I don't know how to do what he wants. I think changing the album names is the simplest solution.

[MrSinatra]

ron, i saw all the posts. what he is saying doesn't make sense to me b/c of the GH logic. the two albums of the same name both by "various artists" should NOT be getting merged into one album b/c they are in different folder locations.

[finnbrodersen]

hi

thanks for all the help

I have re-tagged to "No Stress (a)" and "No Stress (b)" and the problem is solved.

This solution is not elegant, but simple and ok.

[reinholdk]

I've experienced a similar issue:

There are some (very rare) cases where I have two different versions of the same album. For example, I recently bought Pink Floyd's Discovery Box containing all their studio albums, of which I had already a few when they appeared originally.

The different versions of the albums are ripped as flac files and all files in the two versions have exactly the same album and artist tags (double-checked with mp3tag) but are stored in different folders.

SBS (I'm still on V7.6.1) is merging the tracks from the different album versions into a single album now.

The problem appeared a few days ago when I did the first full rescan since quite a long time. Before, I was performing scans for changes only and SBS perfectly displayed the two different versions as different albums. I just verified this behavior in a small test environment and found it reproducible.

Now I don't know, which of the scans is buggy: the full or the changed (of course I prefer the results of the scan for changes).

When I look to the albums table with an sqlite viewer, I see that the title, titlesort and titlesearch fields have the same values in both scenarios. Of course there's no folder information in the albums table, so it looks that the scan for changes adds a new album row due to different cover files in the two folders or due to differences in the replay gain fields.

It looks like there's no other solution than modifying the album title of one of the two album versions - as Ron proposed and how he had done it in the first place. ;-)

Personally, I don't like that too much because it mixes the information about the music with organizational stuff. Especially I thought that plugins like Erland's SongInfo might fail if there's something added to the album title, but a short test returned matching information.

So I think I will do it...

[MrSinatra]

again, as far as i know, if you put the albums in different folders they will appear as separate albums. that is by design, part of the so called greatest hits logic.

for instance, i have at least three albums whose artist, album artist, and album tags are all "Peter Gabriel" but the three show up as three separate and unique albums b/c of the differing folder locations.

(i usually use Home>Albums sorted by "Artist, Year, Album" but what i said should apply anywhere)

if u, or anyone, isn't seeing that, something is wrong. try using the latest beta.

[reinholdk]

I installed the latest beta (LMS 7.7.3-r33913) in a fresh virtual machine and the results are the same.

The full scan is merging the flac files from two different folders and displays them as a single album.

I left the LMS 'My Music' settings untouched except for 'Group Discs', which I've changed to 'Treat multi-disc sets as multiple albums'.

Here are the tags of the first tracks of the two album versions I've tested (additionally, the cover.jpg files in the two folders are also different and correctly shown when I select either track in the web UI):

=== file 1 version 1 ===
Location: D:\Music\test\Pink Floyd\The Division Bell\01 - Cluster One.flac 
Tags:
ALBUM: The Division Bell
ARTIST: Pink Floyd
CATEGORY: musicbrainz
CDID: 860f960b
COMMENT: RK-CDID=0158
DATE: 1994
GENRE: Rock
REPLAYGAIN_ALBUM_GAIN: -1.20 dB
REPLAYGAIN_ALBUM_PEAK: 0.76287842
REPLAYGAIN_REFERENCE_LOUDNESS: 89.0 dB
REPLAYGAIN_TRACK_GAIN: -1.20 dB
REPLAYGAIN_TRACK_PEAK: 0.76287842
TITLE: Cluster One
TRACKNUMBER: 1
VENDOR: reference libFLAC 1.2.1 20070917 
=== end file 1 version 1 ===

=== file 1 version 2 ===
Location: D:\Music\test\Pink Floyd\The Division Bell [Discovery Box]\01 - Cluster One.flac 
Tags:
ALBUM: The Division Bell
ARTIST: Pink Floyd
CATEGORY: musicbrainz
CDID: 7d0f930b
COMMENT: RK-CDID=0787
DATE: 1994
GENRE: Progressive Rock
REPLAYGAIN_ALBUM_GAIN: -4.30 dB
REPLAYGAIN_ALBUM_PEAK: 0.86880493
REPLAYGAIN_REFERENCE_LOUDNESS: 89.0 dB
REPLAYGAIN_TRACK_GAIN: -0.86 dB
REPLAYGAIN_TRACK_PEAK: 0.68704224
TITLE: Cluster One
TRACKNUMBER: 1
VENDOR: reference libFLAC 1.2.1 20070917 
=== end file 1 version 2 ===

Any ideas what could be wrong?

[MrSinatra]

well, hard to say. it shouldn't be doing that.

i typically look for things like itunes integration, comp tags, or disc tags when there is errant behavior like this, but all i can think of with your example above is maybe somehow the musicbrainz tags are causing the issue? try removing them and see if the issue goes away.

otherwise, this looks like a bug to me, unless the devs have killed the greatest hits logic. where do you navigate to see this in the webui? have you tried other ui's?