gasilhire.blogg.se - Foobar2000 song rating plugin

#Foobar2000 song rating plugin manual
#Foobar2000 song rating plugin code
#Foobar2000 song rating plugin license

Within Tools > Tagging ? Quick Tagger I have setup a custom Field known as "Rating" with the Values "1 2 3 4 5"

I downloaded a component for foobar2k called "Quick Tagger" or foo_quicktag. button and choose Create Autoplaylistįor your other autoplaylist you need something like the following: FAVOURITE MISSING AND RATING GREATER 3Īlternatively you could use a numeric value for the custom field in order to allow more than two playlists.

#Foobar2000 song rating plugin manual

To add your new auto playlists, choose Library-> Search.Įnter the following filter string for you manual playlist: FAVOURITE IS "True"Ĭlick the. In the Metadata tab, right-click and select Add new field. To add the metadata field, select and right-click the relevant files from your original list and choose Properties. Note that this assumes that your playlist is a Foobar playlist and not a generic (M3U etc.) playlist That way you can easily create two autoplaylists - one to represent the old one and a new one that doesn't overlap the other. However, my suggestion would be to add a custom metadata field to mark the files from your existing "manual" playlist. The issue is with foo_listenbrainz2 and the foobar2000 component API, if I understand correctly.I don't think it's possible to do exactly what you want without creating a custom plugin. There is no interoperability issue between Picard and foobar2000 here. Many I’ve solved myself by using my own tagging tools and avoiding foobar2000 for tagging. Changes to handling of composer sort name in foobar2000 is a recent example that I haven’t solved to my satisfaction. There are a dozen other ID3 interoperability issues between Picard and foobar2000 anyway. I’m trying to find a solution that works for everyone with default settings. Besides, that only solves the problem for one person. For reasons I won’t get into, retagging the files is a bigger problem than you might think. I already said this myself earlier in the thread.

#Foobar2000 song rating plugin code

Develop your own Picard code to save certain fields to TXXX frames instead of poorly supported fields from the ID3 standard.

It’s not so easy to get rid of the remaining MP3s. So, you see, I’ve already chosen a different codec a very long time ago.

Continue using foobar2000 but choose a different music file formatĪbout 77% of my library is Vorbis or Opus.

Since I haven’t acheived nearly the same functionality out of any other player, this suggestion isn’t so realistic. I have now updated the fork with the changes from your repo: GitHub phw/foo_listenbrainz2Ĭontribute to phw/foo_listenbrainz2 development by creating an account on GitHub. Unfortunately it had been a while since my last sync, so the changes for 1.1.2 and 1.1.3 had not been included. Marc in the meantime had set up a fresh repository, and I had setup a fresh fork for it. But the repository now is based upon an older fork of mine I created to preserve the code after Marc’s last rage quit and contains some obsolete parts. I don’t know why Marc reacted as he did, but there likely is some history behind it.Īnyway, enough of this and back to topic: Great you had the code and thanks for preserving it. I think I most of the time manage to get some distance to situations like these and either ignore it or answer neutrally.

#Foobar2000 song rating plugin license

That’s partly because of my experience that small seemingly harmless questions about “why license XY” usually is a sneaky way to drag one into a often point- and endless licensing discussion. Let’s give a recent example: When you answered me with explaining the merits of the GPL my gut reaction to it was “this guy for sure does not need to educate me on the GPL”. But the way they formulated their requests just felt demanding and/or patronizing. More than once I read comments on my projects that really made me feel angry, even though there was probably no ill intention on the person who wrote it. At times that can feel really demanding or patronizing you feel people try to educate you on things you know about well and asking you for stuff you have explained already a trillion times. If you have an open source project people actually use, there will be people telling you how you really should support feature X, how easy this would be, that others do this and hence should you etc. Not excusing Marc’s behavior, though, which also was inappropriate.īut maybe a few words from me as maintainer of open source projects: I kind of get were Marc’s feelings and reactions are coming from. Someone flagged it now, and I think rightly so. Well, that escalated quickly and I think you know quite well that your last post at Marc went way over the top, escalated the heated debate to the next level and violated the code of conduct.