Recherche avancée

Sur d’autres sites (8254)

• How to recognize that ffmpeg pipe ended ?

  30 juillet 2023, par Veronica

  I am executing an ffmpeg command with a very complex filter and with a pipe within a C# application. I am putting images into the ffmpeg input stream (pipe)for rendering these images as overlays to the final video.

  


  I want to render images with the pipe until the pipe closes. Unfortunately, I do not know how I can recognize that the pipe of the ffmpeg process has closed. Is there any possibility of recognizing this event within C# ?

  


  The process is started like :

  


  this._ffmpegProcess = new Process
{
    StartInfo = new ProcessStartInfo
    {
        FileName = this._ffmpegPath,
        UseShellExecute = false,
        RedirectStandardInput = true,
        RedirectStandardOutput = true,
        RedirectStandardError = true,
        CreateNoWindow = true
    }
};

this._ffmpegProcess.StartInfo.Arguments = ffmpegCmd;
this._ffmpegProcess.OutputDataReceived += this.Proc_DataReceived;
this._ffmpegProcess.ErrorDataReceived += this.Proc_DataReceived;
this._ffmpegProcess.Exited += this._ffmpegProcess_Exited;
this._ffmpegProcess.Start();
this._ffmpegProcess.BeginOutputReadLine();
this._ffmpegProcess.BeginErrorReadLine();


  


  The rendering happens within a timer :

  


  this._renderOverlayTimer = new Timer(this.RenderOverlay);
this._renderOverlayTimer.Change(0, 30);    


  


  The timer is started right after starting the ffmpeg process :

  


  private void RenderOverlay(object state)
{
   using (var ms = new MemoryStream())
   {
      using (var img = GetImage(...))
      {
          img.Save(ms, ImageFormat.Png);
          ms.WriteTo(this._ffmpegProcess.StandardInput.BaseStream);
      }
   }
}


  


  The problem is that I always receive a "The pipe has ended" error at ms.WriteTo().

  


• ASP.NET : Powershell script finishes after the first ffmpeg call

  24 mars 2014, par sk904861

  The following Powershell script only executes the first ffmpeg call, no matter which one is first. Both the ffmpeg and the powershell processes never finish.

  Param($InputFile, $OutputFile, $Thumbnail, $Sprites)
  
  
  
  $ThumbnailWidth = 120
  
  $ThumbnailHeight = 120
  
  
  
  # Thumbnail
  
  ffmpeg -i $InputFile -f image2 -vframes 1 -filter:v "crop=min(iw\,ih):min(iw\,ih), scale=$($ThumbnailWidth):$($ThumbnailHeight)" -crf 18 "$($Thumbnail)\150x150.png"
  
  
  
  # Poster
  
  ffmpeg -i $InputFile -f image2 -vframes 1 -filter:v "crop=min(iw\,ih):min(iw\,ih), scale=$($PosterWidth):$($PosterHeight)" -crf 18 "$($Thumbnail)\1000x1000.png"

  The script gets called within an ASP.NET application as follows :

  ProcessStartInfo startInfo = new ProcessStartInfo();
  
  startInfo.FileName = "powershell.exe";
  
  startInfo.Arguments = String.Format("-executionpolicy RemoteSigned -file \"{0}\" \"{1}\" \"{2}\" \"{3}\" \"{4}\"", scriptPath, fullPath, videoPath, thumbnailPath, sprites);
  
  startInfo.RedirectStandardOutput = true;
  
  startInfo.RedirectStandardError = true;
  
  startInfo.UseShellExecute = false;
  
  startInfo.CreateNoWindow = true;
  
  Process process = new Process();
  
  process.StartInfo = startInfo;
  
  
  
  process.EnableRaisingEvents = true;
  
  process.Exited += delegate
  
  {
  
       // Do some cleaning up
  
  };
  
  
  
  process.Start();

  Does anyone have a clue, why only the first the two ffmpeg calls is working, while each call seems to be correct ?

• Video cutting with ffmpeg with standard i/o

  15 octobre 2023, par Крошка Сын

  I'm struggling with the problem of cropping moments and applying the "blur" effect in ffmpeg from under c#. Here is my process startup code :

  


  _ffmpegProc = new Process
    {
        StartInfo = new ProcessStartInfo
        {
            RedirectStandardInput = true,
            RedirectStandardOutput = true,
            RedirectStandardError = true,
            UseShellExecute = false,
            CreateNoWindow = true,
            FileName = "/usr/bin/ffmpeg"
        },
        EnableRaisingEvents = true
    };


  


  Here is the I/O code via streams :

  


  using (Stream inpt = new MemoryStream(input))&#xA;    {&#xA;        inpt.CopyTo(_ffmpegProc.StandardInput.BaseStream);&#xA;        _ffmpegProc.StandardInput.Close();&#xA;    }&#xA;&#xA;    var response = Array.Empty<byte>();&#xA;    using (var output = new MemoryStream())&#xA;    {&#xA;        _ffmpegProc.StandardOutput.BaseStream.CopyTo(output);&#xA;        response = output.ToArray();&#xA;    }&#xA;</byte>

  


  The problem occurs when I want to crop the video, namely, as soon as I add the -ss hh:mm:ss flag -to hh:mm:ss, an error immediately pops up :

  


  


  System.IO.IOException : Connection timed out ---> System.Net.Sockets.SocketException (110) : Connection timed out

  


  


  Here is the argument I use to crop video fragments :

  


  var arg =
        $"-i - -ss 00:01:05 -to 00:03:10 -c copy -f matroska -";
return StartFfmpeg(arg, input);


  


  Moreover, if I remove the -to hh:mm:ss flag, then everything will be fine.
If you look at the ffmpeg log, then everything works fine there
As far as I understood, the error happens exactly when transferring already from ffmepg

  


  I've tried a bunch of different libraries, but they don't fit because of weak stream support

  


  Audio extraction, video creation from pictures, transcoding everything works, but for some reason with video cropping I can't even figure out where to look to find an error