ffmpegwasm / ffmpegwasm/ffmpeg.wasm

Framehash muxer printing FFMPEG_END on the same line of the final output causing ffmpeg.run not resolving

Abierto
#334 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
C
Estrellas
17.8k
Forks
1.1k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**Describe the bug**

When running `-h muxer=framehash`, the output is as follow:

![image](https://user-images.githubusercontent.com/6388546/157165667-0c2ade35-e426-43d5-a5b5-4dc0c5fcff65.png)

I guess ffmpeg.wasm relies on `FFMPEG_END` signal for end state. However in this case somehow it's printed at the end of the output without a new line.

**To Reproduce**
Steps to reproduce the behavior:

Run the following code

```js
await this.ffmpeg.run("-h", "muxer=framehash");
console.log("Done")
```

**Expected behavior**

Promise should be resolved and next line of code runs.

**Screenshots**

See above

**Desktop (please complete the following information):**
- OS: Windows 11 Home
- Browser Microsoft Edge
- Version 99.0.1150.30 (Official build) (64-bit)

**Additional context**

Running the second command will also cause `ffmpeg.wasm can only run one command at a time` error.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.