Recherche avancée

Sur d’autres sites (6532)

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

  19 mai 2022, par 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.

  


• Cannot Compile C Program That Uses a Library with GCC

  27 juillet 2018, par NetherGranite

  I am unable to compile a C project that uses a library called "FFmpeg" with a compiler called "GCC", and I believe it might be either because I don’t quite understand how #include works or because I am using the wrong compilation process.

  In a folder called Test, I have a file Test/test.c with the following contents :

  #include 
  
  #include 
  
  #include "FFmpeg/libavcodec/avcodec.h"

  The folder FFmpeg is located at Test/FFmpeg. When I try to compile this with GCC, I receive the following error :

  fatal error: libavutil/samplefmt.h: No such file or directory

  The file Test/FFmpeg/libavcodec/avcodec.h has the following code in it :

  #include "libavutil/samplefmt.h"
  
  #include "libavutil/attributes.h"
  
  #include "libavutil/avutil.h"
  
  ... //many more #include statements

  Is the issue here that I need to add "FFmpeg/" to all of these include statements ?

  If so, is there a way to automatically do this ? This library is enormous and probably has hundreds of these statements.

  If not, what should I be doing instead ? Should I attempt to compile the library by itself ? If so, how do I then include this compiled version of the library in my program ?

  ---

  Notes :

  • The command I am using to compile is gcc -c test.c.
  • I have GCC installed via MinGW.
  • I ultimately need to be able to compile this program to both a .dll and an .so.

  ---

  I apologize if any of the terminology I use here is incorrect or if my explanations are poor. I know almost nothing about compilation. Please let me know if I need to fill in more information.

• Imagick refresh

  25 septembre 2013, par Mikko Koppanen — Imagick

  After some hiatus I’ve been getting back on fixing bugs on Imagick and getting the code into more representable condition. This hiatus has been a result of busy work schedule and getting a new start-up running in Kuala Lumpur.

  While fixing a bug related to clone keyword I came across the following resource : http://www.rubblewebs.co.uk/imagick/. The page contains quite a nice collection of Imagick operations and is definitely worth checking out.

  On the other news, the development has been moved to Github. As I’ve been the most active developer of Imagick in the past years I decided to move the code to Github where rest of my projects are located : https://github.com/mkoppanen/imagick. For the past few days there has been quite a lot of development, mainly working on removing the excessive use of macros in the code to make things more readable and debuggable. This might be a good place to give thanks to Remi for fixing quite a lot of compile warnings and raising bugs regarding Fedora Packaging Policy. Most likely there will be a couple of beta releases in the near future.

  As mentioned in the previous post Windows builds are now available via http://windows.php.net and my builds provided here should be considered obsolete.