Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_discogs (Read 1365500 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

foo_discogs

Reply #1025 –
Quote from: fuffi on
and those screenshots too.


Most, if not all, of these are HTML tags which Discogs uses to display special characters and superscripts and things. They can't be used in a simple Unicode textfield for tagging, but I suppose with some cleverness the Discogs tagger could either remove tags or try to translate them to something usable...

foo_discogs

Reply #1026 –
Another nice addition to this component would be if one could import tags into an open properties editor without automatically writing them into the files.
Example:
Select some album's tracks, open their properties. Do something (optional and even more advanced suggestion: select some tag names; the following shall be applied only to these tags; i.e. automatical configuration of tag mappings), open some menu which yields the usual discogs tagger, after retrieving the tags they are filled into the properties editor where you can further edit them, no tag has been written yet, do some additional modifications, save tags.

foo_discogs

Reply #1027 –
Hi there, just registered here to tell the developer of this awesome user component, that it's not working since a few days. Seems like Discogs changed something. An update would be great!

foo_discogs

Reply #1028 –
Hi there, as Fleshgrinder I canot use foo_discogs since a few days, same thing for you ?
When I ask for a research, nothing happen.
Thanks.

foo_discogs

Reply #1029 –
be patient guys! he may be on vacation... its not the first time discogs changed stuff and i'm quite sure bubbleguuum will too! its not his daily business to serve us this beauty, so keep cool!

foo_discogs

Reply #1031 –
Quote from: traxy on
You can use a hex editor to change the user-agent in foo_discogs.dll.

I uploaded a fixed dll here:
http://www.multiupload.com/UH22MN91GC

Please note, that this is a temporary fix only, until the original component gets updated.
It may be worth noting that this change is not that different from how bubbleguuum would fix this "problem" anyhow. If someone would care to go whine at Discogs about this, it'd be appreciated. I don't know why they keep blocking certain user-agent strings. I can't find anything in their documentation that would explain why.

foo_discogs

Reply #1032 –
For now use the hex edited version. I've asked discogs.com for clarification on this topic to hopefully issue a permanent fix.

foo_discogs

Reply #1033 –
a little bit of a tricky one. I have recently noticed the true potential of foo_discogs, when I went to edit the mappings..

I was curious if someone would be able to assist me with the following;

as far as I know, when you tag your music with the discogs tagger, the songs never mention (featuring blablabla) in the title name. If i wanted them to be shown, I was thinking I could have my 'title' column in ng_playlist display:

Code: [Select]
%title% (Feat. %DISCOGS_FEATURING%)

as it would then show the artist that features in the track, but in the 'title' column. However, the above code would leave every track tagged as Songname (Feat.) even if there was no featuring artist. How would I edit the code to say "if there is a featuring artist, it will be displayed" as above?

Hope someone could assist. Many thanks!


EDIT: also, some tags, including %DISCOGS_LABEL_LINK% download the results, and instead of spaces, it parses %20. Is there anyway to automatically/quickly fix this, without having to go through all of my music manually editing it? thanks also

foo_discogs

Reply #1034 –
Quote from: MDMA on
Code: [Select]
%title% (Feat. %DISCOGS_FEATURING%)
as it would then show the artist that features in the track, but in the 'title' column. However, the above code would leave every track tagged as Songname (Feat.) even if there was no featuring artist. How would I edit the code to say "if there is a featuring artist, it will be displayed" as above?

hi,
i'm using UI-Colums Playlist View, but you could try something like this:
Code: [Select]
$if([%DISCOGS_CREDIT_FEATURING%],[%title% '('feat. %DISCOGS_CREDIT_FEATURING%')'],[%title%])
i'm sure, somebody can point out a how-to, but you surely find some more help in related threads.
cheers,

foo_discogs

Reply #1035 –
Quote from: MDMA on
a little bit of a tricky one. I have recently noticed the true potential of foo_discogs, when I went to edit the mappings..

I was curious if someone would be able to assist me with the following;

as far as I know, when you tag your music with the discogs tagger, the songs never mention (featuring blablabla) in the title name. If i wanted them to be shown, I was thinking I could have my 'title' column in ng_playlist display:

Code: [Select]
%title% (Feat. %DISCOGS_FEATURING%)

as it would then show the artist that features in the track, but in the 'title' column. However, the above code would leave every track tagged as Songname (Feat.) even if there was no featuring artist. How would I edit the code to say "if there is a featuring artist, it will be displayed" as above?

It's as simple as
Code: [Select]
%title%[ '('Feat. %DISCOGS_FEATURING%')']

or with a bit dimmed featuring info
Code: [Select]
%title%[ <'('Feat. %DISCOGS_FEATURING%')'>]

You really should acquaint yourself with basic title formatting. It will open a new world of possibilities to you

foo_discogs

Reply #1036 –
Thanks guys. Literally Completely forgot about the [ and ] brackets! d'oh!

foo_discogs

Reply #1037 –
they changed some things 3 days ago...


The API uses a new url: api.discogs.com

An API key is no longer required

We have removed the 5,000 requests per day limit*

We are offering an official Python API client. Check it out on github. Feel free to fork it and submit pull requests. You can help us improve it!

Responses are returned in JSON format now. You can still request XML if you prefer that.

JSONP support


foo_discogs

Reply #1038 –
Nice! Hopefully this will solve a lot of the issues..

foo_discogs

Reply #1039 –
Looking forward to a (hopefully) final fix. Not that it has really been a problem with the lightning fast reactions from bubblegum!

Please consider adding the project to Flattr!

foo_discogs

Reply #1043 –
Could I get a fix to foo2k (not SDK) in version 0.9.5.+?

foo_discogs

Reply #1044 –
Since I didn't get an anwser from Discogs concerning the User-Agent,  I just released 1.27 with the same User-Agent than the hex-edited version (first post to download or components site, or autoupdate)

foo_discogs

Reply #1045 –
Quote from: bubbleguuum on
Since I didn't get an anwser from Discogs concerning the User-Agent,  I just released 1.27 with the same User-Agent than the hex-edited version (first post to download or components site, or autoupdate)

please check out my post above

foo_discogs

Reply #1046 –
Quote from: den_po on
Quote from: bubbleguuum on
Since I didn't get an anwser from Discogs concerning the User-Agent,  I just released 1.27 with the same User-Agent than the hex-edited version (first post to download or components site, or autoupdate)

please check out my post above



Ok, I'll integrate your changes in 1.28 (1.22 is obsolete - and I know the source for the latest version is not available)

foo_discogs

Reply #1047 –
1.28 is available including den_po fix (thanks!) which was the correct solution.

Should work until mid December, until Discogs deprecates the v1 API.

foo_discogs

Reply #1048 –
Searching for Artist does not work for me, no artist or album names appear.
Fetching a specific release by its id or URL works though...
Edit: tried both 1.28 and 1.22 and none of them work
 

foo_discogs

Reply #1049 –
Just tried calling tags for "10CC - Deceptive Bends": Works with the 1.26 hexedited version, but with 1.28 I get weird results.