-
Notifications
You must be signed in to change notification settings - Fork 27
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
Issues with filenames containing spaces #8
Comments
The plot thickens; i've tried dropping the spaces when using the mount option, and it's saying the file doesn't exist, but if i take that exact path and do a
|
Confirmed however that removing the spaces, and using streaming does work. |
Thanks for the exhaustive testing. I'll do some digging to see what the
deal is. I've used it mostly with WSL but will concentrate on testing with
native ffmpeg.
…On Tue, Nov 26, 2019 at 2:34 PM dgibbard-cisco ***@***.***> wrote:
Confirmed however that removing the spaces, and using streaming does work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8?email_source=notifications&email_token=AAHRMTH4IPDUKMJJ6C5S7JDQVV25FA5CNFSM4JR4PFT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHGFHA#issuecomment-558785180>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHRMTFN3J64PKMT5H3TCNLQVV25FANCNFSM4JR4PFTQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I'm having some issues getting a clustered setup working, when using files which contain spaces, both streamed and SSH.
Server: Ubuntu 18.04
Encoding Client: Windows 10, Native SSH (not WSL), Streamed config or Mapped Drive config
With streaming, it successfully copies the file over and then reports:
Running the command against the successfully copied file manually gives:
With the mapped drive it's a similar story, seems the quotes are being passed in, but not escaped, so they're dropped by the client?
The text was updated successfully, but these errors were encountered: