Recherche avancée

Sur d’autres sites (4338)

• Using ffmpeg in Powershell

  27 avril 2016, par Matthew Goode

  Can’t find much information on this, as I believe it’s a pretty noobish problem and there aren’t really any tutorials on it. Can anyone explain how I can use ffmpeg in a powershell script ? I downloaded ffmpeg and I have the path to ffmpeg.exe. Shouldn’t I be able to do something like this ?

  "C:\path\ffmpeg.exe" -i stuff.mp3 stuff.wav

  It returns an error message along the lines of -i not being a recognized parameter. Am I missing something pretty basic here ? Thanks for any help. I’m trying to convert some audio files between .wav, .mp3. and .flac, and if anyone has any better suggestions than ffmpeg then please let me know.

• Issue with Asynchronous Video Processing and New Window Creation in Windows Forms Application

  2 août 2023, par sadra hoseini

  I have a Windows Forms application that uses FFmpeg for video processing tasks. In this application, I have a textBox2_TextChanged event handler that performs some video processing tasks based on user input.

  


  However, I noticed that when textBox2_TextChanged is called, the UI becomes unresponsive, and it seems like another window is being created but doesn't show up. I suspect that this issue is related to threading.

  


  Here's a simplified version of the problematic code :

  


  // Relevant code snippet:
private async void textBox2_TextChanged(object sender, EventArgs e)
{
    if (listBox1.Items.Count > 0 && int.TryParse(textBox2.Text, out int itemvalue) && int.TryParse(textBox1.Text, out int ratio))
    {
        await Task.Run(() =>
        {
            // Video processing code using FFmpeg (e.g., creating thumbnails).
            // This code seems to cause the UI to freeze and prevent new windows from showing up.
        });
    }
}


  


  Expected Behavior :

  


  When a user enters a valid input in textBox2, the video processing tasks should be executed in the background without freezing the UI. The application should remain responsive, and any new windows, including message boxes or progress dialogs, should show up as expected.

  


  Actual Behavior :

  


  When a user enters a valid input in textBox2, the video processing tasks appear to be running, but the UI becomes unresponsive, and new windows, such as message boxes, do not show up as expected. This makes it challenging to display any progress or error messages to the user during video processing.

  


  Steps to Reproduce :

  


  Open the Windows Forms application.
Add some video files to the list (listBox1) and provide valid input in textBox2.
Observe the UI behavior and any new windows that should be displayed, such as progress dialogs or message boxes.
Additional Notes :

  


  I am using Visual Studio [version] for development.
The application uses FFmpeg for video processing tasks, and I've verified that FFmpeg is functioning correctly.
I've also tried using proper error handling to catch any exceptions, but no exceptions are thrown during the video processing tasks.
Any help or suggestions on how to resolve this issue and enable new window creation during video processing would be greatly appreciated. Thank you !

  


• How to scape special characters for linux, nodejs exec function

  22 février 2023, par David Chavez

  I'm running this ffmpeg command on my linux server and while I paste it into the terminal, it works just fine but as soon as I use execPromise to run the EXACT same command, it returns an error.

  


  const { exec } = require('child_process');
const { promisify } = require('util');
const execPromise = promisify(exec);

const encode = async ffmpegCode => {
    try {
        console.log(ffmpegCode) //Here I can see that the code is the
                                //exact same one than the one that works
                                //when pasted into the terminal
        await execPromise(ffmpegCode);
        return 200
    } catch (err) {
        console.log(err)
    }
}


  


  I need \: to be interpreted as such. When I type it as is, \:, the error message shows me that it interpreted it as : which is expected.

  


  If I pass in \\:, I expect it to interpret it as I need it which would be \: but the error shows me that it interprets it as \\:.

  


  \\\: is interpreted as \\: and \\\\: is interpreted as \\\\:.

  


  Part of the command passed :

  


  ...drawtext=text='timestamp \\: %{pts \\: localtime \\: 1665679092.241...

  


  Expected command :

  


  ...drawtext=text='timestamp \: %{pts \: localtime \: 1665679092.241...

  


  Error message :

  


  ...drawtext=text='timestamp \\: %{pts \\: localtime \\: 1665679092.241...

  


  How do I get /: through to the exec function ?