3.0.3.1175: Filter/SQL on Album Comment, Strange Results

[Mizery_Made]

I've recently begun filling the Album Comment section of Albums with "Tags" such as "|Own|" to signify albums I physically own (to filter out Internet Only albums and such) as well as other things like "|Scratch|" for albums I know have a few scratches, though it can contain a combination of "Tags" such as "|Own|Edit|" to signify owning the edited version of an album.

The problem begins when trying to set up a filter with this field. I set up a filter on "Album Comment Contains |Own|". When applying this filter, it works... somewhat.

The Album node appears to function as expected, filtering out albums which do not match the criteria. However, take a look at the Artist, Album Artist or Artist & Album Artist nodes and you find the problem. Several Artists/Nodes that shouldn't be there, ARE there. Not just one or two, I mean SEVERAL. The nodes will open up and show albums within it, however the albums nodes are empty for those that don't match the criteria, artists that shouldn't be there (as in, none of there albums meet the criteria) also show an empty main window but may contain empty albums underneath it.

The strange behavoir of the Album Comment field doesn't stop there, within MediaMonkey at least. Plugging in an SQL query into scripts like SQLViewer or MyCustomNodesthat should filter on the Album Comment part of the database produces strange results as well, those not exactly the same. In the case of MyCustomNodes, instead of showing empty nodes, it shows albums that shouldn't be there.

HOWEVER, taking the same SQL queries entered into either of these scripts and applying them in an outside SQLite viewer (SQLite Database Browser) produces the expected result. Is there some kind of failure in the way MediaMonkey is calling the information from this field or something?

Seems strange that MediaMonkey itself would have trouble filtering on this field (when it comes to the Artists Nodes at least) as well as two different scripts that allow SQL queries.

Maybe the two have nothing to do with each other. Anyway, if you require more information like the queries used, need my Database for your own testing purposes, or any other information, just let me know.

EDIT: Furthermore, setting up an Auto-Playlist with the Criteria of "Album Comment Contains |Own|" will produce almost expected results, however it will contain some results that don't have an album and thus don't have an Album Comment.

Setting up a filter with "Playlist Is 'Playlist with previously mentioned criteria'" will produce further broken results. It will show the nodes that were empty with the filter with the direct criteria, except with this one, they aren't empty.

[Ludek]

Yes I see. You are right, filtering by Album.Comment is messed up when condition "contains" is used. Condition "equals" works fine. It is reproducible and we are looking into it. Thank you.

[Teknojnky]

Mizery_Made, you might try using an un-used classification node instead of putting them in comments.

By using a classification node, you automatically get built-in nodes, multi-item support, better auto-playlist/filter support.

Oh, and you can also use 'Send to > classification' which I also find very convenient.

[Mizery_Made]

Yeah, Teknojnky, the troubles with the Album Comment got me to thinking of using one of the other fields, even maybe an open Custom (I think I might have one left). Besides that, another advantage it would have would be it would then be saved to the tags and not be easily lost if I go to renaming Albums and whatnot.

However, at least my attempt to use the Album Comment field brought out a bug. Still haven't decided if I'll stick with that or move in another direction (Classification, Custom, etc.)

[PetrCBR]

This issue will be fixed in next release.