MusicD Remote - a companion client for Roon

Tinkering Roon API
1

Previously called Roon-Random-Albums

MusicD Remote is a companion client for Roon, read here for its features.

Installation instructions are here for new installs and for MacOS look here

For existing users, the auto update feature may not work due to the name change and you’ll need to follow the instruction here

Apologies in advance and PM me if you have any issues.

2 Likes
New Random Album Extension
2

I reserve the right to remove the :heart: provided if getting it up up and running proves to much in the heat today :zany_face:

1 Like
3

A man of your calibre should have no trouble at all.

But, good luck :crossed_fingers: :wink:

2 Likes
4

@MusicD

Update completed. Thanks again for your work.

1 Like
5

Update completed as I needed 5 minutes out of the sun.

It’s safe for you to go on holiday now :grin:

1 Like
6

I go next Friday :+1:

7

Plenty of time for another 18 releases before that :grin:

3 Likes
8

Totally true

But for now it’ll remain as is for a few weeks

1 Like
9

MusicD is proud to present our new landing page for MusicD Remote for Roon. Comes complete with a new configuration tool and full, easy-to-follow steps throughout.

1 Like
10

@MusicD The Mac IP fix seems to have maybe regressed in this version? There’s no ROON_CORE_IP in the code when I have Claude look at it. Claude suggests the fix below.

2. Reapply the manual-connect patch ourselves as a stopgap

Same fix as before — since this version doesn’t have ROON_CORE_IP support, we can add it back to /app/index.js (in your local build folder, not just inside the container, so it survives rebuilds) with the same edit:

js

if (process.env.ROON_CORE_IP) {
  roon.ws_connect({
    host: process.env.ROON_CORE_IP,
    port: parseInt(process.env.ROON_CORE_PORT || "9330", 10)
  });
} else {
  roon.start_discovery();
}

replacing line 257 (roon.start_discovery();) in your local ~/musicd-remote/index.js before rebuilding — but this will get wiped again on the next auto-update unless we also disable auto-updates.

1 Like
11

@MusicD Confirming that I made this change on a local copy, and it’s working now.

1 Like
12

Appreciate the assist on this

I replied on GitHub :+1:

13

Update available and should appear via the extension upon a full refresh, other wise it’ll appear 7 days after the initial install date.

14

are there any pictures or videos from MusicD in action??

15

Via the Wall Display function - yes

Pictures in terms of artists/bands - yes if available

Video - yes, if available (must meet certain criteria to be valid)

The video part is tricky to implement in all honesty. Never will be in sync with the music and what’s available is limited. I am working on more sources for video but progress is slow due to implementation.

16

@Itchy Lots of screenshots in MusicD’s original post from him and others.

2 Likes
17

Thanks @Dadoo :+1:

Some of those will be out of date now.

I’ll work on a fresh bunch of pics and add them to the GitHub.io landing page.

1 Like
18

one more question, why do you don’t push the image over a container registry?

19

Because I haven’t gotten around to it and this way is working for most :+1:
I’m also doing this for free :wink:

As you removed/edited most of your post, is that to say you have it working?

20

okay, it was only for my understanding. :slight_smile:

i removed my old post, because my question makes no sense, because the image isn’t pushed over a container registry.

1 Like