Problem with Genres nodes (when blank Genre) [#6753]

[windcrest77]

The Genres node lists all the Genres in my database. However I just noticed that several hundred of my tracks had a single space character as the Genre on the media file (from a different program). But these tracks did not show up under the "Unknown" genre node. In fact they did not show up in any Genre category at all, nor was there a Genre node of "Blank". I think this is a bug with the query that is looking at Genre, it should strip all the leading and trailing spaces in Genre, then maybe a Genre of a single blank will show up under "Unknown", like it should. A Genre of all spaces should be considered same as "Unknown".

[Lowlander]

I disagree, if there is a single space or any amount of spaces it should not show under unknown as this would give the false impression that these tracks have no value for genre. Instead they should show under a genre node equaling the amount of spaces the genre field has. This would allow you to see which tracks have incorrect values and modify them accordingly.

What happens when you do right click Find more from same Genre on one of these tracks?

[windcrest77]

I disagree, if there is a single space or any amount of spaces it should not show under unknown as this would give the false impression that these tracks have no value for genre. Instead they should show under a genre node equaling the amount of spaces the genre field has. This would allow you to see which tracks have incorrect values and modify them accordingly.

What happens when you do right click Find more from same Genre on one of these tracks?

Yes that is better, So Unknown basically means "NULL". Or maybe generate a Genre node that says "All spaces" or "Other weird characters" in case someone put binary (non-printable) data in the Genre.

Oops I already set these tracks to a Genre, but maybe I can create another test case. I knew I had these tracks in my library but MM hid them from me because I frequently use Unknown to find things to work on. So I did a search on the artist and there they were but the Genre was a single space character, so they would up being absent in the genre tree because no parent node was generated for them.

[Lowlander]

So I did a search on the artist and there they were but the Genre was a single space character, so they would up being absent in the genre tree because no parent node was generated for them.

That's why I was interested to know what MediaMonkey would do with Find more from same Genre. It seems there might be a bug in here, but I want to figure out what exactly is wrong here.

[windcrest77]

So I did a search on the artist and there they were but the Genre was a single space character, so they would up being absent in the genre tree because no parent node was generated for them.

That's why I was interested to know what MediaMonkey would do with Find more from same Genre. It seems there might be a bug in here, but I want to figure out what exactly is wrong here.

OK I found more test data and lots of it.

I listed my whole library (+75,000 tracks) then sorted the grid by Genre. The first 2001 tracks have a Genre that consists of space (or spaces) (again acquired from the studio off our old computer). None of these tracks show up under the Unknown node of the Genres tree (or any other Genre). Also if I right click and do "Find more of same" on these tracks there is no Genre context menu provided to even do the test you are asking for. Apparently it only shows a "Find more of same Genre" context menu if there is indeed a Genre of non-spaces or non-NULL there.

So the logical bug is that MM is not recognizing non-NULL but spaced out columns as being valid values, (it could be happening in other columns besides Genre too). Glad to help make MM better! The way to reproduce it is to use some other tag editor to set Genre to a Space. (Or I can upload you a test file somewhere, but you should be able to create a test case easily enough with a tag editor that allows you to enter a Space in Genre)

[Lowlander]

Added to the Bug Tracker: http://www.ventismedia.com/mantis/view.php?id=6753