Has anybody seen this effect?

Yes,

If you remember i had reported 2 problems on my uhd8000.
One was a random freeze on boot.
The other was random, non repeatable, that i considered decoding error, like the image was sent without having time to be decoded.

It was only happening with ai pq on, with high bitrate uhd (80 90+ mbps).

At the time i sorted out the fact it coukd be a video file corrupted and even a bad memory as replaying the filé from the zidoo memory was never replaying the error.

It was super rare and only occurrd for me with both conditions met (high bitrate + ai pq on). I suspected at that time that load was too high in thise conditions and was wondering if it was a known bug but answer was no. It was in previous firmware

Because of the freeze booting problem that i was able to caught multiple time on video, i returned the unit. Zidoo answered to my retailler that the motherboard needed to be changed.

 

Never use AI

 

Neither do I - This has nothing to do with the AI settings.

So I assume you haven't seen it?

As I said in the first post I'm interested in reports from people who haven't seen it as much as those that have.

 

I was suggesting NO ONE should be using AI not speaking about my personal use since the poster above me said he used it, lol. Much like CEC.

However to answer your question, no never seen that effect on the Zidoo. I have seen that on poorly encoded files but only on my PC.

good luck figuring it out.

 

I should have been as accurate as i was on my original post.

On that post, i explained that it was not due to corrupted file, nor corruption happening during smb, nor corrupted memory on zidoo, because i was able to replay the same exact spot where it occured from zidoo memory (zidoo wasnt reloading the corresponding video using smb, but it was in previous firmware as they changed how zidoo memory is handled now).

It also prove that it wasnt AI algorithm reproductible, so the way AI treated the frame was probably not the reason, because it would have treated the frame as badly the second time which was not the case. But ofc, if the AI PQ algorithm wasnt predictive then it could have matter mentionning it.

The other reason i mentionned AI is because i suspected it could be related to a process on the zidoo that wouldnt have had enough cpu time to do what it needed to to and sent the image half baked exactly like the screenshots in first post. I forgot to mention that the file was read by zidoo using SMB protocol, as i know this protocol can be demanding on zidoo load. (not on my server i dont go over like 5%cpu ram is ECC, traffic was monitored and non problematic at the time).

thats all i can add to investigate the problem, as i no longer own the UHD8000 having returned it per zidoo request for a motherboard exchnage, due to another problem of random freeze at startup, that i mention in case my testitomy on this problem would have 0 weight because my zidoo seemed to suffer from other problem.

I also checked the cpu load on zidoo but it was almost 100% all the time so no idea if the tool was even accurzate, even though i was suspecting a zidoo process load to be the reason for the problem.

 

I regularly experience this sort of thing.

 

I've just experienced this pixelated bug (once only of 2secs) during a TV episode in mkv and it was followed but missing audio after stop/start. No repeatable.

 

I have observed this effect (pixel error) twice in the last week on 2160p SDR WEB-DL files. Each time, I rewinded 15 seconds, but the error didn't reoccur.

 

Not seen this gladly

 

Great thank you - as I say, negative responses are as important as positive ones.

 

I saw something like that on a Dune with VC1 codec.