Advanced search

On other websites (8537)

• Unknown input format: 'x11grab'

  5 July 2017, by jjh

  guys:

  I have problems when i compile ffmpeg and run ffmpeg in linux.

  My environment:

  1: ubuntu 17.10_x64_bit(i don’t think the os version is the key)

  2: gcc (Ubuntu 6.3.0-19ubuntu1) 6.3.0 20170618

  3: ffmpeg open source code:3.2

  first, i download the source code from ffmpeg official site. I compile this project with there instructions：

  ./configure --prefix=/home/jjh/software/ffmpeg --enable-shared
  
  make
  
  make install

  and it worked without any error except some warning, then i run:

  ./ffmpeg -h

  i make sure that it works and output normally.

  but i want use ffmpeg to grabbing screen. so i use this construction(o):

  ffmpeg -f x11grab -video_size cif -framerate 25 -i :0.0 /tmp/out.mpg

  then output error:

  Unknown input format: 'x11grab'

  i want to re-compile this project with —enable-x11grab option, btw , so many solution tell me to to this. but when i add this option, i get some errors:

  Invalid option --enable-x11grab

  some people says that i should install some libs:

  libxfixes-dev
  
  sudo apt-get install libxext-dev

  so i installed these libs, but it always show this error. pls help me.

• avformat/hlsenc: fix default AES key file url with variant streams

  19 January 2020, by Bela Bodecs

  avformat/hlsenc: fix default AES key file url with variant streams
  Currently when hls_enc is active and there are multiple variant stream
  
  outputs, default key file url construction does not work, because it is
  
  based on the FormatContext' url field. But in case of multiple variant
  
  streams, it contains the variant m3u8 output playlist url that contains
  
  the %v placeholder. So the result key file url will hold the %v
  
  placeholder causing run time error message about "could not write the
  
  key file".
  
  This patch correct this behaviour, and use the master playlist url for
  
  constructing the output key file url when master playlist is vailable.
  Signed-off-by: Bela Bodecs <bodecsb@vivanet.hu>
  

  • [DH] libavformat/hlsenc.c

• @ffmpeg/ffmpeg: Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined

  19 May 2022, by Flobbinhood

  I have a small react app with a node.js backend (monorepo). The client is using @ffmpeg/ffmpeg, and all works fine locally, but when deployed to Heroku I'm getting the error ReferenceError: SharedArrayBuffer is not defined. This happens when I run ffmpeg.load(). Note that I am only using ffmpeg on the client in the React app.

  


  What I have done so far:

  


  

  • Ensured that my deployed app is using https

  


  • Added these lines in setupProxy.js in app.use (located in the client directory). See this answer for context

  


  


  response.setHeader('Cross-Origin-Opener-Policy', 'same-origin');
response.setHeader('Cross-Origin-Embedder-Policy', 'require-corp');


  


  

  • Registered for an origin trial with chrome. This actually worked, but I'd prefer a more permanent solution that works across browsers.

  


  • Tested debugging crossOriginIsolated, and verifying that it is true locally but false on my deployed site.

  


  


  It seems like something is wrong with my Cross-Origin config, or maybe it's just not being applied. Any help would be appreciated.