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

ffmpeg filename handling (red herring: "No protocol not found") #247

Closed
philippera opened this issue Apr 21, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@philippera
Copy link

commented Apr 21, 2019

Hello and thank you for this useful program.
I tried to download the youtube video called "Spacemacs: Magit staging and commit basics" with default settings. At the end of the 2 downloads (1 pure video + 1 pure audio) I got printed:

2019-04-21 14:13:32 (26.0 KB/s) - ‘Spacemacs: Magit staging and commit basics - natNUgnh_no - audio.webm’ saved [7036590/7036590]

[*] Merging into MKV...
Spacemacs: Magit staging and commit basics - natNUgnh_no - audio.webm: Protocol not found
Did you mean file:Spacemacs: Magit staging and commit basics - natNUgnh_no - audio.webm?

The first thing that came to mind was that the filenames contain special characters and indeed that is the problem.
I used ffmpeg to reproduce the problem like so:

$ ffmpeg -i Spacemacs:\ Magit\ staging\ and\ commit\ basics\ -\ natNUgnh_no.webm -i Spacemacs:\ Magit\ staging\ and\ commit\ basics\ -\ natNUgnh_no\ -\ audio.webm -c copy output.mkv

It gives the same error message ("...Protocol not found...").
If I rename the files to something sensible like video.webm and audio.webm then the ffmpeg command works fine.
It's probably just a matter of quoting the filenames or something similar but I have no experience in perl so I'm not proposing a fix here.

@trizen trizen closed this in e2c1d10 Apr 21, 2019

@trizen

This comment has been minimized.

Copy link
Owner

commented Apr 21, 2019

Thanks for finding and reporting this issue. Fixed in the above commit.

Alternative fix would be to set fat32safe => 1 in the configuration file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.