Text Only | Text with Attachments

QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: Raven_Singularity on April 09, 2019, 09:34:06 pm

Title: Question about transparent images
Post by: Raven_Singularity on April 09, 2019, 09:34:06 pm
When using _SETALPHA on a transparent PNG image, it sets the pixel transparency for everything, not just the originally non-transparent pixels.

How do I handle fading in a transparent PNG image so that the formerly-transparent background does not become solid black?

Is there a function to create a mask of the image beforehand, or how should I handle this?

Thanks for any tips!
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 10, 2019, 10:34:33 pm
So I have dug through the documentation and it doesn't seem that QB64 supports changing the opacity of PNGs that already include opacity information.

_SETALPHA changes all pixels in the image, or only pixels of a certain colour.  There is no way to make _SETALPHA take already partially-opaque pixels of the PNG and then apply an opacity to that.

It seems the only way that QB64 supports translucent PNGs is with 1-bit transparency, pixel on or off.  That would be easy enough to create a colour mask for in QB64, but it will look much uglier than a PNG with 256 levels of translucency.

Another way I can see to deal with already translucent PNGs is to _COPYIMAGE the original image, then manually go over the entire image pixel by pixel and update the alpha values manually, taking into account the starting pixel's translucency value.  I doubt this would work fast enough to use in realtime at 1080p/60fps when fading a few translucent images in and out.

The other way I can see possibly working is to use _COPYIMAGE on the original image, then use _SETALPHA on the range that includes all colours more than 50% opaque, while turning colours less than 50% opaque fully transparent.  This way might work fast enough, but it would still have the issue that partially translucent pixels in the original image would not be honoured, thus losing all the beautiful antialised edges of the original image.

Is there really no way to adjust the opacity of an already-partially-translucent image in QB64?

If not, I think this is a really important feature.  As it stands now _SETALPHA is only relevant for 1-bit transparency, which is frankly silly -- _SETALPHA is a command that lets you assign a full 8bits of opacity, but it can't handle images which already contain partially-opaque pixels.  This is saddening.  :-/
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 10, 2019, 10:46:02 pm
Try _SETALPHA to set all pixels, then _CLEARCOLOR to clear certain ones. Should give the desired transparency.
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 10, 2019, 10:51:17 pm
Quote from: FellippeHeitor on April 10, 2019, 10:46:02 pm
Try _SETALPHA to set all pixels, then _CLEARCOLOR to clear certain ones. Should give the desired transparency.

I don't think you're understanding the issue.  My image has no colour for 100% transparent, it has partially translucent pixels to begin with.  If I tell it to _SETALPHA 128 I would expect it to make the pixels that were 50% opaque to become 25% opaque, but it ignores the pre-existing translucency values of the pixels entirely.  There is no combination of _SETALPHA and _CLEARCOLOR that respect the pre-existing translucent pixels of my original image.
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 10, 2019, 10:53:52 pm
I don't think you're understanding my suggestion.

Is pixel (0, 0) a transparent one in your image? Keep it in mind for reference.

Use _SETALPHA in your image and now pixel (0, 0) is not as transparent anymore. A shade of grey with some alpha maybe? Good.

Now call _CLEARCOLOR and aim at the color that POINT will read at (0, 0).

I didn't test it, but in theory it sounds like it should work.
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 10, 2019, 10:58:24 pm
And voilà, it works:

Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(800, 600, 32)
  2. logo& = _LOADIMAGE("forumtitle.png", 32)
  3. IF logo& = -1 THEN PRINT "Image not found": END
  4.  
  5. _SETALPHA 100, , logo&
  6. _SOURCE logo&
  7. _CLEARCOLOR POINT(0, 0), logo&
  9.  
  11.     _PUTIMAGE (x, y), logo&
  12.     x = x + 5
  13.     y = y + 5
  14.     _DISPLAY
  15.     _LIMIT 5
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 10, 2019, 10:59:45 pm
May not be perfect and end up clearing more than the intended pixels, but it is a workaround nonetheless.
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 10, 2019, 11:19:37 pm
It doesn't work at all, because you aren't understanding the issue.  The issue is partially opaque pixels in the original image.

Partially translucent images are a staple of video gaming, so it would be nice to have support for these images in QB64.


I have attached an image "rainbow.png" which will show you the issue first-hand.

I have attached "incorrect.jpg" which is _SETALPHA at 80% opacity, and "correct.jpg" for how this translucent image would look if it were actually made 80% opaque from the original image which contained partially-translucent pixels.
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 10, 2019, 11:38:42 pm
I see. And the alpha level will be changing throughout execution?

Edit: ah, yes I see it.

Quote
fading a few translucent images in and out
.
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 10, 2019, 11:40:55 pm
No built-in solution exists as of yet then.
Title: Re: Question about transparent images
Post by: Ashish on April 11, 2019, 12:25:33 am
Is this what you want?
Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(600, 600, 32)
  2.  
  3. img& = _LOADIMAGE("rainbow.png")
  4.  
  5. FOR i = 0 TO 255
  6.     CLS
  7.     addAlpha2Img img&, -1 'subtract 1 alpha value from each pixel.
  8.     _PUTIMAGE (0, 0)-(600, 600), img&
  9.     _LIMIT 40
  10.     _DISPLAY
  12.  
  13.  
  14. SUB addAlpha2Img (img&, alpha AS INTEGER)
  15.     IF img& >= -1 THEN EXIT SUB
  16.     DIM buffer AS _MEM, o AS _OFFSET, o2 AS _OFFSET
  19.     buffer = _MEMIMAGE(img&)
  20.     o = buffer.OFFSET
  21.     o2 = o + _WIDTH(img&) * _HEIGHT(img&) * 4
  22.     DO
  23.         b = _MEMGET(buffer, o + 3, _UNSIGNED _BYTE)
  24.         IF (b + alpha) > 0 AND (b + alpha) < 255 THEN
  25.             _MEMPUT buffer, o + 3, (b + alpha) AS _UNSIGNED _BYTE
  26.         END IF
  27.         o = o + 4
  28.     LOOP UNTIL o = o2
  29.     _MEMFREE buffer
  32.  
Title: Re: Question about transparent images
Post by: Pete on April 11, 2019, 12:34:38 am
Well that's a neat effect. If I use _INSTRREV() in the code, will it reappear?

Pete
Title: Re: Question about transparent images
Post by: Ashish on April 11, 2019, 12:36:43 am
Quote from: Pete on April 11, 2019, 12:34:38 am
Well that's a neat effect. If I use _INSTRREV() in the code, will it reappear?

Pete
What is the use of _instrrev() in this code Pete?
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 11, 2019, 12:47:07 am
Quote from: FellippeHeitor on April 10, 2019, 11:40:55 pm
No built-in solution exists as of yet then.

Is there an official place to submit feature requests?


I am working on a keyframe/tweening animation library which supports easing in/out on all transitions.  It will eventually be released to the public.  It is already quite functional.

I was working on Obj_Opacity(), but it seems this will only work in realtime if the original image uses only 1bit transparency.  I will attempt to do the opacity adjustment loop manually pixel-by-pixel to see how the performance is, but I suspect it will lag the rendering too much, which is currently very smooth.


@Ashish:
I will look at that code and let you know.  What I am going for is having taking an image handle and drawing it onto the main screen with an opacity applied to it, which affects all pixels correctly, including semi-translucent pixels in the original image.  The opacity is being applied every frame update as a percentage of opaque, 0.000 to 1.000.
Title: Re: Question about transparent images
Post by: Pete on April 11, 2019, 12:47:31 am
The use? Ah, humor. _INSTRREV() is the new reverse function to INSTR(). So, I thought if I inserted that at the end of your code, I could get the .png to reappear. :D

Pete
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 11, 2019, 12:50:42 am
Quote from: Pete on April 11, 2019, 12:47:31 am
The use? Ah, humor. _INSTRREV() is the new reverse function to INSTR(). So, I thought if I inserted that at the end of your code, I could get the .png to reappear. :D

Pete

Lol!
Title: Re: Question about transparent images
Post by: FellippeHeitor on April 11, 2019, 12:53:05 am
Quote
Is there an official place to submit feature requests?

Yes. Both for feature requests and bug reports: https://github.com/Galleondragon/qb64/issues
Title: Re: Question about transparent images
Post by: Ashish on April 11, 2019, 12:54:14 am
Quote from: Pete on April 11, 2019, 12:47:31 am
The use? Ah, humor. _INSTRREV() is the new reverse function to INSTR(). So, I thought if I inserted that at the end of your code, I could get the .png to reappear. :D

Pete
Oh man! You are always happy and want to make everyone laugh with your jokes.
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 11, 2019, 02:28:25 am
Quote from: Ashish on April 11, 2019, 12:25:33 am
Is this what you want?
Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(600, 600, 32)
  2.  
  3. img& = _LOADIMAGE("rainbow.png")
  4.  
  5. FOR i = 0 TO 255
  6.     CLS
  7.     addAlpha2Img img&, -1 'subtract 1 alpha value from each pixel.
  8.     _PUTIMAGE (0, 0)-(600, 600), img&
  9.     _LIMIT 40
  10.     _DISPLAY
  12.  
  13.  
  14. SUB addAlpha2Img (img&, alpha AS INTEGER)
  15.     IF img& >= -1 THEN EXIT SUB
  16.     DIM buffer AS _MEM, o AS _OFFSET, o2 AS _OFFSET
  19.     buffer = _MEMIMAGE(img&)
  20.     o = buffer.OFFSET
  21.     o2 = o + _WIDTH(img&) * _HEIGHT(img&) * 4
  22.     DO
  23.         b = _MEMGET(buffer, o + 3, _UNSIGNED _BYTE)
  24.         IF (b + alpha) > 0 AND (b + alpha) < 255 THEN
  25.             _MEMPUT buffer, o + 3, (b + alpha) AS _UNSIGNED _BYTE
  26.         END IF
  27.         o = o + 4
  28.     LOOP UNTIL o = o2
  29.     _MEMFREE buffer
  32.  


That code does do what I wanted.  I will go through your code later, and work out what exactly it's doing.

It also seems to be going pretty fast when I tried it over a background image, appears to maintain 60FPS without issue at 600x600.

Thank you kindly for your help.
Title: Re: Question about transparent images
Post by: Pete on April 11, 2019, 02:34:10 am
While you fiddle with it, disable (REM out) the  $CHECKING lines.  $CHECKING:OFF makes it run faster, but it sacrifices the debugging messages. Only use  $CHECKING:OFF when you have debugged, ready to use code.

Would you believe Ashish is only 16? If you have time, search for some of his 3-D Open-GL projects on the boards.

Pete
Title: Re: Question about transparent images
Post by: Raven_Singularity on April 11, 2019, 02:44:40 am
By debugging messages, do you mean things like error messages with line numbers, or what exactly?
Title: Re: Question about transparent images
Post by: Pete on April 11, 2019, 01:22:23 pm
Best described here: http://www.qb64.org/wiki/$CHECKING
Title: Re: Question about transparent images
Post by: Jack002 on April 19, 2019, 10:38:29 am
Quote from: Pete on April 11, 2019, 12:47:31 am
The use? Ah, humor. _INSTRREV() is the new reverse function to INSTR(). So, I thought if I inserted that at the end of your code, I could get the .png to reappear. :D

Pete
If I do a DIR listing with INSTRREV will I be able to see deleted files?
:D
Text Only | Text with Attachments