![]() ![]() So, is this really that useful? I do all my DAM in Lightroom and when I want more selective, layer-based edits, I move to Affinity. ![]() It doesn't do DAM (digital asset management) or pixel-level editing. Before I go any further, let me clarify what it doesn't do. It supports a vast array of file formats, allows simple image level manipulations, and has a powerful batch-processing engine. And my vote goes to XnView, an application built from the ground up to view images quickly - very quickly. So when it comes to image viewers, I'm after something that allows me to eyeball photos quickly, supports masses of file formats, has flexible batch-processing, and launches fast. " Simplicity is good, because it strips back to what you need to achieve a task, and in the software world, that often means speed. And on that score, Lightroom and Photoshop may just top the mark for overcomplicated bloatware. I'm not knocking their capabilities for which they are exemplary and market-leading, but if there is a software mantra I like to stick to, then it is "keep it simple. ![]() jpg images, where almost all file sizes are between 1M and 2M and almost all image sizes are either 4000×3000 pixels (if 4:3) or 4000×2248 pixels (if 16:9).Sometimes, I like to keep things simple. I also found a way to reproduce the problem quicker, that is using PAGE UP/PAGE DOWN keys instead of the mouse wheel (keep pressing one or the other), in a folder with > 1000. If, before closing anything, I give the chance for the processes to relax (that is, waiting a bit after going back and forth through images and before closing anything), the problem never occurs. I tried that (with "Read one image ahead" reactivated): closing the tab of the viewing image (not the browser) the problem persists and the application then simply hangs completely (mouse cursor over the application window remains in rotating waiting icon and the window itself turns light gray (inactive) – I have to kill the task). In my screenshot several posts above is the 1st button from the left, the one with some yellow folders on it. in this case, in order to open the browser, just click on the leftmost button on the toolbar. Useless in this context, because I keep "Closing last tab exits XnView" checked. Could be there is a thread (call, subroutine) that, when returning, no longer founds its parent initiator (because I closed it) and remains perplexed ? (just sitting there and consuming in vain 1 CPU core) The problem seems to occur when I hit ESC before the CPU relaxes, that is during the time XnView (probably) tries to catch some next image for caching. When I stop scrolling, the CPU lowers anywhere between 00 and 15. passing through several images in short time (which is the way I do often), the CPU goes as high as 97. When scrolling (with the mouse wheel, probably scroll is not the right word here) forward and backward very quick, i.e. db files there, no difference.īut, hmm, maybe here is a clue: I kept now open the task manager to see "live" the process behaviour. The user data is stored in C:\Users\secarica\AppData\Roaming\XnViewMP which is fully accessible regardless I am admin or not. Btw, are you admin on your laptop/storage where the data/config files are written? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |