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
I see there's basically two issues it seems like with Whammy as a result of the passage of time -- (1) a modification to the webp code and (2) something with CreateObjectUrl (I think this has been superceded).
Has anyone successfully modified to work recently? If so, would you be open to sharing your updated .js?
Thank you,
Philip
The text was updated successfully, but these errors were encountered:
From what i've seen there are problems with the different WebP encodings.
Whammy works for files encode with VP8 (Lossy). Currently in Firefox 104.0.1 canvas are converted to VP8 and whammy works. However, when trying to process VP8X or VP8L (Lossless) it fails.
The VP8X problem can be solved with #70 (comment). Which removes the extra file headers. Resulting in VP8 or VP8L data.
In any case you end up with VP8L data (could be via VP8X) whammy will fail.
var frame_start = VP8.indexOf('\x9d\x01\x2a'); //A VP8 keyframe starts with the 0x9d012a header
Hi,
I see there's basically two issues it seems like with Whammy as a result of the passage of time -- (1) a modification to the webp code and (2) something with CreateObjectUrl (I think this has been superceded).
Has anyone successfully modified to work recently? If so, would you be open to sharing your updated .js?
Thank you,
Philip
The text was updated successfully, but these errors were encountered: