-2

My requirement: I want to stream to a person (Larix?) With my smartphone and get the audio from that person. The latency should be as low as possible and the quality as high as possible. I want to host the whole thing on my server.

What is the best method? I've tried SRS, the quality is high and the latency is low, but I don't know how to get the audio from the other person.

Would SRT also be an option?

What is best suited to make that happen?

Marco Heine
  • 47
  • 2
  • 6

2 Answers2

2

Once published live stream to SRS, over RTMP by OBS, FFmpeg or other encoder, you could play the stream on other devices.

Generally there are serval players, on both H5 or mobile:

  • HLS, about 5~10s latency, easy to play, you only need a H5 video tag, or hls.js.
  • HTTP-FLV, about 1~3s latency, also very easy, please use flv.js player.
  • WebRTC, about 0.5~1s latency, it's realtime, but be careful, especially on your mobile browser.

Note that all H5 native js player works perfect with MSE except iOS Safari browser. For iOS Safari, it's possible to play the HTTP-FLV by WASM also, please read link for details.

On mobile(iOS/Android) platform, it's OK to use ijkplayer which use FFmpeg, and there is some wraps like fijkplayer for flutter.

ChrisF
  • 134,786
  • 31
  • 255
  • 325
Winlin
  • 1,136
  • 6
  • 25
  • Just so you are aware, there is an ongoing discussion about the srs tag on Meta: https://meta.stackoverflow.com/questions/414796/what-to-do-about-a-user-trying-to-change-the-meaning-of-the-srs-tag?cb=1 – Tyberius Dec 16 '21 at 18:37
  • Thank you very much, I answered that question. I really need a tag to gather all questions about SRS. But seems it's not good to use tag srs, because it's too simple and lots of same meanings. – Winlin Dec 17 '21 at 00:55
1

Given the latency requirements it sounds like a real time focused solution leveraging RTSP, Web RTC or similar would be a good approach.

Using something like this as close to standard as possible with video only in one direction and audio only in the other direction (or both if you need it) seems like it might be the easiest approach.

I think you may find this much easier and quicker than starting from scratch yourself, especially to get the best quality within a given latency budget as this is a core consideration of WebRTC.

There are existing Web RTC Android and iOS clients which you can build on - more are available all the time so worth searching but some examples:

Mick
  • 24,231
  • 1
  • 54
  • 120