Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
%(playlist_index) pads neither by playlist size nor to 5 digits #5748
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The man page states that
%(playlist_index)sshould pad to 5 digits and according to an issue here it is supposed to pad to playlist size but it does neither.--playlist-start 1 --playlist-end 9 -o "%(playlist_index)s"starts with 1,--playlist-start 1 --playlist-end 10 -o "%(playlist_index)s"starts with 01,--playlist-start 2 --playlist-end 10 -o "%(playlist_index)s"starts with 2,--playlist-start 2 --playlist-end 11 -o "%(playlist_index)s"starts with 02.Looks like it uses the number of videos in the current job which results in duplicates when overlapping ranges.
Any of the supposed behaviours would be fine to get consistent lexical sort names when downloading parts of a playlist. Or maybe a flag to specify the size as with
$(autonumber)s.