Recherche avancée

Sur d’autres sites (5339)

• Install ffmpeg-php with PHP 5.3.x [closed]

  4 octobre 2012, par Proloy

  I know that this question has been asked many times on this site. I tried all and nothing works for me. I also saw some rumor that ffmpeg-php doesn't work well with PHP 5.3.x.

  I am totally fed up. My FFMPEG-PHP worked fine for PHP 5.2.x but after I upgraded to PHP 5.3.x it stopped to show in phpinfo().

  I have a centOS 5.8 box.

  Can anyone tell me why this happened ?

• How would I add an audio channel to an rtsp stream ?

  9 septembre 2022, par PlayerWet

  Good companions. It turns out that my Raspberry does not give more than itself when it comes to joining video with audio at good quality and sending it by rtsp. But I think I could send the video in rtsp format and then the audio in mp3, but I would need to join it again on another computer (nas Debian) on my home lan where I have the Shinobi program (security camera manager) installed.

  


  I would need something that can somehow grab the rtsp stream and another mp3 audio and merge them into a new rtsp stream. Is this possible ? or is it a crazy idea.

  


  On the one hand I send this, which is the transmission of the camera by rtsp through v4l2rtspserver :

  


  v4l2rtspserver -H 1080 -W 1920 -F 25 -P 8555 /dev/video0


  


  And separately I send an audio in mp3 with sound from a usb microphone through ffmpeg :

  


  ffmpeg -ac 1 -f alsa -i hw:1,0 -acodec libmp3lame -ab 32k -ac 1 -f rtp rtp://192.168.1.77:12348


  


  My idea is to put both things together on a nas server in a new rtsp stream (or another idea).

  


  But I don't know if with ffmpeg I can capture the video from an rtsp video stream and then be able to join it with the mp3 audio and form another new rtsp stream.

  


  Merge these two streams into one and reassemble an rtsp :

  


  rtsp://192.168.1.57:8555/unicast

rtp://192.168.1.77:12348


  


  I have tried this way but it gives me an error :

  


  ffmpeg \
    -i rtsp://192.168.1.57:8555/unicast \
    -i rtp://192.168.1.37:12348 \
    -acodec copy -vcodec libx264 \
    -f rtp_mpegts "rtp://192.168.1.77:5000?ttl=2"


  


  Error :

  


  [h264 @ 0x55ac6acaf4c0] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 0x55ac6acaf4c0] decode_slice_header error
[h264 @ 0x55ac6acaf4c0] no frame!
[h264 @ 0x55ac6acaf4c0] non-existing PPS 0 referenced
    Last message repeated 1 times
[h264 @ 0x55ac6acaf4c0] decode_slice_header error
[h264 @ 0x55ac6acaf4c0] no frame!
[h264 @ 0x55ac6acaf4c0] non-existing PPS 0 referenced
    Last message repeated 1 times


  


  What am I doing wrong ?

  


• Random PIPELINE_ERROR_DECODE : video decoder reinitialization failed on Chromium HTML5 video tag

  9 janvier 2024, par Hello World

  System

  


  Running an Expo React Native app, with a <webview></webview> component that loads a NextJS app with an HTML5 <video></video> tag. The system with issues is running the app on Android 9.0 with WebView implementation set to Android System WebView 84.0. The system without issues is running the app on Android 10.0 with WebView implementation set to Android System WebView 120.0.

  


  Details

  


  Video files being played by the <video></video> element are previously transcoded by the following fluent-ffmpeg node package :

  


  import ffmpeg from 'fluent-ffmpeg'

ffmpeg(rawVideoFileUrl)
  .videoCodec('libx264')
  .audioCodec('aac')
  .outputOption('-strict experimental')
  .outputOption('-movflags frag_keyframe+faststart')
  .format('mp4')


  


  My knowledge on video transcoding is very limited, but I have to do the transcoding to guarantee that the files are compatible to be played by my NextJS web app. In my research, my findings pointed to these FFMPEG command line arguments for my purpose.

  


  For the aforementioned WebView version, H.264 with AAC, should be compatible, yet playback is not stable. Many times it will play just fine, but other times I receive the error :

  


  PIPELINE_ERROR_DECODE: video decoder reinitialization failed


  


  If I refresh the web app, it works again. That leads me to believe it is somehow memory related, maybe caused by incompatibility.

  


  I'm not sure whether video decoder reinitialization failed produced by the HTML5 <video></video> tag is a problem of transcoding or not, as the videos play fine most of the time and only produces that error in the console some of the times, unexpectedly.

  


  Question

  


  Is there something that I can do to the fluent-ffmpeg command to make the video files more widely compatible, including the WebView 84.0 system too, or is the issue somewhere else ?

  


  In this case, updating WebView is not an option.