11/11/2023 0 Comments Xnview mp t vs ctrl t![]() ![]() Unfortunately a quality setting of 85% is not doing the same in all the programs which also can lead to this kind of deviations.Ĭlick to expand.The viewing of one file with various viewers which showed in my opinion some quite large differences, then capturing those differences from my screen was what I was commenting on, that is all.Ĭonsistency of screen capture was important in attempting to show the differences, one file for display in each viewer and one capture option (Greenshot - ) for all the viewers. Many of them have options for JPG export like the quality setting (in the end defining the compression level). It is worthwhile playing around with the display and processing options in the program setup a bit to get rid of this kind of deviations.Īnother source of trouble is saving JPG's from different programs. but as I said, this was just an observation - no scientific test behind it ☺. However, although they are mostly found somewhere among the picture processing preferences, they might have an impact on the way pictures are displayed as well. Some of the viewers offer different options for the algorithms to be used for resizing pictures including resampling them. Interestingly this not only shows an effect for wapp papers and the screen saver slide shows, but also for the photo viewing itself.Ĭoming back to the display quality of viewers there is one thing I haven't tested recently, but I remember discovering when dealing with my business graphics exported as JPG's in the past. This can be changed by an additional entry in the registry that has to be added manually. with XnViewMP.Īnother thing I had to learn is that as a default Windows is importing JPG's for display with 80% quality setting - officially in order to save loading time - which IMHO is a joke with the hardware we have today. This can be done easily with batch cvonversion e.g. ![]() The solution is to store these JPG's separately without an integrated color profile. iIf you save JPG's with integrated color profile and use these JPG's for this you might have severy, ugly color bending caused by this integrated profile, because Windows can'T cope with it. Problems might occur if you use Windows' internal things like the photo viewer or using JPG's of your photos as wallpaper or background slide show. After getting these settings right jumping back and forward between different software packages isn't really an issue. It is not so bad as long as you use applications that allow settings for color management. Something I can confirm that color management under Windows can make life a bit complicated sometimes. Differences between the two work places were minimal, considering that I use two pairs of differetn monitor models that are both calibrated, but used under differetn lighting conditions. ![]() With my setup I could not see visible differences between JPG's using the programs I mentioned above. When looking at processed photos I was more concerned about differences between what I see in the raw processor and the viewer rather then between dfferent viewers, so I will definitely have a closer look with my equipment, which currently is a DELL Precision M6800 with a 4GB AMD Graphics and connected to either two DELL UP2716D or two DELL U2413 - depending on the location where I am working -, in both cases connected via miniDP through a docking station. On the viewer side used IrfanView and then moved to XNViewMP because of its much better organizing and meta data management functions as well as the multi-platform availability (beside photos I have to juggle big quantities of graphics that I manage by using key words). I have been using several raw processing packages in the past (View NX2, Capture NX2, vIew NX-i, Capture NX-D, Capture One) and am now using DxO PhotoLab 4. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |