No volume control via phone when streaming Tidal from phone app #136
Comments
|
Hello Matt, can you post the output of the following command: So we can check what happened during startup.
and
|
|
Hi, sure... docker compose logs |
|
Ops, sorry, the device is "SoftMaster", not master. So there is hope. I need to change the code of entrypoint.sh in order to avoid this false positive! Hang on... |
|
Hello, as a stop-gap solution, I have create a custom asound.conf. So do the following: Cross your fingers because I don't have your exact DAC, so I might have done a mistake. But I tried everything then I replaced "D10" with "Audio". Let's hope this works! |
* No volume control via phone when streaming Tidal from phone app #136 * No need to escape single quotes
|
Thanks for your effort mate! You rock... It does work indeed! |
|
Good to hear! I have also made changes so that the script does not wrongly believe that there is a "Master" control when there is a control that only contains "Master". If you want to try: Should this not work, you can always execute the instructions from the previous post. This feedback might be useful for other users, so thank you in advance if you want to try. |
|
The previous post was edited... be sure to include "-n Audio" in the configure command |
|
With this command from yesterday it didn't work at first but then all of a sudden it did... I don't really know what caused the change. With so far it doesn't work. |
|
Hello, did you also execute the initial part? I just tried this:
I used Thank you |
Yes I did... And I tried again just now. Won't cut it... |
|
I hope the previous configuration which uses the custom asound.conf still works. |
|
Maybe when making changes, it might be a good idea to force container recreation. And maybe watch the logs. Sometimes the binary core dumps, and the script waits up to 30 seconds before restarting, configurable with RESTART_WAIT_SEC in the env file. I need to add a configure.sh switch for this feature as well. To start forcing container recreation and watch the logs in a one-liner, you can do:
|
That leaves me with no sound at all... I then tried again with this
followed by
and now everything is up and running incl. changing volume via the rocker on my phone! I reckon you just earned another bucket of coffee!! 🥇 |
|
Ok S32_LE is not needed for your DAC clearly :-) But isn't this command
the same command that failed before? |
|
Yes
gave me sound and volume control once - after a while. So maybe
was needed to re-initialise the entire business and get it working from the get go. In the meantime I managed to replicate my success on the 2nd Pi which is attached to my stereo in the living room! Anyway, now I won't touch any of them for a while. Thanks again for your awesome support! |
|
Ok I understand the need for stability! I invite you, please have a look at mopidy-tidal here, using my image. Of course have a look at the project references, they are mentioned at the first link. User tehkillerbee is amazing! With that solution, you will have a web app which can play Tidal in full hi-res flac up to 24bit/192kHz (not mqa like this one) to your USB Dac. And it's open source software. |
|
Ah forgot to ask, please star the repo if you can. |
|
Hi, me again... So you made me curious as to whether my almost 54 years old ears will be able to hear the difference between FLAC and Hi Res... I have installed Mopidy and Mopidy-Tidal. Unfortunately I'm stuck right at the end of the instructions when it comes to logging in with Tidal. I have edited my /etc/mopidy/mopidy.conf as instructed but
won't give me any link Also I can't access the Mopidy Web Interface, neither port 8989 nor 6680 do anything. has rejected the connection. Would you be so kind as to point me in the right direction even though this is not the Mopidy support department or even your project ;-) Cheers, |
|
Hello, sorry but I did not give enough information. I forgot to direct you to an example docker compose file which would use my docker image. I assume here that you'd prefer to use a docker image. So...
If the first command shows that your uid is 1000, and the second shows that the audio gid is 29, the following instructions should be good to go. Otherwise you would need to replace 1000 and 29 with your values.
I hope this helps! |
|
You were quite close with your effort. The mopidy was not reachable as it was exposing the port only on the localhost (127.0.0.1), that is why you could not reach the web interface! |
|
Wow man, you really rock... Thanks a lot for your guidance at stupid o' clock! I really AM a Linux and Terminal noob and I get lost very easily as I'm lacking a lot of basics... Unfortunately even after carrying out the steps you listed above the output is still the same. I still can't access the Mopidy web interface. I then carried on reading GioF71/mopidy-docker and even fail to carry out ./local-build.sh because I don't know what's meant by "switch to the root directory of the repo". Somehow I think I'm mixing up two sets of instructions here because even though I had installed docker at some point I can't remember ever building a container. I was still stuck at the end of thekillerbee's instruction set... Kudoz for your patience! |
|
Hello Matt, sorry it didn't work. Let me try answer your questions
Then you can try again to restart the container using:
If this has success, we can then proceed removing the packages you installed, as a final step. |
|
Oh boy... I think I made a mess :-P |
|
Yeah... docker-compose seems to not be working. Try reinstalling it with
|
|
Stuck in the mud |
|
So strange... Have you tried rebooting? |
|
Well, the oldest question in IT support history did indeed take us a step further... Not quite there yet though Do you think it's better so start over? |
|
First version of the scrobbler is available here. |
|
hi |
|
I checked that commit and compared to the current head... there are no relevant changes. Mostly I have added presets, tried to remove the "version" property from docker-compose then reverted the change cause it caused issue with non-updated o.s., but no changes to the main code. Can you post your .env file and the container logs?
Thank you |
|
container_logs.txt Thank you !!! |
|
Hello, I see you did not specify any of CARD_INDEX and CARD_NAME. Back to us, you should be good to go by just specifying CARD_INDEX=0 or CARD_NAME=sndrpirpidac in your .env file. |
|
I have already tried. |
|
Ok, it does not work, but for a different reason. See the logs: �[36mtidal-connect |�[0m Cannot enable softvolume, a 'Master' control already exists for the device at index [0] Your device already has a control device named 'Master', so unfortunately we cannot enable software volume on this app.
it will probably return a line, which is what does not allow us to enable software volume. This app can only use a control which is named "Master". |
|
Would you happen to have a quick suggestion on what to change? :) |
|
Are you sure about this? I need some elements to work on... that paper I linked seems to say that if there is a Master control, we cannot enable a software volume. |
|
If you think it's something I changed in the code, maybe revert to that commit and see if softvol works. If it does, we have something to investigate. |
|
I already tried to revert ... it's not helping... |
Then there must be something else. Anything in /boot/config.txt? overlays, etc ... |
|
I haven't updated the OS and haven't rebooted :) |
|
uhm, I really can't figure out what might be the issue. What is the device you are using? |
|
when you reverted to that commit, did you re-create the container? If you didn't already do that, I would try doing a docker-compose up -d --force-recreate Unless you are positive that the container was actually recreated. |
|
hi |
|
Feel free to let me know if you need more logs, etc. |
|
Not a lot more comes to my mind... have you tried adding: CARD_FORMAT=S32_LE ? |
|
Is Tidal Connect mandatory for you? Would you try a upmpdcli media server and playing back to mpd+upmpdcli? All could fit on your moode device and would support full hires, while this Tidal Connect tops @96kHz (except mqa unfolding on a MQA-enabled DAC, but that's different from full hires). |
|
S32_LE is not supported... |
|
Sorry it does not work, I am really out of ideas here. Why do you say the sound quality is better? In my option Tidal Connect is the same at best, and is more limited. If you think that network package loss with UPD happens with UPnP, fear not, it does not happen in this case. Network discovery uses UPD, but the audio stream comes reliably with https (so tcp). |
|
Just to clarify... the problem with tidal-connect is "only" the missing software volume, of it does not work at all for you? |
|
The soft volume was not worked by default |
|
The main advantage of tidal-connect service is that the audio stream is transmitted from the server directly to the device without extra conversation Hello, the same happens when streaming using upnp! No conversions |
|
About your device, do you have a link or some information about it? |
|
As I see here, maybe try and post the output of: aplay -D hw:0 --dump-hw-params /dev/zero so we can see what format your card can support. |
|
Hello @MattRimkus, I am closing this, feel free to reopen or open another one if you encounter any issue. |
Hi,
I managed to get Tidal Connect going on my Raspberry Pi 4B under Volumio which is attached to an iFi Zen DAC V2 via USB.
Everything works fine apart from the volume rocker of my Samsung Galaxy S24 Ultra having no effect when I try to change the playback volume.
In Volumio choosing Hardware, Software or None under Mixer Type won't make any difference. I still have to change the volume via the Zen DAC's knob.
Thanks for your effort!
Kind regards,
Matt
The text was updated successfully, but these errors were encountered: