Recherche avancée

Sur d’autres sites (3694)

• Read dumepd RTP stream in libav

  25 février 2017, par Pawel K

  Hi I am in a need of a bit of a help/guidance because I got stuck in my research.

  The problem :

  How to convert RTP data using either gstreamer or avlib (ffmpeg) in either API (by programming) or console versions.

  Data

  I have RTP dump that comes from RTP/RTCP over TCP so I can get the precise start and stop for each RTP packet in file. It’s a H264 video stream dump.
  The data is in this fashion because I need to acquire the RTCP/RTP interleaved stream via libcurl (which I’m currently doing)

  Status

  I’ve tried to use ffmpeg to consume pure RTP packets but is seems that using rtp either by console or by programming involves "starting" the whole rtsp/rtp session business in ffmpeg. I’ve stopped there and for the time being I didn’t pursue this avenue deeper. I guess this is possible with lover level RTP API like ff_rtp_parse_packet() I’m too new with this lib to do it straight out.

  Then there is the gstreamer It has somewhat more capabilities to do it without programming, but for the time being I’m not able to figure out how to pass it the RTP dump I have.

  I have also tried to do a little bit of a trickery and stream the dump via socat/nc to the udp port and listen on it via ffplay with sdp file as an input, there seems to be some progress the rtp at least gets recognized, but for socat there are loads of packet missing (data sent too fast perhaps ?) and in the end the data is not visualized. When I used nc the video was badly misshapen but at least there were not that much receive errors.

  One way or another the data is not properly visualized.

  I know I can depacketize the data "by hand" but the idea is to do it via some kind of library because in the end there would also be second stream with audio that would have to be muxed together with the video.

  I would appreciate any help on how to tackle this problem.
  Thanks.

• Read dumepd RTP stream in libav

  25 mai 2017, par Pawel K

  Hi I am in a need of a bit of a help/guidance because I got stuck in my research.

  The problem :

  How to convert RTP data using either gstreamer or avlib (ffmpeg) in either API (by programming) or console versions.

  Data

  I have RTP dump that comes from RTP/RTCP over TCP so I can get the precise start and stop for each RTP packet in file. It’s a H264 video stream dump.
  The data is in this fashion because I need to acquire the RTCP/RTP interleaved stream via libcurl (which I’m currently doing)

  Status

  I’ve tried to use ffmpeg to consume pure RTP packets but is seems that using rtp either by console or by programming involves "starting" the whole rtsp/rtp session business in ffmpeg. I’ve stopped there and for the time being I didn’t pursue this avenue deeper. I guess this is possible with lover level RTP API like ff_rtp_parse_packet() I’m too new with this lib to do it straight out.

  Then there is the gstreamer It has somewhat more capabilities to do it without programming, but for the time being I’m not able to figure out how to pass it the RTP dump I have.

  I have also tried to do a little bit of a trickery and stream the dump via socat/nc to the udp port and listen on it via ffplay with sdp file as an input, there seems to be some progress the rtp at least gets recognized, but for socat there are loads of packet missing (data sent too fast perhaps ?) and in the end the data is not visualized. When I used nc the video was badly misshapen but at least there were not that much receive errors.

  One way or another the data is not properly visualized.

  I know I can depacketize the data "by hand" but the idea is to do it via some kind of library because in the end there would also be second stream with audio that would have to be muxed together with the video.

  I would appreciate any help on how to tackle this problem.
  Thanks.

• How to use the latest version of @ffmpeg/ffmpeg in a React.js project ?

  21 janvier, par Muzammil Raza

  I'm working on a React.js project where I need to process videos in the browser using @ffmpeg/ffmpeg. I noticed that the package has been updated recently, and the API and functions have changed.

  


  In the older version, I used to import the package and functions like this :

  


  import { createFFmpeg, fetchFile } from '@ffmpeg/ffmpeg';


  


  However, in the latest version, I see that the import has changed to :

  


  import { FFmpeg } from '@ffmpeg/ffmpeg';


  


  and all new functions are changed I have checked in by log :

  


  I have check by console ffmpeg, it show :

  


  createDir: path => {…}
deleteDir: path => {…}
deleteFile: path => {…}
exec: ƒ ( /** ffmpeg command line args */ args)
listDir: path => {…}
load: ƒ ()
loaded: true
readFile: ƒ (path)
rename: (oldPath, newPath) => {…}
terminate: () => {…}
writeFile: (path, data) => {…}


  


  I'm not sure about the changes in the API and functions, and I couldn't find any updated documentation or guides on how to use the latest version of @ffmpeg/ffmpeg in a React.js project.

  


  I have task of video processing for streaming and need to add logo in video.

  


  Could someone please provide guidance on how to use the latest version of @ffmpeg/ffmpeg in a React.js project ? Specifically, I'm looking for information on the changes in the API, the new function names, and how to perform video processing tasks with the latest version.

  


  If anyone has experience with the latest version of @ffmpeg/ffmpeg or knows the updated usage, any help or examples would be greatly appreciated. Thank you !