Closed pathammer closed 4 years ago
toDataUrl is Chrome's WebP encoder running, so it can't really be sped up.
On Wed, 8 Apr 2020, 11:44 AM Patrick Hammer, notifications@github.com wrote:
I'm seeing my animation loop go from 60fps to 15-8 fps when I begin recording. It runs a little bit faster when I set the quality lower. I'm trying to record a canvas approx 1280x720
My animation loop runs smoothly when I use the MediaReording API so I know my system can encode video fast enough.
When I profile the code, it's spending 70-80ms in toDataUrl()
Is there any trick to get this to run faster?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/thenickdude/webm-writer-js/issues/10, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOVDAYABXT5D4BKHMLIJDLRLO3EJANCNFSM4MDQFE2Q .
I'm seeing my animation loop go from 60fps to 15-8 fps when I begin recording. It runs a little bit faster when I set the quality lower. I'm trying to record a canvas approx 1280x720
My animation loop runs smoothly when I use the MediaReording API so I know my system can encode video fast enough.
When I profile the code, it's spending 70-80ms in toDataUrl()
Is there any trick to get this to run faster?