02-24-2021, 05:30 PM
I'm not interested in Tidal, Tidal Connect, MQA, yada yada yada.
Looking dispassionately at the referenced github repo, I see a readable script and a LICENSE file. However, the script pulls in binaries from another github repo which says it got them from yet another github repo. They both include various licenses but in a quick search of strings in the two binaries I assume are the core functionality I didn't find any clues of authorship so I don't know if the licenses apply or not. I could not find sources for the binaries.
A Google search reveals a number of github repos besides this one, presumably set up by different devs, which seem to have identical wording in their almost useless README.md files:
I would approach this code with extreme caution.
And as Tim likely would say, this is unsupported by the moOde project.
Regards,
Kent
Looking dispassionately at the referenced github repo, I see a readable script and a LICENSE file. However, the script pulls in binaries from another github repo which says it got them from yet another github repo. They both include various licenses but in a quick search of strings in the two binaries I assume are the core functionality I didn't find any clues of authorship so I don't know if the licenses apply or not. I could not find sources for the binaries.
A Google search reveals a number of github repos besides this one, presumably set up by different devs, which seem to have identical wording in their almost useless README.md files:
Quote:tidal connect service raspberry/ARM based on ppy2/ifi-tidal-release
I found that repository called ifi-tidal-release here on github, created by ppy2. Included are some binaries and some scripts. The names of the binaries intended that this is a tidal connect client. Because the lack of any description i downloaded the repo and play around with the included stuff.
I would approach this code with extreme caution.
And as Tim likely would say, this is unsupported by the moOde project.
Regards,
Kent
