ffmpegwasm / ffmpegwasm/ffmpeg.wasm
Framehash muxer printing FFMPEG_END on the same line of the final output causing ffmpeg.run not resolving
- Lingua principale
- C
- Stelle
- 17.8k
- Fork
- 1.1k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**Describe the bug**
When running `-h muxer=framehash`, the output is as follow:

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.
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.