ffmpegwasm / ffmpegwasm/ffmpeg.wasm

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

Ouverte
#334 0 commentaires 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

**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.

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.