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

Using ':' in -o breaks ffmpeg #6874

Closed
paulguy opened this issue Sep 15, 2015 · 7 comments
Closed

Using ':' in -o breaks ffmpeg #6874

paulguy opened this issue Sep 15, 2015 · 7 comments

Comments

@paulguy
Copy link

@paulguy paulguy commented Sep 15, 2015

I was trying to download a full playlist from youtube, and I wanted the videos numbered so I could watch in order, so I used:
youtube-dl --playlist-reverse -f bestvideo+171/bestvideo+140 -o "%(autonumber)s: %(title)s-%(id)s.%(ext)s" https://www.youtube.com/playlist?list=PL26B36130624FCAF5

The unfortunate side effect is that ffmpeg believes that the filename is specifying a protocol. I could just use a different character, but I was able to fix it by modifying FFmpegPostProcessor.run_ffmpeg_multiple_files and simply prepending 'file:' to each input_path and the out_path.

@yan12125
Copy link
Collaborator

@yan12125 yan12125 commented Sep 16, 2015

input_path can be remote URLs. (for example M3U8 URLs)

@paulguy
Copy link
Author

@paulguy paulguy commented Sep 16, 2015

Well, obviously considerations like that are why I didn't make a pull request, but simply said what I did to fix it. I'm just saying, if it's a file, it should be prefixed with file: so ffmpeg knows it's a file, and you don't get weird issues with filenames like that.

@yan12125
Copy link
Collaborator

@yan12125 yan12125 commented Sep 16, 2015

Oh prepending the filename with './' works. For example:

youtube-dl --playlist-reverse -f bestvideo+171/bestvideo+140 -o "./%(autonumber)s: %(title)s-%(id)s.%(ext)s" "https://www.youtube.com/playlist?list=PL26B36130624FCAF5"
@yan12125 yan12125 closed this Sep 16, 2015
@paulguy
Copy link
Author

@paulguy paulguy commented Sep 16, 2015

That isn't really obvious when all you get is "Protocol not found" without searching for it, and there's no real indicator that's even coming from ffmpeg. I had to dig around to find out even that much, then find out that it was because of the colon. It'd make more sense if it just worked as expected, and it's not like it's something that can't be done.

@rg3
Copy link
Collaborator

@rg3 rg3 commented Sep 16, 2015

@paulguy
Copy link
Author

@paulguy paulguy commented Sep 17, 2015

It does have an explicit protocol syntax, which will force the specific protocol.
http://www.ffmpeg.org/ffmpeg-protocols.html

@jaimeMF
Copy link
Collaborator

@jaimeMF jaimeMF commented Sep 18, 2015

Thanks for the report, it will use the file: protocol in the next version.

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
4 participants
You can’t perform that action at this time.