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 1372061 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

foo_discogs

Reply #1450
that's good enough I think as the limit is reset in a reasonable timeframe. if we'd hit the limit more often, image download could probably be done the old school way by parsing the image section/ links on the release page.

foo_discogs

Reply #1451
After updating from version 1.32 to 1.36 I've got message:     

"Failed to load DLL: foo_discogs.dll
Reason: Unknown error code (3221225501)"

My system: Windows XP SP3, Pentium III


Modern compilers use SSE2 instructions by default. Your CPU doesn't support them.
But it's possible to build foo_discogs that it doesn't require SSE/SSE2.

Try this one: https://www.sendspace.com/file/s6hwpc

I built it with no enhanced instructions.


Many thanks for your efforts. To clarify, Pentium III is SSE capable.   

Unfortunately, after installing this special version I've got this message:

uninteresting: foobar2000.exe - Application Error

The exception unknown software exception (0xc0000417) occurred in the application at location 0x0169af51.

Actually I'm using 47 user components and only foo_discogs makes me now sad. All other components are working "out of box".

I hope that my problem can be solved.


 

foo_discogs

Reply #1452
Many thanks for your efforts. To clarify, Pentium III is SSE capable.   

Unfortunately, after installing this special version I've got this message:

uninteresting: foobar2000.exe - Application Error

The exception unknown software exception (0xc0000417) occurred in the application at location 0x0169af51.

Actually I'm using 47 user components and only foo_discogs makes me now sad. All other components are working "out of box".

I hope that my problem can be solved.

Hmm... I don't know much about this.... Is your foobar2000 up-to-date?

Also, can you try this one? I might've missed something on the last build: https://www.sendspace.com/file/65p5oq

foo_discogs

Reply #1453
that's good enough I think as the limit is reset in a reasonable timeframe. if we'd hit the limit more often, image download could probably be done the old school way by parsing the image section/ links on the release page.

I feel your pain. AFAIC this is a bug on Discogs (it's stupid to rate-limit requests per application rather than per user or per IP). I'm waiting for their response on this issue before I decide what to do. Hopefully they'll remove the limits. :-)

Edit: In the meantime, for those who need to download artwork, here's a version that bypasses the API. (This may not work forever if they change the format of their image URLs.) https://www.sendspace.com/file/erlpps

foo_discogs

Reply #1454
So is the image downloading problem coming to end? I have no error now but albumart is not fetched.

It's not coming to an end, just some minor difficulties. I recommend using this build if you need album art right now: https://www.sendspace.com/file/erlpps

I feel like the plugin needs some more fixing yet. Got hanged at "(fetching additional artist information...)" stage for release 1341431.
Other releases go fine

This artist has 27 pages of releases to load. If each page takes 5 seconds, this would take several minutes to load. So it's not hanged, it's just going very slowly. There may be future improvements to the plugin to load less information (I'm not sure if it really needs to load all those pages), or to make loading each page faster, but for the time being you'll have to be patient. :-)

The old Discogs API didn't break things into pages, so it would all load at once.

foo_discogs

Reply #1455
Few more comments/responses...

Regarding LINK and ID tags: LINK used to be different from ID, but now Discogs has eliminated the old LINK and it's the same as ID. I don't know why DISCOGS_ARTIST_ID isn't written but DISCOGS_ARTIST_LINK can be used instead. In the future, the LINK tags should be completely removed and replaced with the ID tags.

"View Artist Art Page" is broken because it's the only page that doesn't use the artist ID (it uses the old LINK). Since I doubt anyone uses this feature and I suspect that Discogs will eventually change it to use the ID like every other page, I'm not bothering to fix it. AFAIK, everything else regarding artist/album art downloading/previewing/uploading works (but I've personally never used it in the past, so if anything is missing, let me know).

foo_discogs

Reply #1456
thx for explaining! looking forward and wish you all the best.

foo_discogs

Reply #1457
I feel your pain. AFAIC this is a bug on Discogs (it's stupid to rate-limit requests per application rather than per user or per IP). I'm waiting for their response on this issue before I decide what to do. Hopefully they'll remove the limits.

Personally, I wouldn't hold my breath waiting for change, my understanding is Discogs did this deliberately in an attempt to limit their server load. After long involvement and many contributions to thier site, I have come to believe that Discogs management is all about getting, not giving. You, and all the other foobar developers, selfless efforts on our behalf are in stark contrast to thier greed and selfishness. Thanks again.
Quis custodiet ipsos custodes?  ;~)

foo_discogs

Reply #1458
How are folks getting their album art?

foo_discogs

Reply #1459
that's good enough I think as the limit is reset in a reasonable timeframe. if we'd hit the limit more often, image download could probably be done the old school way by parsing the image section/ links on the release page.

