Bandiview stalling when first opening images in folder "reading image information"

[keha...@hotmail.com]

Hi,

When I open an image in my downloads folder that has about 30k files in it, (a very messy mix of downloaded .zip .exe files and a bunch of stable diffusion generated image files among other things), this program stalls for like 20-30 seconds before it opens the image. Bandiview says that it's "reading image information", quoting stable diffusion (novelai) generated images so it's probably related to those. In task manager, I saw that my antivirus was reading something at like 300 MB/s while this was happening, and Bandiview was using only 9% cpu. The nvme drive was being used about 60%. Judging by the file transfer speed (it was very small files), the active protection of my antivirus must've been going through the files Bandiview was accessing.

After it has gone through all the files it works for a bit and is very speedy, but for example after restart or if it's been a long while I need to wait for it to read tags again.

This issue does not occur when opening the images in the folder with Honeyview 5.53. Just mentioning since I moved to Bandiview from it just now.

I am on Windows 10 and using F-Secure total as antivirus, on Bandiview pro 7.05. Any help? Is this just an incompatibility with how Bandiview reads the stable diffusion tags and F-secure, and could something be done about it?

[seyo IM]

Hello, this is Bandisoft.

BandiView opens 50,000 image files in less than a second and the size of the files makes little difference in the processing speed. Please check the following:

1. If you are using the "Smart Double Page" view mode, select other view modes (Press 0, 9, or 8.) and try again.
2. Refer to technical documentation from F‑Secure to configure your antivirus settings and add BandiView to its whitelist.

Thank you very much for using BandiView.

2024년 8월 19일 월요일 오후 10시 37분 46초 UTC+9에 keha...@hotmail.com님이 작성:

[keha...@hotmail.com]

Hi,

Thanks for responding! I was just using single image mode as per usual. I informed F-Secure that this is happening, and while testing the specifics of what was happening I found how to bypass it. In this case, I saw that F-Secure was observing the files it saw BandiView scanning for tags, not BandiView itself. Whitelisting BandiView itself did nothing in this case, and that led me to assign the folder with the images itself as "do not virus scan". After I did this, opening BandiView and reading image information in the folder ran in well under half a second, probably more like 100 - 200 milliseconds. However during testing I also found that if I disable F-Secure antivirus and protection features completely, a Windows process called Antimalware Service Executable chases BandiView around instead doing the same thing. This gives a similar result as F-Secure, using more cpu but moving less data, stalling "reading image information" for a while either way.

So in those terms, for now I get the best result from keeping F-Secure running and then adding the folder that contains the images to the "do not virus scan" bypass list.