-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
globalAlpha and image transparency #9
Comments
Actually I just noticed something related to animating images - I think the issue is related to when animating drawImage seems smoother / faster. |
Thank you for the feedback! Hi, globalAlpha should be supported. I'll take a look at that. Regarding performance: Anything done on the JS side tends to be fairly slow. I'll investigate the drawImage vs putImageData and get back to you. |
@pixelami You mention that you were able to get a canvas over video on the pi. |
@luismreis I am not able to get globalAlpha to work too. I have tried 1, 0.5, 0.1 and 0, but the subsequent drawImage still draws an opaque image. I am using NodeJS v0.10.15 and openvg-canvas v1.1.7 by the way (I installed openvg-canvas via npm). |
Hi, sorry for late response Then I can launch e.g. omxplayer and have my canvas rendering on top. A. On Wed, May 1, 2013 at 8:05 PM, Mark Losey [email protected] wrote:
|
Hello Luis, I am not able to get globalAlpha to work on images. Any chance you may have some insight on how to go about this? Thanks! Vic |
Hi, great work on this library !
The performance on the pi seems great running over video.
One question I have is regarding image alpha / globalAlpha. It seems that globalAlpha does not seem to work on images. I am able to grab the image data and iterate over the RGBA values and set the alpha like that - but this seems quite slow from within node at least.
What would you suggest as a better alternative ? And is it something you plan to add support for. i.e. globalAlpha for images.
Also animating images with alpha has a performance hit (actually it's still not too bad). but is there some optimisation you could suggest ?
The text was updated successfully, but these errors were encountered: