-
Notifications
You must be signed in to change notification settings - Fork 903
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
-filter_complex too long cause cmd prompt crush #161
Comments
I'm converting this to a feature request / enhancement.
(PRs are welcome) |
I think it would be something like stream.run(script_filename='some_script_file') .. or .. stream.run(use_script_tmpfile=True) .. the latter of which automatically determines a temporary script filename and then deletes it when the processing is complete. But this functionality does not exist yet. AFAICT, if your command line arguments are getting too long then this is basically what's needed in order to get around the issue. However, you may still run into issues with command line arguments being too long if you have a lot of input files, because the input filenames probably have to encoded on the command-line either way, even when using But it'd be good to get support for |
On Linux with huge filter chains, I managed to hit the argument length and get this error: I tried bumping the stack size with: I worked around this by getting the ffmpeg command with |
Would using the I haven't tried it, but it seems like we can define input sources within the filter graph, sidestepping the issue entirely. |
I create some code to split and concat with my scenes like below
and when my scenes goes too many
system return
And i found ffmpeg has -filter_complex_script is there any way to use that?
sorry for my poor English. :P
The text was updated successfully, but these errors were encountered: