Fixed it...

my website has had some issues today...

I just uploaded a new version of playlist tree that implements an optional playlist tree browser panel. If the panel is not active, the playlist tree operates as before, but if you have the playlist tree browser panel active, the selected node will send its contents to the browser panel.

To get a similar layout to how my preview screen shot: (from the readme.txt)

--- How to get Playlist Tree & Browser to appear above playlist ---
(i.e. to look like this: http://www.bowron.us/foobar/prev.png)

In under the columns ui preferences, select the other tab, check the box marked [x] List all toolbars in the toolbars selection.

After saving that, right click on your toolbar and select Playlist Tree under Panels, you can then move the panel around to where you want it. You add the playlist tree browser in the same way. If the panels are too tall or too short you can adjust the height of the panels in the Playlist Tree preferences under Browser Min Height. You may have to restart foobar2000 for the new settings to adjust.

Thanks you! I'll test it next year

Happy new year.

I am not sure the panels resize to the right values. Either yours arent using the same measurements as the tabbed panel stack, or either playlist tree or panel stack recieves the wrong value for resizing, because they do not resize correctly. It seems the playlist tree is always larger than the tabbed panel stack at the same given value.

EDIT: oh and also, it would be good to be able to have double clicking a track in the browser window to do something.

I just uploaded a new version that implements multi columns in the browser panel. From the readme.txt:

browser columns mode

Fields are seperated by '|' in the string. For example to get a 3 column display with artist, title and album, set the browser format to "%artist%|%title%|%album%" and the browser headers to "Artist|Title|Album".

The way I implement my minimum height is a little different than the way foo_uie_tabs does it, so the actual height is different if the values are the same.

Hi cwbowron

Thanx for adding 'expand/collapse' to the double click options

Had a couple of requests:

1) The ability to change the middle mouse buttons function from 'send to new playlist' to whatever (in my case 'send to playlist').

2) Make the 'Refresh Query' checkbox option apply to all ways of getting the query to the playlist. Middle clicking and Right click context menus (send to, add to, new) not just double clicking.

3) An option similar to the album list panels 'process keyboard shorcuts'

And again thanx for the plugin, happy new year.

Hello cwbowron ,

%systemdate% doesn't seem to work for me . i tries writing in the query : '$sub(%systemdate%,%added%) LESS 8900' or even tried using '$substr(%systemdate%,5,6)' for months refference but nothing worked.

i am using windows xp sp2 ,foobar2k 8.3 and lastest playlist tree plugin.

thank you and Happy new year.

Hi cwbowron!
Today I started toying with the Playlist Tree; took some time getting started but must say that I'm _very_ impressed!

There is one major drawback for me: startup time
using Albumlist

mem. footprint: 15.7 MB

using Playlist tree

mem. footprint 24.4MB

It really takes too long for foobar to show up.. This is using only 2 queries, with 40GB music in database (+- 8000 files)

Can something be done to speed up loading time?

Another 'problem' is more a feature request. Possibility to change colours for the Tree browser. ATM it just looks too ugly in my configuration

Sorry I didn't read the whole thread, I might be repeating known requests..
Anyway, thanks a lot!
Cheers
eph

edit: BTW, that first query is the same as used in my Albumlist config.

i guess there can't be much done (maybe some sort of background loading but i'm not sure whether foobar supports it).

there can be difference between normal / epg query format ... i haven't tested it though

i have manual query refresh setting on ...

The latest version uses the same color for the browser as you selected for the playlist tree... I am considering adding seperate color preferences for the browser....

There is an option called "Manual Query Refresh" if this is checked, queries will not be populated when you start foobar2000, only when you manually refresh them, so your foobar2k will load more quickly, but when you need to refresh the query it will take the time... It looks like it might be refreshing each query twice in your configuration which I will look into...

EDIT: I just uploaded a new version that should eliminate the double query population.

Fixed it... the problem was that I hadn't forced the day and month to two digits, so the string was returning 200512 instead of 20050102.

Yes but that would disable dynamic playlists like '%artist% IS $playing(%artist%)' wich is IMO one of the main reasons to use the Playlist Tree plugin.. maybe an option per query? I was just wondering why there is this big speed difference with the Albumlist plugin...

