-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
My bad, no issue #9967
Comments
No. The only codec that the opus container supports is opus, so you'd have to re-encode if there are no opus codec formats available:
Would need to see a log
There is a feature request for this: #7832 For now you'd have to manually capture all of yt-dlp's output to a log file, and search through it for In powershell, I think you can do this:
Or else in cmd, you'd need to do this (but you wouldn't see the output in your terminal, it would be redirected only to the log file):
|
Thanks, I'll stick to mkv and Opus then. I had no signs of errors in log file via CMD, but a few files were still missing. I assume they were in mp4 format and I made a mistake somewhere trying to adapt my old script. Should be fine now, thanks Besides that, I usually get the following (or rather similar) messages but everything downloads nonetheless: "WARNING: [youtube] Skipping player responses from android clients (got player responses for video "aQvGIIdgFDM" instead of "Tt-vtc4NHrQ")" P.S. Yes please, add an option to view how many videos were successfully downloaded and how many have failed + links to them and the reason why, if possible. That would be a nice QoL improvement for large playlists or channels. |
It's most likely an isssue with your script. Can't say any more without seeing a full verbose log |
You aren't including the (At least that's what's happening in the actual log you sent where nothing is being downloaded. In the initial run when you actually downloaded all of this, the videos in question may have been downloaded and then later overwritten during the postprocessing stage of the identically named subsequent downloads). These are the problematic filenames:
|
There was no issue here, my fault
The text was updated successfully, but these errors were encountered: