The current yt-dlp code does not know the maximum resolutions of "oar", "maxres" thumbnails for youtube shorts and albums (thumbnails with side stripes). #9837
Labels
site-enhancement
Feature request for some website
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Checklist
Region
No response
Example URLs
https://www.youtube.com/shorts/89B7LcG4uUA
Provide a description that is worded well enough to be understood
The current yt-dlp code does not know the maximum resolutions of
oar
,maxres
thumbnails for YouTube shorts and albums (thumbnails with side stripes).With
--print thumbnails_table
it returns a table of links for the thumbnails with their resolutions and extensions. But some are not recognized and others do not show the correct resolutions. I suppose that for horizontal videos the maximum resolution is 1280x720p since YouTube recommends that.It also does not distinguish vertical thumbnails (for YouTube Shorts) or square thumbnails (for albums or music), they always come out with black or painted stripes on the sides, except for horizontal videos.
In YouTube Shorts, they are always 1280x720 when they also exist in real 1080x1920p (for example: https://i.ytimg.com/vi/89B7LcG4uUA/oar2.jpg).
Other links in 1080x1920 that
--print thumbnail_table
or--list-thumbnails
does not show:For the thumbnails that are displayed from the browser in the youtube shorts section:
It is "oardefault" for:
and I suppose for many more channels (I have tried at least 10 channels).
It is "oar2" for:
But sometimes it doesn't work for other shorts:
for example:
I guess there are others that don't work either, it's strange.
Note:
It seems that "oar" is for vertical videos (Shorts) and "maxres" for horizontal videos, I have not been able to find for square thumbnails (music, albums), they always come out with side stripes.
Provide verbose output that clearly demonstrates the problem
yt-dlp -vU <your command line>
)'verbose': True
toYoutubeDL
params instead[debug] Command-line config
) and insert it belowComplete Verbose Output
The text was updated successfully, but these errors were encountered: