Recherche avancée

Sur d’autres sites (4823)

• Rendering video streaming in android

  16 avril 2013, par user1568549

  I've successfully cross-compiled a c++ streaming library to the ICS platform

  This library contains a sample player that uses sdl library to render the resulting decoded streams and libav for decoding that i've also succeeded to cross compile(libav ... classes) .Then, i 've made the necessary jni classes and tested it log tags it seems that everything is fine but now i want to show the result on the screen(show the real streaming not just log messages)

  I am searching for the easiest way to render my video-stream (just to be sure that everything works fine)

  Am i obliged to cross-compile the SDL library too ? Is it possible ? If yes is there any good tutorial ?

  Is there any other solution to render directly FFmpeg decoded frames ?

• w32pthreads : use the condition variable API directly when targeting newer versions...

  9 octobre 2014, par James Almer

  w32pthreads : use the condition variable API directly when targeting newer versions of Windows
  Wrap the function calls in a similar fashion to how it’s being done
  
  with the critical section API.
  Signed-off-by : James Almer <jamrial@gmail.com>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] compat/w32pthreads.h

• How to resolve "runOnReady command exited with code 0" when restreaming a stream using Mediamtx ?

  2 juillet 2023, par Emad Helmi

  I'm attempting to publish a stream to the RTMP port 1935 using a ffmpeg command with Mediamtx (v0.22.2). Afterward, I want to restream the mainstream to another path using the runOnReady command in the config file. However, I'm encountering an issue where the runOnReady command exits with code 0.

  


  Steps to Replicate :

  


  

  1. Use the provided docker-compose.yml file :

  


  


  version: "3.8"

name: mediamtx
services:
  mediamtx:
    image: aler9/rtsp-simple-server:v0.22.2
    container_name: media_mtx_rtsp_server
    ports:
      - "8554:8554"
      - "1935:1935"
      - "8888:8888"
      - "8889:8889"
      - "9997:9997"
      - "8000:8000"
    volumes:
      - ./configs/mediamtx/config.yml:/mediamtx.yml
      - ../volumes/hls/segments:/hls/segments


  


  

  2. Add the following path to the config.yml file :

  


  


  paths:
  show/test:
    runOnReady: ffmpeg -i rtmp://localhost:1935/show/test -c copy -f flv "rtmp://localhost:1935/compressed/test"
    runOnReadyRestart: yes


  


  

  3. Start the server using docker-compose.

  


  4. Publish an RTMP stream to the server using the following command :

  


  


  ffmpeg -re -stream_loop -1 -i files/sample-30s.mp4 -c copy -f flv "rtmp://localhost:1935/show/test"


  


  

  5. When I check the logs :

  


  


  2023/07/01 15:16:30 INF [RTMP] [conn 172.26.0.1:51044] opened
2023/07/01 15:16:30 INF [path show/test] runOnReady command started
2023/07/01 15:16:30 INF [RTMP] [conn 172.26.0.1:51044] is publishing to path 'show/test', 2 tracks (H264, MPEG4-audio-gen)
2023/07/01 15:16:30 INF [path show/test] runOnReady command exited with code 0


  


  So I can't watch the stream on the new path (/compressed/test)