Conversation
Fixes on_publish redirection to the new stream name based on the location header
|
You just changed the line of one module name located in the config file and the issue fixed ?! |
|
Well, event callback chain of the sub-modules is defined statically. As you can see in the next_publish = ngx_rtmp_publish;
ngx_rtmp_publish = ngx_rtmp_(.*)_publish;Any new, configured sub-module uses their own callback as the new "head" of the chain, pushing others further. So, compilation order matters, and it's resolved in reverse order. To workaround HLS/DASH issue, moving notification sub-module lower in the configuration allows it to be placed closer the beginning of the chain and therefore allows to be evaluated before HLS/DASH sub-module starts their own job. |
|
Thanks! |
|
Awesome, it worked well. |
Fixes on_publish redirection to the new stream name based on the location header