-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Multiplexed stream is not present in OriginMapStore Redis db #1577
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Mux -> ovt_stream.cpp -> OvtStream::Start() GetLinkedInputStream() is always nullptr when start from Mux. when i'm test bypass checking IsFromOriginMapStore, it's work register to Redis.
|
I have resolved this issue and committed it to the master branch. Could you please check if your issue has been resolved as well? |
Could you share your configuration files including Server.xml and xxx.mux files so that I can reproduce the problem. |
Here is the mux file -
|
Here is the config, but sensitive informations has been replaced
|
All mux providers in your app are looking at the same .mux path.
So when you create a mux channel in a particular app, other apps will see that .mux file and create the same channel in their own apps. Try creating different MuxFilesDirs for all apps. |
Suppose I want to multiplex ('mux') 'stream720' and 'stream480' into 'stream'. However, upon inspection, I noticed that 'stream' is not present in Redis, while 'stream720' and 'stream480' are.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When started streaming, redis db should have 3 stream including the multiplexed stream. But it shows two streams only
Logs
ovenmediaengine.log
Server (please complete the following information):
Originally posted by @maruf-cs in #1489 (reply in thread)
The text was updated successfully, but these errors were encountered: