Replies: 2 comments 9 replies
-
This could be a problem with StreamMap, because I don't see the ability there to set a static ID for each push. When you say the entries come back with different IDs, are you aware of how these IDs are being generated? In my scenario we control push publishing entirely through API and it works as intended. In case it inspires or helps, here are the steps we take:
This all works smoothly and as expected, so again I wonder if the issue has to do with StreamMap and whether it is possible to set a static Push ID to avoid duplication of pushes. |
Beta Was this translation helpful? Give feedback.
-
In version 0.17.3, there's an issue where pushing through StreamMap causes session duplication or prevents deletion. This has been patched in the Master branch but hasn't been released yet. It should work properly once the next version is released. Thanks :) |
Beta Was this translation helpful? Give feedback.
-
Hi everybody, as the title says, I need help concerning a strange behavior of the push publishing feature.
We have this feature running in our Oven Media, with a stream map that contains the definitions of the push.
We push streams from FFmpeg to the Oven Media instance, but if we stop FFmpeg, and then we start again, the POST/ pushes api shows us a new entry for the same existent stream with different sequence numbers each time, different ids... Sometimes the two streams are in a pushing state, sometimes one is pushing, and the other one is ready.
So for our workflow, the main problem is, that in case of an unstable network or if we lost the stream for a couple of seconds, and then it starts streaming again the push publishing feature doesn't use the same existent push that has been registered previously, so it recreates a new entry each time.
Can you please tell us if this is a normal behavior or if this could be fixed on next releases?
Thanks a lot,
Beta Was this translation helpful? Give feedback.
All reactions