You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the business background? Please provide a description.
In the live streaming scenario of Oryx, customers have a need to manage and identify specific target devices precisely. The devices and their corresponding stream pushing codes and keys are in a one-to-one mapping relationship. Customers require the ability to explicitly and quickly match the target device and its number based on the stream pushing code. This is crucial for efficient device management and accurate streaming operations.
Who are the users? How do they utilize this feature? What problem does this feature address?
The users are primarily the broadcasters or the technical teams responsible for setting up and managing the live streaming in Oryx. They will utilize this feature to modify the stream pushing code and key of the live streaming room. This addresses the problem of the lack of a direct and convenient way to adjust the stream pushing code and key, which is essential for accurate device identification and stream management. Currently, without this feature, it is difficult for them to quickly match the target device and number based on the stream pushing code, causing inefficiencies in operations and potential errors in device-stream pairing.
Is your feature request related to a problem? Please describe.
I'm always frustrated when trying to manage the live streaming devices in Oryx. As the stream pushing code and key cannot be modified easily, it becomes extremely challenging to accurately match the target device and its corresponding number. This leads to confusion and inefficiency in the overall live streaming setup and management process. Although it is possible to make modifications through the API, this increases the complexity and is not user-friendly for those who are not well-versed in API operations. We need a more straightforward solution.
Describe the solution you'd like
We would like to have a function in the Oryx live streaming room settings that allows users to modify the stream pushing code and key. This function should be easily accessible and intuitive to use. After modification, the system should immediately update the relevant settings and ensure that the new stream pushing code and key are correctly associated with the corresponding device and number. Ideally, this modification can be directly carried out on the front end, eliminating the need to deal with the complexity of API calls.
Describe alternatives you've considered
One alternative considered was to use a workaround by creating a separate mapping table outside the Oryx system to manage the relationship between devices and stream pushing codes. However, this would introduce additional complexity and potential synchronization issues between the external table and the Oryx live streaming system. Another alternative was to rely on a fixed set of default stream pushing codes and keys and try to manage the devices based on other identifying information, but this would not meet the specific requirement of using the stream pushing code for quick and accurate device matching.
Additional context
N/A (As there is no specific screenshot or additional context available at this moment related to this feature request.)
Thank you to the development team for considering this feature request. We truly appreciate your efforts in continuously improving the Oryx platform.
The text was updated successfully, but these errors were encountered:
What is the business background? Please provide a description.
In the live streaming scenario of Oryx, customers have a need to manage and identify specific target devices precisely. The devices and their corresponding stream pushing codes and keys are in a one-to-one mapping relationship. Customers require the ability to explicitly and quickly match the target device and its number based on the stream pushing code. This is crucial for efficient device management and accurate streaming operations.
Who are the users? How do they utilize this feature? What problem does this feature address?
The users are primarily the broadcasters or the technical teams responsible for setting up and managing the live streaming in Oryx. They will utilize this feature to modify the stream pushing code and key of the live streaming room. This addresses the problem of the lack of a direct and convenient way to adjust the stream pushing code and key, which is essential for accurate device identification and stream management. Currently, without this feature, it is difficult for them to quickly match the target device and number based on the stream pushing code, causing inefficiencies in operations and potential errors in device-stream pairing.
Is your feature request related to a problem? Please describe.
I'm always frustrated when trying to manage the live streaming devices in Oryx. As the stream pushing code and key cannot be modified easily, it becomes extremely challenging to accurately match the target device and its corresponding number. This leads to confusion and inefficiency in the overall live streaming setup and management process. Although it is possible to make modifications through the API, this increases the complexity and is not user-friendly for those who are not well-versed in API operations. We need a more straightforward solution.
Describe the solution you'd like
We would like to have a function in the Oryx live streaming room settings that allows users to modify the stream pushing code and key. This function should be easily accessible and intuitive to use. After modification, the system should immediately update the relevant settings and ensure that the new stream pushing code and key are correctly associated with the corresponding device and number. Ideally, this modification can be directly carried out on the front end, eliminating the need to deal with the complexity of API calls.
Describe alternatives you've considered
One alternative considered was to use a workaround by creating a separate mapping table outside the Oryx system to manage the relationship between devices and stream pushing codes. However, this would introduce additional complexity and potential synchronization issues between the external table and the Oryx live streaming system. Another alternative was to rely on a fixed set of default stream pushing codes and keys and try to manage the devices based on other identifying information, but this would not meet the specific requirement of using the stream pushing code for quick and accurate device matching.
Additional context
N/A (As there is no specific screenshot or additional context available at this moment related to this feature request.)
Thank you to the development team for considering this feature request. We truly appreciate your efforts in continuously improving the Oryx platform.
The text was updated successfully, but these errors were encountered: