Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[whoareyou]

Similar to 31.0.24 Changed: When matching, Spotlight will ignore any extra user data in movie or tv show titles enclosed in brackets.  For example, "Avatar [3D]" will match just Avatar.

Could same be implemented for album related lookups?  For example;When I have several different versions of the same album, I like to name them as follows: 
AlbumA
AlbumA - remaster
AlbumA SACD 
AlbumA HdTracks. 

Issue is that when naming in this fashion, cover art lookup will fail.   

So perhaps the bracket solution could be applied to album titles?

AlbumA
AlbumA [remaster]
AlbumA [SACD] 
AlbumA [HdTracks]

Thanks

[whoareyou]

Bumping this change request related to how album lookups works ....

When you have multiple releases of the same album, but you want to identify the different releases in your view, the lookup will fail if the album name has information uniquely identifying the release. 

In order for lookup to succeed, you need to rename the album (remove unique info), complete the album art download, and then rename the album, to once again include the unique info, after lookup has completed.

 

[TheShoe]

I typically use "(" and ")" in the name, often because I have multiple versions of albums (Multichannel, Stereo, various bitrates and formats, e.g. LPCM, DTSMA, TrueHD, etc.)

Cover art lookup fails.  it would be nice if we could at least edit the name in the cover-art "Get from Internet" search....

I wonder if I could just manipulate the display name to just dynamically display that info from existing tags, in which case the base "Name" would always be the proper album name, but displayed with an expression, e.g. Album Name + "(" + AudioCodec + ", " + Channels, etc....

[Hendrik]

I would recommend to keep any data thats not actually part of the name itself in a separate field, and then tailor your views to include the extra field as needed. That way all lookup functionality works right out of the box and there is no need to guess at the album name anywhere its needed.
You can easily setup a "DisplayName" fiel or "Formatted Album Name" field or whichever case in particular based on an expression that takes the name and adds any tags to it you would like to have shown there, and then just redirect the views to that custom field, rather then Name.

[TheShoe]

Yup - this worked.  Created a new custom field:

[Album] /[[Sample Rate]//[Bit Depth]/, [Channels] Channel/]

...worked perfectly.  Modified the view to group under this new field as the "Album" title, replacing the stock "Album" field.

Cover art lookup works as expected.

What is the cover art source by the way?

--

Been so long since I've messed with custom library fields but incredibly powerful.

[BryanC]

What is the cover art source by the way?

JRiver's in-house database (not sure if YADB or yet another YADB).

[whoareyou]

Thanks for all the replies. 

Sounds like this request wouldn't have wide appeal and can be handled in other ways.

I did think about customizing, but because I also use the the same files / tags with a couple of other applications, that really doesn't work for me.  Within JRiver of course it works, but I already have several customizations and I don't want to add yet one more field to my mix, and then rework all of my views. 

I'll just keep doing what I'm doing.

[TheShoe]

JRiver's in-house database (not sure if YADB or yet another YADB).

Thanks.  It's missing some album cover art for more recent releases where the album art has changed from the original, e.g. Pink Floyd's Animals (2018 Remix), which I believe is the official album title.  But at least I can grab that and just add it manually if needed.

Generally though, spot on