Recherche avancée

Sur d’autres sites (7574)

• Pushing on-fly transcoded video to embeded http results with no seekbar

  11 juillet 2017, par BigRetroMike

  I’m trying to achieve a simple home-based solution for streaming/transcoding video to low-end machine that is unable to play file properly.

  I’m trying to do it with ffmpeg (as ffserver will be discontinued)
  I found out that ffmpeg have build in http server that can be used for this.

  The application Im’ testing with (for seekbar) is vlc

  I’m probably doing something wrong here (or trying to do something that other does with other applications)

  My ffmpeg code I use is :

  d :\ffmpeg\bin\ffmpeg.exe -r 24 -i "D :\test.mkv" -threads 2 -vf
  scale=1280:720 -c:v libx264 -preset medium -crf 20 -maxrate 1000k
  -bufsize 2000k -c:a ac3 -seekable 1 -movflags faststart -listen 1 -f mpegts http://127.0.0.1:8080/test.mpegts

  This code also give me ability to start watching it when I want (as opposite to using rtmp via udp that would start video as soon as it transcode it)

  I readed about moving atoom thing at file begging which should be handled by movflags faststart

  I also checked the -re option without any luck, -r 25 is just to suppress the Past duration 0.xx too large warning which I read is normal thing.
  test file is one from many ones with different encoder setting etc.

  The setting above give me a seekbar but it doesn’t work and no overall duration (and no progress bar), when I switch from mpegts to matroska/mkv I see duration of video (and progress) but no seekbar.

  If its possible with only ffmpeg I would prefer to stick to it as standalone solution without extra rtmp/others servers.

• Node.js FFMPEG Reporting Progress Architecture

  11 septembre 2018, par munkee

  I’m running a node.js HTTP server which has a video conversion API built using ffmpeg. I am wondering how best to report on the progress of the file conversion to a separate front end. The HTTP server is going to be standalone as its own service, so I would like to be able to render the percentage complete of the conversion to another server with a simple front end. Upon completion of the conversion the file is downloaded automatically.

  My current end point /convert takes a file URL with a .mov extension, downloads the file and runs it through the conversion process to only output Audio. Using response headers I force the browser to download the file once the conversion has ended, I also delete the temporary file once download has completed.

  A full request would look like

  https://www.someurl.com/convert?file=https://www.filetodownload.com/Skating.mov

  I am using the fluent-ffmpeg npm package : https://github.com/fluent-ffmpeg/node-fluent-ffmpeg which serves a "progress" event :

  ffmpeg('/path/to/file.avi')
  
    .on('progress', function(progress) {
  
      console.log('Processing: ' + progress.percent + '% done');
  
    });

  I am thinking of emitting the progress.percent information on to a separate endpoint maybe along the lines of :

  https://www.someurl.com/progress

  Which will simply be my http server sending the percentage back to the browser. I feel as though I am going about the architecture incorrectly and there must be a better way of architecting the final outcome.

• Silence -finline-functions warning

  22 juin 2017, par Thomas Zander

  Silence -finline-functions warning
  This warning flag is gcc-specfic.
  Signed-off-by : Erik de Castro Lopo <erikd@mega-nerd.com>
  

  • [DH] build/exe.mk
  • [DH] build/lib.mk