srt VS KCP

Is receiver side also using mobile internet? You could try to setup this on separate server and both sender and receiver connnect to it. https://github.com/Haivision/srt/blob/master/docs/apps/srt-live-transmit.md

Here is one example how to feed SRT stream to ffmpeg. Try streaming directly to this via OBS first and confirm it works before stacking more software between endpoints. https://github.com/Haivision/srt/issues/506

SRT, or Secure Reliable Transport, is a type of streaming protocol that provides enhanced security and reliability for video streaming. SRT is becoming increasingly popular among broadcasters and streamers including industry stalwarts such as ESPN because of its ability to deliver high-quality content over challenging network conditions and for its ability to make contribution and stream ingestion easy. SRT streams provide improved security, low latency, and flexibility and is supported by a global community of developers all contributing to the open-source project. Because of the power of SRT streams, Dolby.io Real-Time Streaming has decided to launch support with an SRT open beta program.

https://github.com/Haivision/srt/discussions/2220 I think this is probably the basis of what i did...

If it turns out to be an SRT/socket issue (rather than an audio issue) you can pump FFmpeg into https://github.com/Haivision/srt srt-live-transmit, and let that do the SRT. It is a very long time since I played with srt-live-transmit, but it did behave differently to both FFmpeg and TSDuck's SRT impementations when there were input issues. Obviously, putting more components in the chain may be disadvantageous, but component abstraction can help when debugging.

SRT is an open-source protocol developed by streaming technology provider Haivision. Known for its security, reliability, compatibility, and low-latency streaming it is the preferred protocol for members of the SRT Alliance. This protocol does not rely on a single codec, which allows developers to pair it with any audio and video codecs they desire.

I've also looked at SRT, which to all intents and purposes ought to work, but doesn't?

KCP Is a kind of protocol ( like UDP and TCP ) that is reliable like TCP but is faster, at to cost of slightly bigger bandwidth costs.

I'd consider KCP protocol over TCP, it has 30-40% lower latency at the expense of 20% higher bandwidth.

i see, i know KCP implementation i don't see in your code any of the GO KCP implementations did you write it by yourself?