1a118e225a
Solved Issue: https://github.com/jmbannon/ytdl-sub/issues/706 From our discussion with yt-dlp folks (https://github.com/yt-dlp/yt-dlp/issues/8108), we learned that best practices for date--range filtering is done using match-filters. We now set the `date_range` plugin values to be a 'breaking' match filter, and any custom ones specified from users in the `match_filters` plugin as non-breaking. This means match-filters can be performed at the metadata stage, which should yield a significant speedup Relevant docs: - date_range: https://ytdl-sub.readthedocs.io/en/latest/config.html#date-range - match_filters: https://ytdl-sub.readthedocs.io/en/latest/config.html#match-filters |
||
|---|---|---|
| .. | ||
| music_audio_config.yaml | ||
| music_audio_subscriptions.yaml | ||
| music_videos_config.yaml | ||
| music_videos_subscriptions.yaml | ||
| README.md | ||
| tv_show_config.yaml | ||
| tv_show_subscriptions.yaml | ||
Example Configurations
This directory shows how you can use ytdl-sub for various use cases. These are the configs I personally use and have incorporated as part of the e2e tests.
Each example has a config.yaml and subscription.yaml. The config defines
how you format your media, whereas the subscription defines what you
download plus some additional configuring if needed.