Well then have fun testing all versions. Only if it occurs comprehensibly from one version to the other, we can look at the changes. Too many changes and 5 years have passed since 4.1.
- Forums
- → Viewing Profile: Posts: joergm6
ATTENTION !!!
Due to a database corruption issue, we were forced to restore last-nights backup. This means all posts of Saterday Febuary 17th have been lost.Community Stats
- Group Senior Member
- Active Posts 31 ( per day)
- Profile Views 3,254
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
Contact Information
1
Neutral
User Tools
Friends
joergm6 hasn't added any friends yet.
Latest Visitors
Posts I've Made
In Topic: Slow zap on Vu+ Duo 4K
2 June 2019 - 13:33
In Topic: Slow zap on Vu+ Duo 4K
19 May 2019 - 11:41
Yes, that's the delay after a tap. Zap within the time restart the timer. Only when the time has expired does L4L begin to create the display.
If L4L is activated but nothing is configured, a black image is created anyway. This will take almost no time.
I also think that some I/O is time-critical and other I/O are not so great at the zap time. (File-I/O to /tmp)
In Topic: Slow zap on Vu+ Duo 4K
18 May 2019 - 23:12
lcd4linux certainly has no influence on the tuning. It seems that tuning is now time-critical and no other CPU activities are allowed. L4L uses the CPU for the creation. The problem didn't exist in the past.
L4L can be delayed in its work. Attempts by users have determined here approx. 700ms. "Global" - "other" - "Display Delay [ms]"
- Forums
- → Viewing Profile: Posts: joergm6