-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tidal extention not found in image: giof71/mopidy #1
Comments
Hello, are you running this on the same Moode Audio box on the Pi2, that you mentioned here? |
I've try it on my host maschine a i7 "adler-lake" Laptop. Here is what i did:
|
maybe you started the container with a different user? the mounted directories are not writable. Try restoring the ownership:
then recreate the container:
|
Also this line:
is not ok in your system, you should replace "D10" with "sndrpihifiberry" or even hw:0 considering you have only that audio device. |
Yes all of this is true. But why is the tidal extension not found? "Ignoring config section 'tidal' because no matching extension was found" |
uhm, that in fact is quite strange. Is your o.s. 32bit or 64bit? I assume it's 32, am I right?
I have tried the solution on pi4 running raspberry pi os arm64 and osmc on pi4 again. The latter is 64bit kernel and 32bit userland I believe. So maybe I never tried a plain 32 bit system. If you confirm your system is 32bit with the output of that command, I might be able to try and reproduce the issue in the next few days on a 32bit moode installation. Of course on a Pi3, not a Pi2 as I don't own one. |
I also see you have created the docker-compose file in the home directory. That means that the config, cache and data directories are created directly under the home. I'd suggest to create a subdirectory under home so the mounted volumes are separated from the directories in the home. |
Ok, so the problem is that your directories are not available before the container is created.
As an alternative, you can change the compose and avoid the "user" property, and use PUID and PGID instead. This way, the folders are chowned while the container starts. Your compose would become:
|
Please also open port 8989 which is needed for pkce authentication. After that, you might also remove that exposed port. If you use LOSSLESS and HI_RES, but not HI_RES_LOSSLESS, that port is not necessary. Just watch the logs, you will see a url, open it with your browser, authenticate with Tidal and authorize the app. |
With the folder in place. Also no tidal plugin available.
|
which user are you using? try:
and post the output. If you are not uid 1000, some values must be changed. |
Ups the plugin is under "browse". The error message is not correct the plugin is there. Thanks for your help. |
so it is working? |
yes its working also with named volumes or folder self created. |
Ok excellent news. Feel free to open other issue, maybe if you want to configure hires. |
Hello, thanks to your ticket, I found a few issues with user mode specifically. user: "1000:29" was working fine, but setting PUID/PGID/AUDIO_GID was not working properly. |
Also, I wrongly suggested to set PGID to the audio group.
you can find the gid of the audio group using the command:
|
Hello, i use the compose example to test mopidy with the tidal plugin. On start the log says
The text was updated successfully, but these errors were encountered: