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

Cannot extract audio from video with fancy characters in its name #3675

Open
giacomodrago opened this issue Sep 4, 2014 · 3 comments
Open

Cannot extract audio from video with fancy characters in its name #3675

giacomodrago opened this issue Sep 4, 2014 · 3 comments

Comments

@giacomodrago
Copy link

@giacomodrago giacomodrago commented Sep 4, 2014

This does not work:
youtube-dl --extract-audio --audio-format mp3 http://www.youtube.com/watch?v=ZV0Ks4cujNU

(ERROR: WARNING: unable to obtain file audio codec with ffprobe)

whereas this does:
youtube-dl -o asd.mp4 --extract-audio --audio-format mp3 http://www.youtube.com/watch?v=ZV0Ks4cujNU

I am on Microsoft Windows 7 x64, latest version of youtube-dl.

@giacomodrago
Copy link
Author

@giacomodrago giacomodrago commented Sep 4, 2014

I was using the youtube-dl Windows executable I found on the project's website.
Now I actually cloned the repository, and run the program with python from the command line. I get different results with Python 2 and Python 3, that is the former does not work, the latter does. So if you are embedding Python 2 in the Windows executable, youtube-dl is not able to download that video, I guess because it has odd fancy symbols in its name.

@l3uddz
Copy link

@l3uddz l3uddz commented Sep 5, 2014

Use --restrict-filenames allows it to work

@giacomodrago
Copy link
Author

@giacomodrago giacomodrago commented Sep 5, 2014

I know various workarounds, but I think the application should either: 1) fail with a proper error message ("use --restrict-filenames please"); or 2) auto-engage --restrict-filenames emitting a warning.
Anyway, it shouldn't do different stuff in Python 2 and 3, or this should be documented. Generic failure with catch-all reason is bad, AFAIK.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.