Recherche avancée

Sur d’autres sites (6923)

• issue starting ffmpeg screen capture on OSX (AVFoundation) from Java

  24 juin 2022, par stewori

  I would like to launch from Java on OSX a screen capture command like explained here : https://trac.ffmpeg.org/wiki/Capture/Desktop

  



  It works fine from the terminal. But when I launch exactly the same command using Java's Runtime.exec I get the following output :

  



  [AVFoundation input device @ 0x7f892f500400] Video device not found

'1:': Input/output error


  



  Assume the command I run is stored as String cmd = "ffmpeg -f avfoundation -i '1:' output.mkv". Things I tried :

  



  


  • Using ffmpeg -f avfoundation -list_devices true -i "" I asserted that 1 is the correct index for the screen. I ran that command also via Runtime.exec and it gives the same indexes as when I run it from terminal.

  


  • It does not make a difference whether I use '1:' or "\"1:\"". Well, in the latter case it says "1:": Input/output error. Both variants work in terminal.

  


  • Neither does it make a difference whether I call
Runtime.getRuntime().exec(cmd),
Runtime.getRuntime().exec(cmd.split(" ")) or (new ProcessBuilder(cmd.split(" "))).start(). In principle it starts ffmpeg and that terminates with the output given above.

  


  • It does not seem to make a difference whether I read out ffmpeg's output or not (via process.getErrorStream())

  


  • The only thing that works is to store the command in a file, e.g. in run.sh and then call e.g. Runtime.getRuntime().exec("run.sh"). It should be possible to execute this properly from Java without this kind of workaround, right ? What am I doing wrong ?

  


  • On Linux, using e.g. ffmpeg -video_size 1024x768 -framerate 25 -f x11grab -i :0.0+100,200 output.mp4 it works fine, from command line or from Java, with Runtime.exec and via ProcessBuilder.

  


  



  I did not try it on Windows. On OSX (Mojave 10.14.5) I used Java 12, on Linux (Mint 18, 64bit) Java 8. Would be some hassle to try it with Java 12 on Linux and I suspect the Java version is not the cause, given that avfoundation vs x11grab is the far more dominant difference.

  


• Swift A script of macOS is not running on the M2 chip ?

  15 avril 2024, par Muhammad Danish Qureshi

  I am making a macOS app using SwiftUI, app is working fine on mac Intel chip, mac Apple M1 chip but not working on the mac M2 chip.
Below is the following code which is crashing on M2 chip for force unwrapping the data in String(data: data!, encoding: .utf8).

  


  I know that force unwrap is not suitable, but for testing purpose I am doing force unwrap.

  


  When I run the which ffmpeg in terminal it provides the path in result, no matter which mac terminal is (it always return actual path of ffmpeg), but when run this command from the swift Program it does not found anything and got crashed on apple M2 chip.

  


  My actual scenario (or requirement) is I need to get the path using the command which ffmpeg and write that path in the file on macOS app.

  


  Kindly guide me why the code is crashing or not providing the actual path.

  


  func findFFmpegPath() -> String? {
            let task = Process()
            task.launchPath = "/bin/bash" // Path to bash shell
            task.arguments = ["-l", "-c", "which ffmpeg"] // Execute "which ffmpeg" command
    let pipe = Pipe()
    task.standardOutput = pipe
    task.standardError = pipe // Capture any errors as well

    do {
        try task.run()
        let data = try pipe.fileHandleForReading.readToEnd()
        let output = String(data: data!, encoding: .utf8)
        print("data:\(data)\n\(output)\n\(output?.trimmingCharacters(in: .whitespacesAndNewlines))")
        return output?.trimmingCharacters(in: .whitespacesAndNewlines)
    } catch {
        print("Error running task: \(error)")
        return nil
    }
}


  


  When I run which ffmpeg in the terminal it gives me path correctly, See the screenshot bleow.

  


  

  


  When I run the /bin/bash -l -c "which ffmpeg" in the M2 than I got this result.

  


  

  


  When I run the /bin/bash -l -c "which ffmpeg" in the Apple M1 than I got this result.

  


  

  


  Getting desired result in the terminal, but not getting result from the Swift Program.

  


• getruntime() exec() with double quotes in command

  29 décembre 2012, par brux

  I want to execute an ffmpeg command, the method I am using works with every command on my list except the following one which contains double quotes to set a filter (-vf) parameter

  ffmpeg -i 2012-12-27.mp4 -vf "movie=bb.png [movie]; [in] [movie] overlay=0:0 [out]" -vcodec libx264 -acodec copy out.mp4

  I have tried changing the quotes for single quotes with no luck. The command works at the android terminal with both single and double quotes.

  The app I'm developing uses about 5 ffmpeg commands, all work except this one, is this some bug ?

  I can't find a concrete solution to this problem, breaking the args into an array and then passing this to runtime().exec() as suggested elsewhere doesn't seem to work, or simply trying to escape the quotes with \" won't work.

  Both of the files referenced in the above command are located in the sdcard, I removed the concatenation of the command out so that things don't get messy, rest assured these commands work in a terminal when referencing the full paths to the files.
  I contatenate the string passed to getRuntime().exec() using a stringbuilder and`getexternalstorageDirectory().getabsolutepath() to get the path to each file like I have been doing with previous commands when using the process class.

  I am using Jelly Bean 4.2 in case that is of any significance.