-
Notifications
You must be signed in to change notification settings - Fork 30
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
Tidal Connect | MQA not working after rebooting the hifiberry OS. #19
Comments
I don't think you can use passthrough MQA on Hifiberry OS. (You can't send unfolded MQA down an SPDIF/Toslink pipe, it has to go via USB, which Hifiberry doesn't do.)The best you'll get is the 1st unfold using the MQA codec. I know the option is there to turn passthrough on but this whole thing wasn't designed specifically for Hifiberry in the first place. |
MQA passthrough is working for some. not sure if its usb only or not as i cant test it. you can try |
Nevermind. I've just done it on HifiBerry OS. Running MQA passthrough on an Ifi Zen DAC V2. I don't own a DAC HAT from hifiberry. |
Found my way back to this thread while looking for updates: Your EarMen TR-AMP only supports MQA Rendering so you need specify |
That is great news. Unfortunately i dont have a eternal DAC to test this, nor contribute. |
Let me know if there's anything you want me to test. I use an Ifi Zen DAC V2 and I've also purchased a DAC2 Pro (but I'll only see that in June when my in-laws arrive from the US). My Zen DAC V2 produces a Magenta light if I set the passthrough to false: it then runs in "render mode" instead of "decode and render". It produces green or blue as is the case if passthrough is set to true. After running the --help function on the tidal_connect_application I think the --codec-mqa doesn't actually modify anything going to the DAC per se. It seems to tell the connect application whether to make MQA content available or not (but it doesn't seem to make any difference to what I can and can't play on my side). The --codec-mpegh seems to be related to the 360 headphone content. And there is a Dolby Atmos codec mention in the --help as well. I actually found the details first by opening the application in a hex editor and simply searching for "--" to see the plaintext and later just ran the app using the --help flag. |
Dear Tony,
I have done changes in the CONFIG file but still the MQA not working. It didnt work after reboot the hifiberry os.
Here are my CONFIG file and docker-compose.yml file
CONFIG file
FRIENDLY_NAME=hifiberry
MODEL_NAME=hifiberry
MQA_PASSTHROUGH=True
MQA_CODEC=True
PLAYBACK_DEVICE=EarMen TR-AMP: USB Audio (hw:1,0)
docker-compose.yml
version: '2.2'
services:
tidal-connect:
container_name: tidal_connect
env_file:
- .env
image: edgecrush3r/tidal-connect:latest
tty: true
restart: always
network_mode: host
devices:
- /dev/snd
volumes:
- ./entrypoint.sh:/entrypoint.sh
- /var/run/dbus:/var/run/dbus
restart: always
dns:
- 8.8.8.8
Thank you
regards
The text was updated successfully, but these errors were encountered: