Validated continuations for playlists

[Pachandre]

Is your feature request related to a problem? Please describe.
Yes. The get_album() method has a limit parameter, but it only limits how many tracks are retrieved starting from the beginning of the playlist. This becomes inefficient when dealing with large playlists. Setting limit=None doesn't fetch all tracks either (possibly due to a YouTube-imposed limit); I only get 1914 out of 2054 tracks of my liked songs playlist

Describe the solution you'd like
It would be helpful to have support for pagination via offset and count parameters (or similar). For example, to retrieve tracks in batches, one could first request offset=0, count=100, then offset=100, count=100, and so on. This would make it easier to process large playlists incrementally and avoid performance issues

Describe alternatives you've considered
None that are practical or reliable - manually adjusting the limit and re-requesting from the start is inefficient and doesn't solve the problem

Additional context
This feature would be especially useful for users trying to fully export or analyze large playlists

[sigma67]

Something like this is already implemented, but only for get_library_songs. Feel free to send a PR for the function you would like (I assume get_playlist).

ytmusicapi/ytmusicapi/mixins/library.py

Line 108 in 445833f

get_validated_continuations(

"Yes. The get_album() method has a limit parameter, but it only limits how many tracks are retrieved starting from the beginning of the playlist. This becomes inefficient when dealing with large playlists."

This makes no sense to me. Why are you using get_album to fetch playlists?

[Pachandre]

This makes no sense to me. Why are you using get_album to fetch playlists?

My bad, meant to write get_playlist

[lovegaoshi]

im happy to be corrected but i doubt an offset parameter even exists to begin with.

[sigma67]

It doesn't, the approach is too keep retrying until you have the expected amount