-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output Filename Template: Request for upload-datetime #1706
Comments
Bump. I was just about to suggest this when I found it as a suggestion. I too would like an "HHMMSS" field that could be added to the existing YYYYMMDD fields. |
Looks like because the way youtube-dl is architected (each site having custom code to extract the date string, and then unifying the formatting but returning the result as a string rather than a datetime) this might involve a lot of change (but none of it very complex AFAICT):
Does this seem sane? |
Almost 5 years now... Still can't include an HHMM in the filename :'( |
I would be happy to get the format "YYYY-MM-DDTHH:MM:SS " in the filename too. |
Upvoted! |
Having a separate upload_time field would be fine - If you're grabbing from a source that doesn't provide the time, then you won't use it in any templates or code, and it can default to midnight in whatever timezone the date is in (which should be knowable per extractor)... or just not be in the info_dict at all if it's not provided, and dependent code can check to see if upload_time is available as necessary. Since the extractors abstract all the parsing of the video info, they can make the determination on what should be in the upload_time field, or if it should exist in the dict at all. @l0b0 has a decent suggestion as well to keep things unified. |
There is already a |
However, now: yt-dlp/yt-dlp#9829 (comment). |
The current %(upload_date)s gives YYYYMMDD. Could you please consider adding another that includes time like YYYYMMDD-hhmmss ? Maybe a date-time combination option %(upload_datetime)s or a separate %(upload_time)s ?
The text was updated successfully, but these errors were encountered: