SRS Cloud: Using FFmpeg+SRS for live streaming transcoding cluster

[winlinvip]

How to achieve multi-bitrate streaming for live streaming, so that the streams viewed on PCs and mobile phones are different, of course, using FFmpeg, but it involves some logic:

• Match different streams from SRS, not all streams need to be transcoded.
• Need a simple background to see the status of these transcoding tasks.
• Need some template management to reduce the difficulty of using FFmpeg command line directly.

Currently, it mainly pushes streams to cloud vendors for transcoding, and it's worth making a DEMO.

If you need it, please leave a message in the comments section.

[lonelygo]

Well, this Feather (Demo) is still very meaningful. Transcoding (1 input N output, ABR) is needed for multi-terminal/multi-network environment streaming testing/production.

[jinleileiking]

I personally think this is not something SRS should do; it should be done by a larger project (which we are currently doing). Transcoding is a transcoding system; the SRS system and the transcoding system are scheduled through an API: srs-cluster <-- grpc server -> trans system (ffmpegs)

[winlinvip]

@jinleileiking This is an open-source replica solution, not transcoding in SRS, but making an additional DEMO, combining FFmpeg and SRS, as well as the management background.

If it's a feature, it wouldn't be called "open-source replica"; it would be called invoking FFmpeg API for transcoding. Calling it an open-source replica means making a complete solution DEMO, and this kind of label is also a Solution, not a Feature.

Many people have implemented live streaming transcoding systems; Zhang San has implemented one, and Li Si has also implemented one, but no one has open-sourced it, and new friends still don't know how to do it. Newcomers can't possibly know how to create a live streaming transcoding system based on just one sentence.

If you're interested, we can work on it together, and there will be a separate repository coming out later.

[lonelygo]

Yes, in larger usage scenarios, "Demo" it to let users understand the "best practices" and optional technical routes/solutions for SRS applications in such scenarios.