Recherche avancée

Sur d’autres sites (6393)

• lavfi/vf_stack_vaapi : factor out the common code for stack setting

  7 février 2023, par Haihao Xiang

  lavfi/vf_stack_vaapi : factor out the common code for stack setting
  The common code will be used in QSV based stack filters.
  Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
  

  • [DH] libavfilter/stack_internal.c
  • [DH] libavfilter/stack_internal.h
  • [DH] libavfilter/vf_stack_vaapi.c

• fftools/ffmpeg_demux : move InputStream.guess_layout_max to stack

  11 février 2023, par Anton Khirnov

  fftools/ffmpeg_demux : move InputStream.guess_layout_max to stack
  It is only needed while processing the stream in add_input_streams(), no
  
  reason to store it in the context.
  

  • [DH] fftools/ffmpeg.h
  • [DH] fftools/ffmpeg_demux.c

• 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"]
  }