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
Interesting project, I was wondering if you've tried to create an ffmpeg wasm encoder for CCapture.js
The problem with your current approach is that it gets double compressed: first through webm, then through mp4.
The other problem is that it's pretty unoptimised due to these two steps. If we can capture them in one go, which should be possible with ffmpeg, it's probably faster than webm-writer, as ffmpeg is wasm and webm-writer isn't.
I'm currently re-writing CCapture in Typescript, upgrading the dependencies and adding video + audio support, it's very old code.
Perhaps we can do this together?
The text was updated successfully, but these errors were encountered:
Hi - yeah that does sound like a better approach and it would solve some of the webm problems I'm having with firefox at the moment. Your project sounds really nice – to be honest this codebase is not really a high priority for me, I just need to it work well enough to support some of my other projects, so I probably won't be making any optimizations any time soon. But let me know when you finish your CCapture TS port, I'd like to check that out!
Interesting project, I was wondering if you've tried to create an ffmpeg wasm encoder for CCapture.js
The problem with your current approach is that it gets double compressed: first through webm, then through mp4.
The other problem is that it's pretty unoptimised due to these two steps. If we can capture them in one go, which should be possible with ffmpeg, it's probably faster than webm-writer, as ffmpeg is wasm and webm-writer isn't.
I'm currently re-writing CCapture in Typescript, upgrading the dependencies and adding video + audio support, it's very old code.
Perhaps we can do this together?
The text was updated successfully, but these errors were encountered: