Skip to content
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

error="update failed: failed to parse duration : bad format string" #638

Open
fqx opened this issue Jun 28, 2024 · 6 comments
Open

error="update failed: failed to parse duration : bad format string" #638

fqx opened this issue Jun 28, 2024 · 6 comments

Comments

@fqx
Copy link

fqx commented Jun 28, 2024

This error keeps showing in the log, in the last 24 hours.
I will look into this and update this issue.

@fqx
Copy link
Author

fqx commented Jun 28, 2024

I have a feeling that this bug occurs when the channel has upcoming live broadcast.

@fqx
Copy link
Author

fqx commented Jun 28, 2024

It appears that YouTube changed the default value of video.ContentDetails.Duration for live broadcasts. I have created a quick fix pull for this. However, I don't really know go, so please look into it carefully. #639
For anyone need this fix urgently, you can get binary here https://github.com/fqx/podsync-with-yt-dlp/releases/tag/v2.7.1-b .

@fqx
Copy link
Author

fqx commented Jun 29, 2024

It may cause apple podcast shows wrong duration, however the playback is ok.
IMG_4657

@fqx
Copy link
Author

fqx commented Jul 1, 2024

@thurstonsand
Copy link

thurstonsand commented Jan 10, 2025

EDIT: never mind. the below did not fix the problem.

fwiw I've run into the same issue, and noticed it was happening on premiere videos that have not yet aired. so i was able to filter them out and prevent the problem by adding

youtube_dl_args = [
    "--match-filters",
    "live_status!=is_upcoming",
]

to my config.

it might make sense to just add that as an always-on filter, since i can't think of any good scenario where you'd want to include an unaired premiere video in the podcast feed

@thurstonsand
Copy link

thurstonsand commented Jan 11, 2025

I've attempted to fix the problem as well. in my PR, it's more clear why we're continueing: #677

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants