oleg.okunevych Comments - Answer Overflow

oleg.okunevych

Posts Comments

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

I've found sps and pps in handle_announce SDP payload and it worked once, will continue debugging, thank you!

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

thank you, it seems setting this option helped with warnings, but still experience issue with Parser: it receives payload, but no actual demand on output pad. What could cause it?

    |> child(:depayloader, Membrane.RTP.H264.Depayloader)
    |> child(:rtsp_video_parser, %Membrane.H264.Parser{
      generate_best_effort_timestamps: %{framerate: {25, 1}},
      output_stream_structure: :annexb
    })
    |> via_in(:input,
      options: [encoding: :H264, segment_duration: Membrane.Time.seconds(4)]
    )
    |> child(:hls, %Membrane.HTTPAdaptiveStream.SinkBin{
      target_window_duration: Membrane.Time.seconds(120),
      manifest_module: Membrane.HTTPAdaptiveStream.HLS,
      storage: %Membrane.HTTPAdaptiveStream.Storages.FileStorage{
        directory: "/tmp/"
      }
    })

    |> child(:depayloader, Membrane.RTP.H264.Depayloader)
    |> child(:rtsp_video_parser, %Membrane.H264.Parser{
      generate_best_effort_timestamps: %{framerate: {25, 1}},
      output_stream_structure: :annexb
    })
    |> via_in(:input,
      options: [encoding: :H264, segment_duration: Membrane.Time.seconds(4)]
    )
    |> child(:hls, %Membrane.HTTPAdaptiveStream.SinkBin{
      target_window_duration: Membrane.Time.seconds(120),
      manifest_module: Membrane.HTTPAdaptiveStream.HLS,
      storage: %Membrane.HTTPAdaptiveStream.Storages.FileStorage{
        directory: "/tmp/"
      }
    })

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

@Billal good catch, we actually haven't done it. Implemented a Filter which reorders packets by sequence number and sends when buffer reaches a limit, the amount of warnings reduced, packets are coming to the Parser through the Depayloader, however it got stuck in the Parser (no demand at output pad according to Pipeline Dashboard). PS: We are receiving NACKs from RTCP Receiver, do we need to handle it somehow? Right now we aren't handling the RTCP Socket at all.

13:05:26.381 [debug] pid=<0.1097.0> mfa=Membrane.RTCP.Receiver.handle_event/4  <0.1016.0>/:video_rtp/{:stream_receive_bin, 2787058368}/:rtcp_receiver Sending NACK to 2787058368 with ids [6305, 6306, 6307, 6308, 6309, 6310, 6311, 6312, 6313, 6314, 6315, 6316, 6317, 6318, 6319, 6320, 6321, 6322]

13:05:26.381 [debug] pid=<0.1097.0> mfa=Membrane.RTCP.Receiver.handle_event/4  <0.1016.0>/:video_rtp/{:stream_receive_bin, 2787058368}/:rtcp_receiver Sending NACK to 2787058368 with ids [6305, 6306, 6307, 6308, 6309, 6310, 6311, 6312, 6313, 6314, 6315, 6316, 6317, 6318, 6319, 6320, 6321, 6322]

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

FFmpeg command used to push the stream:

ffmpeg -re -stream_loop -1 -i ~/big_buck_bunny_1080p_h264.mov \
-c:v libx264 \
-b:v 2000k \
-maxrate 2000k \
-bufsize 4000k \
-c:a aac \
-b:a 128k \
-ar 44100 \
-ac 2 \
-f rtsp \
-rtsp_transport udp \
-timeout 5000000 \
rtsp://localhost:8554/5e1671fa-171a-4d9b-b2b6-2eaf13452ced

ffmpeg -re -stream_loop -1 -i ~/big_buck_bunny_1080p_h264.mov \
-c:v libx264 \
-b:v 2000k \
-maxrate 2000k \
-bufsize 4000k \
-c:a aac \
-b:a 128k \
-ar 44100 \
-ac 2 \
-f rtsp \
-rtsp_transport udp \
-timeout 5000000 \
rtsp://localhost:8554/5e1671fa-171a-4d9b-b2b6-2eaf13452ced

Would you mind to help us sort out, what's wrong with the implementation?

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

15:10:28.603 [error] pid=<0.1086.0> mfa=Membrane.Core.Element.handle_info/2  <0.1043.0>/:aac_depayloader Error occured in Membrane Element:
** (MatchError) no match of right hand side value: <<128, 225, 11, 77, 99, 55, 181, 189, 165, 80, 172, 29, 0, 48, 0, 232, 7, 120, 32, 152, 222, 2, 0, 76, 97, 118, 99, 54, 49, 46, 49, 57, 46, 49, 48, 48, 0, 66, 43, 5, 0, 168, 132, 1, 64, 42, 33, 0, 224, 33, ...>>
    (membrane_rtp_aac_plugin 0.9.4) lib/membrane_element_rtp_aac/utils.ex:63: Membrane.RTP.AAC.Utils.parse_packet/2
    (membrane_rtp_aac_plugin 0.9.4) lib/membrane_element_rtp_aac/depayloader.ex:37: Membrane.RTP.AAC.Depayloader.handle_buffer/4
    (membrane_core 1.1.2) lib/membrane/core/callback_handler.ex:139: Membrane.Core.CallbackHandler.exec_callback/4
    (membrane_core 1.1.2) lib/membrane/core/callback_handler.ex:69: Membrane.Core.CallbackHandler.exec_and_handle_callback/5
    (elixir 1.18.1) lib/enum.ex:2546: Enum."-reduce/3-lists^foldl/2-0-"/3
    (membrane_core 1.1.2) lib/membrane/core/element/buffer_controller.ex:81: Membrane.Core.Element.BufferController.do_handle_incoming_buffers/4
    (membrane_core 1.1.2) lib/membrane/core/element.ex:231: Membrane.Core.Element.handle_info/2
    (stdlib 5.2) gen_server.erl:1095: :gen_server.try_handle_info/3
    (stdlib 5.2) gen_server.erl:1183: :gen_server.handle_msg/6
    (stdlib 5.2) proc_lib.erl:241: :proc_lib.init_p_do_apply/3

15:10:28.603 [error] pid=<0.1086.0> mfa=Membrane.Core.Element.handle_info/2  <0.1043.0>/:aac_depayloader Error occured in Membrane Element:
** (MatchError) no match of right hand side value: <<128, 225, 11, 77, 99, 55, 181, 189, 165, 80, 172, 29, 0, 48, 0, 232, 7, 120, 32, 152, 222, 2, 0, 76, 97, 118, 99, 54, 49, 46, 49, 57, 46, 49, 48, 48, 0, 66, 43, 5, 0, 168, 132, 1, 64, 42, 33, 0, 224, 33, ...>>
    (membrane_rtp_aac_plugin 0.9.4) lib/membrane_element_rtp_aac/utils.ex:63: Membrane.RTP.AAC.Utils.parse_packet/2
    (membrane_rtp_aac_plugin 0.9.4) lib/membrane_element_rtp_aac/depayloader.ex:37: Membrane.RTP.AAC.Depayloader.handle_buffer/4
    (membrane_core 1.1.2) lib/membrane/core/callback_handler.ex:139: Membrane.Core.CallbackHandler.exec_callback/4
    (membrane_core 1.1.2) lib/membrane/core/callback_handler.ex:69: Membrane.Core.CallbackHandler.exec_and_handle_callback/5
    (elixir 1.18.1) lib/enum.ex:2546: Enum."-reduce/3-lists^foldl/2-0-"/3
    (membrane_core 1.1.2) lib/membrane/core/element/buffer_controller.ex:81: Membrane.Core.Element.BufferController.do_handle_incoming_buffers/4
    (membrane_core 1.1.2) lib/membrane/core/element.ex:231: Membrane.Core.Element.handle_info/2
    (stdlib 5.2) gen_server.erl:1095: :gen_server.try_handle_info/3
    (stdlib 5.2) gen_server.erl:1183: :gen_server.handle_msg/6
    (stdlib 5.2) proc_lib.erl:241: :proc_lib.init_p_do_apply/3

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

15:10:28.596 [warning] pid=<0.1070.0> mfa=Membrane.RTP.H264.Depayloader.log_malformed_buffer/2  <0.1043.0>/:depayloader An error occurred while parsing H264 RTP payload.
Reason: malformed_data
Packet: %Membrane.Buffer{payload: <<128, 224, 7, 165, 204, 224, 151, 40, 149, 236, 50, 6, 65, 154, 100, 75, 225, 8, 67, 200, 124, 12, 194, 144, 51, 8, 0, 151, 255, 0, 0, 3, 0, 2, 217, 255, 200, 244, 102, 8, 135, 253, 99, 64, 0, 0, 3, 0, 0, 3, 0, 2, 85, 73, 220, 166, 97, 103, 240, 14, 0, 0, 3, 0, 0, 3, 0, 0, 27, 20, 103, 200, 2, 18, 22, 117, 188, 6, 116, 101, 152, 129, 128, 0, 0, 3, 0, 0, 27, 102, 93, 165, 175, 142, 103, 222, 251, 113, 169, 253, 135, 191, 234, 217, 191, 2, 116, 90, 61, 114, 75, 16, 2, 82, 163, 25, 5, 188, 15, 182, 7, 68, 230, 233, 142, 123, 4, 59, 236, 160, 19, 71, 79, 230, 62, 49, 11, 130, 129, 178, 131, 62, 235, 85, 241, 124, 32, 22, 182, 139, 157, 4, 17, 113, 115, 7, 206, 93, 32, 188, 11, 5, 131, 163, 234, 29, 203, 21, 226, 27, 33, 78, 89, 38, 15, 112, 129, 129, 132, 73, 59, 79, 217, 232, 152, 118, 235, 176, 25, 4, 62, 187, 66, 167, 252, 176, 82, 55, 150, 220, 54, 5, 2, 6, 209, 119, 139, 210, 39, 73, 216, 200, 171, 232, 192, 91, 124, 15, 212, 130, 121, 100, 2, 16, 86, 139, 173, 159, 220, 195, 48, 175, 112, 189, 0, 53, 234, 236, 197, 144, 84, 33, 70, 39, 130, 231, 89, 225, 149, 198, 201, 206, 125, 165, 67, 162, 113, 157, 168, 144, 123, 118, 127, 146, 167, 116, 184, 150, 139, 226, 194, 198, 209, 147, 211, 11, 135, 174, 236, 170, 107, 142, 17, 100, 104, 234, 25, 228, 17, 18, 182, 65, 199, 11, 184, 6, 130, 1, 215, 169, 163, 184, 173, 139, 223, 40, 26, 78, 226, 40, 8, 55, 81, 14, 147, 14, 89, 223, 103, 95, 98, 75, 10, 27, 11, 255, 11>>, pts: nil, dts: nil, metadata: %{name: :source_video, port: 17002, socket: #Port<0.52>, ip: {127, 0, 0, 1}}}

15:10:28.596 [warning] pid=<0.1070.0> mfa=Membrane.RTP.H264.Depayloader.log_malformed_buffer/2  <0.1043.0>/:depayloader An error occurred while parsing H264 RTP payload.
Reason: malformed_data
Packet: %Membrane.Buffer{payload: <<128, 224, 7, 165, 204, 224, 151, 40, 149, 236, 50, 6, 65, 154, 100, 75, 225, 8, 67, 200, 124, 12, 194, 144, 51, 8, 0, 151, 255, 0, 0, 3, 0, 2, 217, 255, 200, 244, 102, 8, 135, 253, 99, 64, 0, 0, 3, 0, 0, 3, 0, 2, 85, 73, 220, 166, 97, 103, 240, 14, 0, 0, 3, 0, 0, 3, 0, 0, 27, 20, 103, 200, 2, 18, 22, 117, 188, 6, 116, 101, 152, 129, 128, 0, 0, 3, 0, 0, 27, 102, 93, 165, 175, 142, 103, 222, 251, 113, 169, 253, 135, 191, 234, 217, 191, 2, 116, 90, 61, 114, 75, 16, 2, 82, 163, 25, 5, 188, 15, 182, 7, 68, 230, 233, 142, 123, 4, 59, 236, 160, 19, 71, 79, 230, 62, 49, 11, 130, 129, 178, 131, 62, 235, 85, 241, 124, 32, 22, 182, 139, 157, 4, 17, 113, 115, 7, 206, 93, 32, 188, 11, 5, 131, 163, 234, 29, 203, 21, 226, 27, 33, 78, 89, 38, 15, 112, 129, 129, 132, 73, 59, 79, 217, 232, 152, 118, 235, 176, 25, 4, 62, 187, 66, 167, 252, 176, 82, 55, 150, 220, 54, 5, 2, 6, 209, 119, 139, 210, 39, 73, 216, 200, 171, 232, 192, 91, 124, 15, 212, 130, 121, 100, 2, 16, 86, 139, 173, 159, 220, 195, 48, 175, 112, 189, 0, 53, 234, 236, 197, 144, 84, 33, 70, 39, 130, 231, 89, 225, 149, 198, 201, 206, 125, 165, 67, 162, 113, 157, 168, 144, 123, 118, 127, 146, 167, 116, 184, 150, 139, 226, 194, 198, 209, 147, 211, 11, 135, 174, 236, 170, 107, 142, 17, 100, 104, 234, 25, 228, 17, 18, 182, 65, 199, 11, 184, 6, 130, 1, 215, 169, 163, 184, 173, 139, 223, 40, 26, 78, 226, 40, 8, 55, 81, 14, 147, 14, 89, 223, 103, 95, 98, 75, 10, 27, 11, 255, 11>>, pts: nil, dts: nil, metadata: %{name: :source_video, port: 17002, socket: #Port<0.52>, ip: {127, 0, 0, 1}}}

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

The issue that when we push the stream using FFmpeg, we are receiving warnings for some of video packets and errors for all audio packets. The warnings and errors are as follows:

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 1/24/2025 in #membrane-help

RTSP push approach with Membrane.RTSP.Server

UDPReceiver module:

12 replies

SMSoftware Mansion

•Created by tobbbles on 12/29/2024 in #membrane-help

Guidance on turning a low fps stream of jpegs into a video

fffpwd

3 replies

SMSoftware Mansion

•Created by oleg.okunevych on 9/25/2024 in #membrane-help

stream RTMP to VLC Network stream

@mat_hek @Łukasz Kita thank you for details, will come back to that feature in a while

9 replies

SMSoftware Mansion

•Created by oleg.okunevych on 9/25/2024 in #membrane-help

stream RTMP to VLC Network stream

I believe that the idea of RTMP.Sink is to push stream to some endpoint that is already listening for incoming connections

9 replies

SMSoftware Mansion

•Created by oleg.okunevych on 9/25/2024 in #membrane-help

stream RTMP to VLC Network stream

Exactly, using Membrane.RMTP.Sink module was first that came into my mind, however it can be used to push the stream to something that already waiting the stream itself. It worked for me with Youtube. However, we need the ability to send RTMP stream on demand, for instance user clicks the link, we handle this http response adding some Sink to the pipeline and respond user with rtmp url that he can use with ffplay or some other tool

9 replies

SMSoftware Mansion

•Created by oleg.okunevych on 9/25/2024 in #membrane-help

stream RTMP to VLC Network stream

Hey @mat_hek thanks for your answer. Using ffplay to validate the stream is totally fine for our purposes, the thing is that I still getting an error. Currently we run the RTMP server to receive the stream using following code:

handle_new_client = fn client_ref, app, stream_key ->
      Logger.info("New RTMP connection: #{inspect(client_ref)}")
      send(parent_process_pid, {:client_ref, client_ref, app, stream_key})
      Membrane.RTMP.Source.ClientHandlerImpl
    end

{:ok, _server} =
      RTMPServer.start_link(
        handle_new_client: handle_new_client,
        port: Keyword.get(state.opts, :server_port, 1935),
        use_ssl?: Keyword.get(state.opts, :use_ssl?, false)
      )

handle_new_client = fn client_ref, app, stream_key ->
      Logger.info("New RTMP connection: #{inspect(client_ref)}")
      send(parent_process_pid, {:client_ref, client_ref, app, stream_key})
      Membrane.RTMP.Source.ClientHandlerImpl
    end

{:ok, _server} =
      RTMPServer.start_link(
        handle_new_client: handle_new_client,
        port: Keyword.get(state.opts, :server_port, 1935),
        use_ssl?: Keyword.get(state.opts, :use_ssl?, false)
      )

Our pipeline looks following:

child(:rtmp_funnel, Membrane.Funnel),
child(:rtmp_tcp_sink, %Membrane.TCP.Sink{
        connection_side: :server,
        local_address: {127, 0, 0, 1},
        local_port_no: 1937,
        close_on_eos: false,
        on_connection_closed: :drop_buffers
}),
child(:source, %SourceBin{
        client_ref: state.client_ref
      })
|> via_out(:video)
|> get_child(:rtmp_funnel)
|> get_child(:rtmp_tcp_sink),
get_child(:source)
|> via_out(:audio)
|> get_child(:rtmp_funnel)
|> get_child(:rtmp_tcp_sink)

child(:rtmp_funnel, Membrane.Funnel),
child(:rtmp_tcp_sink, %Membrane.TCP.Sink{
        connection_side: :server,
        local_address: {127, 0, 0, 1},
        local_port_no: 1937,
        close_on_eos: false,
        on_connection_closed: :drop_buffers
}),
child(:source, %SourceBin{
        client_ref: state.client_ref
      })
|> via_out(:video)
|> get_child(:rtmp_funnel)
|> get_child(:rtmp_tcp_sink),
get_child(:source)
|> via_out(:audio)
|> get_child(:rtmp_funnel)
|> get_child(:rtmp_tcp_sink)

I assume that this pipeline should pass the payload from the RTMP server through the funnel into :rtmp_tcp_sink which creates a TCP connection on the 1937 port. Using netcat, I see that we are receiving the payload over the TCP Connection, also Membrane Pipeline visualization tool show that TCP Sink processes the data. However, when using ffplay ffplay rtmp://localhost:1937/app/stream1 we get an error:

[rtmp @ 0x60000331ab50] Server response validating failed
rtmp://localhost:1937/app/stream1: Input/output error

[rtmp @ 0x60000331ab50] Server response validating failed
rtmp://localhost:1937/app/stream1: Input/output error

Should I use Membrane.TCP.Sink, or we may consider other library/module/approach for our use case?

9 replies

SMSoftware Mansion

•Created by oleg.okunevych on 4/26/2024 in #membrane-help

Running Docker image with Membrane RTMP Plugin

I think I found the problem, error dissapeared after updating app alpine image from alpine:3.17 to alpine:3.18.5 Thank you for help!

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 4/26/2024 in #membrane-help

Running Docker image with Membrane RTMP Plugin

still the same results. What other Docker image would you suggest to try?

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 4/26/2024 in #membrane-help

Running Docker image with Membrane RTMP Plugin

for build stage following libs are used:

RUN \
  apk add --no-cache \
  build-base \
  git \
  npm \
  make \
  cmake \
  openssl-dev \
  libsrtp-dev \
  libsrt-dev \
  ffmpeg-dev \
  fdk-aac-dev \
  opus-dev \
  openssh-client \
  ca-certificates \
  curl

RUN \
  apk add --no-cache \
  build-base \
  git \
  npm \
  make \
  cmake \
  openssl-dev \
  libsrtp-dev \
  libsrt-dev \
  ffmpeg-dev \
  fdk-aac-dev \
  opus-dev \
  openssh-client \
  ca-certificates \
  curl

for app stage we have:

RUN \
  apk add --no-cache \
  libstdc++6 \
  openssl \
  libsrtp \
  ffmpeg \
  fdk-aac \
  opus \
  openssh-client \
  curl \
  ncurses \
  mesa \
  mesa-dri-gallium \
  mesa-dev

RUN \
  apk add --no-cache \
  libstdc++6 \
  openssl \
  libsrtp \
  ffmpeg \
  fdk-aac \
  opus \
  openssh-client \
  curl \
  ncurses \
  mesa \
  mesa-dri-gallium \
  mesa-dev

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 4/26/2024 in #membrane-help

Running Docker image with Membrane RTMP Plugin

thanks for quick answer 🙂

membrane_rtmp_plugin uses bundlex under the hood.

membrane_rtmp_plugin uses bundlex under the hood.

Does it mean that BundlexProject module is required to be configured in the application? I am using elixir:1.16.2-otp-26-alpine image. There are no warnings when building rtmp plugin:

#24 149.7 ==> membrane_rtmp_plugin
#24 149.7 Bundlex: Building natives: rtmp_sink
#24 149.9 Compiling 38 files (.ex)
#24 150.3 Generated membrane_rtmp_plugin app

#24 149.7 ==> membrane_rtmp_plugin
#24 149.7 Bundlex: Building natives: rtmp_sink
#24 149.9 Compiling 38 files (.ex)
#24 150.3 Generated membrane_rtmp_plugin app

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 4/26/2024 in #membrane-help

Running Docker image with Membrane RTMP Plugin

2024-04-26 16:11:04 =INFO REPORT==== 26-Apr-2024::13:11:04.944615 ===
2024-04-26 16:11:04     application: kernel
2024-04-26 16:11:04     exited: {{shutdown,
2024-04-26 16:11:04                  {failed_to_start_child,on_load,
2024-04-26 16:11:04                      {on_load_function_failed,
2024-04-26 16:11:04                          'Elixir.Membrane.RTMP.Sink.Native.Nif',abort}}},
2024-04-26 16:11:04              {kernel,start,[normal,[]]}}
2024-04-26 16:11:04     type: permanent
2024-04-26 16:11:04 
2024-04-26 16:11:05 Kernel pid terminated (application_controller) ("{application_start_failure,kernel,{{shutdown,{failed_to_start_child,on_load,{on_load_function_failed,'Elixir.Membrane.RTMP.Sink.Native.Nif',abort}}},{kernel,start,[normal,[]]}}}")
2024-04-26 16:11:05 
2024-04-26 16:11:05 Crash dump is being written to: erl_crash.dump...done

2024-04-26 16:11:04 =INFO REPORT==== 26-Apr-2024::13:11:04.944615 ===
2024-04-26 16:11:04     application: kernel
2024-04-26 16:11:04     exited: {{shutdown,
2024-04-26 16:11:04                  {failed_to_start_child,on_load,
2024-04-26 16:11:04                      {on_load_function_failed,
2024-04-26 16:11:04                          'Elixir.Membrane.RTMP.Sink.Native.Nif',abort}}},
2024-04-26 16:11:04              {kernel,start,[normal,[]]}}
2024-04-26 16:11:04     type: permanent
2024-04-26 16:11:04 
2024-04-26 16:11:05 Kernel pid terminated (application_controller) ("{application_start_failure,kernel,{{shutdown,{failed_to_start_child,on_load,{on_load_function_failed,'Elixir.Membrane.RTMP.Sink.Native.Nif',abort}}},{kernel,start,[normal,[]]}}}")
2024-04-26 16:11:05 
2024-04-26 16:11:05 Crash dump is being written to: erl_crash.dump...done

I've seen similar kind of error related to bundlex in this group, however I am not using Bundlex and it seems to be another kind of error.

12 replies

SMSoftware Mansion

•Created by oleg.okunevych on 4/26/2024 in #membrane-help

Running Docker image with Membrane RTMP Plugin

2024-04-26 16:11:04 =CRASH REPORT==== 26-Apr-2024::13:11:04.944480 ===
2024-04-26 16:11:04   crasher:
2024-04-26 16:11:04     initial call: application_master:init/4
2024-04-26 16:11:04     pid: <0.2480.0>
2024-04-26 16:11:04     registered_name: []
2024-04-26 16:11:04     exception exit: {{shutdown,
2024-04-26 16:11:04                          {failed_to_start_child,on_load,
2024-04-26 16:11:04                              {on_load_function_failed,
2024-04-26 16:11:04                                  'Elixir.Membrane.RTMP.Sink.Native.Nif',
2024-04-26 16:11:04                                  abort}}},
2024-04-26 16:11:04                      {kernel,start,[normal,[]]}}
2024-04-26 16:11:04       in function  application_master:init/4 (application_master.erl, line 142)
2024-04-26 16:11:04     ancestors: [<0.2479.0>]
2024-04-26 16:11:04     message_queue_len: 1
2024-04-26 16:11:04     messages: [{'EXIT',<0.2481.0>,normal}]
2024-04-26 16:11:04     links: [<0.2479.0>,<0.2478.0>]
2024-04-26 16:11:04     dictionary: []
2024-04-26 16:11:04     trap_exit: true
2024-04-26 16:11:04     status: running
2024-04-26 16:11:04     heap_size: 233
2024-04-26 16:11:04     stack_size: 28
2024-04-26 16:11:04     reductions: 166
2024-04-26 16:11:04   neighbours:
2024-04-26 16:11:04

2024-04-26 16:11:04 =CRASH REPORT==== 26-Apr-2024::13:11:04.944480 ===
2024-04-26 16:11:04   crasher:
2024-04-26 16:11:04     initial call: application_master:init/4
2024-04-26 16:11:04     pid: <0.2480.0>
2024-04-26 16:11:04     registered_name: []
2024-04-26 16:11:04     exception exit: {{shutdown,
2024-04-26 16:11:04                          {failed_to_start_child,on_load,
2024-04-26 16:11:04                              {on_load_function_failed,
2024-04-26 16:11:04                                  'Elixir.Membrane.RTMP.Sink.Native.Nif',
2024-04-26 16:11:04                                  abort}}},
2024-04-26 16:11:04                      {kernel,start,[normal,[]]}}
2024-04-26 16:11:04       in function  application_master:init/4 (application_master.erl, line 142)
2024-04-26 16:11:04     ancestors: [<0.2479.0>]
2024-04-26 16:11:04     message_queue_len: 1
2024-04-26 16:11:04     messages: [{'EXIT',<0.2481.0>,normal}]
2024-04-26 16:11:04     links: [<0.2479.0>,<0.2478.0>]
2024-04-26 16:11:04     dictionary: []
2024-04-26 16:11:04     trap_exit: true
2024-04-26 16:11:04     status: running
2024-04-26 16:11:04     heap_size: 233
2024-04-26 16:11:04     stack_size: 28
2024-04-26 16:11:04     reductions: 166
2024-04-26 16:11:04   neighbours:
2024-04-26 16:11:04

12 replies

Gaming

Programming