forked from shawaj/ifi-tidal-release
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Driving me insane #35
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In short, I can't get this Tidal Connect running inside a Docker image to recognise my USB interface (Scarlett 2i2) connected to my Raspberry Pi 4 running DietPi. Here's as far as I can get, Tidal connect pops up on my phone and laptop but when I play audio to it it insists on coming out the headphone jack (which I have headphones connected to to verify) regardless of my settings. Perhaps I've overlooked something.
EDIT: Setting default device in DietPi to the Scarlett 2i2 causes the Docker image to not be able to start up and it restarts in an endless loop. I suspect that is something to do with DietPi taking "control" of the audio device exclusively.
Docker logs:
my
aplay -l
- as far as I can see my device is called USB: USB Audio (hw:1,0)entrypoint.sh edited for my USB interface:
Strangely aplay -l shows exactly the same output INSIDE the Docker container yet it complains that it cannot find the USB device.
The text was updated successfully, but these errors were encountered: