starred/tidal-ui
1
0
Fork 0
mirror of https://github.com/binimum/tidal-ui.git synced 2026-04-26 12:25:48 +03:00
Code Issues 48 Projects Releases Packages Wiki Activity

[GH-ISSUE #84] Playlist and queue capped on 100 songs only #70

New issue
Open
opened 2026-03-03 00:07:33 +03:00 by kerem · 12 comments
kerem commented 2026-03-03 00:07:33 +03:00
Owner
Copy link

Originally created by @tmatzxzone on GitHub (Dec 26, 2025).
Original GitHub issue: https://github.com/binimum/tidal-ui/issues/84

Describe the bug
Playlist and queue capped on 100 songs only

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'any playlist that has 100+ music'
  2. Click Play all and it just load 100 queue, even if u scroll through the playlist it just capped at 100 tracks

Example of bug

A link to a 100+ playlist : https://music.binimum.org/playlist/5c0e1a0f-8291-42c6-a52a-30e217147ed4

Expected behavior
It should display all 185 tracks as it shown in the playlist

Screenshots

Image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser : Firefox
  • Browser version : 146.0.1
  • Website version : v3.3

Additional context
Add any other context about the problem here.

Originally created by @tmatzxzone on GitHub (Dec 26, 2025). Original GitHub issue: https://github.com/binimum/tidal-ui/issues/84 **Describe the bug** Playlist and queue capped on 100 songs only **To Reproduce** Steps to reproduce the behavior: 1. Go to 'any playlist that has 100+ music' 2. Click Play all and it just load 100 queue, even if u scroll through the playlist it just capped at 100 tracks **Example of bug** A link to a 100+ playlist : https://music.binimum.org/playlist/5c0e1a0f-8291-42c6-a52a-30e217147ed4 **Expected behavior** It should display all 185 tracks as it shown in the playlist **Screenshots** <img width="1604" height="817" alt="Image" src="https://github.com/user-attachments/assets/d59e4969-cb29-4d98-81f3-6ed3e288b5ce" /> **Desktop (please complete the following information):** - OS: Windows 10 - Browser : Firefox - Browser version : 146.0.1 - Website version : v3.3 **Additional context** Add any other context about the problem here.
kerem commented 2026-03-03 00:07:34 +03:00
Author
Owner
Copy link

@Asher-1971 commented on GitHub (Dec 28, 2025):

same here did u find a fix ?

<!-- gh-comment-id:3694691514 --> @Asher-1971 commented on GitHub (Dec 28, 2025): same here did u find a fix ?
kerem commented 2026-03-03 00:07:34 +03:00
Author
Owner
Copy link

@PlsJustDoIt commented on GitHub (Dec 29, 2025):

I think it's because of the limit used in the api call to retrieve songs : getAlbum

<!-- gh-comment-id:3695164426 --> @PlsJustDoIt commented on GitHub (Dec 29, 2025): I think it's because of the limit used in the api call to retrieve songs : [getAlbum](https://github.com/uimaxbai/hifi-api/blob/48a965eb93d7197181a234733716e9e2f1dac1fc/main.py#L314-L317)
kerem commented 2026-03-03 00:07:34 +03:00
Author
Owner
Copy link

@LDprg commented on GitHub (Dec 29, 2025):

It seems the api has no offset function, so ths will likely need a backend update first.

<!-- gh-comment-id:3696594899 --> @LDprg commented on GitHub (Dec 29, 2025): It seems the api has no offset function, so ths will likely need a backend update first.
kerem commented 2026-03-03 00:07:34 +03:00
Author
Owner
Copy link

@Asher-1971 commented on GitHub (Jan 1, 2026):

It seems the api has no offset function, so ths will likely need a backend update first.

did u manage to find a work around ?

<!-- gh-comment-id:3703182421 --> @Asher-1971 commented on GitHub (Jan 1, 2026): > It seems the api has no offset function, so ths will likely need a backend update first. did u manage to find a work around ?
kerem commented 2026-03-03 00:07:34 +03:00
Author
Owner
Copy link

@LDprg commented on GitHub (Jan 1, 2026):

No, I looked into the code and it seems like there is no way to bypass this without upstream changes.

<!-- gh-comment-id:3703492974 --> @LDprg commented on GitHub (Jan 1, 2026): No, I looked into the code and it seems like there is no way to bypass this without upstream changes.
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@LDprg commented on GitHub (Jan 1, 2026):

No, I looked into the code and it seems like there is no way to bypass this without upstream changes.

<!-- gh-comment-id:3703493002 --> @LDprg commented on GitHub (Jan 1, 2026): No, I looked into the code and it seems like there is no way to bypass this without upstream changes.
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@JulienMaille commented on GitHub (Jan 1, 2026):

https://github.com/uimaxbai/hifi-api/pull/2

<!-- gh-comment-id:3704232180 --> @JulienMaille commented on GitHub (Jan 1, 2026): https://github.com/uimaxbai/hifi-api/pull/2
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@Asher-1971 commented on GitHub (Jan 4, 2026):

No, I looked into the code and it seems like there is no way to bypass this without upstream changes.

i hope its fixed soon

<!-- gh-comment-id:3708176183 --> @Asher-1971 commented on GitHub (Jan 4, 2026): > No, I looked into the code and it seems like there is no way to bypass this without upstream changes. i hope its fixed soon
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@binimum commented on GitHub (Jan 5, 2026):

@JulienMaille has pushed a change to enable this from the upstream API, and now it just needs to be implemented in the frontend.

<!-- gh-comment-id:3709507082 --> @binimum commented on GitHub (Jan 5, 2026): @JulienMaille has pushed a change to enable this from the upstream API, and now it just needs to be implemented in the frontend.
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@Asher-1971 commented on GitHub (Jan 17, 2026):

@JulienMaille has pushed a change to enable this from the upstream API, and now it just needs to be implemented in the frontend.

is it applied yet ?

<!-- gh-comment-id:3764225897 --> @Asher-1971 commented on GitHub (Jan 17, 2026): > [@JulienMaille](https://github.com/JulienMaille) has pushed a change to enable this from the upstream API, and now it just needs to be implemented in the frontend. is it applied yet ?
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@binimum commented on GitHub (Jan 18, 2026):

No, I haven't applied it yet. I'm beginning to encourage migration to Monochrome (https://monochrome.samidy.com) because I'm winding down and switching to other projects. I might push every now and then but they push much more.

<!-- gh-comment-id:3765130987 --> @binimum commented on GitHub (Jan 18, 2026): No, I haven't applied it yet. I'm beginning to encourage migration to Monochrome (https://monochrome.samidy.com) because I'm winding down and switching to other projects. I might push every now and then but they push much more.
kerem commented 2026-03-03 00:07:35 +03:00
Author
Owner
Copy link

@thedavidweng commented on GitHub (Jan 26, 2026):

Album also capped on 100 songs, example being The Beatles (White Album / Super Deluxe), a 107 tracks album

<!-- gh-comment-id:3798517401 --> @thedavidweng commented on GitHub (Jan 26, 2026): Album also capped on 100 songs, example being [The Beatles (White Album / Super Deluxe)](https://tidal.squid.wtf/album/97871757), a 107 tracks album
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
clean-v3.5-polish
No results found.
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
wontfix
No labels
bug
duplicate
enhancement
pull-request
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tidal-ui#70
No description provided.