How to turn on service? #10
Comments
|
Hello, I am not sure I understand your question. Let me know if this helps.
|
|
Edit: Updating id_certificate still won't help. Stopping after 10-30 secs. |
|
I think here is problem with rtc clock or packages. On volumio this script working. I don't know why on Volumio works, but on Moode not. I'm running on Moode 8.3.3 32 bit on RPI4. tidal-connect | STARTED TidalConnect services. |
|
Hello, from a quick search, I found this link: https://support.hifiberry.com/hc/en-us/community/posts/360013667717-Tidal-Connect-#comments One user posted an issue similar to yours. the suggested solution has been to set dns to 8.8.8.8 (google). I dumped that setting because the container was working for me even without it, but maybe it does depend on how you set your dns on your Pi. You might add Google DNS on the container or at the host level tuning /etc/resolv.conf. Please le me know it this solution works. Cheers |
|
I'll try it tomorrow. |
|
I set dns to 8.8.8.8 and 8.8.4.4 by changing in moode settings and etc/resolv/conf but i have still same errors. Even changing dns on router and phone don't help. https://drive.google.com/file/d/1GI4a-Y13xp27_488VZI5Rf9TrMBbRaTq/view?usp=drivesdk |
|
Hello, sorry to hear that. I just renewed my subscription (HiFi) and I am playing songs with no issues. The device you are using (Pi3, Pi4, etc) The DAC are you using. Is it a hat like the hifiberry or an usb dac? Do the other features of Moode play correctly on the same DAC? For example, some radio from their selection. Then, maybe a few details about your audio setup as seen from moode's point of view: you might want to post the output of these commands:
Last thing that comes to my mind is system architecture: are you running moode 32 or 64 bit? From a terminal, you can run While I am typing, I have played from Tidal to two instances of Tidal Connect, one is a Moode Audio 64 bit on a Pi3 with a Hifiberry DAC+ Pro, the other one is OSMC on a Pi4 on a Topping D10 USB DAC/DDC feeding another dac via coaxial. No issue whatsoever, and I did not set the dns. About dns, can you post the contents of the /etc/resolv.conf when you tried this change? Edit: just typos |
|
Also the contents of the ".env" file on your tidal-connect directory might be useful. And maybe the command you used (the parameters you passed to ./configure.sh). |
|
Last thing, are you using wifi or wired? |
|
Last thing again, check if you are updated with the upstream docker image.
then restart:
|
|
Also sd card size and free space? |
|
|
|
|
uname -a |
|
Env file: |
|
Aplay- L: moode@moode:~ $ aplay -L |
|
Full log:
|
|
Everything looks ok still tidal connect seems unable to lock the card. Try this: watch cat /proc/asound/card1/pcm0p/sub0/hw_params When Tidal Connect is not playing (moode not selected as tidal output), it should display "closed" Tomorrow I can try a usb dac on moode, and see if I can make it work. p.s. moode is 64bit same as mine. The difference is that my hat is at index 0, your dac is at index 1. There is hope I guess, we'll see! |
|
Edit sorry I see it's a Pi4, so this comment could even be deleted |
|
When tidal connect playing shows this:
But after playback stops after some seconds, it showing closed. |
|
Here is lsusb:
|
I downloaded from this link so i don't know why it's 64 bit, but upper version 64 bit doesn't work good on my RPI.
|
|
ok let's see how moode sets up alsa, considering that moode itself works. Can you post the contents of these commands:
Also maybe take a screenshot of moode's Audio settings page... let's see if we can find something |
|
Does your pi get enough power? You can check with "dmesg -T" and see if there are messages like "Under-voltage detected". Also you can run vcgencmd get_throttled Source this page |
|
Had another look at the container output and the lines with "GetExactSampleRate" got my attention. |
I'm using original raspberry wall adapter 5.1v 3a. To raspberry usb i have only connected Fiio K5 Pro dac which has its own power supply. It could even play DSD files from nas server so i don't think the power is problem. But i will check that tomorrow. On same raspberry with same power supply but with volumio, this script working. So i think it's something with settings/packages. Volumio natively supports tidal connect and i think it's have a packages for it, which Moode don't. It behaves similiar to situation when id_certificate was outdated. But when i updated certificate it works perfect on volumio. I think there is problem with RTC clock and/or problem with SSL authentication of certificate on Moode. I don't know. |
|
Ok if the ptoblem is on the certificate, it might explain why it plays for 30 sec (or so) then stops. Usually the first few seconds are sent unencrypted in order to give some time for buffering or for fast playback start. Is the time reported by your pi accurate? I see you talk about RTC clock. The raspberry pi does not have a RTC clock and it relies on external NTP (or similar) in order to have the correct time.
amd compare with the web page, e.g.
If the difference is notable, this might be the issue. I have been having this problem for a while: the pi would not sync to the current time for a long time. Then I tried disabling ipv6 and this solved the issue. Recently instead, I enabled NTP on the router (it's an OpenWRT) and then set the NTP to 192.168.1.1 (the router ip) in the Or, as the last option/doublecheck: can you try with a mint Raspbian install, with docker and tidal connect alone? That would avoid any doubt on Moode and create a simpler (hopefully) scenario. |
|
|
it's incredible, everything seems to be ok but nothing works... |
moode@moode:~ $ cat /etc/alsa/conf.d/_audioout.conf This file is automatically generatedby the MPD configuration page.######################################### music_directory "/var/lib/mpd/music" decoder { input { resampler { audio_output { audio_output { audio_output { moode@moode:~ $ |
I have this too. There is no hope. |
|
Did you try removing the old library? Because alternatively you can stay with raspbian and install mpd, upmpdcli, librespot, squeezelite etc via docker, unless you specifically need the Moode gui |
|
I was trying a one time again with Ifi Zen dac but without success. Rather that i would back to Volumio where this script working and lirc for IR remote controller has easy installation from plugin shop. I wanted to switch to Moode because Volumio had trouble playing music from the NAS. And Moode has slightly better sound. |
I was burn new Moode image, and i'm installed aptitude. I have same libssl version. |
|
it's really weird. |
|
I watched the video again, it seems to me that starting tracks is very sluggish at least when you use tidal connect on moode. |
|
I pushed a change to the main branch, you can get it with
In any case I changed docker-compose.yaml and added google dns, if you want to try Edit:
after changing the compose file.
would unconditionally recreates the container. Maybe you knew that already, sorry if this is the case |
That would be difficult because i have only 32gb cards, and with my internet upload speed this will be very long process and i don't know which hosting site have that much space for free. |
|
Well the actual size should be much smaller, the compressed file will be smaller. Empty space will be collpsed to nothing in the final file. df -h shows for your root ( In my moode, here is the situation: But I am using additional docker images which are responsible for a size increase: I expect your used space to be less than 4GB before compression, unless you have music store on the microsd (unlikely). |
|
Do you know any windows software which can do it? |
|
I am trying Win32diskimager with a 16gb microsd. It is creating an uncompressed file which will be 16GB in size, then you just need to zip it. |
|
ISP is google in this DNS test. |
Ok, i will send it. |
|
Perfect |
This still don't help. |
|
OK I downloaded the file and I am flashing the image. I will try it tomorrow. Can you tell me the ssh password? |
|
user: moode I set ip to DHCP before ripping. |
|
Hello, I tried your image yesterday and this morning. I would try checking dns. Install dns utils with
Then try:
My output: Let's see how it works on your side. Maybe you can compare with the result on the Raspian box if it's still available. |
|
And may also api.tidal.com |
|
`moode@moode:~ $ time nslookup tidal.com Non-authoritative answer: real 0m0.241s Non-authoritative answer: real 0m0.146s |
|
This is crazy. I changed DNS in docker-compose.yaml to address of my router and now it's working 😊 |
|
It's crazy that it's always DNS!!! |
|
Can you take a few moments to test a branch of the repo? Here are the commands: Keep in mind that
change "192.168.1.2" to the address you used before, might be 192.168.0.1 possibly. Also change friendly and model name to your taste. Thanks! |
I tested it and it works. Thanks for all your help! |
|
On router i changed from google dns to my ISP dns address and it still works. So there is no need to change DNS to Google on the router. But only set in Moode as DNS, address of router. |
|
Even better |
|
So the change is now pushed to the main branch. If you want to switch back to the main branch: Close the issue is everything is OK. Also if you want, consider starring the repo! |
Hi!
I was installed this on moode audio 8.3.3 but after install it doesn't showing in tidal apps.
The text was updated successfully, but these errors were encountered: