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
Currently, the forwarding mode in circulation needs to be configured through a configuration file. Can you please add the option to configure the forwarding URL?
For example:
Forwarding URL: rtmp://192.168.1.2/myapp/mystream?forward=rtmp://cdn.com/myapp/mystream?XXXXXX
This would make it more convenient to change whether the stream needs to be forwarded at any time. Currently, we have a use case where most of the streams only need to be viewed within the local network and do not require internet access. However, sometimes certain playback sources need to be played on the internet. Configuring this forwarding through a config file is not very flexible.
Could you please add this functionality or suggest a way to achieve a similar effect? Alternatively, could you provide guidance on how I can quickly modify the code to achieve this functionality?
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered:
Currently, the forwarding mode in circulation needs to be configured through a configuration file. Can you please add the option to configure the forwarding URL?
For example:
Forwarding URL: rtmp://192.168.1.2/myapp/mystream?forward=rtmp://cdn.com/myapp/mystream?XXXXXX
This would make it more convenient to change whether the stream needs to be forwarded at any time. Currently, we have a use case where most of the streams only need to be viewed within the local network and do not require internet access. However, sometimes certain playback sources need to be played on the internet. Configuring this forwarding through a config file is not very flexible.
Could you please add this functionality or suggest a way to achieve a similar effect? Alternatively, could you provide guidance on how I can quickly modify the code to achieve this functionality?
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: