2015-11-10, 14:18
My mistake, I've just checked Isengard and every level in MyMusicSongs is classed 'files'.
(2015-11-10, 14:18)Hitcher Wrote: My mistake, I've just checked Isengard and every level in MyMusicSongs is classed 'files'.
(2015-11-10, 16:11)jjd-uk Wrote:(2015-11-10, 16:04)DaveBlake Wrote: But if the source has already been scanned into the library then in file view you see album cover art for folders.
No need for that if you have embedded covers as they also show in Files view without the files being scanned into Library.
(2015-11-10, 16:17)DaveBlake Wrote:(2015-11-10, 16:11)jjd-uk Wrote:(2015-11-10, 16:04)DaveBlake Wrote: But if the source has already been scanned into the library then in file view you see album cover art for folders.
No need for that if you have embedded covers as they also show in Files view without the files being scanned into Library.
Yes embedded covers show for the selected song file without scanning to library. But also a selected folder in a list can show cover art, but it seems only when there is a library entry. I don't get the same behaviour for subfolders unless the library knows about them.
(2015-11-09, 19:48)DaveBlake Wrote: Well I certainly misunderstood you before!! That is providing by "file properties" you mean all data inherent in the file including tags.Definitely.
Quote:What you say about the mixed content of folders is certainly true. What I am less clear about is whether Isengard having CGUIViewStateWindowMusicSongs, other than being yet another window to code, caused similar skinning or content problems?I don't have an Isengard install available at the moment but I didn't have the same problem. But in Isengard and before, because of the clear distinction between MyMusicNav.xml and MyMusicSongs.xml it was "manageable" I guess. The removal of the latter is something I definitely applaud though.
Quote:I may still be misunderstanding you so please bear with me....
Does the first point in your list mean that once the user has added a folder as a music source you are OK with setting content to "songs" even though the music files themselves may be several subfolders down, and there could be other kinds of file in there too?
Is it that the way the fix is implemented even the top level window that lists the sources (and has an "add music..." item) gets labelled as having content of "songs" that is the problem?
Quote:Of course using the fact that the user has added a folder as a music source does not ensure it contains only music files.
So say we have a "files" content type. Would it be possible for a skin to adapt to what kind of file is currently selected and show the music tag data, or picture data or whatever data we may have available that is inherent to the file? Could it adapt the sort criteria available depending on the files it finds. Or would it all become a matter of lowest common denominator?
<value condition="ListItem.IsFolder">Show stuff you want a folder to display</value>
<value condition="!ListItem.IsFolder + !IsEmpty(ListItem.Artist)">show music / artist / song related data</value>
<value condition="!ListItem.IsFolder + StringCompare(ListItem.FileExtension,jpg)">show data like file data, dimensions or whatever</value>
<value condition="!ListItem.IsFolder>fallback to any set of generic file properties / data</value>
(2015-11-10, 22:40)Jeroen Wrote:Good(2015-11-09, 19:48)DaveBlake Wrote: Well I certainly misunderstood you before!! That is providing by "file properties" you mean all data inherent in the file including tags.Definitely.
Quote:It is unclear to me why setting the content type to songs is needed for the file properties to show in the music files node? Would it be possible to not set a content type or set any non-library node to a "files" content type? That way the behaviour would be more predictable for skinners. They could adjust the layout simple based on whether an entry is a folder or a file (and I guess also based on the file extension) and use variables to set the desired infolabels. I think that would cover most needs in that regard, but other skinners might have different opinions.
<visible>Window.IsVisible(MusicFiles) | Window.IsVisible(MusicPlaylist) | Container.Content(Songs) | Container.Content(Albums)</visible>
<visible>Window.IsVisible(MusicPlaylist) | Container.Content(Songs) | Container.Content(Albums)</visible>
<visible>Container.Content(files) | Window.IsVisible(MusicPlaylist) | Container.Content(Songs) | Container.Content(Albums)</visible>
(2015-11-23, 13:23)blutstein Wrote: As a user with a large database of musik (~1 TB) manually tagged with all information i need (mostly DJ mixsets), i would scream no to a simple filelist, and for a software calling itself "mediacenter" it would be a shame if tagging would be abandoned.
Imho get rid of the file view and use only tag, THIS would be contemporary.
(2015-11-23, 13:56)DaveBlake Wrote: Having such a large music collection, could you give some feedback on this thread http://forum.kodi.tv/showthread.php?tid=24843That's a post on WOL....
(2015-11-23, 13:56)DaveBlake Wrote: Do you use the music library (scan all that tag data)? Do you scrape artist or album data?As another heavy music users I have been watching these threads, but a difference is I do use the library mode. So I do all that scanning you are asking about to another TB+ of tunes..
(2015-11-23, 14:21)BatterPudding Wrote: As another heavy music users I have been watching these threads, but a difference is I do use the library mode. So I do all that scanning you are asking about to another TB+ of tunes..