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 1374461 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_discogs

Reply #1000 –
Quote from: mitchmalibu on
Fair enough, it's not really a deal breaker anyway but it does happen quite often in electro releases.


Certainly not a deal breaker for me, but just adding a "+1" too. It happens "enough" in releases ranging from prog rock (Pink Floyd even) through industrial (Einstürzende Neubauten) to postrock and electronica. It's certainly totally non-standardised though, it's a problem for Discogs I think.

foo_discogs

Reply #1001 –
When file already has albumart attached and I write tags using Discogs->Write Tags... so the albumart is removed. Can you please fix this?
Happens only in MP3 files with preffered scheme APE + ID3v1, and not with FLAC files.
Thanks a lot.

foo_discogs

Reply #1002 –
Since a few days I can't connect to discogs.com database and I'm getting a message like "discogs error: release id=xxxxxx problem connecting to discogs.com". My foo is 0.9.6.9. and foo_discogs 1.22. Anybody know what is going on?

foo_discogs

Reply #1003 –
Quote from: tobik on
Since a few days I can't connect to discogs.com database and I'm getting a message like "discogs error: release id=xxxxxx problem connecting to discogs.com". My foo is 0.9.6.9. and foo_discogs 1.22. Anybody know what is going on?


the same here...

foo_discogs

Reply #1004 –
There has been an update, look at the last page.
 

foo_discogs

Reply #1007 –
Great plugin.  I use it loads, helps with tagging a lot.

One bug I have noticed sometimes, although could potentially be discogs problem.  Albums will sometimes appear in a completely screwed order, despite all the track names being correct.  Obv the move / down helps workaround this.

foo_discogs

Reply #1008 –
Untick 'Automatically match....' at the Tagging pane of the Configuration tool.

Quote from: krayon on
Albums will sometimes appear in a completely screwed order, despite all the track names being correct.

foo_discogs

Reply #1009 –
Hey there bubbleguuum,

I've been using your component for quite some time now. It is brilliant! :-)

I have another request though:

I'd like to store the actual primary main artist names (non ANV) WITH the Discogs numeric suffix.
This is currently disabled by default and cannot be changed within the component, I believe.
I'd like to do this to accurately distinguish between artists with the same name.
Could you enable this as optional setting please?

Simultaneously it would be awesome to automatically store the listed artist names without
the numeric suffix as Artist Name Variation.


I have one issue as well, but I'm not sure if this only affects me.
I'm storing the discogs release format as %format%, but it is not
saved as multi-value field even though the description says so.

Thanks for your support!

foo_discogs

Reply #1010 –
Quote from: SpaceAgeHero on
I'd like to store the actual primary main artist names (non ANV) WITH the Discogs numeric suffix.
This is currently disabled by default and cannot be changed within the component, I believe.
I'd like to do this to accurately distinguish between artists with the same name.
Could you enable this as optional setting please?

Simultaneously it would be awesome to automatically store the listed artist names without
the numeric suffix as Artist Name Variation.


Not sure if it'd do what you want, but the numeric suffix is stored in the <DISCOGS_ARTIST_LINK> tag.
So you could keep the artist as it should be - just the artist name - but sort and do whatever other operations you want via <DISCOGS_ARTIST_LINK>.

foo_discogs

Reply #1011 –
Quote from: tobik on
Since a few days I can't connect to discogs.com database and I'm getting a message like "discogs error: release id=xxxxxx problem connecting to discogs.com". My foo is 0.9.6.9. and foo_discogs 1.22. Anybody know what is going on?


I also have this same problem every now and then, not always. Even though I'm fully updated (foobar 1.1.7b6 and discogs 1.26). Once it starts to happen I cant find a way to solve it...
If I search for an artist the discogs tagger window just loses and regains focus in a split second and nothing happen.
If I put a release id straight I geet the same message as above "discogs error: release id=1528086: problem connecting to discogs.com"
Strange enough this does not happen if I put a local http debugging (Fiddler) proxy between foobar and the internet.

foo_discogs

Reply #1012 –
Just reporting that at least from my machine it looks like discogs is apparently blocking User-Agent: foobar2000/1.1.7_beta_6.

foo_discogs

Reply #1013 –
i'm kind of lost right now, can anyone plz help me in finding the right script for adding the artist art into the parent folder of the album? my structure looks like \artist\album\files.mp3 and i'd like to copy the artist art into the artist folder... $directory(%path%,2) doesn't work, as it cannot create the file then (?!?).

thx i.a.

foo_discogs

Reply #1014 –
not working today

foo_discogs

Reply #1015 –
first, i'd like to say many thanks to the author of this very-very usefull plugin. how can we live without it?)

and second - it stop working. version 1.26. it doesn't search for artist, while adding new releases. when trying to search by discogs_id i get the error message:

discogs error: release id=2535847: problem connecting to discogs.com

upd: foobar version is 1.1

foo_discogs

Reply #1016 –
Same issue here.  Using Foobar 1.1.7b6 with foo_discogs 1.26.  Search is essentially non-responsive.  Thanks once again for the continued support!! 

foo_discogs

Reply #1017 –
It looks like discogs is blocking certain User-Agents from using their service:
Code: [Select]
GET http://www.discogs.com/release/2855740?f=xml&api_key=df4f42ee8c HTTP/1.1
Host: www.discogs.com
Connection: close
Accept-Encoding: gzip
User-Agent: foo_discogs/1.26
Accept: */*

This results in a "500 Client Refused" answer from discogs. There is a thread on discogs website on the matter here that suggest some other developer with the same trouble to open a support request to get his/her app unblocked.
As a temporary workaround you can use some software to change the user-agent on the fly to avoid the blockage. Certain debugging proxies software like Fiddler or ad-blocking software like Ad-Muncher lets you do that.

foo_discogs

Reply #1018 –
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.


foo_discogs

Reply #1019 –
Thank you, the fix is working for me. However, in my case (unknown album names) the utility costs as much as time as adding data by hand

foo_discogs

Reply #1020 –
If discogs wants to be a bitch about controlling http access I humbly request that the user agent in foo_discogs be an editable field.

foo_discogs

Reply #1022 –
Thank you for the fix, works perfect again!

foo_discogs

Reply #1023 –
thanks too, the fix works. usereditable string would be a self helper.

btw:
the last months i collected some screenshots which show some "broken" entries from some albums i tagged over the last time.
i don't know, if its the plugin or the website which i producing those "bad" tags. (unescaped characters? some html code inside tracknames, etc)
maybe, if you see those screenshots, you can hunt down the broken entries and fix them? if not, nevermind. great plugin :-)








foo_discogs

Reply #1024 –
and those screenshots too.