-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
AV1/VP9 via SRT, out as MPEG-TS? Or AV1 via RTMP? #4239
Comments
Is it actually necessary to convert SRT to RTMP before converting it to MPEG-TS or HTTP-FLV? Why not remux it directly from SRT to MPEG-TS? In that case, codecs wouldn’t be an issue. I don’t see any benefits of using SRT because it still gets converted to RTMP by SRS, so using it seems pointless. |
Is that the case right now and that's possible already with SRS? Or are you saying it should be the way. |
No not possible yet. Would still be nice to have, as MPEG2-TS supports more codecs / audio channels then RTMP. |
That would be amazing, yes. Or, if the srt_to_rtmp step is crucial, supporting ERTMP V2 spec would suffice as well, I guess. |
As far as i know, AV1 is not yet supported with SRT (only WebRTC and eRTMP), because SRT uses MPEG-TS and AV1 is not yet implemented for transport stream usage. |
What is the business background? Please provide a description.
No business, private use.
Is your feature request related to a problem? Please describe.
This is twofold.
Nowadays AV1 and VP9 get more and more widely adopted. SRS still seems to focus on HEVC, though, at least in version 6.
As far as I know the only way to ingest a stream with AV1 video with SRS is to use SRT or WebRTC.
Describe the solution you'd like
The Enhanced RTMP spec allows for other codecs apart from HEVC, too, so it would be great if SRS could support this.
Otherwise: is it possible to ingest a stream containing AV1 using SRT and converting it to MPEG-TS/HTTP-FLV, so it can be used with mpegts.js, which now supports those newer codecs?
Thank you so much for your work!
The text was updated successfully, but these errors were encountered: