-
Notifications
You must be signed in to change notification settings - Fork 8
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
Coreelec/tidal-connect Hi-Res/MQA bad streaming to SPDIF out #72
Comments
Hello, thank you for the kind words. AFAIK mConnect does not support tidal hires (hires flac without mqa I mean) so in any case it would stream <= 48kHz, that might confirm the issue, because the Tidal Connect instead can do the first mqa unfolding which can result in an output sampling rate of 96kHz or 88.2kHz. If you can connect the dac via usb, then execute
and maybe post the output here.
is enough. You might want to force container recreation (just in case), you can do:
Let me know, cheers |
With Mconnect and BubbleUPnP track Hi-Res/MQA work without issues using Coreelec using DLNA to SPDIF port, also FLCA test file 192Khz@24bit work . With USB Hi-Res/MQA not work, TIDAL app on PC cast only HI-fi nott switch to MAX/MQA, and i try to find a solution for some forum user/friends that have only SPDIF DAC. this mine step : I think is very nice to create a new tidal-connect docker for Coreleelec/libreelec with simple config file ,maybe can a start point to crate a new kodi music addon. |
Uhm good to hear. |
very low CPU load |
That is very strange. Does it do the same when using both MQA parameters set to false?
I have a Minix Neo U1 which I'd like to repurpose with some armbian distro. During the w/e I saw that Corelec guys dropped support for Neo 1 some time ago. Can you point me to a distro which might run on this device? It also has an optical spdif out so it would be nice to see if it can work. |
Ok i format and start again,now with USB tidal-connect docker and Hi-Res/MQA work :). So with SPDIF port there is some bug or problem, analog/HMDI/SPDIF they share same card "0":
save issues MQA parameters false or true. with Minix Neo U1 you can use legacy Generic https://github.com/CoreELEC/CoreELEC/releases/download/9.2.8/CoreELEC-Amlogic.arm-9.2.8-Generic.img.gz, for music or tidal-connect is equal. I try many time ,but armbian not boot with mine Ki pro and i like more corelec there are lot for addon for music . |
I believe probably we need to select the subdevice 1 "SPDIF". I will try and prepare a branch for you to test, probably in the next few days. |
Would you please try this branch: I have added support for CARD_DEVICE
or
to the |
i do some test with this track https://tidal.com/browse/track/77649978, and i think che problem about 16 or 32 bit playback track with kodi addon the sound is good and "format: S16_LE"
playback track from pc to docker tidal-connect the sound is bad and "format: S32_LE"
so i think docker send wrong bit format. Not all MQA/Hi-res track wrong , some track playback fine like this https://tidal.com/browse/track/79530261 where is ".env" file ?!? |
The .env file is created by the configure.sh file in the same tidal-connect directory. This can also be edited directly specifying the variables one needs to tune. |
I assume you are changing directly the entrypoint.sh and/or the docker-compose file? |
SPDIF supporto only 24 bit, USB support 32 bit. so i have test some local FLAC file at 192khz@24bit with coreelec and output is .
i think there are some problem/limitation about coreelec and S24_LE, so system output only 16 bit. I can force docker tidal-connect with S24_LE? CoreELEC:~ not have asound.conf file
|
I have updated the same branch with support for card format.
Example is my .env file for topping D10:
The asound.conf file I am referring to is the one that is created inside the container on its startup, not the system-level asound.conf.
Let me know if this helps |
now setting CARD_FORMAT=S24_LE now bitstrteam i correct :) ,but wrong subdevice
SPDIF is "AML-MESONAUDIO: - (hw:0,1)" i can force subdevice 1? CARD_DEVICE=0.1 ? grazie |
I think you should set CARD_INDEX=0 Let me know! |
nope , 32 bit and wrong subdevice
|
From what I see you are probably not using the latest version from the branch. Anyway the changes are now in the main branch so I suggest you to start over. Delete the repo:
Clone the repo:
Enter the repo directory:
Create the .env file:
Restart the container:
Post the container logs:
|
I corrected an error in the post before, there was a meaningless: S24_LE=S24_LE instead of CARD_FORMAT=S24_LE |
with .env file:
docker logs
but cat report S32_LE
playback sound was very good and DAC report MQA 192khz + red dot, so i suppose "work" :)) If was 16,24 o 32 bit ..it's a mistery... |
Hello, good to hear it works.
And then restart container and see the logs! |
I also see from the logs, that the 'default' device does not seem to be valid, see:
So maybe instead of CARD_INDEX=0 you might also try CARD_NAME=AMLMESONAUDIO |
It also looks that it is playing through device 2, not 1 |
Ah, of course, before I suggested CARD_INDEX=1 while it should be CARD_INDEX=1 like you did. It is better to use the CARD_NAME if possible, so that the CARD_INDEX is retrieved at container start time |
with this not sound, tidal connect work there is only silence from speaker
|
Hello, about using the card name, it is very strange that it does not work. If you want, please execute
so we can see the correct names. About the configuration that works, it appears that the important thing is using S24_LE... considering that it seems that device 2 is actually playing, can you try with this variation of your working config:
In any case it's good that is works for you :-) |
I just made a few changes, to update just execute the following:
The changes make sure that the device declared in asound.conf is Let me know if you want to try it! |
CARD_DEVICE=2 -> HMDI -> no sound
with
logs
NOT work , no sound only silence
only format: S32_LE work |
work ,but not sound from speaker |
nope, not sound |
ok. So to revert to the previous repo state:
Then use known working config and try
|
Before reverting, can you post the logs of the configuration that used to work? |
now work again all ok: playback sound was very good and DAC report MQA 192khz + red dot
PS: every time i remove/delete docker |
Happy to hear it works again.
Or clone the repository completely it this does not work. Keep you working .env file safe of course. In order to maintain you working version, I have set a tag for you working version, so in case the latest version should not work, you should be able to switch to that version using:
Or you can clone the directory at that tag using:
|
i try the brand and work: very good and DAC report MQA 192khz + red dot
|
Hello, I do not understand: you tried latest and worked, then reverted to the tag? Does everything work? |
first i have delete tidal-connect folder and docker. than git the branc(i suppose) with command |
ok but that is the tag that preserves the versionthat we know works for you. git clone https://github.com/GioF71/tidal-connect.git It this also works we can mark this as solved and I can remove the tag! Thank you! |
i have done it |
I suppose it's working as well? :-) |
yes ,very good and DAC report MQA 192khz + red dot. PS: do you can be foce TIDAL MAX? with right Device Type. |
As far as I know this app does not work with tidal max (so hires flac). |
do you have try coreelec on Minix Neo U1 ? and tidal-connect . |
Not yet, maybe during the weekend. Isn't that legacy version of coreelec too old? Which version of Kodi is included? Thank you |
Hello, I have successfully installed armbian in my Neo U1. Quite a slow device at least for i/o operations on the sd card, but it works |
Audio quality with Tidal Connect is bad with Minix Neo U1 on recent armbian. That's because of an emulation issue, probably related to the old cpu (it's a wild guess I know). |
i don't now. I think CoreELEC is 32-bit userspace on top of a 64-bit kernel. you can try it's very esay
|
Hello, that pdf is not current, if I do the same things I get to this github release page: https://github.com/CoreELEC/CoreELEC/releases/tag/9.2.8 Which version should I use? Edit: this answer suggests CoreELEC-Amlogic.arm-9.2.8.tar |
yes, right. |
Hello, I could use that legacy version of CoreELEC on my box and also could make Tidal Connect work. Librespot as well, and also SqueezeLite but only max 16bit. Kodi works beautifully even in 4k, I don't know if it can play 4k streams successfully though, I will test it. LibreELEC (latest version) also worked, but Kodi wouldn't work in 4k as well as CoreELEC did. Also no way to run Tidal Connect, the container just hangs. Didn't take much time to try and configure the other containers I use considering how bad Kodi was. With Armbian (bookworm), all the audio containers work up to 24/192, except for Tidal Connect which only apparently works, but has issues with emulation which result in bad audio quality all-around. With Tidal Connect turned off everything works perfectly audio-wise. Kodi is software only so awfully slow. I believe Armbian solution, when CoreELEC becomes too old for the bundled kodi version, might be the endgame for this box. At least as a audio-only player, it can do something good. |
CoreELEC is more optimized for amlogic box. with CoreELEC i suggest you also to try TIDAL 2 addon + d Add-on Artist Slideshow on MQ9/8 skin...very very beautiful interface. |
Hello, how did you install inputstream.ffmpegdirect in coreelec? |
some addon need mandatory other to work. |
Tried it... it works @192KHz. |
Hello @looun, can we close this ticket? If there are outstanding issue, you can open another. |
hello, after some trouble i have successful run docker tidal-connect on amlogic box(Ki pro) with Coreelec ;) ...very nice
When i playback the hi-fi(44.1k/16bit) track it's work fine SPDIF out to my external DAC loxjie D30, without any issues.
when i playback Hi-Res/MQA playback very bad with lot of noise,interruption.
I have force also:
--codec-mqa true
--enable-mqa-passthrough true
When i playback with kodi addon or Mconnect/UPnp there are not issues, but i prefer tidal-connect ;)
Thanks.
The text was updated successfully, but these errors were encountered: