Recherche avancée

Sur d’autres sites (10768)

• 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 ?

  


• Error : Error : Cannot find module '@ffmpeg.wasm/core-mt' Require stack :

  30 septembre 2023, par James

  I'm getting this error "Error : Error : Cannot find module '@ffmpeg.wasm/core-mt', When my code is deployed on Vercel (Node.js + TypeScript) Does I get confused because when I try to run the same code on my local machine it works fine

  


  But as I deploy it on Vercel it gives that error. Obviously, i do have "@ffmpeg.wasm/core-mt" installed as said in the package https://github.com/FFmpeg-wasm/FFmpeg.wasm#installation So how do I fix it ?

  


  I'm currently using it like this

  


  import { FFmpeg } from "@ffmpeg.wasm/main";

async function myFunction() {
    const ffmpeg = await FFmpeg.create({
        core: "@ffmpeg.wasm/core-mt",
        log: true,
    });
}


  


  However, in the docs, i see doing like this

  


    import { FFmpeg } from "@ffmpeg.wasm/main";
    
     const ffmpeg = await FFmpeg.create({
            core: "@ffmpeg.wasm/core-mt",
            log: true,
        });

    async function myFunction() {
        // use ffmpeg here
    }


  


  But then i start getting errors like "top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', or 'nodenext', and the 'target' option is set to 'es2017' or higher."

  


  I tried a couple of StackOverflow solutions but nothing works in my case. So what should I do ?

  


  tsconfig.json :

  


  {
    "compilerOptions": {
     "module": "CommonJS",
     "esModuleInterop": true,
      "allowSyntheticDefaultImports": true,
      "target": "es2017",
      "noImplicitAny": true,
      "moduleResolution": "node",
      "sourceMap": true,
      "outDir": "dist",
      "baseUrl": ".",
      "paths": {
        "*": ["node_modules/*", "src/types/*"]
      }
    },
    "include": ["./src/**/*", "src/firebase/serviceAccountKey.ts"]
  }


  


• Exception thrown at 0x00007FFC0B57BCEF (swscale-6.dll) in App.exe : 0xC0000005 : Access violation reading location 0xFFFFFFFFFFFFFFFF

  9 novembre 2023, par JIUN-YU

  Trying to play a video using FFmpeg on visual studio 2022 on windows 10.
Exception is thrown at sws_scale in the code. Don't know why this is occurred.
It is worth noting that this error sometimes occurs when reading the camera and sometimes it does not.

  


  here is my code

  


  bool CalibrationPanel::video_reader_read_frame(VReaderState* state, cv::Mat cvimg)
{
    // Unpack members of state
    auto& width = state->width;
    auto& height = state->height;
    auto& av_format_ctx = state->av_format_ctx;
    auto& av_codec_ctx = state->av_codec_ctx;
    auto& video_stream_index = state->video_stream_index;
    auto& av_frame = state->av_frame;
    auto& av_packet = state->av_packet;
    auto& sws_scaler_ctx = state->sws_scaler_ctx;


    // Decode one frame
    int response;
    while (av_read_frame(av_format_ctx, av_packet) >= 0)
    {
        if (av_packet->stream_index != video_stream_index)
        {
            av_packet_unref(av_packet);
            continue;
        }

        response = avcodec_send_packet(av_codec_ctx, av_packet);
        if (response < 0)
        {
            char errStr[256] = {0};
            av_strerror(response, errStr, sizeof(errStr));
            printf("Failed to decode packet: %s\n", errStr);
            return false;
        }

        response = avcodec_receive_frame(av_codec_ctx, av_frame);
        if (response == AVERROR(EAGAIN) || response == AVERROR_EOF)
        {
            av_packet_unref(av_packet);
            continue;
        }
        else if (response < 0)
        {
            char errStr[256] = {0};
            av_strerror(response, errStr, sizeof(errStr));
            printf("Failed to decode packet: %s\n", errStr);
            return false;
        }

        av_packet_unref(av_packet);
        break;
    }
    int64_t* pts = &ppts;
    *pts = av_frame->pts;

    // Set up sws scaler
    if (!sws_scaler_ctx)
    {
        sws_scaler_ctx = sws_getContext(width, height, av_codec_ctx->pix_fmt,
                                        width, height, AV_PIX_FMT_BGR24,
                                        SWS_BILINEAR, NULL, NULL, NULL);
        if (!sws_scaler_ctx)
        {
            printf("Couldn't initialize sw scaler\n");
            return false;
        }
    }


    // Creating an image space to hold YUV images
    AVFrame* frameYUV = av_frame_alloc();
    auto* out_buffer = (unsigned char*)av_malloc(av_image_get_buffer_size(AV_PIX_FMT_BGR24, width, height, 1));
    av_image_fill_arrays(frameYUV->data, frameYUV->linesize, (const uint8_t*)out_buffer, AV_PIX_FMT_BGR24, width, height, 1);

    uint8_t* dest[4] = {cvimg.data, NULL, NULL, NULL};
    sws_scale(sws_scaler_ctx, av_frame->data, av_frame->linesize, 0, av_frame->height, dest, frameYUV->linesize);

    return true;
}


  


  fixed this bug, so it's not luck that makes the camera turn on every time.