Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Grouping/TIT1 tag. #1860

Open
crocket opened this issue Dec 21, 2019 · 1 comment
Open

Support Grouping/TIT1 tag. #1860

crocket opened this issue Dec 21, 2019 · 1 comment
Labels
A-audio Area: Audio layer C-enhancement Category: A PR with an enhancement or an issue with an enhancement proposal

Comments

@crocket
Copy link

crocket commented Dec 21, 2019

MPD started supporting Grouping/TIT1 tag a while ago upon my request.

According to id3v2.4.0 frames,

TIT1
The 'Content group description' frame is used if the sound belongs to a larger category of sounds/music. For example, classical music is often sorted in different musical sections (e.g. "Piano Concerto", "Weather - Hurricane").

According to Foobar2000:ID3 Tag Mapping - Hydrogenaudio Knowledgebase, TIT1 corresponds to grouping tag in vorbis comment.

I'd like to use Grouping/TIT1 tag for designating the name of movie or game that a song is made for. For example, I want to find movie OST songs by the name of the movie.

I used to use album artist tag for this, but grouping tag is more appropriate.

@adamcik adamcik added the A-audio Area: Audio layer label Dec 21, 2019
@adamcik
Copy link
Member

adamcik commented Dec 21, 2019

If GStreamer supports this then it's probably doable, assuming we add the right field to our models.

@jodal jodal added the C-enhancement Category: A PR with an enhancement or an issue with an enhancement proposal label Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-audio Area: Audio layer C-enhancement Category: A PR with an enhancement or an issue with an enhancement proposal
Projects
None yet
Development

No branches or pull requests

3 participants