BRT Community

Is the alias effect visible on your real hardware(LCD)?

Quote from: Prog_11 on December 11, 2019, 11:03:05 AM
Hello,

here is my display list. But in the heat of battle it seems I have not stored the version I have sent in the picture. As you can see, in the version below there is a gray dot in the middle.

CLEAR(1, 1, 1)
CMD_GRADIENT(17, 64, 0x0075AF, 230, 226, 0xA6F1FF)

COLOR_MASK(0, 0, 0, 1)
BLEND_FUNC(ONE, ONE_MINUS_SRC_ALPHA)
COLOR_A(255)
BEGIN(POINTS)            
POINT_SIZE(1000)
VERTEX2II(133, 176, 0, 0)

COLOR_MASK(1, 1, 1, 0)   
BLEND_FUNC(ONE_MINUS_DST_ALPHA, SRC_ALPHA)
BEGIN(RECTS)            
VERTEX2II(0, 0, 0, 0)         
VERTEX2II(239, 319, 0, 0)

COLOR_MASK(0, 0, 0, 1)
COLOR_A(128)
BLEND_FUNC(ZERO, ONE_MINUS_SRC_ALPHA)
BEGIN(POINTS)            
POINT_SIZE(500)
VERTEX2II(133, 177, 0, 0)


COLOR_MASK(1, 1, 1, 0)         
BLEND_FUNC(ONE_MINUS_DST_ALPHA, DST_ALPHA)
BEGIN(RECTS)            
VERTEX2II(0, 0, 0, 0)         
VERTEX2II(239, 319, 0, 0)

I tried the display list in ESE and found the effect is acceptable, although the alias effect can be seen if you zoomed in the picture.

For widget creating in dynamic way,  you may find the reference code in "Examples\Intermediate\ScrollPanel" under installation folder.  Open the project and see
the code in MainPage.c.

Tested your first failure case on my setup (Riverdi 5 inch 800x480) by using the flash file Rudolph sent.

Quote
0 1 2 3 4 5 6
7 0 0 0 0 0 0

The result is as picture and no failure at all.

Here is my EVE code:

Quote
CLEAR(1, 1, 1)

CMD_SETBITMAP(0x800000 | 128, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
BEGIN(BITMAPS)
VERTEX2II(0,0,0,0)

CMD_SETBITMAP(0x800000 | 214, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX2II(104,0,0,0)

CMD_SETBITMAP(0x800000 | 300, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX2II(208,0,0,0)


CMD_SETBITMAP(0x800000 | 386, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX2II(312,0,0,0)


CMD_SETBITMAP(0x800000 | 472, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX2II(416,0,0,0)

CMD_SETBITMAP(0x800000 | 558, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX_FORMAT(0)
VERTEX2F(520,0)


CMD_SETBITMAP(0x800000 | 644, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX_FORMAT(0)
VERTEX2F(624,0)

CMD_SETBITMAP(0x800000 | 730, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX_FORMAT(0)
VERTEX2F(0,104)

CMD_SETBITMAP(0x800000 | 128, COMPRESSED_RGBA_ASTC_8x8_KHR, 104, 104)
VERTEX2F(104,104)
VERTEX2F(208,104)
VERTEX2F(312,104)
VERTEX2F(416,104)
VERTEX2F(520,104)
VERTEX2F(624,104)

Tried to display 28 different ASTC8x8 images(each image is 100x100) : 7 from flash and 21 from RAM_G.  Found no issue
at my side, see the picture attached.

The code is as below:


CLEAR(1, 1, 1)
CMD_MEMSET(3155324, 0, 4)

CMD_FLASHREAD(0, 23360, 57792)
CMD_TEXT(101, 421, 31, 0, "1-7: Flash      8-28: RAM_G")

The first row 7 images are rendered from flash directly
---------------------------------------------------------------------------------------------------------
CMD_SETBITMAP(0x800000 | 128, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2II(0,0, 0,0)

CMD_SETBITMAP(0x800000 | 214, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2II(104,0, 0,0)

CMD_SETBITMAP(0x800000 | 300, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2II(208,0, 0,0)

CMD_SETBITMAP(0x800000 | 386, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2II(313, 0, 0, 0)

CMD_SETBITMAP(0x800000 | 472, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2II(417, 0, 0, 0)

CMD_SETBITMAP(0x800000 | 558, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(8368, 0)

CMD_SETBITMAP(0x800000 | 644, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(10016, 0)

The following 21 images are rendered from RAM_G , instead from Flash
---------------------------------------------------------------------------------------------------------

CMD_SETBITMAP(0x0, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(16, 1616)

CMD_SETBITMAP(2752, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(1632, 1616)

CMD_SETBITMAP(5504, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(3296, 1600)

CMD_SETBITMAP(8256, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(4976, 1600)

CMD_SETBITMAP(11008, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(6640, 1552)


CMD_SETBITMAP(13760, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(8336, 1584)

CMD_SETBITMAP(16512, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(9968, 1536)
=================================================

CMD_SETBITMAP(19264, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(0, 3248)

CMD_SETBITMAP(22016, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(1632, 3248)

CMD_SETBITMAP(24768, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(3280, 3248)

CMD_SETBITMAP(27520, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(4960, 3248)

CMD_SETBITMAP(30272, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(6640, 3248)

CMD_SETBITMAP(33024, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(8320, 3200)

CMD_SETBITMAP(35776, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(10000, 3200)

=================================================


CMD_SETBITMAP(38528, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(-32, 4864)

CMD_SETBITMAP(41280, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(1600, 4896)

CMD_SETBITMAP(44032, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(3264, 4864)

CMD_SETBITMAP(46784, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(4928, 4912)

CMD_SETBITMAP(49536, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(6592, 4864)

CMD_SETBITMAP(52288, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(8272, 4928)

CMD_SETBITMAP(55040, COMPRESSED_RGBA_ASTC_8x8_KHR, 100, 100)
BEGIN(BITMAPS)
VERTEX2F(9984, 4832)



Can you have a test on the flash read speed?  I guess the issue may be related to flash read throughput.

I tried at my side to display 35 images at one screen (9 images are different, each image is 100x100 in ASTC8x8 format).  All those 9 images
are stored in flash and rendered directly as your code. It has no such issue as you mentioned.

Sharing several tips :   
1).  Use a separate display list to set up bitmap handle:
     
      CMD_DLSTART
      BITMAP_HANDLE(x)
      CMD_SETBITMP(...)
      BITMAP_HANDLE(y)
      CMD_SETBITMP(...)
      CMD_DLSWAP
     
2) Draw the bitmap in another display list using the bitmap set up above.

I think rendering the image from RAM_G, instead of flash, shall be helpful.
You can use cmd_flashread to copy the ASTC data into RAM_G.

First, "CMD_FLASHDETACH â†' CMD_FLASHATTACH â†' CMD_FLASHERASE â†' CMD_FLASHFAST cycle"  is not feasible because after flash is erased , it is in Basic mode and there is no way to way to go back the full speed mode,  due to the lack of flash driver(known as blob).  The flash erase
will write every bytes of the whole chip into 0xFF. 
So you shall not run the cycle again and again.

Secondly,  at my side,  with your code logic, cmd_flashread can read the flash sector correctly
after cmd_flasherase is done.   The buffer is filled with 0xFF, not 0x55.

If you are not using the full unicode font characters,  you shall define your own set of characters to be used in your application.  It can minimize the size of font data.  Here is the screenshot of
EAB. Try to use ASTC8x8 or ASTC10x10 to see if the quality meets your needs and it saves the space too.

Hope it is helpful for you.

Forgot to mention one point: The cmd_inflate2 fetching data from flash only works correctly when flash is in full speed mode.  So remember to issue command cmd_flashfast before all other commands are sent.

To use the compressed assets in flash by cmd_inflate2, you need send cmd_flashsource to specify the address, which is offset from address 0.  In the image enclosed,you can see the number 4096
is the parameter of cmd_flashsource, which is the first asset after flash driver (unified.blob).

Check the image enclosed for details.

CLEAR(1, 1, 1)
CMD_FLASHSOURCE(4096)
CMD_INFLATE2(0, OPT_FLASH)

CMD_SETBITMAP(0, RGB565, 128,128)

BEGIN(BITMAPS)
VERTEX2II(104, 93, 0, 0)

From my opinion, that is a trade-off between the display list (RAM_DL utilization) and flash space. 
Compared to flash space, the RAM_DL can be reused across all the frames.
For instance, the GIF I enclosed here, is in 480x176 and converted into ASTC8x8 based animation object, which takes only 23K bytes flash space
for 8 frames, due to the common tile optimization.    However, saving those 8 frames in ASTC8x8 will take 260Kbytes flash space.
We can see in this use case,  with around 400 display list overhead,  flash space is saved around 220 Kbytes.

For no tiling option, it is better not to use animation converter. 
Instead, use the flash file generation to store the images consecutively frame by frame.

Like this:

"
Unified.blob
frame0.astc
frame1.astc
.......
framen.astc
"

In the display list,  change the bitmap source to display different frame from time to time.   It works well to me although it may take more spaces. 

Bitmap Handle 15 is a scratch handle used by Eve built-in widget. See programming guide 5.66 cmd_setscratch.

I suggest to use other bitmap handle , 0 to 14 and see if it works.

BT815/6 has supported it natively.