-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
second publish event just before unpublish #789
Comments
I've noticed this problem too, it's happening 100% of the time when using wirecast 10.0. If the empty
config file:
|
Hi there, We were facing similar issues with the "done" notification having an empty |
@PyvesB Thanks for that ! However on my end, the main problem is that I receive this second "publish" event, and I ended up adding special rules to let it through in order to receive the "done" notification. |
@PyvesB @Pat-rice I've just been messing around with a similar issue with missing What I really don't understand is why my previous version worked fine a few weeks ago. Probably a timing issue of some description, perhaps due to docker or other gremlins on my dev machine. |
@PyvesB We tried your fork with Wirecast 12.2.1 and same issues still happen as other people reported once you stop streaming in Wirecast:
The below is nginx log when starting/stopping a stream from the same machine using OBS and Wirecast (compare the events after notify: publish): OBS: Wirecast: |
Same issue with Wirecast 13.0.1. This is my suggested solution (from version v1.2.1):
|
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.flv
instead 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:
The text was updated successfully, but these errors were encountered: