Ev0

 

most likely. Now flashing the Dual without acceleration enabled, see if it makes any difference.

 

It doesn't. If anything it even looks marginally slower.

 

No idea if this info helps or not.

But I just put the OE-A drivers into OpenPli 9.0 and it didn't change anything.

 

I can only speak out of personal experience, the delay is long enough for me to doubt the box has seen the keypress (most HiSil boxes have notouriously bad AB's or IR receptors) and press the key again.

Yes I understand what you are saying (I have done it myself), but I use the Ultimo4K as my main box, all day everyday, so when using HiSi the slight delay is noticable.

However if I stop using the Ultimo4K for a day or 2, and use only a HiSi box (which I have done a few times in the last couple of years), you soon stop noticing the delay and it becomes "normal".

Then when I go back to using the Ultimo4K again, I notice it's much more responsive again.

But as said, most end users, they only have 1 or 2 boxes to use and usually they have the same chipset, so after the 1st day they will never notice the delay again.

 

I agree it is a workaround, but you have to decide which is better for the end user...

To have the infobar show instantly and then build in stages on the screen, or a slight delay before it appears complete.

The issue isn't just with this skin, it is every skin where AB is used.

True.

 

But I'd rather see something happening when I press a button, then press a button and nothing happens (so I press it again which can have nasty side effects). So from an end-user perspective, I don't like the work around.

 

I am a PHP developer, in web there is the same discussion, show the user the buildup of the page vs building the page and then slowing, every study shows most people like to see something happening, as waiting for something to happen always feels longer that it actually is.

 

I take your point, however a slight delay to show the infobar complete (as said in obh this is approx 0.5s), compared to loading a complete webpage is a big difference.

For developers that use all different hw all the time, we notice these slight delays when testing.

*Most* end users, only have 1 or 2 boxes and it seems they usually stick to the same / similar brands, which means they are far less likely to notice a 0.5s delay as it will have always been like that for them.

I didn't write there is a second time difference between HiSIl and BCM, I said the time to completion is about a second on the Dual 4K, both on ATV and on PLi.

 

My only point was that AB isn't fixed in OE-A, but the problem was hidden by delaying updating the FB so you don't see the effect.

I agree it is a workaround, but you have to decide which is better for the end user...

To have the infobar show instantly and then build in stages on the screen, or a slight delay before it appears complete.

The issue isn't just with this skin, it is every skin where AB is used.

 

Well I have tested Dual 4K, SF8008, Pulse4K, Multibox4K Pro, Sx88v2, H11s which are all HiSi boxes and none of them have the issue you have in PLi with this skin.

 

Like I added, OE-A has just worked around it by holding FB updates until the drawing is complete.  It hasn't fixed the slow processing, it just doesn't show it.

 

Sorry I missed your edit.

Yes you are correct, AB is an issue with HiSi, i've not tried this skin on ATV, but on OpenBh when compared to Vu+, there is a slight delay in showing the infobar, but I would say it is around 0.5s, not 1+ seconds.