Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Beets, Chromaprint, and USE flags
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
Itserpol
n00b
n00b


Joined: 23 Jan 2010
Posts: 22

PostPosted: Tue Jul 18, 2017 1:38 am    Post subject: Beets, Chromaprint, and USE flags Reply with quote

Preemptive tl;dr - In order for Beets' acoustic fingerprinting feature to function properly, one needs to set the "tools" USE flag for Chromaprint, (in addition to the "chroma" USE flag for Beets) and this is not made obvious to the user. What gives?


First, for those of you who don't know, Beets (http://beets.io/) is "the media library management system for obsessive-compulsive music geeks." It's a highly configurable system for organizing your music collection and automatically tagging files with metadata from MusicBrainz (or Discogs or Beatport, if you prefer). I highly recommend it, especially for people like me who've spent countless hours hunting down accurate metadata and manually tagging their collections.

One of the features I found most interesting is its use of Chromaprint (https://acoustid.org/chromaprint) to automatically calculate a unique audio fingerprint for music files, which can be useful for identifying songs with no or completely wrong metadata. To enable this feature, one simply sets the "chroma" USE flag and Beets pulls in Chromaprint as a dependency.

It worked great for me at first, but several months ago I noticed Beets failing to fingerprint newly imported files and complaining about not being able to find some program called fpcalc. I eventually became annoyed enough to try and fix it, and after a lot of Google sleuthing I discovered that Chromaprint needs to have the "tools" USE flag set in order to build fpcalc. So I set the flag, re-emerged, and Beets went back to contentedly fingerprinting my music.

But I'm left wondering why this happened. At the very least, it seems like there should be some hint in the chroma USE flag's description that the other flag is necessary. But then again, there's almost definitely a good reason for this that I'm just ignorant of. Are there any other Beets users this has happened to who can shed some light?
Back to top
View user's profile Send private message
Telemin
l33t
l33t


Joined: 25 Aug 2005
Posts: 734
Location: Glasgow, UK

PostPosted: Tue Jul 18, 2017 12:02 pm    Post subject: Reply with quote

That should bb considered a bug in the beets ebuild, for not having the correct dependency listing. You should report it on bugs.gentoo.org to alert the beets maintainer who can add media-libs/chromaprint[tools] as a direct dependency for the chroma use flag.

-Telemin-
_________________
The Geek formerly known as -Freestyling-
When you feel your problem has been solved please add [Solved] to the topic title.
Please adopt an unanswered post
Back to top
View user's profile Send private message
Itserpol
n00b
n00b


Joined: 23 Jan 2010
Posts: 22

PostPosted: Wed Jul 19, 2017 12:05 am    Post subject: Reply with quote

Telemin wrote:
That should bb considered a bug in the beets ebuild, for not having the correct dependency listing. You should report it on bugs.gentoo.org to alert the beets maintainer who can add media-libs/chromaprint[tools] as a direct dependency for the chroma use flag.

-Telemin-


Thank you Telemin. I figured filing a bug would be necessary, but of course it's nice to get confirmation. :D

Bug filed here: https://bugs.gentoo.org/show_bug.cgi?id=625578
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum