Screen tearing when using a Makerfabs Matouch 4.0" 480x480 parallel LCD screen about lovyangfx HOT 7 CLOSED

hi,

maybe try lower freq?

cfg.freq_write = 14000000;

16 bit parallel can give really good performances even at 2MHz

in order to find the sweet spot you can start with a low value, then increase by 1MHz until the tearing occurs

from lovyangfx.

Hi @tobozo!

maybe try lower freq?

I tried all the way down to 1 MHz, and worked my way all the way up to 14 MHz.

Below 5.6 MHz the picture wasn't displayed properly on the screen, and when I got to 5.6 MHz and above, the tearing effect was noticeable. So sadly, this didn't fix the issue for me.

from lovyangfx.

There is no easy way to prevent tearing because the timing of data transmission from the ESP32 is not synchronized with the operation of the LCD scan lines.

from lovyangfx.

There is no easy way to prevent tearing because the timing of data transmission from the ESP32 is not synchronized with the operation of the LCD scan lines.

Interesting. Is something that could be solved with a hardware modification or similar? I'm planning to design a custom PCB with and ESP32S3 and this exact screen. Could a custom design solve this?

FYI I have another Matouch screen at my desk. This 7.0" 480x800 model. I have not used it with the LovyanGFX library, but I managed to get it working using this esp-idf (v5.0) project. It uses the same ESP32S3 module, and with this exact project I didn't have any screen tearing at all. It did occasionally lag, but then the entire screen lagged without any tearing.
I thought this was because the double PSRAM frame buffering. But maybe it was just a coincidence?

I would much, much rather use this library and the Arduino framework instead of having to deal with the esp-idf directly.

from lovyangfx.

After some more research, it seems like the esp-idf project I mentioned earlier (right here) is doing some RTOS magic in order to synchronize to the vsync signal. Is this library able to do the same?

from lovyangfx.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from lovyangfx.

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

from lovyangfx.