Recherche avancée

Sur d’autres sites (8457)

• lavc/flacdsp : R-V V LPC16 function

  15 novembre 2023, par Rémi Denis-Courmont

  lavc/flacdsp : R-V V LPC16 function
  In this case, the inner loop computing the scalar product can be reduced
  
  to just one multiplication and one sum even with 128-bit vectors. The
  
  result is a lot simpler, but also brings more modest performance gains :
  flac_lpc_16_13_c :       15241.0
  
  flac_lpc_16_13_rvv_i32 : 11230.0
  
  flac_lpc_16_16_c :       17884.0
  
  flac_lpc_16_16_rvv_i32 : 12125.7
  
  flac_lpc_16_29_c :       27847.7
  
  flac_lpc_16_29_rvv_i32 : 10494.0
  
  flac_lpc_16_32_c :       30051.5
  
  flac_lpc_16_32_rvv_i32 : 10355.0
  

  • [DH] libavcodec/riscv/flacdsp_init.c
  • [DH] libavcodec/riscv/flacdsp_rvv.S

• Error : bad memory at /opt/render/project/src/node_modules/@ffmpeg.wasm/core-mt/dist/core.js:15:1

  1er octobre 2023, par James

  While deploying nodejs app on render.com i get this error Error : bad memory at /opt/render/project/src/node_modules/@ffmpeg.wasm/core-mt/dist/core.js:15:1.

  


  how to avoid this error i am using ffmpeg for merging audio with video.

  


  full error

  


   /opt/render/project/src/node_modules/@ffmpeg.wasm/core-mt/dist/core.js:15&#xA;Oct 1 04:53:37 PM  Error("bad memory");var Aa=z.buffer;e.HEAP8=A=new Int8Array(Aa);e.HEAP16=C=new Int16Array(Aa);e.HEAP32=E=new Int32Array(Aa);e.HEAPU8=B=new Uint8Array(Aa);e.HEAPU16=wa=new Uint16Array(Aa);e.HEAPU32=F=new Uint32Array(Aa);e.HEAPF32=xa=new Float32Array(Aa);e.HEAPF64=ya=new Float64Array(Aa);za=z.buffer.byteLength;var H,Ba=[],Ca=[],Da=[],Ea=[],Fa=[],Ga=!1,Ha=0;function Ia(){return noExitRuntime||0opt/render/project/src/node_modules/@ffmpeg.wasm/core-mt/dist/core.js:15:1&#xA;Oct 1 04:53:37 PM      at Function.<anonymous> (/opt/render/project/src/node_modules/@ffmpeg.wasm/main/dist/index.js:165:64)&#xA;Oct 1 04:53:37 PM      at Generator.next (<anonymous>)&#xA;Oct 1 04:53:37 PM      at fulfilled (/opt/render/project/src/node_modules/@ffmpeg.wasm/main/dist/index.js:28:22)&#xA;</anonymous></anonymous>

  


  my code

  


  import express from "express";
const router = express.Router();
import { readFile, writeFile } from "fs/promises";
import { FFmpeg } from "@ffmpeg.wasm/main";
import path from "path";

const currentDirectory = process.cwd();

const inputFilePath = path.join(currentDirectory, "video3.mp4");
const inputFilePath1 = path.join(currentDirectory, "wolf-howl-6310.mp3");
const outputFilePath = path.join(currentDirectory, "video3-2.mp4");

const ffmpeg = await FFmpeg.create({ core: "@ffmpeg.wasm/core-mt", log: true });

try {
  ffmpeg.fs.writeFile("/video3.mp4", await readFile(inputFilePath));
  ffmpeg.fs.writeFile("/wolf-howl-6310.mp3", await readFile(inputFilePath1));
  console.log(ffmpeg.version);
  await ffmpeg.run(
    "-i",
    "/wolf-howl-6310.mp3",
    "-i",
    "/video3.mp4",
    "-c",
    "copy",
    "-map",
    "0:a:0",
    "-map",
    "1:v:0",
    "/video3-2.mp4"
  );
  await writeFile(outputFilePath, ffmpeg.fs.readFile("/video3-2.mp4"));
  console.log("Conversion successful!");
} catch (error) {
  console.error("Error:", error);
}

router.post("/", (req, res) => {});
export { router as Merge };


  


• Why is the external executable I bundled with my azure function not being found at runtime, despite it being present in the expected location ?

  6 septembre 2023, par Cristian Camilo Garcia Barrera

  I have a group of Azure functions that I publish to a functions app. One of these is a blob triggered function, meant to extract thumbnails from videos uploaded to Azure storage, and to do so, uses ffmpeg.exe.

  


  I have published the project via Visual Studio, adding the executable in a directory in the root of the project. The relative path is exe/ffmpeg.exe. To include the executable in the published bundle I followed the instructions in this Microsoft Developer instructional video.

  


  After publication, If I enter the Kudu debug console for this function app, I can find the file under C:\home\site\wwwroot\exe\ffmpeg.exe, as expected. I can even use that absolute path to execute ffmpeg inside the Kudu console.

  


  This is the code I use to call the ffmpeg executable in the blob function :

  


  using (var process = new Process())
{
    process.StartInfo = new ProcessStartInfo
    {
        FileName = @"C:\home\site\wwwroot\exe\ffmpeg.exe",
        Arguments = $"-hide_banner -loglevel error -i {videoTempPath} -frames:v 1 {thumbTempPath}",
        UseShellExecute = false,
        RedirectStandardOutput = true,
        RedirectStandardError = true,
        CreateNoWindow = true
    };

    process.Start();
    await process.WaitForExitAsync();
}


  


  However, this does not work. I get the following error in the logs :

  


  


  An error occurred trying to start process 'C :\home\site\wwwroot\exe\ffmpeg.exe' with working directory 'C :\Program Files (x86)\SiteExtensions\Functions 4.25.2132bit. The system cannot find the file specified.

  


  


  And indeed my thumbnails are never created. How can I solve this, or why does it happen ?