Web (GUI) that displays album art?

[halloleo]

I’ve tried the web plugin and it does show the tracks, but for me it doesn’t show album art.

Is there another GUI which does show the album art? (It can be a web app or a macOS app.)

Thanks for pointers!

[out-of-range]

You could use the beets AURA plugin along with AURA web client (both written by me). I find the main downside to be you can’t use beets queries

[scuttlefish]

Not a beets plug-in, but this is the one I use. It works very good in coordination with beets.

Euterpe Music

[halloleo]

Thanks @out-of-range. I’ve tried the AURA approach, but I get a “TypeError: Load failed” message.

What have I done?:

1. I run the server in the default config on http://127.0.0.1:8337.
2. I run the client locally from the index.html file.
3. I enter “http://127.0.0.1:8337/aura/” in the Server URL field in the web app, then click “Make Request”.

Any idea why this happens?

[out-of-range]

@halloleo That would be a cross-origin resource sharing error, if you put

aura:
  cors:
    - "null"

in your beets config file it should work.

I should definitely make it clear in both server and client documentation that that is required for using browser clients

[ctrueden]

@halloleo

Is there another GUI which does show the album art?

Another option is Beetle:

Beetle : a web interface for beets

Hello everyone, I recently create a web interface for beets called Beetle. It is based on top of the beet web API and has the following features: list of albums and artists infos of albums and lyrics of tracks text-based search playing and playlist support I have made a demo video, where you can see the design of the beast: Source: La Bécasse / beetle · GitLab

[halloleo]

@ctrueden Thanks for suggesting Beetle. I just tried it!

However in the web browser I get an error 500:

request to http://localhost:8337/album/query/added- failed, reason: connect ECONNREFUSED ::1:8337

FetchError: request to http://localhost:8337/album/query/added- failed, reason: connect ECONNREFUSED ::1:8337
    at ClientRequest.<anonymous> (/Users/me/audio/beetle/src/node_modules/@sapper/server.mjs:1966:14)
    at ClientRequest.emit (node:events:513:28)
    at Socket.socketErrorListener (node:_http_client:494:9)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Any idea why this happens?

[halloleo]

@out-of-range

aura:
  [...]

Coo,l that works! Thanks.

[ctrueden]

@halloleo

However in the web browser I get an error 500:
…
Any idea why this happens?

Sorry, I’m not sure. @labecasse Any suggestions?

[labecasse]

Hi @halloleo
It seems that your Beet API is not reachable at http://localhost:8337. Some ideas :

• Have you checked whether you can access to http://localhost:8337/album/query/added- ?
• Are you sure that beet web is running properly ?
• Have you configured Beet web plugin as explained here (expecially the cors property) ?

Also both aura and web plugins are running on the port 8337 by default. So, it can lead to some conflicts if you are running them at the same time.

[halloleo]

@labecasse

Also both aura and web plugins are running on the port 8337 by default. So, it can lead to some conflicts if you are running them at the same time.

Ah, I guess that’s the problem. (I think I haven’t disabled the aura plugin.) Will check it out tonight.

Thanks for chiming in, @labecasse.