edit: Wow thanks already for your edit/upload
edit2: INFO (CORE) : startup time: 6550 ms
..but I see this '%artist% IS $playing(%artist%)' doesn't update on song change as I envisaged it. oh well

While we're at it..


Yea I didn't notice because playlist tree changes are immediate, while the browser window needs a restart. Maybe you are already aware..



Maybe a better idea would be (an option to) to auto-refresh queries containing $playing(%tag%)? Wouldn't interfere with normal/manual query refreshes.

Big Thanks!
eph

The browser is a great addition to this plugin. However, when I have it enabled I get an error when closing foobar:



Thanks!

Rob

I still seem to be having trouble with %systemdate%. This query yields 0 results:



This code, however, works perfectly:



Assuming my system clock is set correctly (and it is), shouldn't $substr(%systemdate%,5,6) be 01? Can someone let me know what I'm doing wrong? Thanks.

Take a look at your console output. the latest version should show the string before and after the systemdate replacement. There should be a line that says:

system date query before: bla bla bla %systemdate% blah

system date query after: bla bla bla 20050102 blah

see if that looks right

Here is what the console shows:



And yet the query still gives nothing...

try adding double or single quoates around it so its $substr("%systemdate%",5,6) or $substr('%systemdate%',5,6)

no, neither of those work...

I just uploaded a new version that implements minimum height in a way that should be compatible with foo_uie_tabs. I believe the scale will be the same now.

Believe I may have a bug on my hands...

I like to have a query for music I haven't sorted yet, i.e., files in a "_download" directory:



The display format I use is:



I'm trying to have albums listed first, followed by the untagged files listed by filename. This displays correctly on the playlist tree, but when I select one of the untagged files in the playlist tree, the wrong file is selected in the playlist tree browser:



What might the cause be?

Another thing that would be great (not sure if this has been suggested) is a customizable playlist tree browser based on which query you're looking at - for instance, if you have a query that's set up specifically to display only singles, you won't need an "Album" column.

Try getting the latest version and see if the problem still shows up, I noticed a similar problem last night and fixed it...

I asked about sorting on a files last modified in explorer but got no response on this. I would like to show files in the order i have downloaded them. Is this doable?

I dont think there is any way to do this now. The only way I could see it working is if I added a special tag for the tree that inserts the date, but I'd rather not add more fake tags unless it pertains to a feature of the playlist tree. ($sum and $avg have meaning in the tree but nowhere else, but a tag like %modified_date% would be something that should be in the core formatting not an add on for one particular application)

would it be possible to configure double clicking a track in the browser list to do something (like play, or add to playlist, or both?)

I might make it configurable eventually, but for now double clicking does the following actions (from readme.txt)

right click:context menu

left click: Sets the focus of the playlist to the current item in the browser if it is in the playlist

double click: Send active list to playlist and play selected item

control dbl click: Add selected item to playlist

shift dbl click: Add active list to playlist

Hi,

I was away for just a couple of weeks and I found great additions to this plugin... The browser is the main one and I have to say it's a great idea. So you can browse your music without messing up your active playlist...

Making a new browser window implies a huge amount of work, I guess - fonts, columns, background etc. have to be customizable, drag and drop is needed, etc. I'm sure cwbowron has already planned all these features and probably musicmusic's columns ui is a great help for implementing them. However, I found out an issue which is probably not very easy to solve...

Here it is: if you browse your files in the main playlist window, other plugins like Track info or Album art could visualize informations about the selected track with the "follow cursor" feature. However, if you browse your files in a specific browsing window, Track info and Album art don't respond unless you browse files which are already present in the active playlist.

I know this behaviour does not depend entirely on Playlist tree, still it raises some questions about the way the plugins communicate with each other. It seems that plugins can only react to events that occur in the main playlist area and not in other plugins... At which level does this limitation exist? In the core? In Columns UI? Is some kind of new standard needed?
Maybe this topic has to be raised in a new thread...

Just a little request regarding the core of Playlist tree now...

