Play on rAudio: [WebsocketServer Start Error] Address family not supported by protocol #21
Comments
|
Hello, I understand from the github repo that rAudio is based on Arch Linux Arm, which I never tried. Thank you |
|
I will try on Volumio 32bit. And more question, how can I set config to degault--playback-device "default". Not use CARD_INDEX number. |
|
Hello, Volumio afaik is still on debian buster (quite old now), but still it should work as long as you get docker and docker-compose installed. About the question, can you show me, in a scenario with more that one card, how should I configure for the selection of "default". In the end I need to put an index to the custom asound.conf file that is generated when the container starts. |
|
Volumio 3.449 work Ok, I will make new SD Card rAudio and recheck. Attaching to tidal-connect |
|
ok good... will be waiting |
|
Hello, do you have further information to share? |
|
Hello, I just renewed Tidal for this month and tested the change, it's on the main branch now. |
Yes, it's working for me on volumio. |
|
Good to hear... but did you solve the issue when running on rAudio? |
|
Hello, can you please give a feedback about this issue? Thank you. |
|
I can't run Tidal Connect with rAudio 64-bit, even when I add it directly (without using Docker) on rAudio 32-bit. All the libraries are available, but it still reports a WebSocket error. Sorry for the late response! |
|
Is there a way for me to try and reproduce the issue? Thank you |
|
I believe the rAudio kernel does not support IPv6 or is not configured for IPv6, leading to the Tidal Connect error: asio listen error: asio.system:97 (Address family not supported by protocol) [WebsocketServer.hpp:67] [WebsocketServer Start Error] Address family not supported by protocol |
|
ping6 ipv6.google.com |
|
Ok, maybe you can try disabling IPv6 in sysctl.conf. Then
Maybe this can help, if disabling IPv6 is acceptable on your solution. |
|
Sorry for my unclear writing. rAudio doesn't support ipv6, so I believe Tidal Connect isn't working correctly. I tried to install/configure ipv6 for rAudio, but it was not successful. |
|
Hello, I was running tidal-connect on Raspberry pi os 64 bit, with ipv6 "disabled" with the above settings in sysctl.conf, and it was working properly. That is bad, but at least we reproduced your issue. The problem is that, even if we eventually came to the conclusion that Tidal Connect isn't working properly with ipv6 disabled, there is little (or nothing) to be done on my side. You might already know about how the software included in the docker image was originally sourced, and crucially about the fact that that software is not open-source and will probably never be. Tidal is probably not bothering with this stuff because, in order to make use of it, we still need to pay for the premium account, and also because there are probably people who are willing to pay the account fees just because they can use their Raspberry Pi as a Tidal Connect device. As an alternative, you might want to consider the new Tidal plugin for Upmpdcli (disclaimer: I am the author of the new plugin). This would give you access to playing Tidal to upmpdcli (and ultimately to mpd), which you already include in rAudio from what I understand. Or, as another alternative, is there a chance that you can consider using Raspberry Pi OS (or one with a kernel with ipv6 support) as the base o.s. of your solution? |
|
Thank you for providing detailed information about your experience with Tidal Connect and IPv6 on Raspberry Pi OS 64-bit. I am just an enthusiast exploring sound options based on Pi. I tried running Tidal Connect on 32-bit OSes over a year ago (Volumio, MoodeAudio, piCorePlayer, RoPieeeXL, SMPD). All worked without issues apart from requiring the necessary libraries. RoPieeeXL used ArchLinux, but they recently closed SSH access. Until RuneAudio was rebooted with the name rAudio (also using ArchLinux). Many believe ArchLinux provides better sound, including myself. However, efforts to run Tidal Connect faced IPv6 obstacles as we have seen. Perhaps I should contact the rAudio project leader to understand how to activate IPv6. piCorePlayer and LMS have a Tidal plugin option to display albums, search, and play Tidal directly within the LMS interface. For now, I accept using it within LMS + Squeezelite on rAudio. I love Tidal Connect for its convenience and quality. Thank you for the suggestion about the new Tidal plugin for Upmpdcli. When comparing Squeezelite and MPD, I prefer using Squeezelite. Your work is excellent, especially the value it brings when we can operate on a 64-bit platform. Best regards. |
My pleasure :-)
The new tidal plugin on upmpdcli has more features, allows navigability for similar artists, artist radio, top tracks, it is currently in active development. I would ask you to give it a try if you have some spare time to dedicate. Plus, considering recent changes on upmpdcli, it is now possible on LMS, to successfully stream from upmpdcli media servers running tidal/qobuz plugins. It did not use to work because upmpdcli was generating URLs with query parameters which LMS would not understand, now it is using paths. This is new in version 1.8.3 of upmpdcli.
I am also a user of Squeezelite, I love it as well!
Thank you for the kind words. If you can, please consider starring the repo. Thank you! Edit: arguments -> query parameters |
Of course I understand Tidal Connect cannot be replaced by LMS or upmpdcli with plugins, it serves a slightly different use case. |
|
This sounds really intriguing, and I'd like to give it a try when I have some time. Could you guide me on how to try it? Additionally, I have some friends who share the same interest in listening to music on Pi. Would it be okay to share this with them? By the way, knowing that you like using Squeezelite. Recently, I've been working on a few things on LMS , and this is one of them. If you find it interesting, you can give it a try and customize the background according to your preference. |
|
And something else: |
sure. You can start with the discussion here where you will find the docker compose file. The container image runs on amd64, arm 32 and 64 bit. Start the container as usual and you should be good to go.
yes sure, of course. |
|
If you experience any difficulty installing/configuring this server, please report it on the upmpdcli repository as an issue, so that I can fix the code and/or improve the documentation. |
|
Also it is needed for me to mention that the plugin relies on this implementation of the Tidal API. |
The skin looks nice. Is there a way to install it on a debian/ubuntu box where logitech media server is installed using the official .deb file? |
|
Thanks @GioF71 and @lovehifi ! With your information, I was able to get it working on the rAudio x64bit rpi4. |
You can change the skin for LMS on any OS as long as you find the location containing the CSS file and the image directory, similar to: \usr\share\squeezeboxserver\HTML\Default\slimserver.css Note that the location of squeezeboxserver may vary depending on the OS. Someone on the slimdevices forum has assisted me in turning them into a plugin, but I haven't had the time to do it yet. |
Good news, thank you. I will reinstall. |
Hello @SejaMarginal thank you for the changes. I wrongly assumed that the issue was in the binary itself (or in some statically linked library), but luckily that was not the case. Are you going to publish an updated image? Thank you, great work! |
Sorry, I deleted the message. I just realized that I installed Docker incorrectly earlier. sudo apt-get update |
|
Thank you @lovehifi I will correct immediately |
|
Uhm, doesn't the README file already say |
|
Ah, my bad: |
|
It's working on my rAudio 64bit on a rpi4 with an external DAC. Thank you, @GioF71 |
|
Ok as for me... what about with ipv6 disabled? |
|
It didn't work when I disable "ipv6.disable=1" on /boot/cmdline.txt But my old installation of rAudio didn't come with the ipv6 disabled on cmdline.txt. I don't know with a new and clean installation of rAudio. |
same as me
So maybe I can drop that branch. Thoughts? |
|
No, I think you can merge it on master. It's working for me with this branch I have one error on log, but it's working. |
|
Yes but also with the main branch, everything should work if ipv6 is not disabled. Can you test it? |
can you post the output of
and maybe
Thank you |
|
It's also working, thanks |
so you should probably use
please let me know if this solves the error... it's probably falling back to the default output with the current configuration you are running... |
|
Sorry, I've didn't put the complete output. My bad. I think it's an error that we can ignore. |
|
I flash new IMG rAudio-64bit-20230918.img.xz. Go to the Addon menu and update the new version. Install Tidal Connect Docker repository from https://github.com/code-SL/tidal-connect-docker. I have created a simple script to install Tidal Connect from your repository, with a minor modification using rAudio's default sound card. I successfully played music from Tidal Connect to my rAudio Pi 4. I have stored them here: |
How to change sound card, dns etc. in your script? I need to change dns to address of my router, because when i use google dns it won't work for me. I was had same issue on moode. |
|
Hello, this can be done in two ways. Or you can add this to the .env file: In both cases you will need to restart the container with a
|
|
For the sound card, it can be specified by name or by index. You can find the name or the index of your sound card using:
or
Generally using the card name is more reliable, at least IMO. Arguments for configure.sh: -n -> specify card by name Alternatively directly in the .env file, you can set CARD_NAME or CARD_INDEX respectively for sound card name or index. Example: assuming you want to use X20, you should specify
or
when using configure.sh. Alternatively if you want to directly edit the .env file, you will want to set
or
Always restart the container when doing those changes. |
Mainly i need help with DNS. The dac working with default setting. But audio stops after few seconds. lovehifi script is different than your and ./configure.sh not working. Where is .env file? |
|
The .env file is not in the repository because it represents your own settings.
and there you can set the desired values. If you post the output of
and
I might create the configure.sh command line for you.
|
|
@Maverick565 I updated the README file to change the sound card, DNS, etc. The setting --playback-device 'default' on rAudio works well with my USB DAC and I2S DAC. |
Thank you! Now everything works. |
|
Edit: Playback still stopping after some seconds. |
|
@Maverick565 who are you asking to? I'm confused. If you're using my repo, please send me the logs, using
|
I'm using @lovehifi repo. |
|
ok in that case, you should proceed with an issue on his repository. |
|
Regarding configuring the sound card and .env after installing Tidal Connect Docker (from any repository, in my opinion), as I mentioned in my previous response. @Maverick565 You can also delete the current tidal-connect-docker to install from GioF71's repository to check the audio pause issue. Thank you, GioF71. This issue has been resolved. I think it can be closed. |
|
About audio pause issue, @Maverick565, please create a new issue, and remember to post the container logs. It is probably as you mentioned dns-related. |
Please help me check! Cannot connect to rAudio (Pi 4)
rAudio: https://github.com/rern/rAudio
Get log: [WebsocketServer Start Error] Address family not supported by protocol
rAudio:~/tidal-connect # time nslookup tidal.com
Server: 192.168.11.1
Address: 192.168.11.1#53
Non-authoritative answer:
Name: tidal.com
Address: 13.35.166.34
Name: tidal.com
Address: 13.35.166.55
Name: tidal.com
Address: 13.35.166.123
Name: tidal.com
Address: 13.35.166.88
;; ;; Question section mismatch: got 34.166.35.13.in-addr.arpa/PTR/IN
;; communications error to 192.168.11.1#53: timed out
;; ;; Question section mismatch: got 34.166.35.13.in-addr.arpa/PTR/IN
;; communications error to 192.168.11.1#53: timed out
;; ;; Question section mismatch: got 34.166.35.13.in-addr.arpa/PTR/IN
;; communications error to 192.168.11.1#53: timed out
;; no servers could be reached
real 0m15.400s
user 0m0.028s
sys 0m0.033s
rAudio:~/tidal-connect # cat /proc/asound/cards
0 [sndrpirpidac ]: RPi-simple - snd_rpi_rpi_dac
snd_rpi_rpi_dac
rAudio:~/tidal-connect # ./configure.sh -i 0 -f "Pi4" -m "Pi 4 rAudio"
card_index=[0]
card_name=[]
Setting FRIENDLY_NAME to [Pi4]
Setting MODEL_NAME to [Pi 4 rAudio]
MQA_CODEC not specified
MQA_PASSTHROUGH not specified
SLEEP_TIME_SEC not specified
DNS_SERVER_LIST not specified
Setting CARD_INDEX to [0]
Final .env file:
FRIENDLY_NAME=Pi4
MODEL_NAME=Pi 4 rAudio
CARD_INDEX=0
CARD_NAME=NOT_SET
rAudio:~/tidal-connect # docker-compose up -d
[+] Running 1/1
✔ Container tidal-connect Started
rAudio:~/tidal-connect # docker-compose logs
tidal-connect | FRIENDLY_NAME=Pi4
tidal-connect | MODEL_NAME=Pi 4 rAudio
tidal-connect | MQA_CODEC=false
tidal-connect | MQA_PASSTHROUGH=false
tidal-connect | CARD_NAME=NOT_SET
tidal-connect | CARD_INDEX=0
tidal-connect | Set card_index=[0]
tidal-connect | Creating sound configuration file (card_index=0)...
tidal-connect | Sound configuration file created.
tidal-connect | defaults.pcm.card 0
tidal-connect | pcm.!default {
tidal-connect | type plug
tidal-connect | slave.pcm hw
tidal-connect | }
tidal-connect | Starting Speaker Application in Background (TMUX)
tidal-connect | Sleeping for a while (3 seconds)...
tidal-connect | Starting TIDAL Connect ...
tidal-connect | STARTING TidalConnect services, version: 1.1.3
tidal-connect | Expression 'GetExactSampleRate( hwParams, &defaultSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 895
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
tidal-connect | ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
tidal-connect | Cannot connect to server socket err = No such file or directory
tidal-connect | Cannot connect to server request channel
tidal-connect | jack server is not running or cannot be started
tidal-connect | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
tidal-connect | JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
tidal-connect | [2023-08-31 04:12:00.571] [tisoc] [critical] [DeviceInfo.cpp:56] ioctl error. ret=-1, errno="No such device"
tidal-connect | [2023-08-31 04:12:00.571] [tisoc] [critical] [DeviceInfo.cpp:57] [ASSERT] generateDeviceId(0)
tidal-connect | [2023-08-31 04:12:00] [info] asio listen error: asio.system:97 (Address family not supported by protocol)
tidal-connect | [2023-08-31 04:12:00.592] [tisoc] [error] [WebsocketServer.hpp:67] [WebsocketServer Start Error] Address family not supported by protocol
tidal-connect | STARTED TidalConnect services.
The text was updated successfully, but these errors were encountered: