You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is very similar to the issue I mentioned here: #714 (which I found a workaround by using jpg instead of png). But the behavior are similar: there's no feedback at all (no error, no log, no progress), and the command after it aren't executed (so it's stuck).
As usual, I tested with simpler commands in isolation and they work perfectly: combining images into video, and combining audio with video. Combining them both are not working in FFmpeg.WASM, despite the command I run working perfectly in native FFmpeg.
The current workaround I have is to do it in two steps, generating the video first then adding the audio. This should mean there's some gap between the WASM implementation and the native one. While that's to be expected, I kinda curious why does the FFmpeg decided to just get "stuck" without any logs or error.
The text was updated successfully, but these errors were encountered:
ArsenicBismuth
changed the title
FFmpeg can't convert images to a video while also combining audio
FFmpeg can't combine images & audio to a video, hangs with no callback
Apr 3, 2024
This is very similar to the issue I mentioned here: #714 (which I found a workaround by using
jpg
instead ofpng
). But the behavior are similar: there's no feedback at all (no error, no log, no progress), and the command after it aren't executed (so it's stuck).As usual, I tested with simpler commands in isolation and they work perfectly: combining images into video, and combining audio with video. Combining them both are not working in FFmpeg.WASM, despite the command I run working perfectly in native FFmpeg.
The command I run is below:
The current workaround I have is to do it in two steps, generating the video first then adding the audio. This should mean there's some gap between the WASM implementation and the native one. While that's to be expected, I kinda curious why does the FFmpeg decided to just get "stuck" without any logs or error.
The text was updated successfully, but these errors were encountered: