Recherche avancée

Sur d’autres sites (8427)

• avfilter/graphparser : allow specifying filter@id as filter instance

  17 mai 2017, par Muhammad Faiz

  avfilter/graphparser : allow specifying filter@id as filter instance
  See http://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-April/035975.html
  
  Parsed_filter_X could remain and user can override it with custom one.
  Example :
  
  ffplay -f lavfi "nullsrc=s=640x360,
  
  sendcmd='1 drawtext@top reinit text=Hello ; 2 drawtext@bottom reinit text=World',
  
  drawtext@top=x=16:y=16:fontsize=20:fontcolor=Red:text='',
  
  drawtext@bottom=x=16:y=340:fontsize=16:fontcolor=Blue:text=''"
  Reviewed-by : Paul B Mahol <onemda@gmail.com>
  
  Signed-off-by : Muhammad Faiz <mfcc64@gmail.com>
  

  • [DH] doc/filters.texi
  • [DH] libavfilter/graphparser.c

• Rails 5 - Concurrent large Video uploads and FFMPEG encoding in the background is making the server very slow

  8 septembre 2022, par Milind

  I have a working Rails 5 apps using Reactjs for frontend and React dropzone uploader to upload video files using carrierwave.

  



  So far, what is working great is listed below -

  



  

  1. User can upload videos and videos are encoded based on the selection made by user - HLS or MPEG-DASH for online streaming.

  


  2. Once the video is uploaded on the server, it starts streaming it by :-


     

     • FIRST,copying video on /tmp folder.

     


     • Running a bash script that uses ffmpeg to transcode uploaded video using predefined commands to produce new fragments of videos inside /tmp folder.

     


     • Once the background job is done, all the videos are uploaded on AWS S3, which is how the default carrierwave works

     


  


  3. So, when multiple videos are uploaded, they are all copied in /tmp folder and then transcoded and eventually uploaded to S3.

  


  



  My questions, where i am looking some help are listed below -

  



  1- The above process is good for small videos, BUT what if there are many concurrent users uploading 2GB of videos ? I know this will kill my server as my /tmp folder will keep on increasing and consume all the memory, making it to die hard.How can I allow concurrent videos to upload videos without effecting my server's memory consumption ?

  



  2- Is there a way where I can directly upload the videos on AWS-S3 first, and then use one more proxy server/child application to encode videos from S3, download it to the child server, convert it and again upload it to the destination ? but this is almost the same but doing it on cloud, where memory consumption can be on-demand but will be not cost-effective.

  



  3- Is there some easy and cost-effective way by which I can upload large videos, transcode them and upload it to AWS S3, without effecting my server memory. Am i missing some technical architecture here.

  



  4- How Youtube/Netflix works, I know they do the same thing in a smart way but can someone help me to improve this ?

  



  Thanks in advance.

  


• Use a video editing library (not executable) via Node [on hold]

  25 septembre 2018, par Merc

  I need to edit clips using node. I am looking around, and most (if not all) libraries seem (like Fluent FFMpeg) seem to be based on the fact that they run FFMPEG as an executable and get the resulting output.

  That’s not what I want. I worked with FFMPEG executable in the past, and I know how flaky it is in terms of return codes and error codes.

  Ideally, I would love to find a native library for video editing and make calls using node.

  In terms of libraries :

  • Gstreamer
  • FFmpeg/LibAV (does they come with C libraries to bind to ?)
  • libVLC

  In terms of binding with them :

  • node-gir. Gstreamer seems to have updated git files

  • native bindings. For example Gstreamer has gstreamer-superficial. I couldn’t find any javascript bindings forFFMPEG — only "run the executable and hope for the best" libraries

  • VLC has a bindings library that is quite old and had its last commit years ago.

  Am I getting this all wrong ?
  My ideal outcome is to have a nice, robust library that I use directly using node, but my lack of experience in terms of using native libraries, and the somehow fragmented world of video editing libraries.