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
as shader input in conjunction with the usage of an Xflow operator results in an
Error: WebGL: texImage2D: invalid typed array type for given texture data type
Instead of directly passed the HTMLElement to WebGL, an ImageData object is retrieved from an internal canvas to fetch a frame of the video stream. This call returns an Uint8ClampedArray, which in turn is not valid as argument to be given to texImage2D (requires Uint8Array).
The text was updated successfully, but these errors were encountered:
Xflow uses Uint8ClampedArrays when web workers are involved, which is the right way to go about it I think. However WebGL doesn't accept these as data sources for tex2D, the suggested fix for this is to simply create a Uint8Array view on the underlying ArrayBuffer.
The above commit should cover all cases where a clamped array is used because the conversion is applied just before the data is sent to the gl context. With that I'll close this issue, if you still have this problem with the 4.9 release go ahead and reopen it.
Using the texture filter combination (linear/linear)
as shader input in conjunction with the usage of an Xflow operator results in an
Instead of directly passed the HTMLElement to WebGL, an ImageData object is retrieved from an internal canvas to fetch a frame of the video stream. This call returns an Uint8ClampedArray, which in turn is not valid as argument to be given to texImage2D (requires Uint8Array).
The text was updated successfully, but these errors were encountered: