Track Browser refilters incorrectly at times

[DaledeSilva]

Hello,

EDIT: THIS POST IS INCORRECT, READ THE NEXT 'REVISED' POST

if you create a new node via scripting, the trackbrowser doesn't work properly with it. It still displays a list of artists and genres.. but they are not properly relevant to the nodes contents...
It also often filters it's genre column when you click on a genre.


I would REALLY like this fixed because I'm really over using the tree now that the trackbrowser is here.
I've made a script that hides the library node and create 3 different root notes for my 3 different database sets - and relies on the trackbrowser for browsing.
however, while this works great (and is actually alot quicker than using filters)... it's unusable because the trackbrowser doesn't work with it.

Dale.

[DaledeSilva]

okay.. this above post is incorrect.

for some reason, the track browser wasn't working with those nodes but now it is (yay)...

HOWEVER, the "re-filtering" bug is still present and is not only an issue for script created nodes.. it's an issue throughout MM.

steps to reproduce:


- open the trackbrowser
- click on an artist and an album (or anything, as long as the tracklist filters)
- double click on a file in the tracklist to queue it or play it.
- if you queue it, then in the now playing panel, double click it to play
- NOTE HOW THE TRACKBROWSER NOW UPDATES TO ONLY SHOW WHAT IS VISIBLE IN THE TRACKLIST. this is incorrect behaviour.

note:
- it only happens if you double click a track in the tracklist before playing it, it doesn't simply happen whenever you start a track playing

[gab]

I have the same issue. The Browser has been buggy throughout the development cycle but the good news is that it has improved from the first Alpha.