I feel your pain. AFAIC this is a bug on Discogs (it's stupid to rate-limit requests per application rather than per user or per IP). I'm waiting for their response on this issue before I decide what to do. Hopefully they'll remove the limits. :-)

Edit: In the meantime, for those who need to download artwork, here's a version that bypasses the API. (This may not work forever if they change the format of their image URLs.) https://www.sendspace.com/file/erlpps


That's cool  Good for me. Your quick updates are really appreciated. I think you deserve a paypal beer from me too  Will scroll through the history later to donate some money for you

foo_discogs

Reply #1460
Hmm... I don't know much about this.... Is your foobar2000 up-to-date?

Also, can you try this one? I might've missed something on the last build: https://www.sendspace.com/file/65p5oq

Yes, my foobar2000 is 1.3.3. I've tried the last version and it seems to be OK now, no more errors.   

Many thanks for your help. And at the end, could the version without SSE2 optimization be an official one for now and in the future too? I suppose that shouldn't be any decrease of speed. Also I won't ask you for help when the new version will be released 


foo_discogs

Reply #1461
Hmm... I don't know much about this.... Is your foobar2000 up-to-date?

Also, can you try this one? I might've missed something on the last build: https://www.sendspace.com/file/65p5oq

Yes, my foobar2000 is 1.3.3. I've tried the last version and it seems to be OK now, no more errors.   

Many thanks for your help. And at the end, could the version without SSE2 optimization be an official one for now and in the future too? I suppose that shouldn't be any decrease of speed. Also I won't ask you for help when the new version will be released

Good to hear that. I'm not sure what the best practices are on how to build the component, but I'm happy leaving enhanced instructions disabled for future official builds unless I hear otherwise.

foo_discogs

Reply #1462
Hi all,
I get the 'cannot connect to discogs' error; someone suggested trying to delete an old .cfg file, but I'm running a fresh install of the newest versions of Foobar and the component, and cannot find any old .cfg files (I assume these should be somewhere downstream of the Foobar program folder).

Do any of you have an idea how to fix this? Many thanks in advance; I love this component!

foo_discogs

Reply #1463
I've seen some tags writen with brackets and a number, such like DISCOGS_ARTIST_ALIASES, i.e. Gang Green (2) where you'd expect only Gang Green (Release 890618).
Did I miss something? Is there a reason for this  No rush though in fixing it if it's fixable

foo_discogs

Reply #1464
foo_discogs 1.37: https://www.sendspace.com/file/1d80af

* Fixed the above issue with artist name not having the number removed.
* Built with enhanced instructions disabled to support older CPUs.
* Does not use the API for images, due to rate-limiting problems.


foo_discogs

Reply #1466
Hi all,
I get the 'cannot connect to discogs' error; someone suggested trying to delete an old .cfg file, but I'm running a fresh install of the newest versions of Foobar and the component, and cannot find any old .cfg files (I assume these should be somewhere downstream of the Foobar program folder).

Do any of you have an idea how to fix this? Many thanks in advance; I love this component!


So apparently I was using an old version of foo_discogs; no idea how I got that to be honest, but it happened. Anyway, problem solved.

foo_discogs

Reply #1467
Anybody else suddenly pulling down only 90x90ish micro-art today?  It was fine last night.  I'm using 1.37 with 1.3.3 Foobar.

foo_discogs

Reply #1468
Anybody else suddenly pulling down only 90x90ish micro-art today?  It was fine last night.  I'm using 1.37 with 1.3.3 Foobar.


Yep, seems so. Hopefully zoomorph can work out another direct HTTP way of downloading images...

(Not that I really mind tagging, then opening the release in the browser and downloading the cover image direct. But if you're tagging a lot at once rather than a release at a time, it's no fun!)

foo_discogs

Reply #1469
Anybody else suddenly pulling down only 90x90ish micro-art today?  It was fine last night.  I'm using 1.37 with 1.3.3 Foobar.


Yep, seems so. Hopefully zoomorph can work out another direct HTTP way of downloading images...

(Not that I really mind tagging, then opening the release in the browser and downloading the cover image direct. But if you're tagging a lot at once rather than a release at a time, it's no fun!)


Yeah, that's exactly what I'm doing.  Fortunately I had just finished ripping a few hundred CDs this past week.  Hopefully there's a fix of some sort, but if not, I'd rather have this be the glitch than some tagging problem.

foo_discogs

Reply #1470
nope- 600x600 ... which release didn't work for you?

foo_discogs

Reply #1471
ah ok, got it now too :|


foo_discogs

Reply #1473
Hi
and thank you bubbleguuum for your great work all the years
and thank you zoomorph for your help and work, giving us all the fine things, ppl need to tag their musicfiles decently!

question:
does anybody know, if there is a limit on Artists Aliases, or Artists Name Variations?

using 1.37, I get:

<DISCOGS_ARTIST_ALIASES> : Pink Floyd; Architectural Abdabs; The Screaming Abdabs
<DISCOGS_ARTIST_ANVS> : Pink Floyd; ピンク・フロイド; Пинк Флоид; Пинк Флойд; Floyd; P. Floyd; P.F.; Pink Floid; The Pink Floyd; pinkfloyd


but tagging with very old versions gave something like this:

<DISCOGS_ARTIST_ALIASES> : Pink Floyd; Blue Calx; Bradley Strider; Brian Tregaskin; Caustic Window; The Dice Man; GAK; The Grateful Dead; Karen Tregaskin; PBoD; Polygon Window; Power-Pill; Q-Chastic; Richard D. James; The Screaming Abdabs; Smojphace; Soit-P.P.; The Tuss
<DISCOGS_ARTIST_ANVS> : Pink Floyd; Пинк Флойд; Floyd; P. Floyd; P.F.; The Pink Floyd

I don't know, if this might be an discogs issue or maybe ... something else ;-)
The discogs website shows the same as the v1.37 offers me.

cheers and thank you. keep up the good work!

foo_discogs

Reply #1474
Also having the image fetch issue with the size really small..