ffmpegwasm / ffmpegwasm/ffmpeg.wasm

ffmpeg.run() never completes/resolves when passed '-' for output file name

Ouverte
#191 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
C
Étoiles
17.8k
Forks
1.1k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

As the title says, if '-' is passed so that 'stdout' is sent through 'ffout' in the logger, then code afterwards will never be reached. The below example shows this. I am using 0.9.5 since versions above this gives the #124 error.
```



html, body {
margin: 0;
width: 100%;
height: 100%
}
body {
display: flex;
flex-direction: column;
align-items: center;
}




link



// NOTE: Version 0.9.6+ of ffmpeg.wasm does not like to work, using 0.9.5
const { createFFmpeg, fetchFile } = FFmpeg;
const ffmpeg = createFFmpeg({ log: false});

ffmpeg.setLogger(({ type, message }) => {
if(type != "ffout"){
console.log("[" + type + "]", message);
}
});

// Do the ffmpeg conversion using ffmpeg.wasm
const transcode = async ({ target: { files } }) => {
var input_file = files[0];
const { name } = input_file;
await ffmpeg.load();
ffmpeg.FS('writeFile', name, await fetchFile(input_file));

console.log("Running ffmpeg for VIDEO data...");
await ffmpeg.run('-i', name, '-f', 'image2pipe', '-vsync', '-1', '-vcodec', 'rawvideo', '-pix_fmt', 'bgr565be', '-f', 'rawvideo', '-');

console.log("DONE!");

```
In the above code, 'console.log("DONE!");' is never reached. However, if '-' is replaced with an actual output file name, like "output.mp4" then code after run() will be reached.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.