-
Notifications
You must be signed in to change notification settings - Fork 432
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
[WIP]: Tidal connect plugin #399
base: master
Are you sure you want to change the base?
Conversation
- update the unicode quotes to ascii so copy and paste works - add link to dac2 hd debugging issue - add link to issue where debugging for dac2 hd occured and was subsequently fixed - add screenshot and description of alternative dt overlay option Connects-to: #377 Change-type: patch Signed-off-by: Aaron Shaw <[email protected]>
Your landr site preview has been successfully deployed to https://landr-balenalabs-repo-balena-sound-preview-399.netlify.app Deployed with Landr 6.13.1 |
Tidal connect application help output...
Full error output running tidal_connect_application with no flags...
Full error output when running with all flags...
Output of ifi-pa-devs-get...
Output of pa_devs...
These appear to be the key error messages stopping it from working:
This is the output of the speaker_controller_application which requires
|
Well - that was easier than I thought... Added dbus stuff in this commit and it now works!! 2246118 Now just need to test it with a DAC... |
Good news! It is working (albeit intermittently and with no volume control)... WhatsApp.Video.2021-01-04.at.00.59.33.mp4Also still getting some warnings / errors...
|
Volume control issue. Gives the above volume control on Android phone but doesn't actually cause the volume to go up or down This is from the electron desktop app on MacOS - also doesn't work. I assume the tidal_connect_application script is receiving the volume commands (doesn't seem to be a way to tell - no log output as far as I can see). But perhaps I am missing something. |
Ok, just discovered that the speaker_controller_application gives some playback info: And crucially - when running, the volume control works perfectly! Happy days 👍 Error message when you close the application:
|
Receiving the following when trying to push to balena:
|
@asifjahmed what Pi version are you on? Also, do you have the error message where it failed higher up where it should say the specific error? Note that this is a work in progress so isn't expected to work properly just yet. |
Rpi 4 Model B+ Totally understand it is a WIP., just stoked that you are this far along and longing for lossless audio on balena-sound :-P
|
For me, it only switches between mute (0) and 100. If I select a volume lower than 100%, the volume control is set directly to 0. The volume control in the speaker_controller_application via +/- is working fine. Did you have to change anything else to make the volume control work? |
I found that the speaker_controller_application needs to be running in order for volume control et al to work. I created a service for it: `[Unit] [Service] [Install] save this into /etc/systemd/system, chmod+x it, and then enable it as a system service. Works like a charm! |
RPi 3B+ with Hifiberry Dac+ |
Hi, i've tried this solution on moode audio 7.1.0 , but it show me on boot
edit: I discover there is no /usr/bin/screen in moode. what i should use instead it? |
I'll be happy to help test this with my Pi4-HiFiBerry DAC+ once it gets updated to current - I'm hoping to deploy in the next few days... Here's a thread HiFiBerry pointed me to that may help: https://support.hifiberry.com/hc/en-us/community/posts/360013667717-Tidal-Connect- |
FYI this might be useful if anyone has time to work on this further https://github.com/TonyTromp/tidal-connect-docker and https://github.com/seniorgod/ifi-tidal-release/blob/master/tidal_connect_application_as_docker_container/ifi_docker.md |
Good find! Worth digging into…
Sent from nowhere near my ready room with my new tricorder
… On Oct 21, 2021, at 15:04, Aaron Shaw ***@***.***> wrote:
FYI this might be useful if anyone has time to work on this further https://github.com/TonyTromp/tidal-connect-docker
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I've been looking into this and have discovered that you likely don't even need the speaker_controller application/service. Everything seems to come out of and be sent through /tmp/tisoc-controller. If you connect to it you can see a flood of JSON messages with all the now playing info, player state etc. The only issue I'm having is connecting to it and not "breaking" the tidal service. If you connect to it before you've connected your phone to the service, you can see the request going through but then it freezes and you have to restart the tidal service. If you connect your phone first, then connect to the socket, you can see all the messages but it still breaks TC for a phone reconnect afterwards. Also when you do this the speaker controller service doesn't work anymore without a TC restart. I'm obviously not reading the port correctly. The phone service also runs on websocket port 2019 so that could be a way in, but I haven't gotten very far with that yet either. |
@asifjahmed did you manage to fix your error code 100 build issue? How? |
I hope this was not abandoned. I would love to see something like this in action! |
Hey Gyus! Great work you all have done so far. Is there any news on if and when this will make it into the main branch? |
First attempt at a tidal connect plugin. See #371 for origin.
To Do List