Recherche avancée

Sur d’autres sites (6722)

• How to set the ffmpeg path in a Windows Electron app

  21 août 2024, par Arco Voltaico

  My electron app has these dependencies at app folder level (node), not /src (angular) :

  


      "ffmpeg-static-electron": "2.0.3",
    "fluent-ffmpeg-corrected": "1.0.0",


  


  On main.ts I execute this function :

  


  function initFfmpeg() {
    const p = detectPlatformAndArch();
    const originalPath = ffmpegBin.path;
    let ffmpegPath2 = originalPath;
    if (!serve) {
        console.log('Running in packaged mode');

        if (p.os !== 'mac') {
             // forcing for now win x64
             ffmpegPath2 = path.join(process.resourcesPath, 'app.asar.unpacked', 'node_modules', 'ffmpeg-static-electron', 'bin', 'win', 'x64', 'ffmpeg.exe');
        }
....
    } 
....
    ffmpeg.setFfmpegPath(ffmpegPath2);
    mainWindow.webContents.send('ffmpegPath', {"path": ffmpegPath2, "originalPath": originalPath});
}


  


  When the electron is compiled/packed and running in a Mac, ffmpeg works, but in Windows does not.
I suspect the path is not the right one on the latter.

  


  I have no acccess to the Win PC, so I'm sending the path values to the mainWindow and there I persist it to a DB, so I know the ffmpegPath2 is :
C:\Users\aran\AppData\Local\Temp\2kQuOPO86a60WbRClif2pSzIOMn\resources\app.asar.unpacked\node_modules\ffmpeg-static-electron\bin\win\x64\ffmpeg.exe

  


  when in my Mac from where I code it is :

  


  /Users/me/myApp/release/win-unpacked/resources/app.asar.unpacked/node_modules/ffmpeg-static-electron/bin/win/x64/ffmpeg.exe


  


• Is there an efficient way to use ffmpeg to perform a large quantity of cuts from a single file ?

  16 mars 2024, par Giuliano Oliveri

  I'm trying to cut video files into smaller chunks. (each one being one word said in the video, so they're not all of equal size)

  


  I've tried a lot of different approaches to try to be as efficient as possible, but I can't get the runtime to be under 2/3rd of the original video length. That's an issue because I'm trying to process 400+ hours of video.

  


  Is there a more efficient way to do this ? Or am I doomed to run this for weeks ?

  


  Here is the command for my best attempt so far

  


  ffmpeg -hwaccel cuda -hwaccel_output_format cuda -ss start_timestamp -t to_timestamp -i file_name -vf "fps=30,scale_cuda=1280:720" -c:v h264_nvenc -y output_file


  


  Note that the machine running the code has a 4090
This command is then executed via python, which gives it the right timestamps and file paths for each smaller clip in a for loop

  


  I think it's wasting a lot of time calling a new process each time, however I haven't been able to get better results with a split filter ; but here's the ffmpeg-python code for that attempt :

  


  Creation of the stream :

  


  inp = (
    ffmpeg
    .input(file_name, hwaccel="cuda", hwaccel_output_format="cuda")
    .filter("fps",fps=30)
    .filter('scale_cuda', '1280','720')
    .filter_multi_output('split')
)


  


  Which then gets called in a for loop

  


  (
    ffmpeg
    .filter(inp, 'trim', start=row[1]['start'], end=row[1]['end'])
    .filter('setpts', 'PTS-STARTPTS')
    .output(output_file,vcodec='h264_nvenc')
    .run()
)


  


• Is there an efficient way to use ffmpeg to create a huge quantity of small video file, cut from a larger one ?

  9 mars 2024, par Giuliano Oliveri

  I'm trying to cut video files into smaller chunks. (each one being one word said in the video, so they're not all of equal size)

  


  I've tried a lot of different approaches to try to be as efficient as possible, but I can't get the runtime to be under 2/3rd of the original video length. That's an issue because I'm trying to process 400+ hours of video.

  


  Is there a more efficient way to do this ? Or am I doomed to run this for weeks ?

  


  Here is the command for my best attempt so far

  


  ffmpeg -hwaccel cuda -hwaccel_output_format cuda -ss start_timestamp -t to_timestamp -i file_name -vf "fps=30,scale_cuda=1280:720" -c:v h264_nvenc -y output_file


  


  Note that the machine running the code has a 4090
This command is then executed via python, which gives it the right timestamps and file paths for each smaller clip in a for loop

  


  I think it's wasting a lot of time calling a new process each time, however I haven't been able to get better results with a split filter ; but here's the ffmpeg-python code for that attempt :

  


  Creation of the stream :

  


  inp = (
    ffmpeg
    .input(file_name, hwaccel="cuda", hwaccel_output_format="cuda")
    .filter("fps",fps=30)
    .filter('scale_cuda', '1280','720')
    .filter_multi_output('split')
)


  


  Which then gets called in a for loop

  


  (
    ffmpeg
    .filter(inp, 'trim', start=row[1]['start'], end=row[1]['end'])
    .filter('setpts', 'PTS-STARTPTS')
    .output(output_file,vcodec='h264_nvenc')
    .run()
)