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

exec_options in rtmp or server block ignored #1316

Open
half-duplex opened this issue Sep 4, 2018 · 2 comments
Open

exec_options in rtmp or server block ignored #1316

half-duplex opened this issue Sep 4, 2018 · 2 comments

Comments

@half-duplex
Copy link

nginx 1.15.3
nginx-rtmp-module 1.2.1

The wiki says exec_options is valid in rtmp, server, or application blocks, and it is indeed accepted in all of them, but only appears to have an effect in an application block.

rtmp {
    exec_options on;
    server {
        listen 1935;
        application live {
            live on;
            exec_push ffmpeg -i foo bar name=mystream;
        }
    }
}

Expected: exec_options on; applies to all servers and applications where it's not overridden
Observed: exec_options on; is not observed (ffmpeg is run for all stream names), and name=mystream is put into the ffmpeg arguments.

Workaround: Add exec_options on; to each application block

@TalkVideo
Copy link

There is a bug here. See other postings on similar topic. It seems the whole exec system is not working.

@zarat
Copy link

zarat commented Nov 14, 2019

In windows it doesnt work as far as i know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants