Recherche avancée

Sur d’autres sites (2684)

• avfilter/af_astats : do not clear previous sample value

  26 février 2016, par Paul B Mahol

  avfilter/af_astats : do not clear previous sample value
  Should help when using reset=1 and metadata=1
  Signed-off-by : Paul B Mahol <onemda@gmail.com>
  

  • [DH] libavfilter/af_astats.c

• How to host a react.js ssr on vercel ?

  2 janvier 2024, par UltimateSheepConfusedAtCode

  I want to host a react.js server side rendering because of ffmpeg killing me with SharedArrayBuffer is not defined

  


  I've tried so many hosting service provider like firebase but now I want to host it to Vercel but I don't know how to make it works with react ssr. Can anyone help me ?

  


  When I run 'ssr' command in my machine it's work and ffmpeg is not throwing 'bad memory' or 'SharedArrayBuffer is not defined' but when I run it in vercel build command it stucks but the index.js/server.js is running I know because the main script is running and won't stop so the build is stuck but any solution ? I've search the problem but I guess nobody haven't asked this yet

  


  

  


  and this a code of package.json

  


  {
  "name": "ultimatesheep-vidreverse",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@babel/preset-env": "^7.18.10",
    "@babel/preset-react": "^7.18.6",
    "@babel/register": "^7.18.9",
    "@ffmpeg/core": "^0.11.0",
    "@ffmpeg/ffmpeg": "^0.11.0",
    "@testing-library/jest-dom": "^5.16.5",
    "@testing-library/react": "^13.3.0",
    "@testing-library/user-event": "^13.5.0",
    "bootstrap": "^5.2.0",
    "cors": "^2.8.5",
    "ignore-styles": "^5.0.1",
    "react": "^18.2.0",
    "react-bootstrap": "^2.5.0",
    "react-dom": "^18.2.0",
    "react-scripts": "5.0.1",
    "uuid": "^8.3.2",
    "web-vitals": "^2.1.4"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "ssr": "npm run build && node backend/index.js",
    "deploy": "npm run build && firebase deploy",
    "git" : "git add . && git commit -m 'ahawdaw' && git push -u origin main"
  },
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "externals": {
    "react": "React"
  },
  "description": "This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).",
  "main": "backend/index.js",
  "keywords": [],
  "author": "",
  "license": "ISC"
}


  


  

  


• random_seed : Rewrite the generic clock() based seed code

  11 juin 2012, par Michael Niedermayer

  random_seed : Rewrite the generic clock() based seed code
  The new code is faster and reuses the previous state in case of
  
  multiple calls.
  The previous code could easily end up in near-infinite loops,
  
  if the difference between two clock() calls never was larger than
  
  1.
  This makes fate-parseutils finish in finite time when run in wine,
  
  if CryptGenRandom isn’t available (which e.g. isn’t available if
  
  targeting Windows RT/metro).
  Patch originally by Michael Niedermayer but with some modifications
  
  by Martin Storsjö.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavutil/random_seed.c