[Suggestion] Add cover resolution column in the search results

Hello
Cover resolution info will be useful to find better covers more easily.
Now, sometimes I need to check a dozen of result to find a good cover. I try to use square images in my collection. Usually 500x500, 600x600 or 300x300

As I see in the HTTP debugger, Discogs API response contains this info (like 150px previews in the first column):

Screenshot

Thanks

It’s only available when querying the actual release and not in the list of query results.

Querying all releases at this stage already would create huge amounts of traffic and would definitely trigger rate limiting.

Ah, got it, I saw in the album's file. Thanks for reply.

But now I found the necessary info in the Artist+Album search, without opening a result.
Please look

I think cover_image can be parsed, and it's value - /h: and /w: parts of URL :slight_smile:

"cover_image": "https://i.discogs.com/VSlgHVdhZH25H1kEBmzSOThfwAwvewhIg-MM7OBY7d8/rs:fit/g:sm/q:90/h:600/w:600/czM6Ly9kaXNjb2dz/LWRhdGFiYXNlLWlt/YWdlcy9SLTEwNzgx/OTQ2LTE1MDQzODY2/MzMtMjU5OC5qcGVn.jpeg"

Of course, this is more complicated than parsing the json itself.

So what?) Can be resolution obtained from search results list JSON as I described above?)

I think it's possible, but I'll need to conduct some experiments first. I'm currently busy with other topics, so you'd need to practice your patience. I'll keep you posted.

Got it. I know how to wait:) harold.jpg
Thanks + special thanks)

I've created a preliminary version that adds a new Cover column with cover dimensions to the list of query results.

Please give it a try: Discogs-2024-05-28.zip (4.4 KB)

Great! It works.

I see probably a typo, and reverse order of dimensions (Height*Width) in comparison to loaded data of search result (Width*Height).

With $2x$1 in the regexps I got same order in both windows.

Thanks.

OK, thanks. I wanted to use the multiplication sign × but it seems it's not available with all fonts. Good catch with the order of width x height!

Here is an updated version: Discogs-2024-05-28_2.zip (4.4 KB)

It is ok now, thanks :+1:

But I see a problem with covers loading - when too much search results, it seems bulk loading of previews is considered as DDoS, and loading blocked for some time. Maybe it will be a good idea to apply a rate limit, or allow to filter covers by width/height ranges (for example, [490...505]-[590-605] to ignore and no load any other files), or option to disable previews loading.

When I search Black Sabbath - Technical Ecstasy:


Opened 429 response - 429 Too Many Requests

I'm currently rebuilding the Discogs Image Cache, so it's running into rate-limiting multiple times a day for usually not more than 60s. What you see as HTTP 429 is the response from Discogs, what you see as HTTP 503 is from the caching proxy as it waits for the limit to be lifted (and serves cached images in the meantime).

It's currently at around 2:1 uncached vs. cached images and I hope (and think) the situation improves in the coming days.

I was also thinking about an option to disable loading of previews. For so many requests as in your example, it indeed makes sense to request the images in multiple slightly delayed batches.

Got it.

I commented out these lines in Cover Preview section and now no previews loading:)

say http://cache.mp3tag.de/coxy|
sayregexp (?<=\.com).*|

Another idea (not a feature request, at least from me :slightly_smiling_face: ) related to the server load and images loading. I did not create a new topic, because this question has already been touched here.

I will describe my scenario of using cover art search:

  • Previously: I searched for Artist+Album, and went through a bunch of covers in search of a suitable one (square with resolution from 300px) => were many unnecessary requests and server's traffic consumption.

  • Now: it is possible to see the size of the image, but the images themselves may not fit, because often on discogs uploaded not scans of covers, but various photos of disks, or sloppily processed scans (not trimmed, for example). You can't always tell from the 150px previews and load full image on the next step.

The essence of the idea - it would be possible to call loading the full image by interface button or right mouse button, when a user almost sure that it is what he need, and display the image as a floating window for example (now I find the necessary square image with 1-3 attempts for popular albums, and the load on the server in any case is likely to be lower than when loading all previews, and if there is no the necessary resolution - I copy from sites).
Sure, a user can press Next, but it's not very convenient to go back and forth (the position of the search results list changes) when you are processing, for example, a discography and there are unsuitable images.

Honestly I would not use discogs as a source for covers unless you have no other choice. Their 600px restriction and -as you said- fairly unsorted way of storing the images is hardly useful in my opinion.

Personally I use this site to search for covers and I've integrated it into my mp3tag workflow with a tool that I've written. Usually doesn't take me more than a couple of seconds to find a sharp 1400px album cover that way.

Another site I use as well that tends to have great qualioty images, but less avaialbility for fringe/rare titles.
https://www.albumartexchange.com/covers

I've used that site in the past as well, but it's far less convenient (and I heard the owner seems to arbitrarily ban people or entire regions on a whim).
Unless you also have a tool where you can simply select a track in mp3tag, press ctrl+1 (or whichever tool position you have it on) and a new browser tab opens with album, artist and selected sources prefilled. If so, I'm interested. :slight_smile:

I add covers to a relatively small number of discographies. Only my favorites) And pics resolution doesn't matter much - such albums usually have a directory with scanned covers next to them. But as an additional source of covers, it's a good option.

I have never had an issue myself and have registered been on their site for a very long time.

No tool that I have built, nor am I aware of one. The low-tech method of using their search function and using the AlbumArtist and Album works pretty easily though. Minimum res is 600x600. The others standards usually found are 800, 1000, and 1500 in square. Seldom are there any that aren't square except for some odd releases. The quality of the results makes it worth the effort.