Recherche avancée

Sur d’autres sites (11954)

• lavf : do not use the parser duration for video

  13 avril 2014, par Anton Khirnov

  lavf : do not use the parser duration for video
  The parser has no way of knowing video duration, and therefore no video
  
  parsers set it.
  

  • [DBH] libavformat/utils.c

• FFMPEG : Working of parser of a video decoder

  4 décembre 2013, par Zax

  I'm going through the working of H.263 video decoders parser in FFMPEG multimedia framework.

  What i know :

  Every video decoder needs a parser to fetch frames from a given input stream and once data related to a frame is obtained, it is sent to the decoder for decoding process.

  Every codec's parser needs to define a structure of type AVCodecParser. This structure has a function pointers :

  .parser_parse -> Points to the function which deals with the parsing functionality

  .parser_close -> points to a function that performs buffer deallocation.

  Taking the example of a video decoder H.264, it has a parser function as shown below :

  static int h263_parse(AVCodecParserContext *s,
  
                             AVCodecContext *avctx,
  
                             const uint8_t **poutbuf, int *poutbuf_size,
  
                             const uint8_t *buf, int buf_size)
  
  {
  
      ParseContext *pc = s->priv_data;
  
      int next;
  
  
  
      if (s->flags & PARSER_FLAG_COMPLETE_FRAMES) {
  
          next = buf_size;
  
      } else {
  
          next= ff_h263_find_frame_end(pc, buf, buf_size);
  
  
  
          if (ff_combine_frame(pc, next, &buf, &buf_size) < 0) {
  
              *poutbuf = NULL;
  
              *poutbuf_size = 0;
  
              return buf_size;
  
          }
  
      }
  
  
  
      *poutbuf = buf;
  
      *poutbuf_size = buf_size;
  
      return next;
  
  }

  Could anyone please explain, the parameters of the above function.

  According to me :

  poutbuf-> is a pointer that points to parsed frame data.
  
  
  
  poutbuf_size-> contains the size of the data.

  Are my above assumptions right ? Which parameter holds the input buffer data ? And what is the above parse function returning ? Also a brief explanation for the above code will be anyone who is referring to the post. Any information regarding the same will be really helpful.

  Thanks in advance.

  -Regards

• react vite ffmpeg how to resolve worker module returning 404

  19 novembre 2024, par pmkob

  I have imported the js, wasm, and worker modules into my project
https://unpkg.com/@ffmpeg/core@0.12.6/dist/esm/ffmpeg-core.js

  


  https://unpkg.com/@ffmpeg/core@0.12.6/dist/esm/ffmpeg-core.wasm
https://unpkg.com/@ffmpeg/core-mt@0.12.2/dist/esm/ffmpeg-core.worker.js

  


  and upon calling the function that the load is in, i get the error in the worker module
Request URL :
http://localhost:3000/node_modules/.vite/deps/worker.js?worker_file&type=module Status Code :
404 Not Found
Referrer Policy :
strict-origin-when-cross-origin

  


  In order to resolve this issue i have added these to my config and looked at similar issues with different threads https://github.com/ffmpegwasm/ffmpeg.wasm/issues/532
but with no luck. The load also never completes.

  


  CONFIG:
export default defineConfig(({ mode }) => ({
//other config stuff
  plugins: [react()],
  optimizeDeps: {
    exclude: ["@ffmpeg/ffmpeg", "@ffmpeg/util"]
  },
  server: {
    headers: {
      "Cross-Origin-Opener-Policy": "same-origin",
      "Cross-Origin-Embedder-Policy": "require-corp"
    }
  }
}));

FILE:
import { FFmpeg } from "@ffmpeg/ffmpeg";
import { fetchFile, toBlobURL } from "@ffmpeg/util";
 const ffmpeg = new FFmpeg();
    await ffmpeg.load({
      coreURL: await toBlobURL(
        `${importedURL}/ffmpeg/ffmpeg-core.js`,
        "text/javascript"
      ),
      wasmURL: await toBlobURL(
        `${importedURL}/ffmpeg/ffmpeg-core.wasm`,
        "application/wasm"
      ),
      workerURL: await toBlobURL(
        `${importedURL}/ffmpeg/ffmpeg-core.worker.js`,
        "text/javascript"
      )
    });