Messages

1

Bug Reports / Re: Dropdown lists in Playlist Mixer criteria window are not working(ver.3.3.7165 P)

« on: September 01, 2019, 01:37:34 PM »

Not exactly. There is no dropdown menu shown when I click on the criteria field (left hand side field - here:genre) nor when I click on the right-hand field. Only way to cycle through the choices is to click the field, and then use keyboard arrows. Meanwhile, the field in the middle is behaving OK. I have tried this on two different computers, from the same portable installation (I always just extract all the files in the folder of the previous version, I guess it is the proper way of upgrading the portable MB - it worked every time before for me). I'll try with the fresh portable MB, and report the results.

2

Bug Reports / Re: Dropdown lists in Playlist Mixer criteria window are not working(ver.3.3.7165 P)

« on: September 01, 2019, 11:15:07 AM »

Sorry for confusion. Here is a screenshot to illustrate. Dropdowns in red are not working, green is OK.
https://we.tl/t-CdNBYhDrNj

3

Bug Reports / Dropdown lists in Playlist Mixer criteria window are not working(ver.3.3.7165 P)

« on: September 01, 2019, 10:37:00 AM »

Just as it is stated in the subject: There are no dropdown lists when clicked on field for song property, as well as for the property value field in the Playlist Mixer criteria window. This is not the case for the criteria field, it works as it should. MusicBee version 3.3.7165 P

4

Questions / Re: Order by "play count per month", possible?

« on: November 26, 2014, 05:08:16 PM »

My idea was to have one global variable, a predefined value [average playcount] (something like [playing track] that you can choose as value for Album field). This could be used as second criteria, the one that could come after "Last Played not in last x days".
This way you could ban from playing those tracks that are about to be played more than average.

It wouldn't stop playing tracks with above average playcount to be EVER played in that playlist, because [average playcount] isn't constant value, and at some point in time, tracks that couldn't pass this criteria before, should pass it eventually. This way you could force all the tracks to be played similar number of times.

[average playcount] has to be autocalculated by MusicBee, at startup, or after every played track, or on user demand (if it's heavy task for cpu to be taken out that often).
This is something that shouldn't be hard to implement, and could improve auto playlists and mixer playlists.

Advanced, predefined value [playlist playcount average] could be calculated before populating playlist, and should mean the average for all the tracks that match the playlist criteria. This one, I guess, could be hard for implementation, but again, just an idea.