Recherche avancée

Sur d’autres sites (7795)

• The system cannot find the file specified error when trying to execute FFMpeg command with C# (same code works fine in a different app)

  5 mars 2023, par m_kr

  I know there are similar questions to this one. I have gone through every single one I could find and nothing worked for me. Here is my issue :

  


  I am trying to execute a FFMpeg command in command-line through .NET.

  


  Before anything I tried doing it with the following code :

  


  public static string executeCommand(string commandToBeExecuted)
    {
        Process cmd = new Process();
        cmd.StartInfo.FileName = "cmd.exe";
        cmd.StartInfo.RedirectStandardInput = true;
        cmd.StartInfo.RedirectStandardOutput = true;
        cmd.StartInfo.CreateNoWindow = true;
        cmd.StartInfo.UseShellExecute = false;
        cmd.Start();

        cmd.StandardInput.WriteLine(commandToBeExecuted);
        cmd.StandardInput.Flush();
        cmd.StandardInput.Close();
        cmd.WaitForExit();
        return cmd.StandardOutput.ReadToEnd();
    }


  


  Sending the "ffmpeg -h" command in commandToBeExecuted. This did not work.

  


  I next tried the following solution :

  


  public static string ffmpegCommand(string commandToBeExecuted)
    {
        ProcessStartInfo startInfo = new ProcessStartInfo();
        startInfo.CreateNoWindow = false;
        startInfo.UseShellExecute = false;
        startInfo.FileName = "c:\\ffmpeg\\bin\\ffmpeg.exe";
        startInfo.WindowStyle = ProcessWindowStyle.Hidden;
        startInfo.Arguments = "-h";

        startInfo.RedirectStandardOutput = true;
        startInfo.RedirectStandardError = true;


        Process exeProcess = Process.Start(startInfo);

        // string error = exeProcess.StandardError.ReadToEnd();
        string output = exeProcess.StandardOutput.ReadToEnd();
        exeProcess.WaitForExit();
        return output;
    }


  


  This returns the following error :

  


  


  The system cannot find the file specified

  


  


  I am assuming this is referring to this part of the code :

  


  startInfo.FileName = "c:\\ffmpeg\\bin\\ffmpeg.exe";


  


  However, I checked and this is the correct path to my ffmpeg.exe file. On an even weirder note, this code works correct when tested in a new .net console application. However, I am creating an extension for OutSystems in integration, and when testing this code there it no longer works. The long exception from the logs is the following :

  


  


  CssbobffmpegCommandTestFolder
System.ComponentModel.Win32Exception : The system cannot find the file specified
at Object.s [as getException] (https://personal-jwy0bfog.outsystemscloud.com/FFMpegCommandGeneratorFFProbeVisual/scripts/OutSystems.js?RnlDcii3Xz75iIHHERIZtA:2:10241)
at c.onSuccess (https://personal-jwy0bfog.outsystemscloud.com/FFMpegCommandGeneratorFFProbeVisual/scripts/OutSystems.js?RnlDcii3Xz75iIHHERIZtA:3:7232)
at XMLHttpRequest. (https://personal-jwy0bfog.outsystemscloud.com/FFMpegCommandGeneratorFFProbeVisual/scripts/OutSystems.js?RnlDcii3Xz75iIHHERIZtA:3:2648)

  


  


  I researched similar problems and tried the following solutions :

  


  In place of :

  


  startInfo.FileName = "c:\\ffmpeg\\bin\\ffmpeg.exe";


  


  I tried :

  


    startInfo.WorkingDirectory = "c:\\ffmpeg\\bin";
  startInfo.FileName = @"ffmpeg.exe";


  


  I also tried changing the :

  


  startInfo.Arguments = "-h";


  


  to :

  


  startInfo.Arguments = "/C -h";


  


  I tried to "add new item" to my solution : the ffmpeg.exe file, and I tried the following logic :

  


  public static string testingNewApproachTwoThree(string commandToBeExecuted)
    {
        string res;
        ProcessStartInfo startInfo = new ProcessStartInfo();

        startInfo.CreateNoWindow = false;
        startInfo.UseShellExecute = false;
        startInfo.FileName = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "ffmpeg\\ffmpeg.exe");
        startInfo.Arguments = "-h";
        startInfo.RedirectStandardOutput = true;
        //startInfo.RedirectStandardError = true;

        res = string.Format(
            "Executing \"{0}\" with arguments \"{1}\".\r\n",
            startInfo.FileName,
            startInfo.Arguments) + " NEXT: ";

        try
        {
            using (Process process = Process.Start(startInfo))
            {
                while (!process.StandardOutput.EndOfStream)
                {
                    res = res + process.StandardOutput.ReadLine();

                }

                process.WaitForExit();
            }
        }
        catch (Exception ex)
        {
            res = res + "exception:" + ex.Message;
        }

        return res;
    }


  


  as suggested in a different question.

  


  I tried changing the capitalization of letters in the specified filepath to make sure it matches the naming of my folders. Nothing worked.

  


  Any ideas ?

  


• Revision 105467 : Ne lancer ces getScripts que si on n’a pas déjà $.fn.sortable qui pourrait ...

  26 juillet 2017, par kent1@… — Log

  Ne lancer ces getScripts que si on n’a pas déjà $.fn.sortable qui pourrait être déjà présent (dans le head par un autre plugin par exemple)
  Evite des erreurs js possibles et le chargement de scripts non nécessaires

• Added SetHandler None directive. Closes #3381

  1er janvier 2015, par blueimp

  Added SetHandler None directive. Closes #3381
  The ForceType directive should already prevent execution of any scripts
  
  in this directory.
  
  However there might be environments where this does not apply, so we
  
  remove any associated handlers in addition.