Pat-rice
commented
6 years ago I've noticed this problem too, it's happening 100% of the time when using wirecast 10.0. If the empty publish event is successful then I receive an empty publish_done
Request body received:
{
"app": "source",
"flashver": "Wirecast/FM 1.0 (compatible; MS",
"swfurl": "",
"tcurl": "rtmp://my-rtmp-server/source",
"pageurl": "",
"addr": "x.x.x.x",
"clientid": "670",
"call": "publish",
"name": "",
"type": ""
}config file:
rtmp {
server {
listen 1935;
ping 30s;
application source {
live on;
wait_key on;
wait_video on;
record all;
record_path /tmp/live/source-records;
record_suffix -%d-%b-%y-%H_%M_%S.flv;
on_publish http://localhost/publish;
on_publish_done http://localhost/unpublish;
on_record_done http://localhost/recorded;
idle_streams off;
hls on;
hls_type event;
hls_path /tmp/live/source_hls;
hls_fragment 2s;
hls_playlist_length 5m;
hls_nested on;
hls_fragment_naming system;
}
}
}
PyvesB
tmakin
atyachin
cescp
I'm having some weird problems where there is a second publish event with no name or type just before an unpublish event. This only happens sometimes, but about 70% of the time. I came across this because the exec_recording_done directive was returning wrong values for $path, $name, $basename etc. where the filename part would be
-1459442871.flvinstead ofstream-1459442871.flv. I'm assuming because the second publish event has no name, it simply takes the empty string as the name and passes that to to the variables.The behavior is similar to what is referenced in #341 and #351. I'm using Wirecast 6.0.6 to stream to nginx.
nginx version:
My nginx config:
debug log:
Wirecast log: