Recherche avancée

Sur d’autres sites (9841)

• libavformat/mpegtsenc : allow to set service_type in sdt

  2 février 2015, par dhead666

  libavformat/mpegtsenc : allow to set service_type in sdt
  This adds an option to set the service type in mpegts as defined in ETSI 300 468.
  I added what I believe are the most useful service types as pre defined values,
  
  the others can be sent by using their hexdecimal form directly (e.g. -mpegts_service_type digital_radio, -mpegts_service_type 0x07).
  I’ve been using this patch in order to pipe internet radio stream (originally as HLS/m3u8) from ffmpeg to tvheadend,
  
  when the service type set right tvheadend recognize the mpegts stream as a radio channel.
  The patch in its original form was written by linuxstb from freenode’s hts channel which allowed me pushing it upstream.
  This close issue 4118.
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] doc/muxers.texi
  • [DH] libavformat/mpegtsenc.c

• FFMPEG av_read_frame() return an I/O error (-5) ?

  7 mars 2019, par vominhtien961476

  I’m using ffmpeg library to capture screen (desktop). Everything works fine when I run my app in debug/release mode. The I/O error comes when this app run in c# window service mode (win 10 OS). I googled but still don’t know why the error come. In the service mode there is no problem when connecting to some rtsp link (Camera) except desktop capture.

  AVInputFormat * pAVInputFormat = av_find_input_format("gdigrab"); 
  
  if (pAVInputFormat != NULL) 
  
  { 
  
     int err = avformat_open_input(&pFormatCtx, "desktop", pAVInputFormat, NULL); 
  
     if(err== 0) 
  
     { 
  
        err = av_read_frame(&pFormatCtx, &packet); 
  
        if (err < 0) 
  
        { 
  
            char errs[AV_ERROR_MAX_STRING_SIZE]; 
  
            av_make_error_string(errs, AV_ERROR_MAX_STRING_SIZE, err ); 
  
            String^ errStr = gcnew String(errs); 
  
            WriteLog("Error in function av_read_frame() return = " + errStr); 
  
            return -1; 
  
       } 
  
     } 
  
  }

  ---

• Trouble with Cross-Origin Headers : Stripe and ffmpeg Integration in Next.js

  7 février 2024, par Duke

  I'm using this excellent template from vercel as a base for my project :

  


  https://vercel.com/templates/next.js/subscription-starter


  


  I've used it for many projects and the Stripe integration works flawlessly. However for a new project I needed to incorporate ffmpeg which relies on SharedArrayBuffer :

  


  https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer


  


  So I need to set the appropriate HTTP response header which i've set in my next.config.js file as below :

  


        {
        source: '/(.*)',
        headers: [
          {
            key: 'Cross-Origin-Embedder-Policy',
            value: 'credentialless'
            // value: 'require-corp'
          },
          {
            key: 'Cross-Origin-Opener-Policy',
            value: 'same-origin-allow-popups'
          }
        ]
      }


  


  Now the issue is that settings these breaks Stripe. It blocks the request :

  


  https://js.stripe.com/v3/m-outer-3437aaddcdf6922d623e172c2d6f9278.html


  


  Which appearently loads more resources that are needed for the checkout session to function. The customer portal works but checkout doesn't. I've literally tired every possible permutation of headers with different values but in all cases either Stripe works but ffmepg doesn't (cause SharedArrayBuffer doesn't work) or vice versa. It's been a week and I've tired everything and can't find anything online that works. Not even ChatGPT can help which ironcelly asks me to contact Stripe customer support. I would highly appreciate if anyone could even point me in the right direction. I Thank you in advance good Sir/Maam.

  


  Note that Checkout works fine with just :

  


  key: 'Cross-Origin-Opener-Policy',
value: 'same-origin'


  


  Just Cross-Origin-Embedder-Policy breaks it