You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a couple of issues -- it's all a little hazy but some notes if helpful
a) open(...) used to get the file handle for the pipes, seems unhappy when the path has spaces
b) the commands for ffmpeg seem unhappy when there is spaces in the path to ffmpeg
about (a) I am not 100% certain but I think it's an issue.
the solution for me for (a) was to use a relative path without spaces -- since I'm doing something kind of funky and having ffmpeg inside the app bundle and for (b) the solution was to modify how the command is put together and wrap the path to ffmpeg in some quotes.
I'll investigate this some more before a PR but in case it's helpful, just writing some notes here.
The text was updated successfully, but these errors were encountered:
Thanks for the bug report. There have been issues in the past with spaces in filenames, and ffmpeg seems to be extra finicky in that regard. I'll take a look soon, and happy to accept a PR if you're able to pin it down in the meantime.
I noticed a couple of issues -- it's all a little hazy but some notes if helpful
a) open(...) used to get the file handle for the pipes, seems unhappy when the path has spaces
b) the commands for ffmpeg seem unhappy when there is spaces in the path to ffmpeg
about (a) I am not 100% certain but I think it's an issue.
the solution for me for (a) was to use a relative path without spaces -- since I'm doing something kind of funky and having ffmpeg inside the app bundle and for (b) the solution was to modify how the command is put together and wrap the path to ffmpeg in some quotes.
I'll investigate this some more before a PR but in case it's helpful, just writing some notes here.
The text was updated successfully, but these errors were encountered: