How feasible is to take the current and compile as WASM in order to allow for a browser version? Like how I took FFmpeg.js and made this tool, making an online version would be useful for those who don't know how to use console applications and/or cannot download executables.
Surely one roadblock would be performance since, even using WASM, audio decoding is not that fast in a browser. In the other hand, I mostly use alass by taking two subtitles and synchronizing one with the other, which is really fast. I think that at least this "mode of operation" could be implemented initially. FFmpeg.js could be used to decode audio for now, but I hope that in the future browsers support a streaming version of decodeAudioData.
How feasible is to take the current and compile as WASM in order to allow for a browser version? Like how I took FFmpeg.js and made this tool, making an online version would be useful for those who don't know how to use console applications and/or cannot download executables.
Surely one roadblock would be performance since, even using WASM, audio decoding is not that fast in a browser. In the other hand, I mostly use alass by taking two subtitles and synchronizing one with the other, which is really fast. I think that at least this "mode of operation" could be implemented initially. FFmpeg.js could be used to decode audio for now, but I hope that in the future browsers support a streaming version of decodeAudioData.