Recherche avancée

Sur d’autres sites (5632)

• lavc/vaapi_encode : Separate reference frame into previous/future list

  11 septembre 2023, par Fei Wang

  lavc/vaapi_encode : Separate reference frame into previous/future list
  To support more reference frames from different directions.
  Signed-off-by : Fei Wang <fei.w.wang@intel.com>
  
  Reviewed-by : Neal Gompa <ngompa13@gmail.com>
  

  • [DH] libavcodec/vaapi_encode.c
  • [DH] libavcodec/vaapi_encode.h
  • [DH] libavcodec/vaapi_encode_h264.c
  • [DH] libavcodec/vaapi_encode_h265.c
  • [DH] libavcodec/vaapi_encode_mpeg2.c
  • [DH] libavcodec/vaapi_encode_vp8.c
  • [DH] libavcodec/vaapi_encode_vp9.c

• avcodec/av1dec : export pixel format even if no hardware decoder is present

  7 septembre 2023, par James Almer

  avcodec/av1dec : export pixel format even if no hardware decoder is present
  And remove the AVOID_PROBING flag, given it's the last av1 decoder to be tested
  
  either way.
  
  This fixes a regression introduced in 1652f2492f88434010053289d946dab6a57e4d58,
  
  where even if forcing the native av1 decoder, if another decoder was present,
  
  like libdav1d or libaom-av1, they'd be used for probing and some fate tests
  
  would have different results.
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] libavcodec/av1dec.c
  • [DH] tests/fate-run.sh
  • [DH] tests/fate/flvenc.mak
  • [DH] tests/fate/lavf-container.mak
  • [DH] tests/fate/mpegps.mak
  • [DH] tests/ref/fate/av1-annexb-demux
  • [DH] tests/ref/lavf-fate/av1.mkv
  • [DH] tests/ref/lavf-fate/av1.mp4

• Why is the external executable I bundled with my azure function not being found at runtime, despite it being present in the expected location ?

  6 septembre 2023, par Cristian Camilo Garcia Barrera

  I have a group of Azure functions that I publish to a functions app. One of these is a blob triggered function, meant to extract thumbnails from videos uploaded to Azure storage, and to do so, uses ffmpeg.exe.

  


  I have published the project via Visual Studio, adding the executable in a directory in the root of the project. The relative path is exe/ffmpeg.exe. To include the executable in the published bundle I followed the instructions in this Microsoft Developer instructional video.

  


  After publication, If I enter the Kudu debug console for this function app, I can find the file under C:\home\site\wwwroot\exe\ffmpeg.exe, as expected. I can even use that absolute path to execute ffmpeg inside the Kudu console.

  


  This is the code I use to call the ffmpeg executable in the blob function :

  


  using (var process = new Process())
{
    process.StartInfo = new ProcessStartInfo
    {
        FileName = @"C:\home\site\wwwroot\exe\ffmpeg.exe",
        Arguments = $"-hide_banner -loglevel error -i {videoTempPath} -frames:v 1 {thumbTempPath}",
        UseShellExecute = false,
        RedirectStandardOutput = true,
        RedirectStandardError = true,
        CreateNoWindow = true
    };

    process.Start();
    await process.WaitForExitAsync();
}


  


  However, this does not work. I get the following error in the logs :

  


  


  An error occurred trying to start process 'C :\home\site\wwwroot\exe\ffmpeg.exe' with working directory 'C :\Program Files (x86)\SiteExtensions\Functions 4.25.2132bit. The system cannot find the file specified.

  


  


  And indeed my thumbnails are never created. How can I solve this, or why does it happen ?