Skip to main content


Please be aware that much of the software linked to or mentioned on this forum is niche and therefore infrequently downloaded. Lots of anti-virus scanners and so-called malware detectors like to flag infrequently downloaded software as bad until it is either downloaded enough times, or its developer actually bothers with getting each individual release allow listed by every single AV vendor. You can do many people a great favor when encountering such a "problem" example by submitting them to your AV vendor for examination. For almost everything on this forum, it is a false positive.
Topic: Library Tree (Read 40611 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Library Tree

Reply #75
^ That report is for v2.1.2. The issue should be fixed in the current version (v2.1.3).

Re: Library Tree

Reply #76
Thanks for this very nice script!
It works really well, however I've noticed that there seems to be an issue with sorting in "View by Folder-Structure" (using v2.1.3):
  • if I drag-and-drop an album with more than 10 tracks to a playlist using "View by Album" the resulting sort-order
     with respect to the track-numbers is fine, e.g.         1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 ...

  • if I do the same thing with "View by Folder-Structure", i get:  20, 10, 11, 21, 01, 02, 22, 12, ....

Re: Library Tree

Reply #78


I suspect its because the track number isn't padded in the filename.
i.e. they're 1, 2, 3, 10, 11 etc as opposed to 01, 02, 03, 10, 11 etc
I could see the issue. DUI album list behaves the same way.

The order is determined by OrderByRelativePath() which I have no control over.

%tracknumber% that's used in view by album automatically pads.

Library Tree also does a display sort for displayed text strings which has full numeric handling and so all displays in the actual tree correctly. But using that string sort on the whole library instead of OrderByRelativePath() doubles the initialisation time and likely wouldn't be compatible with the condensed style that OrderByRelativePath() produces.

I always pad track numbers in filenames.


Thanks. It looks nice!

Re: Library Tree

Reply #80
Well I reproduced it with 1.3.1 beta...

Re: Library Tree

Reply #81
@WilB, osenboz's problem was the following: 10, 11 ... 20, 21 was sorted as 10, 20, 11, 21 ..., which was caused by a bug in SMP v1.2.3 that resulted in the first character of path to be ignored during sort.
`OrderByRelativePath` (bugs aside) uses the same algorithm as Windows file explorer (hence the usual 1, 10, 11... problem).

[EDIT]: Judging by the bug report, osenboz actually has a proper padding for track numbers, so they won't be affected by Windows sorting problem either =)

Re: Library Tree

Reply #82
@TheQwertiest @WilB
Thanks a lot for your updates! (since my file-namings are properly padded, updating to SpiderMonkey Panel v1.3.1 solved the problem!)

Re: Library Tree

Reply #83
Thank you for this component, it's very fast! I love the now playing filter feature.

Feature idea/request: allow specifying multiple tags at the same branch level that will create multiple entries. This is a feature of Facets. For example the first tree level could be %<artist>%OR%<album artist>%, where OR is some divider. Then under the The Beatles node, for example, you will see albums where album artist = The Beatles, and also any tracks where artist=The Beatles from other albums (without duplicate entries where album artist == artist == The Beatles)

Re: Library Tree

Reply #84
Hi @WilB , testing Library Tree right now :)
So far so good, but I have noticed a glitch maybe :
In Panel Properties, if I change _CUSTOM COLOURS/FONTS : USE from False to True, all results disappear, regardless of what I put in _CUSTOM COLOURS/FONTS : EMPTY = DEFAULT (e.g. 255-0-0). Playing a new track doesn't solve the issue.

My goal would be to keep the same font, but change its color and make it bold instead of regular. Is that possible ?
Also, I would like to know if I can rename the "All Music" to something else. Thanks !

Re: Library Tree

Reply #85
It should work. I tested & it seemed fine.

All the custom handling has changed in the next version anyway & so it will be much easier to change.

Options > root node > view name enables use of the 'view name' which is configurable. Again all this will be much easier in the next version.

Re: Library Tree

Reply #87
No reply yet, but here's a new question about Library Tree. This code doesn't seem to work as a custom filter :

Code: [Select]
$nowplaying{$meta(comment,0)} HAS artist

@WilB , could you tell me why it doesn't work?
The goal would be to find other tracks where the artist would be mentioned in the %comment% field of the current playing track.
That's because some of my tracks have a %comment% field that says : "This track has a small sample taken from this other track : ARTIST / TITLE".
In that case I'd like Library Tree to help me fetch that other track.

Re: Library Tree

Reply #88
Code: [Select]
comment HAS $nowplaying{$meta(artist,0)}

I don't have a definitive eta. All release scripts have had a significant upgrade. Ini file has gone from bio plus all scripts now have proper settings dialog. Additionally, there's a bunch of new features mostly eluded to here or there. Code changes are mostly done now. Code clean up and testing needed tho...

SimplePortal 1.0.0 RC1 © 2008-2021