When I expand/collapse a branch in the tree, everything is fine as long as the operation does not make appear/disappear scrollbars. If this happens, the background flickers in an annoying way. This is more obvious if the Playlist tree background is set to a dark color.
As far as I can understand, when I expand/collapse a branch in a way that a scrollbar has to appear/disappear, first the background turns gray (sidebar's original background), then the scrollbar appears, then the background turns blue (my Playlist tree background custom color), then the new tree appears.
In Albumlist the process is smoother: the background doesn't seem to turn gray at all.

Thanks for the great work and happy new year

Yes, making a really nice browser would take a lot of work, and unfortunately I probably don't have the time necessary to do it... I would like to make it customizable with all the bells and whistles of column ui, but it is not likely..

If someone else would like to make a coolor browser, my code is available and I welcome it...

I think in the long run the best possibility would be to create a service that every plugin would be able to utilize and that way if someone wanted to create a better one it would be a matter if overriding a base class... If a browser service were added then any plugin that wanted to display a list of files could use the same browser....



I just uploaded a new version that I believe will solve the flicker issue...



Thank you, and happy new year to you as well.

Hi cwbowron, about the double query population bug: ATM I have 2 queries that use the $playing() command. On startup I get the following output;

..is this normal behaviour? I do have a total of 6 queries.

Would it be possible to add a shortcut, i.e. F5, to refresh the current node? Would mean a great deal to me

Thanks!
eph

Just discovered another quirk:
With the album 300% Dynamite!, the playlist tree displays 300[SYNTAX ERROR IN FORMATTING STRING]... but I understand changing this probably has some less pleasant consequences

Yep, that is normal behaviour. Only 6 queries are populated. The reason that "Nothing playing" prints out a total of 4 times is that each query population gets the format string twice in the current implementation, but this should should have very little impact on the speed of the population.

I just uploaded a new version that offers a menu option for populating the current selection under Components->Playlist Tree->Refresh Selected which you can add as a global hotkey for whatever key you would like.

As for the 300% Dynamite quirk, Any folder name that has a $ or % in it will be run though the title formatting process... if this is a static folder you are making you can rename it with single quotes...

Hi,

It's much better now, the gray background does not come up any more.

There are still some minor cosmetic issues though. When you expand/collapse a branch which makes a scrollbar appear/disappear, the window border flickers for a while... The same thing happens if you resize the Playlist tree window. Albumlist panel doesn't seem to have this problem when resizing the window, expanding branches, etc.

Last little request: the gray background appears for a while when you refresh the tree. If the tree is very complex, the empty gray background stays for two-three seconds. Can you just leave the tree on?

Thanks again

I think I got the refresh tree issue solved... the tree should stay put while the queries are being refreshed, hopefully no more empy gray background...

The border flicker I'm not sure about... Being that its a rather minor issue, I'm probably not going to worry too much about it...

Hi cwbowron,

You've done a great job. I've been two weeks away and now I see that you've implemented a lot of new features, including a playlist browser, your plugin rocks dude

I'm playing with some of the new features, mostly the playlist browser. Now some suggestions for that new feature :

- Maybe adding a tab for the playlist tree browser inside the playlist tree preferences will be more comfortable. You'll also get more space for more options

- Possibility to add options for double-click in the browser i.e. add to playlist, send to playlist, send to new playlist, etc... we have the shortcuts (control dbl click, etc...) but we all love to customize stuff, do we? [Edit: Sorry, I've just seen that someone has already requested it]

- Possibility to disable autoresize columns. I like to have my columns size locked.

- Disable 'Sets the focus of the playlist to the current item in the browser if it is in the playlist'. I will like only to select it.

About other features:

- Dequeue: Great, thanks you very much, that's exactly what I was looking for Just one thing, I've noticed that if you play one track, but you don't play it completely, the track remains in the playlist (which is normal, since you didn't played it completely) but after that if you select it again (in the active playlist) it will then disappear. It's this intended?

- $playing():

Is there a way to implement something that gets $playing() info into a query name? I.e. Feels like [%title% IS $playing(%title%)]

Possibility to auto-refresh individual queries could be great for this type of function. For ex. on track change.

- Playlist tree search: Possibility to remove 'cancel' button. It takes to much height and I don't know if it's really useful in the toolbar usage (in the panel it is because it closes the find window, but in the toolbar it doesn't close anything).

what do you mean exactly? for example i have query like %_directoryname% IS $playing(%_directoryname%) and it works like a charm, though i've requested features that would allow using that in query's name etc. atm there are some problems with parsing so i can't do all that i would like to do.

as for automatic refresh on track change for such queries - that has been requested by me too (in a more general way)

You're right, it's not a major issue, although it is more noticeble with a dark background... I hope this could go in your todo list anyway, even if with a low priority



I second this... Also, I think the toolbar should be as simple as possible, with just one button. The kind of search selected could go in the preferences, maybe in a search tab. Otherwise, if you want to keep two buttons in the toolbar, maybe you could make an option in the preferences to set your default search... So that, if you hit enter after the keyword, you'll start your preferred search.

I also noticed that if I search for a popular artist with the All button, the search takes quite a lot. This is mainly due to the fact that the search is done in the whole tree, which in my case replicates the database 5 or 6 times... If it's too much work to make the All button search the database instead of the tree, a workaround could be that you could set in the preferences in which node the All search has to operate... So you can set it to search just in one of your general views...

Thank you very much for solving the gray background issue and all my other requests!!!

I mean, I would like to create a static folder which will contain dynamic folders based on now playing track, and I would like that folder to be called 'Feels like "song title now playing"' If i.e. the song "Digital bath" is playing the folder should display 'Feels like "Digital Bath"'

I just uploaded a new version that should allow you to use $playing() in the title of a folder.

ok then, that was requested - titleformatting in folders / names. that's exactly what i want to do

edit: oi, cwbowron, man i love you

Thanks!

Hi cwbowron,
Thanks for all your magic!


Thanks I noticed that the shortcut doesn't update the browser window though..


Another vote


Nope it's in a query (full database).. what about only replacing a list of known commands, as for the tags, maybe only replace if the % sign is not followed by space/EOL?


I wanted to comment on this before, because it doesn't only happen when skipping tracks, but I couldn't find an exact way to describe it. Try selecting the track after the one playing (also with shuffle on), now select the playing track. One of the tracks disappears. This is also repeatable after the playing track is already gone..

It happens here too

I just uploaded a new version that fixes this....




Well, don't want to only replace on known commands in case the list of commands changes... but here's my suggestion: wrap your %album% tag in the query format with a $replace(%album%,'%',Percent) or $replace(%album%,'%', $char(39)'%'$char(39))... it should work as a work around to the problem..



I'm doing a pretty half-assed implementation of the dequeue stuff, i think there is a better way to do it, which i will look into...

cwbowron,

Could it be possible to disable (or make an option) to not send to the browser the node content when you click (single click) on the + (expand) to expand/collapse a node? It slow down the expand/collapse function and if I want to really browse the content of the node I just have to single-click on the node itself (not the +)

Thanks.

BW: Last track on the playlist with dequeue function on isn't removed from the playlist.

I've just read that musicmusic is working on a new column UI build that will be implement the playlist window as a panel, I don't know if you could use it as a base for the playlist tree browser
http://www.hydrogenaudio.org/forums/index....ndpost&p=263335

I just uploaded a new version that uses a different implementation for dequeue that should work better...

When I single click to expand/collapse a node it doesnt automatically send the content to the browser, only when i actually select the label... If my selected node is a child of the node I am collapsing then I do see the parent node getting selected when the child is no longer visible, but just randomly expanding/collapsing another node I do not have the same problem.

I just uploaded a new version that you can disable the resizing... the sizes are not saved between instances of the program though, so you may have to arrange them to your liking when you startup foobar2k or the browser.

I just uploaded a new version that implements auto refreshing on tracks that use $playing()

to turn it on select Components->playlist tree->settings->auto refresh $playing

There might be some issues if auto-refresh is on and you delete a query node that is supposed to get updated, but I think I resolved the issue...

Your mother ever told you that you rock?
Thanks!