Every video returns "Uncaught frame [x] has a different width.

[shaynasymons]

I am attempting to create a webm video from an array of images (webp). I am using the below code:
var webmBlob = Whammy.fromImageArray(frames, 24);
url = window.URL.createObjectURL(webmBlob);
Every time this code runs, it throws an error that 1 frame has a different width and the video fails to render.
I have set the width and height of the video source and the canvas both inline and in the css and don't know what else I can do.

[km147]

Did you get a solution for this, only we have been seeing the same issues. Updates to the meadiastream api seem to have killed it!

[KaranLala]

I faced the same issue - I realized that the issue is not really about the canvas width and height but the width and height of the canvas background (i.e. if it is transparent, it doesn't count). I'm not sure if this explanation is correct, but I got through the issue by adding this to the canvas before taking a picture

context.clearRect(0, 0, 1400, 1400);
context.fillStyle = 'white';
context.fillRect(0,0,1400,1400); //my canvas size was w = 1200 and height = 900

//draw rest of the pic 

[adkanojia]

Hi,

I encountered the same issue today while recording video using PixiJS animation.
I was creating a pen to share the issue here but just then I found out that the
'Uncaught frame [x] has a different height' issue was not on the pen. I tried the same example code on my local environment but issue was there.
Then I repaced the link to scripts on my local environment with that of cdn, and the recording worked just fine. I tried updating the scripts on local system but it didn't work. Though having the <script> tag link to the online resources worked like a charm.

What could be the issue?

Regards,
Akash Kanojia

[paarthenon]

I had this problem when I was using 1 as my quality setting. From what I understand eventually chrome started serving lossless webp and whammy hasn't been updated to support that so it barfed. I switched the quality setting to 0.9 which resolved the issue.

[harlos0517]

@paarthenon I get the very same problem and also fixed it with setting quality to 0.9
It's been almost 2 years, any solutions?