-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
setComplexVideoFilter with unexpected results with filtergraph #81
Comments
setComplexVideoFilter
with unexpected results with adelay/amix
More failed tests with similar results
The last filter would allow us to run from the command line as |
It seems like it is related to how
Not sure the |
@bramp Would you accept a pull request with this modification? |
There are a lot of Windows users of this library, so I wouldn't want to put a Linux specific fix in place. I will accept pull requests to fix this in a generic way. |
I just read more about the failings in how java handles character escaping. http://bugs.java.com/view_bug.do?bug_id=6468220 and http://bugs.java.com/view_bug.do?bug_id=6518827 It might be worth using https://commons.apache.org/proper/commons-exec/index.html instead of the process builder. Happy to accept that pull request. |
I'm using the
setComplexVideoFilter
to add anadelay/amix
filter, to merge audio and video tracks that have different lengths, into a single file. I have ffmpeg 3.2 installed in OS X.The actual command that works is
ffmpeg -y -v error -i video.trk -i audio.trk -filter_complex "[1:0]adelay=10000|10000[t1];[t1]amix=inputs=1" -c:v copy out.webm
. To have the library generating the same command, I had to add escaped quotes to the string, producing the following lineoutputBuilder.setComplexVideoFilter("\"[1:0]adelay=10000|10000[t1];[t1]amix=inputs=1\"");
. This yields the following result.Issuing the following line
outputBuilder.setComplexVideoFilter("[1:0]adelay=10000|10000[t1];[t1]amix=inputs=1");
produces an expected error, as the complex filter should go between quoteswhich is expected, as it is the same output that you get when running from command line.
Not sure if there's anything we can do here, and is a problem from the
ProcessBuilder
itself. Any ideas?The text was updated successfully, but these errors were encountered: