Recherche avancée

Sur d’autres sites (9407)

• Unable to load FFMpeg in file in laravel project

  14 février 2024, par Hatim Ahmad

  i'm trying to convert a varity of audio files into a specific audio type of my chossing on my laravel project.
on my search i landed on a package called Laravel FFMpeg, i started with a fresh installation with laravel 6.2, and did the installation as it shows on github, as soon as i started using it i had this error :

  


  


  FFMpeg\Exception\ExecutableNotFoundException : Unable to load FFMpeg in file C :\Users\Hatim\Desktop\Projects\Audio\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver\FFMpegDriver.php on line 55
#0 C :\Users\Hatim\Desktop\Projects\Audio\vendor\pbmedia\laravel-ffmpeg\src\Support\ServiceProvider.php(61) : FFMpeg\Driver\FFMpegDriver::create(Object(Illuminate\Log\LogManager), Object(Alchemy\BinaryDriver\Configuration))

  


  


  I'm currently just working with a simple thing :

  


  FFMpeg::fromDisk('s3');


  


  and yes I have called it my Controller : use ProtoneMedia\LaravelFFMpeg\Support\FFMpeg;

  


  I have also tried to install the PHP-FFMpeg Package and also tried to install FFmpeg on my device and link it using the path in my config\laravel-FFmpeg

  


  This is how it looks now without any modification, I went to my .env folder but it has nothing regarding FFmpeg so it takes the default value, that's why I tried installing it on my device and replacing the default value with the path of the FFmpeg on my device.

  


  return [
'ffmpeg' => [
    'binaries' => env('FFMPEG_BINARIES', 'ffmpeg'),
    'threads'  => 12,
],

'ffprobe' => [
    'binaries' => env('FFPROBE_BINARIES', 'ffprobe'),
],

'timeout' => 3600,
'enable_logging' => true


  


  ] ;

  


  I'm currently working on my local environment, but this has to work on a server.

  


• FFMPEG RTX 8000 out of memory

  23 juin 2020, par Mahdi Adnan

  I have an RTX 8000 and I'm using FFMPEG to transcode multiple streams concurrently.
Each stream consume around 575MiB, and when the memory usage reaches around 28000MiB, FFMPEG throw the following message when starting a new transcode session :

  



  [h264_nvenc @ 0x55cd1d574800] dl_fn->cuda_dl->cuCtxCreate(&ctx->cu_context_internal, 0, cu_device) failed -> CUDA_ERROR_OUT_OF_MEMORY : out of memory
[h264_nvenc @ 0x55cd1d574800] No NVENC capable devices found
Error initializing output stream 2:0 — Error while opening encoder for output stream #2:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  



  The machine is running Ubuntu 20.04
FFMPEG is a snap package from Ubuntu repo "version 4.2.2-1ubuntu1"
nVidia driver nvidia-driver-435 installed from Ubuntu repo

  



  command used for the transcode :
ffmpeg -i SRC -c:v h264_cuvid -vcodec h264_nvenc -preset:v medium -profile:v main -vf "scale=1920 :-2" -hls_flags delete_segments -hls_init_time 4 -hls_time 4 -maxrate 6000k -g 100 -bufsize 12000k -b:v 3000k -start_number 1 -async 1 -c:a aac -b:a 128k 1080.m3u8

  



  Is the RTX 8000 have any limitation on the Memory usage ? are the parameters I'm using causing this issue ?

  



  Thanks

  


• Why are there vaapi filters that exist in libavfilter but do not exist in my compiled version of ffmpeg ?

  13 juin 2020, par John Allard

  I've compiled the most recent snapshot of ffmpeg with vaapi enabled

  



  $ ffmpeg -hwaccesls
ffmpeg version N-98129-g0b182ff Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.12) 20160609
  configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libass --enable-fontconfig --enable-libfreetype --enable-libvidstab --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-libsrt --enable-vaapi --extra-cflags=-I/opt/ffmpeg/include --extra-ldflags=-L/opt/ffmpeg/lib
  libavutil      56. 54.100 / 56. 54.100
  libavcodec     58. 92.100 / 58. 92.100
  libavformat    58. 46.101 / 58. 46.101
  libavdevice    58. 11.100 / 58. 11.100
  libavfilter     7. 86.100 /  7. 86.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
Hardware acceleration methods:
vaapi


  



  I know that vaapi is working because I can use it for hardware decoding and encoding of h264 videos. I can see some vaapi filters as well

  



  $ ffmpeg -filters | grep vaapi
 ... deinterlace_vaapi V->V       (null)
 ... denoise_vaapi     V->V       (null)
 ... procamp_vaapi     V->V       (null)
 ... scale_vaapi       V->V       (null)
 ... sharpness_vaapi   V->V       (null)


  



  However, I notice that this list is missing the filter that I'm specifically looking for, namely , transpose_vaapi. If you look in the libavfilter source code you'll see the following

  



  This shows the transpose_vaapi filter defined in the allfilters.c file
https://github.com/FFmpeg/FFmpeg/blob/master/libavfilter/allfilters.c#L414

  



  This shows the transpose_vaapi filter source code
https://github.com/FFmpeg/FFmpeg/blob/master/libavfilter/vf_transpose_vaapi.c

  



  If the filter is defined in source code, it's defined in allfilters.c, and I've compiled ffmpeg from this source with vaapi enabled, why can I not use this filter with ffmpeg ?

  



  $ ffmpeg -y -hide_banner -nostats -loglevel error \
    -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi \
    -i ./test_video.mp4 \
    -vf 'format=nv12,transpose_vaapi=2' \
    -c:v h264_vaapi \
    /tmp/rotated_video.mp4
[AVFilterGraph @ 0xf14000] No such filter: 'transpose_vaapi'
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument


  



  EDIT -

  



  Looking through the source code for vf_transpose_vaapi.c I see the following logic

  



      if (!pipeline_caps.rotation_flags) {
        av_log(avctx, AV_LOG_ERROR, "VAAPI driver doesn't support transpose\n");
        return AVERROR(EINVAL);
    }


  



  that's inside of the transpose_vaapi_build_filter_params function which is part of the filter initialization process. I guess it's possible that, if that call failed, the filter would fail to be built and it would not be registered as a valid filter ? This seems like something that would happen at runtime when I attempt to run the filter rather than something that would happen at compile time when setting which filters are defined.