Some of us listen to classical music and maintain extensive collections of it. Unfortunately, proper classical music sorting requires different metadata fields than pop music. For example, the composer field is not very important with pop music, but is a big requirement with classical music.
Currently, Emby supports a single content type for music, which is tailored for pop music. It has views to list Artists, Album artists, Albums, Songs and Genre. I propose to create a second content type dedicated to classical music. This would be a very coherent move since there already are distinct content types for movies, series, concerts or home movies, even if they all deal with video files.
The views of this new content type would better fit classical music: for example, we would be able to list music by composer or by conductor, but not by song as this does not mean anything in classical music.
Furthermore, audio metadata support should be improved. Currently, Emby supports the Composer tag. That's great, but not enough to deal properly with a classical music collection. We need to support a bunch of other tags, like the Conductor, Performer and Orchestra tags. Adding support for such tags should not be very difficult, as many of them are part of the official ID3 specifications and already supported by ffprobe.
Classical music support is a very important feature for me and some other people. So important that I would even pay to have it added to Emby. If I can help to build it, I would do it very happily.
If developers do not wish to add those features, maybe it could be implemented by a 3rd-party plugin. In that case, could someone point me towards some kind of guide or tutorial to get started ? I know C# and .Net but have no idea about how Emby works with plugins, and how to extend the metadata schema.
Edited by MarinBernard, 10 January 2016 - 06:04 AM.