2019-08-28, 16:21
1) I quite understand about doing db access on a separate thread to the GUI. You are right in that I didn't think about it in that context. I also know you're not keen on the GUI option. Yes it did seem at the time to be an easy way to tidy up some unexpected results that I got during testing but on reflection, that was probably more down to the way I had set the rules up initially rather than anything else. A GUI option seemed to be a quick solution to that, but better rules on what constitutes a set, coupled with decent tagging is a better option.
That is my preference too. Adding to RELEASETYPE would certainly allow Kodi to generate disc names if they are missing which would give users less messing around with tags and is a definitive method for a user to say to Kodi "Treat this album as a boxed set", perhaps falling back to the rules that Kodi follows at the moment if that tag doesn't contain 'boxset'. Not everyone will be aware that they need to update their tags initially and the ability for Kodi to generate some sets automatically without that tag might stimulate more interest in sets as a whole.
It is already possible to override Kodi's rules by either exporting the library as a single file and editing the required album(s) and then importing it, or by creating an album.nfo file, turning on "prefer online info" (which I have to say I find a bit misleading as a local .nfo file won't override anything in the tags without that on
) and then rescanning the album.
Necessary info is
The fact that we start with an 'album' is because that is the container for the songs. Splitting that container into more manageable chunks (whether that's because it was physically like that originally, or just because it makes it easier to manage a large amount of tracks in that container) just makes more sense to me.
@jjd-uk TPOS contains the disc number and total discs for a multi-disc album. It's impossible to determine from that alone if the album is indeed a box-set or just a multi-disc compilation or an anthology.
Quote:At the moment my preference for "Boxed set" to be a fact about music files. That is to derive it from tags using a clear methodology but allowing for what Picard produces to be a nearish miss that is easy to edit, and get the user to set those tags according to the result they want.
That is my preference too. Adding to RELEASETYPE would certainly allow Kodi to generate disc names if they are missing which would give users less messing around with tags and is a definitive method for a user to say to Kodi "Treat this album as a boxed set", perhaps falling back to the rules that Kodi follows at the moment if that tag doesn't contain 'boxset'. Not everyone will be aware that they need to update their tags initially and the ability for Kodi to generate some sets automatically without that tag might stimulate more interest in sets as a whole.
It is already possible to override Kodi's rules by either exporting the library as a single file and editing the required album(s) and then importing it, or by creating an album.nfo file, turning on "prefer online info" (which I have to say I find a bit misleading as a local .nfo file won't override anything in the tags without that on
) and then rescanning the album.Necessary info is
xml:<boxset>true</boxset>
<disctitles>CD 1 / CD 2 / CD 3 / CD 4 / </disctitles>
Quote:I think what is needed is some clear vision if this feature is about organising songs based on music file tagging, or about selecting certain albums.For me, it's about the songs ultimately. I mean, that's what I want to listen to, but getting to some of them currently is a pain in the arse. A tree full of secrets is 18 discs and kodi lists the entire thing normally. Thats a lot of stuff to wade through if you're looking for a specific track. Much easier when MB has split it into 10 volumes (vol 10 is a data cd) of two discs each. It's the same with other stuff I have. I might want to just listen to disc 3 of something but then I have to look through a list of stuff I don't want, to find bit I do. Also, aesthetically it looks better (or I think it does) and nearer to what you would once have had in your hand.
The fact that we start with an 'album' is because that is the container for the songs. Splitting that container into more manageable chunks (whether that's because it was physically like that originally, or just because it makes it easier to manage a large amount of tracks in that container) just makes more sense to me.
@jjd-uk TPOS contains the disc number and total discs for a multi-disc album. It's impossible to determine from that alone if the album is indeed a box-set or just a multi-disc compilation or an anthology.
There is an extra level in play for a boxset, which isn't there for an ordinary album. Normally, an album just contains tracks and there is no intermediary bit to navigate but in the case of a boxset, the 'album' contains discs and the disc title becomes the link between the top container (album) and the tracks. So yes, an album needs to know which discs belong to it and songs need to know which disc they belong to. Your comments are indeed useful Dave. I'd probably not have added the boxset tag without them so keep them coming. In fact, I'd probably never have got this far if I'd just set off on my own and various people hadn't chipped in with comments and advice etc.
