Previews are displayed to the right by default (though you can change this using the View menu), and any image you select is opened in a new tab. The first tab is home to the browser, which you used to navigate through folders of images. XnView works like a cross between Windows Explorer and a web browser, with a tabbed interface that makes it easy to work with multiple files and tools. You'll quickly discover that XnView is more of an image toolkit than a viewer. However, sorry to say, the feature to change the font in the UI isn't something which is closely tied to the essence of the program, rather a corner case in some configuration - usually this thing is configured system-wide and not application wide - and perhaps that's why you didn't receive the desired attention.There's also TWAIN support for capturing scans of photos, a screen capture tool, and much more. You can look at the beginning of the 'General Support' forum and/or in tracker to see the progress. Only this year appeared several versions with quite a lot of improvements. And I would dare to say that it is quite active. Hope it will be more interest of improving XnViewMP since I saw that your post was back in 04-2013 and I was the only one to reply (1 year later). The other thing is that I prefer to use gnome/unity environment. It's slow when you have a bigger database of images. See for yourself here:įrancelipuzic wrote:Well I notice that here are not really interested of improving the app. a new SSD or any other hardware arrived, the collection changes size and/or shape etc.). Hence you can safely delete the thumbs database and the program will (re)generate on demand the thumbs without without forcing the user to wait in order to see the images.įinally, one doesn't need to have a correct initial setup for XnView, the flexibility of the database back-end allow for powerful maintenance and configuration actions during the photo collection life-cycle if the user decides it (eg. But if you are concerned to obtain the ultimate speed possible you can store smaller thumbnails and XnView will upscale them automatically if the user wants to.Īlso the XnView's thumbnail generation engine is faster than the human ability to scan the photos. And yes, you can have big thumbnails: 300x200 or even bigger - as you wish. Hence the database scales much more than in other DAMs which usually use JPEG compression for the thumbnails. The latest iteration of XnView MP uses a new compression algorithm for thumbs (WebP from Google) which gives for the same visual quality a 60-70% reduction in size. Also, the comparison isn't the total size of the images but how the metadata and thumbs is stored. We have here ~ 7 TB against XnView MP and till now it doesn't seem to have big problems with it. I don't say that this is a good thing, I just describe a phenomenon. All the mankind nowadays has gone photo crazy. And this not with 10.000 photos but with 100.000 - 700.000 or even more. The problem with databases is not the program's starting time. Aand, very important, it is worth wile to go completely through the set up and give ample place for the database. The only time it takes a bit longer is when you add a new folder/new pictures. I have a database of more than 265 GB and the whole starting procedere is just about 2 seconds. But you can also define smaller thumbnails. Arran wrote:Yes, digiKam can be a bit slow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |