Replies: 54 comments
-
Can srs3 be used in production now?
|
Beta Was this translation helpful? Give feedback.
-
SRS3 is currently in alpha-4, and it will be available for production use once it reaches beta stage.
|
Beta Was this translation helpful? Give feedback.
-
The milestone plan has almost covered everything, and there are no new expected abilities to propose. If used for production, stability should be the most important indicator. I hope stability can be further improved. Additionally, I would like to give you a thumbs up for your efforts. This project is a great work. 👍
|
Beta Was this translation helpful? Give feedback.
-
Don't you plan to support RTSP? For example: input RTSP and output RTMP/RTSP.
|
Beta Was this translation helpful? Give feedback.
-
The milestone plan is already comprehensive, and everything I wanted to say is included in it.
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Webrtc is essential for streaming via browser. Rtmp without flash doesn't work well via browser (ex. I can't publish streaming). |
Beta Was this translation helpful? Give feedback.
-
@ciaoamigoschat Agreed. I think RTC is one of the next extreme important things for live streaming. And I am sure SRS will support WebRTC in future, mabye in SRS4 or SRS5, it depends on how many time I have for working on this project, it also depends on whether it's stable enough to enable us to add more big/huge features like this. |
Beta Was this translation helpful? Give feedback.
-
This is the right time to implement webrtc. Many sites are abandoning flash and looking for a viable alternative. |
Beta Was this translation helpful? Give feedback.
-
I wish we could support the conversion of WebRTC streams, so that we can play them directly on mobile devices. It would be more real-time compared to HLS.
|
Beta Was this translation helpful? Give feedback.
-
WebRTC is mainly used natively on mobile devices, and it may not be readily available for use on mobile web pages. It is primarily stable on PCs, but it can also be integrated into native mobile applications.
|
Beta Was this translation helpful? Give feedback.
-
QUIC should be supported
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
You are losing sight of the problem. |
Beta Was this translation helpful? Give feedback.
-
As a complete novice in the field of live streaming, video processing, and streaming media, my expectations for SRS are "plug-and-play" and "enterprise-level application stability". I used SRS2 before and encountered many problems during compilation. It was only when I used an "unofficial" Docker image that I was able to partially solve the "plug-and-play" issue. Of course, now that SRS has provided an official Docker image, I immediately switched to the official one. As for stability, as it was my first attempt to use a streaming media solution for real-time access, I encountered many issues during the process. However, as long as the infrastructure (such as the network) is sufficiently reliable, I have not observed any "unstable" situations, which exceeded my expectations. I am very grateful to SRS for this. Lastly, regarding the application scenario, the cameras are distributed in independent network environments in 20 cities. They are connected to the public cloud network through a VPN and ffmpeg is used to pull the camera's RTSP stream according to policies, and then push it to the SRS server in the public cloud for distribution.
|
Beta Was this translation helpful? Give feedback.
-
I would live to contribute and help building the WevRTC support. |
Beta Was this translation helpful? Give feedback.
-
@itzikgili Thanks, SRS4 has supported publishing by RTMP and playing by WebRTC, please read #307 , welcome to join us to make it better. 😄 |
Beta Was this translation helpful? Give feedback.
-
希望可以考虑下H265转码后在网页的播放 |
Beta Was this translation helpful? Give feedback.
-
Sure thing, I would love to! |
Beta Was this translation helpful? Give feedback.
-
Damn i will give a look at WebRTC too ! |
Beta Was this translation helpful? Give feedback.
-
因为对直播来说,延迟至关重要。RTMP是基于TCP的,哪怕用商业CDN,延迟也在2~3s。这个延迟还是很大,对于一些连麦直播或在线游戏直播来说,还是大。所以,希望能够在SRS5支持QUIC。 |
Beta Was this translation helpful? Give feedback.
-
@freeman1974 延迟问题,SRS已经支持了RTMP推流WebRTC播放,以及WebRTC推流和播放。 |
Beta Was this translation helpful? Give feedback.
-
JT1078要是也能支持,那么srs在交通行业就完美了 |
Beta Was this translation helpful? Give feedback.
-
SRS 4.0会考虑支持webrtc推流转RTMP或者hls之类的播放不 |
Beta Was this translation helpful? Give feedback.
-
@winlinvip SRS 4.0会考虑支持webrtc推流转RTMP或者hls之类的播放不 |
Beta Was this translation helpful? Give feedback.
-
SRS 4.0 会支持webrtc视频会议么? |
Beta Was this translation helpful? Give feedback.
-
kcp应该支持下呢? |
Beta Was this translation helpful? Give feedback.
-
你能做得到吗?做不到就用Go吧,用CPU换稳定性。 是不是go的版本已经处于放弃状态了? 在webrtc风口之上,go对网络的亲和性相对比ST更好。从团队维护产品及自动化运维的角度来说也是更优的(单从效率来说)。 SRS现在的release版本已经是非常稳定且生产可用的了。 是不是有团队可以继续维护go的版本? |
Beta Was this translation helpful? Give feedback.
-
监控上云是现在监控行业想摆脱设备厂商的痛点,28181 解决痛点的关键技术 |
Beta Was this translation helpful? Give feedback.
-
监控上云是现在监控行业想摆脱设备厂商的痛点,28181 解决痛点的关键技术。 |
Beta Was this translation helpful? Give feedback.
-
About the Development Direction of SRS
SRS3 is currently being enhanced for stability and is being released intensively. This means that SRS3 will not support major changes but will only focus on improving stability, indicating that SRS4 is coming.
SRS4's codename is Leo. Thanks to all the brothers and sisters who have been fighting together for over a decade. You can find the story about the codename Leo here.
This issue is to discuss what SRS4 should support. I understand that there is a strong demand for new protocols such as WebRTC, SRT, QUIC, and KCP. However, I have already decided that supporting new protocols will not be the focus. SRS4 will probably support some new protocols, but the main focus will be on usability and ease of use, in simple terms, it will be more stable and user-friendly.
Is SRS unstable? For an open-source project, it may meet the requirements. There are very few open-source projects with a core protocol coverage rate of over 95% and an overall coverage rate of around 50% (of course, stability has many more aspects that are not discussed here). However, the requirements for SRS are to directly provide services on industrial servers, requiring even higher stability. There are many areas that need careful handling, especially in cases of inconsistency, such as player timeouts, source cleaning, race conditions, and cooperation among multiple coroutines. Stability is a fundamental capability that cannot be compromised. The more investment, the more stability.
Is SRS difficult to use? Based on feedback and continuous observations, it should not be considered difficult to use. However, the requirements for SRS are to directly provide services on commercial servers, so usability needs to be further improved. This mainly involves Dockerization, integration with cloud services, HTTP protocol enhancements such as monitoring the online audience of HLS, and providing operational data solutions through JSON-structured logs. Currently, the HTTP part of SRS mainly refers to the implementation of HTTP 1.1 in Go. In the future, consideration will be given to porting more underlying capabilities from NGINX. For example, it may be possible to directly run NGINX modules on SRS, which gives us something to look forward to. See reference #1657.
In addition, security and licensing have always been the focal points of SRS. In terms of security, it mainly involves anti-leeching measures, enhanced restrictions such as rate limiting and client limitations, encryption and decryption, and code vulnerability detection. As for licensing, the only issue currently is replacing ST with at least one optional version that does not have licensing limitations.
So, dear reader, what key capabilities do you expect SRS4 to support? Please reply to this issue 😄 😄
Make sure to maintain the markdown structure.
TRANS_BY_GPT3
Beta Was this translation helpful? Give feedback.
All reactions