GioF71

Hello, the default setting should enable the first unfolding on the application. Unfortunately I don't own a MQA dac so I cannot try verify if other combinations actually work with mqa-enabled DACs. Maybe open an issue on the github repo, other users with MQA dacs might help you.

did you clone the repository using sudo? if so you can just remove the directory with sudo rm $HOME/tidal-connect and clone the repository again. Maybe keep track of the current .env file

uhm, it's probably ok because it's the only sound card available. Maybe you can open an issue here so we don't hijack this thread

hello, is the repository updated? I would expect a asound.conf file to be created and displayed. To update the repository: cd $HOME/tidal-connect git pull docker-compose up -d --force-recreate

are you using a Pi4 or Pi3? Also, wired or wireless? Maybe look at the box status, with something like htop sudo apt-get update sudo apt-get install -y htop htop

Ok then, let's then have a look at tidal connect logs: cd $HOME/tidal-connect docker-compose logs

From what you write I understand you are using a Pi4 with a usb dac, is that correct? Can you enter the ssh shell and post the results of: cat /proc/asound/cards and lsusb also, with regards to using your device with BubbleUpnp, it might be useful to have a look at the mpd logfile, it should be accessible using cat /var/log/mpd.log although I don't know how Moode sets the log level. It's worth a look anyway

With all my current devices (other than the WiiM pro acquired just a few days ago) I run all my audio applications as docker containers. I never noticed any difference in audio quality but otoh I would never go back to installing packages directly into the distribution. In time I have built different container images, for example for Squeezelite, MPD, upmpdcli, minidlna, etc

Hello, mine is just a script, which mostly focus on easily selecting the output device. The contents are in the docker image here and in the related github repo.

Hello, the tidal solutions you can run on a raspberry pi are all based on a software sourced from ifi, which will probably never be updated. In time, some maintainers have been able to keep it running by updating certificates (external to the app binaries). But I believe that it needs to be acknoledged that these solutions might stop working one day. Not ifi's fault of course: they surely keep their software updated. But the software that has been "sourced" is at a specific version and will probably be stuck where it is. If there will be changes in Tidal which will require changes to the code, those changes won't be available. I would keep any considerations about the sound quality out of my posts, especially when MQA is involved. Also, my gear is not that resolving anyway, so I pass here :-) Edit: typos

Ok alexopth1512, as I mentioned, I was not saying anything about the maximum capabilities of Linux, I was only speaking of the "Tidal Connect" solutions that are currently available on Linux. Specifically I was answering to this post. Currently afaik the only way to see 192kHz in the DAC is to have a MQA-enabled dac. About this: For the ifi-connect I have a Raspi 5 with Allo Hat hat but I use the USB. And last thing of course, if you use coax or BNC you cannot go over 192. What happens if you connect to a non-mqa enabled dac? I believe the maximum you will get when using Tidal Connect will be 88.2 or 96, so the first unfolding, performed by the ifi software player itself. Also as you imply, if you disabled MQA decoding on the tidal connect software, you should only get 24/44 and 24/48 on a non-mqa cable dac.

Hello @alexopth1512 and thank you for your comment. I never said that linux cannot stream up to 384kHz. I have my Squeezelite and MPD based configuration with 4 and 8x upsampling working flawlessly on linux. Linux on its own cannot decode MQA, at least not at the o.s. level. But that ifi-sourced application does the first unfolding, to 88.2/96kHz, when if plays MQA tracks. The rest of the process is performed on the DAC side. You can verify it by using a DDC like a Topping D10. If that's not what you meant, maybe can you elaborate the sentence "And MQA works like a charm"? Thank you

Hello "Belinteo", congratulations for the nickname, I might get what it means :-) Back to the questions, well it's all based on observations. If I use the Tidal Connect software from ifi (those that has been acquired from a repository that has gone public, probably unwillingly), when I play one hi-res playlist, I see 96KHz on my DAC. When I play the sample playlist through my tidal plugin for upmpdcli, which is based on python-tidal (not authorized by tidal), the dac shows 48kHz. When I stream from BubbleUpnp to upmpdcli on the same Raspberry Pi, I get 192kHz. When I stream the same track to my newly acquired WiiM Pro, using either its Tidal Connect or BubbleUpnp, I get 192kHz. If again, I use my tidal plugin for upmpdcli and play to the WiiM Pro, I am back to 48kHz (not 96 probably because I did not enable the beta MQA decoding). Those unofficial Tidal Connect solutions might stop working at any time. Ifi's software has been probably updated over time and it's no surprise it works at 192kHz like "alexopth1512" says, assuming he speaks about a genuine Ifi device. Edit: I forgot to mention that none of my DAC support MQA

Hello, as far as I know, there is now way to stream content higher than 24/44.1 and 24/48 to these solutions which are based on that Ifi software. Also, MQA content seems to be going away over time, so the solution is going to be viable for the HiFi plan only (16/44.1 FLAC). If you want to stream Tidal HiRes Lossless to a Pi, a currently working solution is upmpdcli, which is embedded in Moode and Volumio. Then an Android App like BubbleUpnp, which fully supports Tidal HiRes Flac, will be able to stream to it. I am using this solution on a daily basis and it works very well. I understand that Audirvana also has Tidal support and can play to UPnP devices, so this might also be a good solution as well.

About exclusive use: yes it is expected, it's how the underlying application works, it is closed source, so there is nothing we can do about it. As per the moode without ssh question, I believe having an ssh connection is mandatory. Afaik there are no alternative ways for installing the necessary packages on Moode, and also no alternative ways of controlling the service. Anyway the service starts automatically and, until you connect your tidal app to tidal connect, does not exclusively lock the audio device.