odingrail Comments - Answer Overflow

odingrail

Posts Comments

SMSoftware Mansion

•Created by nickdichev_fw on 5/9/2023 in #membrane-help

Intermittent Failures with RTMP Sink

So it is somehow trying to call Native.write_video_frame with the audio payload

8 replies

SMSoftware Mansion

•Created by nickdichev_fw on 5/9/2023 in #membrane-help

Intermittent Failures with RTMP Sink

But unlike your case, our payload is actually the audio payload: %Membrane.Buffer{payload: <<255, 241, 80, 128, 1, 191, 252, 33, 16, 4, 96, 140, 28>>, pts: 4318911564, dts: nil, metadata: %{name: :rtsp_source_tcp_receiver, socket: #Port<0.26100>, rtp: %{timestamp: 3337790470, extensions: [], marker: true, sequence_number: 911, payload_type: 97, ssrc: 3256846846, padding_size: 0, csrcs: [], total_header_size: 12}}}

8 replies

SMSoftware Mansion

•Created by nickdichev_fw on 5/9/2023 in #membrane-help

Intermittent Failures with RTMP Sink

Hey! Any updates on this? We are running in the same issue when doing the forwarding to the RTMP sink.

8 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

Hey! Yes, you are right. When we were prototyping the pipeline we just set the socket to active mode and forgot about that 👀 .

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

Thanks everyone, I think that issue was that in the source element we set the TCP socket to active mode. After switching to the active: size and manual flow control the machine is able to sustain 28 WebRTC streams without significant growth of memory. (The CPU's are on 100%)

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

We are trying to do the WebRTC distributed streaming. The architecture is roughtly the following: the have some node that consumes the stream (running the webrtc_sink and other elements), and then we are sending packets to "Room" process, which in turns distributes the packets accorss the peers, for that we are using the Phoenix PubSub.

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

We are streaming RTSP with TCP transport, but similar resource consumption is also noted with RTMP streaming.

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

The docs suggested the format:

[:membrane, :element | :bin | :pipeline, callback, :start | :stop | :exception]

[:membrane, :element | :bin | :pipeline, callback, :start | :stop | :exception]

18 replies

SMSoftware Mansion

•Created by odingrail on 3/28/2025 in #membrane-help

High WebRTC CPU consumption

Also, it is unclear how to consume the telemetry metrics even after reading the documentation(. I'm trying this and I got 0 events reported with working pipeline, what is the issue here?:

summary("membrane.http_adaptive_streaming_parser.handle_buffer.start", unit: {:native, :millisecond})

summary("membrane.http_adaptive_streaming_parser.handle_buffer.start", unit: {:native, :millisecond})

Also, my config.exs:

config :membrane_core,
  telemetry_flags: [
    tracked_callbacks: [
      bin: :all,
      element: :all,
      pipeline: :all
    ]
  ]

config :membrane_telemetry_metrics, enabled: true

config :membrane_core,
  telemetry_flags: [
    tracked_callbacks: [
      bin: :all,
      element: :all,
      pipeline: :all
    ]
  ]

config :membrane_telemetry_metrics, enabled: true