Recherche avancée

Sur d’autres sites (8205)

• Unable to choose an output [closed]

  17 février 2024, par Xdangin

  I try to change the time for subtitle and every time this pop up on my face

  


  


  Unable to choose an output format for 'output-subfamily' ; use a standard extension for the filename or specify the format manually

  


  


  srry guys cuz I don't get it but I'm new at this

  


  here's the full log im case I wrote something wrong

  


  /sdcard $ ffmpeg -itsoffset 2 -i Family.Guy.S04E23.srt -c:v copy output-sub family guy.srt

ffmpeg version 6.1.1 Copyright (c) 2000-2023 the FFmpeg developers

  built with Android (10552028, +pgo, +bolt, +lto, -mlgo, based on r487747d) clang version 17.0.2 (https://android.googlesource.com/toolchain/llvm-project d9f89f4d16663d5012e5c09495f3b30ece3d2362)

  configuration: --arch=aarch64 --as=aarch64-linux-android-clang --cc=aarch64-linux-android-clang --cxx=aarch64-linux-android-clang++ --nm=llvm-nm --pkg-config=/home/builder/.termux-build/_cache/android-r26b-api-24-v1/bin/pkg-config --strip=llvm-strip --cross-prefix=aarch64-linux-android- --disable-indevs --disable-outdevs --enable-indev=lavfi --disable-static --disable-symver --enable-cross-compile --enable-gnutls --enable-gpl --enable-version3 --enable-jni --enable-lcms2 --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgme --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenmpt --enable-libopus --enable-librav1e --enable-libsoxr --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-mediacodec --enable-opencl --enable-shared --prefix=/data/data/com.termux/files/usr --target-os=android --extra-libs=-landroid-glob --disable-vulkan --enable-neon --disable-libfdk-aac

  libavutil      58. 29.100 / 58. 29.100

  libavcodec     60. 31.102 / 60. 31.102

  libavformat    60. 16.100 / 60. 16.100

  libavdevice    60.  3.100 / 60.  3.100

  libavfilter     9. 12.100 /  9. 12.100

  libswscale      7.  5.100 /  7.  5.100

  libswresample   4. 12.100 /  4. 12.100

  libpostproc    57.  3.100 / 57.  3.100

Input #0, srt, from 'Family.Guy.S04E23.srt':

  Duration: N/A, bitrate: N/A

  Stream #0:0: Subtitle: subrip

[AVFormatContext @ 0x75b7eb2500] Unable to choose an output format for 'output-sub'; use a standard extension for the filename or specify the format manually.

[out#0 @ 0x75b7e3e840] Error initializing the muxer for output-sub: Invalid argument

Error opening output file output-sub.

Error opening output files: Invalid argument

/sdcard $ ffmpeg -itsoffset 2 -i Family.Guy.S04E23.srt -c copy output-sub family guy.srt


  


  I searched YouTube but didn't find anything

  


• FFmpeg bug with a image that has a #ededed color

  11 avril 2023, par Денис Выхрыстюк

  I want to generate a video from images. When the pictures have a gray(#ededed) background then a strange error occurs, but when with other colors everything is good.

  


  I will be grateful for any help.

  


  I run the following commands :

  


  ./ffmpeg.exe -s 1080x1080 -framerate 1 -i ./scene0_%6d.png -crf 1 -c:v rawvideo -pix_fmt yuv420p ./result.yuv


  


  ./ffmpeg.exe -s 1080x1080 -framerate 1 -i ./result.yuv -c:v libx264 -crf 15 -preset veryslow -pix_fmt yuv420p -maxrate 900M -bufsize 12000k ./final.mp4


  


  Result :

  


  Error: Option framerate not found


  


  FFmpeg version :

  


  ffmpeg version N-110165-g9a245bdf5d-20230403 Copyright (c) 2000-2023 the FFmpeg developersbuilt with gcc 12.2.0 (crosstool-NG 1.25.0.152_89671bf)configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-pthreads --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --disable-libmfx --enable-libvpl --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --disable-libdrm --disable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra-version=20230403 libavutil 58. 5.100 / 58. 5.100 libavcodec 60. 9.100 / 60. 9.100 libavformat 60. 4.101 / 60. 4.101 libavdevice 60. 2.100 / 60. 2.100 libavfilter 9. 5.100 / 9. 5.100 libswscale 7. 2.100 / 7. 2.100 libswresample 4. 11.100 / 4. 11.100libpostproc 57. 2.100 / 57. 2.100


  


  

  


  I tried other colors and everything is fine. I expect that I will be able to combine the gray images to the video and that the desired color profile will be finded

  


• Node 18 or Node 20 break ffmpeg (in google cloud functions -> ffprobe was killed with signal SIGSEGV)

  10 janvier 2024, par user20206929

  Please see below, the code is working on node js 16, but not when upgrading to node 18 or 20.

  


  const ffmpeg = require("fluent-ffmpeg");

// Following is inside a .https.onRequest Google Cloud function with enough memory

try {
  const duration = new Promise((resolve, reject) => {
  ffmpeg.ffprobe(videoUrl, async (err, metadata) => {
    if (err) {
      if (res.headersSent) {
        console.error("Response already sent");
        return;
      } else {
        console.log("Metadata:", metadata);
        console.log("err: " + err);
        res.status(400).send("Error getting video metadata");
        return;
      }
    }
  const duration = metadata.format.duration;
  console.log("video duration in second: " + duration);
  resolve(duration);
  });
});
  videoDuration = await duration;
} catch (err) {
  console.log(err);
  throw err;
}


  


  When upgrading to node 18/20 (No other change than upgrading node), the error "ffprobe not found" appears.

  


  But setting the path manually using ffmpeg.setFfprobePath(ffprobePath) ;
trigger the error : Error : ffprobe was killed with signal SIGSEGV

  


  So it seem its a permissions issue.

  


  However, I tried a lot of different solutions, none of them made this work.
For instance i tried to download manually the ffprobe from the official website https://ffbinaries.com/downloads. Then manually add it to the code.

  


  I tried to use https://www.npmjs.com/package/@ffprobe-installer/ffprobe or others package like https://www.npmjs.com/package/ffprobe-static

  


  I also tried to download the ffprobe file to the temporary folder of google cloud, and change the permission of this folder.

  


  All of those was doing the same error.

  


  None of what i could think of made any difference.

  


  Please help because i need to update node 16 to 18 or 20 before google remove node 16 on january 31 2024 and for now i don't see a solution.

  


  I also looked for other solution to get this duration from a video file url, but using ffmpeg seem to be the only one that should work out of the box. As it is working on node 16.

  


  Thank you,

  


  UPDATE - 11/26/2023

  


  GCP Functions NodeJS 16 runtime uses Ubuntu 18.04 with FFMpeg installed.
NodeJS 18/20 use Ubuntu 22.04, and Google decided not to include FFMpeg.

  


  https://cloud.google.com/functions/docs/runtime-support#node.js
https://cloud.google.com/functions/docs/reference/system-packages

  


  No workaround or solutions found as of now

  


  UPDATE - 01/10/2024

  


  Google added back ffmpeg to latest version, this is working as before now.