Recherche avancée

Sur d’autres sites (6828)

• Create conversion queue using ffmpeg and C #

  22 octobre 2017, par Alexei Agüero Alba

  Ok, the idea is to create a file queue that can be modified and reorganized (this is done) and for each file execute a ffmpeg process to convert it to another format.

  For conversion use Xabe.FFmpeg and .Net 4.5 all using async and await.

  The question would be how to execute an x ​​number of processes in parallel (example 4) of that variable queue and when one of them finishes executing the next one, keeping in execution always the same amount in parallel. I can start from scratch but I need ideas on how to do this in the simplest way possible. The program itself is simple (with gui) takes a folder and its subfolders all the video files and queues them and starts the conversion, you can add other folders with more files, and independent files reorder them, to convert whichever is the greater.

  At one point I found a package I think nuget (or github) that did exactly what I needed but I have not been able to get back.

  Thanks for your help in advance.

  Excuse the English because I use the translator of Google for being faster because my domain of this is limited but sufficient to understand the answers.

  ---

  Ok, I found what I was looking for called ProcessManager is a nupkg package. It has 2 years of development but seems stable. The only drawback is that it does not allow me to organize the conversion queue once you have added the files, although I have to try some ideas that maybe functions.

  var manager = new Manager(4); // Max 4 processes will be started simultaneously
  
  manager.Start();
  
  
  
  manager.ProcessErrorDataReceived += (sender, e) => Console.WriteLine(e.Data);
  
  manager.ProcessOutputDataReceived += (sender, e) => Console.WriteLine(e.Data);
  
  
  
  foreach (var videoFileName in Directory.EnumerateFiles("videos"))
  
  {
  
      var info = new ProcessInfo(
  
          "ffprobe.exe",
  
          string.Format("-v quiet -print_format json -show_format -show_streams \"{0}\"", videoFileName));
  
  
  
      manager.Queue(info);
  
  }

  Process Manager

• Merge commit '07a2b155949eb267cdfc7805f42c7b3375f9c7c5'

  21 octobre 2017, par James Almer

  Merge commit '07a2b155949eb267cdfc7805f42c7b3375f9c7c5'
  * commit '07a2b155949eb267cdfc7805f42c7b3375f9c7c5' :
  
    Bump major versions of all libraries
  A few API deprecated 2 years ago or more are also postponed here for
  
  varying reasons.
  FF_API_LOWRES :
  
  Since this functionality depends on AVStream->codec, i figure the two can
  
  be removed at the same time in the next bump or so.
  FF_API_AVCTX_TIMEBASE :
  
  Couldn't get this one to work. Not just libavcodec but apparently also
  
  libavformat and ffmpeg.c expect AVCodecContext->time_base to be set for
  
  decoding. Upon removal some tests report a different generic stream time
  
  base (like 1/25), and others lose packet duration values. I guess it's
  
  somehow tied to the AVStream->codec clusterfuck.
  
  It can be dealt with alongside FF_API_LAVF_AVCTX in the next bump.
  FF_API_OLD_FILTER_OPTS_ERROR :
  
  This one is meant to remain after FF_API_OLD_FILTER_OPTS is removed.
  
  Its purpose is displaying the corrected command line using the new syntax
  
  as a suggestion as part of the error message.
  Merged-by : James Almer <jamrial@gmail.com>
  

  • [DH] libavcodec/version.h
  • [DH] libavdevice/version.h
  • [DH] libavfilter/version.h
  • [DH] libavformat/version.h
  • [DH] libavresample/version.h
  • [DH] libavutil/version.h
  • [DH] libpostproc/version.h
  • [DH] libswresample/version.h
  • [DH] libswscale/version.h
  • [DH] tests/ref/fate/api-mjpeg-codec-param
  • [DH] tests/ref/fate/api-png-codec-param

• MPEG-DASH not working. MPD validation fails

  16 novembre 2017, par Marko36

  I am trying to serve video using MPEG-DASH. No success. I have tried the following :

  Following the instructions on webproject.org, using FFMPEG, I have created several variants of the original video and the DASH MPD manifest, containing metadata. However, the manifest does not validate using http://dashif.org/conformance.html. This validator itself is quite useless, as it provides unusable info about the error. I have found in a post from 2014, that one of the errors generated by FFMPEG is capital letters in some metadata (not a critical one, but could have been fixed for years !). Other errors detected, but not described. No tangible info from any of these other validators either : http://www-itec.uni-klu.ac.at/dash/?page_id=605 (produces rubbish info), https://github.com/Eyevinn/dash-validator-js (throws an exception)

  Following instructions on mozilla.org, produces the same non-working result, as the instructions are nearly identical (including same resolution*bitrate sets), except that Mozilla omits the use of dash.js, which is deemed necessary by the rest of the internet.

  This guide on Bitmovin, utilizing x264 and MP4Box does not work either. Going by the instructions, I have to recode the original x264 video twice. The final version of videos are in some cases twice the size of their intermediate versions and 720p video is actually larger than its 1080p, higher bitrate counterpart. No need to go further. (Yet, this is the only way that actually produced segments..)

  I have spent 3 days on the above, read about all there is on the web from the other frustrated adopters, and ran out of options. I would really apreciate some pro tips ! Thanks !