mirror of
https://github.com/binimum/tidal-ui.git
synced 2026-04-26 12:25:48 +03:00
[GH-ISSUE #77] FLAC files on most songs are not losseless or his-res files #65
Labels
No labels
bug
duplicate
enhancement
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tidal-ui#65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aadityarajsinghnaruka4512-glitch on GitHub (Dec 13, 2025).
Original GitHub issue: https://github.com/binimum/tidal-ui/issues/77
So i have been using it for a time and i noticed sum songs albums are not sounding like i have others so ran a analysis on https://www.verifaiaudio.com/ this was result this
explain bruh excellent ones were only losseless quality and other were converted to flacs and encoded as high 320kbps
??????????????????????????????????????????????????????????????????????????????????????????????????????????
@sliipkat commented on GitHub (Dec 14, 2025):
Why are you using a vibecoded website instead of Spek to analyze the audio?
@0x09AF commented on GitHub (Dec 14, 2025):
This has been a long debate. Unfortunately some albums are recorded in mp3 or some compressed format. The streaming services provide what they received from the recorded label, I doubt they would spend any effort on recompressing their database if they advertise as "lossless".
Example, I bought an discography on Bandcamp and one of the albums peaked at 16 kHz, meaning all the frequencies were cut off past 16k. Discovered that the album was reissued in 2025 on another label and was available for purchase now in 24 bit FLAC. It's one of my favorite albums - I purchased it again, analyzed, and it still was 16 kHz max. This tells me that it was how it was recorded...
TLDR; not a tidal-ui issue
@binimum commented on GitHub (Dec 15, 2025):
This is an upstream issue on Tidal's end, not anything to do with me.