-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[Bug] FFmpeg not finding files downloaded by yt-dlp #1273
Comments
The filename is too long. Use a shorter output template |
is there a way to make a "backup" filename format in case this happens instead of just completely changing the template? as having such an issue could be pretty problematic for bulk archiving like in my case, perhaps I'd miss one video where it errored out without me realizing it and thus having an actually incomplete archive, and this happened for like %3 of the videos... which is a bit high for such a thing also, the audio and videos tracks are all being downloaded correctly even through they are the same length... shouldn't the temp file be possible then (it's even one character short than |
There is an issue open for this. #1136
Use the |
Checklist
Verbose log
Description
As far as I can tell, FFmpeg isn't finding the the files it was provided by yt-dlp for some reason (not passing the dir correctly?), it worked for the full channel but a few videos had this exact issue
Videos IDs that had this issue for me (not all 28, just some):
What I could think happened is some filename encoding issue or something that has to do with Arabic text, but I'm not really sure as other videos worked fine, just a few that kept having this exact issue (not matter how much I tried), and I've verified that the files actually exist and that I'm updated to the latest (10.10.2021 as of now)
There was no mention of this issue anywhere I've looked, I searched with keywords but the only thing that was close was #871 but it was still for an entirely different issue (mine isn't about a problem with muxing tracks... probably)
Hopefully I did the bug reporting right
The text was updated successfully, but these errors were encountered: