video preview overlay issue

[izildur]

Hello,

First of all, thank you for this tool. I purchased a lifetime license yesterday and I really think it is the definitive windows explorer.

I probably found a bug in video preview overlay. On my laptop all is working perfectly, but on my desktop I have the following issue:

When I start XYplorer and click on the video, I can see it is starting (sound is working) but nothing is displayed in the preview pane

1.png (66.74 KiB) Viewed 2250 times

I have a similar behavior in the info panel if I close the preview pane

2.png (83.83 KiB) Viewed 2250 times

If I move to raw view (working) and go back to preview, it looks the display is not refreshed

3.png (95.19 KiB) Viewed 2250 times

I order to get the correct behavior I have to start a second instance of XYplorer. In this one preview pane is working

4.png (176.28 KiB) Viewed 2250 times

And same for info panel preview

5.png (315.81 KiB) Viewed 2250 times

I was thinking initially that is was a codec problem and tested a lot of things but, after a a long investigation, it looks to be related to the nvidia video driver. I tested 3 latest driver versions and it the the same, except when I totally uninstall it, just before the reboot (I think windows is using a generic driver at this point). The version I'm currently using is 398.36. My system is a windows 10 Enterprise x64 v1803 fully patched.
I also tried to install XYplorer beta v19.10.0101, it has the same issue.

Do you have any idea about what is causing this issue ? Thank you very much.
Best regards,

[admin]

Hi and sorry for the late reply!

No idea what's causing this. I assume it is still happening? Is it only MOV files?

[jupe]

Slightly off topic, so sorry to interject but since the OP has already posted screenshots here that can be compared with mine, I thought here was a good place to ask, does anyone else see the alignment issues I have pointed out in the below screenshot, I am running Sergoe UI 9 for B&L @ 120 DPI if that is relevant.

xy_alignment-clipboard-28_07_2018.png (5.09 KiB) Viewed 2169 times

[admin]

Slightly off topic, so sorry to interject but since the OP has already posted screenshots here that can be compared with mine, I thought here was a good place to ask, does anyone else see the alignment issues I have pointed out in the below screenshot, I am running Sergoe UI 9 for B&L @ 120 DPI if that is relevant.
xy_alignment-clipboard-28_07_2018.png

Yes, these are some of the few elements that cannot scale. One day I will have to redesign this panel.

[izildur]

Hello,

Thank you for your reply.
I confirm it is still happening, even in version 19.10.0200. This can be reproduced with any video file (size and extension doesn't matter), it could be avi, mov, mp4 ...

I tested it on different computers each time with an NVIDIA card as primary device (GeForce 9XX or 10XX) and always reproduced the problem. With a laptop using an intel as primary GPU and NVDIA as secondary, all is fine.

I also tested all nvidia drivers:
windows update nvidia driver is 391.25 -> OK
v 391.35 (from nvidia site) -> OK
v 397.64 -> not working
v 397.93 -> not working
v 398.11 -> not working
v 398.36 -> not working
v 398.82 -> not working

Best regards,

[RalphM]

So you clearly found the culprit to be the Nvidia drivers from v397.64 onward but still seem to expect XY to fix it???

[izildur]

Hello RalphM,

Indeed NVIDIA is the problem. I'm not really expecting a resolution and can live with it, but it could also happens for some other cards manufacturer and it could be interresting to understandand the issue.
The strange thing is that if you start 2 instances of XY, the second has the correct behavior. This make me thing that something is happening when the overlay control is created. I don't have details about the source code and if I open a ticket to NVIDIA will not be able to provide all information.

Cheers,

[admin]

The strange thing is that if you start 2 instances of XY, the second has the correct behavior.

This is really strange. The reason might be that the driver uses hardware acceleration which is probably only possible in one instance (the 1st instance), and it has a bug somewhere in that module. You might be able to turn off hardware acceleration (it can by disabled somewhere in Windows AFAIK) and thereby work around that bug.