Bug 12875 – Missing genres

Bug 12875 - Missing genres

Summary:

Missing genres

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Scanner
Version:	7.4.0
Platform:	PC Windows Home Server

Importance:	-- normal (vote)
Target Milestone:	7.4.0
Assigned To:	Andy Grundman

URL:
Keywords:	Audio::Scan

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-07-15 11:47 UTC by Marius Ono Wingerei
Modified:	2009-10-05 14:28 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
An sample file that gets "No Genre" (9.96 MB, audio/x-m4a) 2009-07-15 11:47 UTC, Marius Ono Wingerei	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marius Ono Wingerei 2009-07-15 11:47:25 UTC

Created attachment 5473 [details]
An sample file that gets "No Genre"

I am using 7.4 27567 on Windows Home Server and it does not recognize my custom genres in m4a files. Please find attached an sample file (ripped in iTunes from cd). The genres should be "Hip-Hop/Rap" but now it shows up as "no genre". In my previous installation based on a old beta (26520) it show up with this genre.

Comment 1 Andy Grundman 2009-07-15 11:58:32 UTC

It was just an oversight in the tag mapping.  Fixed in change 27581.

Comment 2 Marius Ono Wingerei 2009-07-16 12:57:43 UTC

Works for me also now with the latest nightly - great support. Thanks!

Comment 3 James Richardson 2009-10-05 14:28:28 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.