XnView

Store Thumbnails database in photos folder

helmut — Thu Aug 28, 2008 4:35 pm

Author: helmut

Posted: Thu Aug 28, 2008 4:35 pm

JohnFredC wrote:

We have spend a lot of time on the XnView GUI design in this forum. Because of that XnView has extremely good usability and looks great! ...

I don't want to start a big (and more or less useless) discussion, here, but just some thoughts on this statement:

From my point of view, the focus in the forum in the recent past was much on GUI design and usability. But comparatively few of those things have made it into the recent XnView versions. So there's still quite a lot on Pierre's ToDo list and to improve, see topic Core functionality, formats, and usability.

But I agree:
The corner stones of XnView MP are set right now, so it's important to discuss basic and general ideas like the management and handling of metadata, now, and implement it in XnView MP, soon. So for a while it would be good if we could progress the ideas and discussion regarding management and handling of meta data and Pierre would try to join those discussions and implement it in XnView MP. Changing architecture and basic ideas later will be much more effort (or even impossible) and people might loose their metadata if a new concept was introduced later.

XnV crashes on XP when launched from the zip install

Anonymous — Thu Aug 28, 2008 4:30 pm

Author: Anonymous

Posted: Thu Aug 28, 2008 4:30 pm

xnview wrote:

Try to drag&drop a picture on xnview's icon?

It works. Launching xnview.exe seems to work also now. Curious...it did not work for days, and now it works...

Thanks for your answer, I'll post again if it crashes again.

hidden images

Irving — Thu Aug 28, 2008 3:26 pm

Author: Irving

Posted: Thu Aug 28, 2008 3:26 pm

If you open a hidden image in a hidden folder, XnView crashes upon loading.

Copy the hidden image to a normally viewable folder and everything's fine, though.

While I'm at it:

If you open an image in a certain folder, resize it or whatever and save to another folder, when you hit Next Image it begins reading the folder you saved to, not the one you're working in.

If you change an image the original thumbnail in the My Pictures folder remains. For instance, you change an image to grey but the color thumbnail stays.

When viewing full screen, closing with the Escape button works fine, but a right click and Close causes a crash.

Please please PLEASE bring back the Gamma/Brightness box that was in 1.31 and 1.74! The new one is clunky and real time viewing of adjustments are slow.

Common graphic formats

Troken — Thu Aug 28, 2008 3:25 pm

Author: Troken

Posted: Thu Aug 28, 2008 3:25 pm

Reading a little about formats on the web, this sentence pretty much says it all (source: Wikipedia):

Quote:

PNG was designed for transferring images on the Internet, not professional graphics, and so does not support other color spaces (such as CMYK).

But after reading more about PNG, I think I'll go from JPG to PNG when it comes to web and screen imagery. Why are all images on the internet still JPG?

A few Mezich-like icons

JohnFredC — Thu Aug 28, 2008 3:08 pm

Author: JohnFredC

Posted: Thu Aug 28, 2008 3:08 pm

Hi RGBA

No... no NLP, that's new to me. Basic CHI stuff + Cognitive psychology + minor background in linguistics.

We're in agreement about "too many" eyes. That could look a little... unsettling. On the other hand, there is only one "official" eye icon currently and one or two more might not "look" so ocular on the toolbar.

I can't imagine that an eye per se as a compoment of an icon would be proprietary. What trademarks are you thinking of?

How to reduce an image's file size?

Aokromes — Thu Aug 28, 2008 9:39 am

Author: Aokromes

Posted: Thu Aug 28, 2008 9:39 am

You forgot the "Use a external compresor" like zip, rar, 7zip etc.

Fenix/Bennu Graphics Formats

splinter — Thu Aug 28, 2008 5:45 am

Author: splinter

Posted: Thu Aug 28, 2008 5:45 am

Hi!
Let me introduce me... I was maintain of Fenix proyect in last years, and now continue it with the name of "Bennu Game Development" (http://forum.bennugd.org/)... I too made some questions in this forum time ago, zx (.scr) and other creation plugin problems...
This post is only for thanks you by Fenix/Bennu graphics formats supports...
Soon I'll include new graphics formats, and I'll share this formats info with you, and I'll thanks you for include support for they in the future versions of your work...
Greetings
Splinter

PS: Sorry for my bad english.

Z80 Screendump(.scr) association

Anonymous — Thu Aug 28, 2008 5:05 am

Author: Anonymous

Posted: Thu Aug 28, 2008 5:05 am

xnview wrote:

moroz1999 wrote:

question is: why isn't this format supported by the latest version of xnview? I was quite surprised when I downloaded the latest version and it couldn't open SCR

Do you have enabled option/general/startup/Use all formats?

thanks... now working...

great work...

FAQ index

DOS386 — Thu Aug 28, 2008 2:29 am

Author: DOS386

Posted: Thu Aug 28, 2008 2:29 am

http://newsgroup.xnview.com/viewtopic.php?t=3722

other AGIF resizing + creation thread

Resizing image results in larger file

DOS386 — Thu Aug 28, 2008 2:21 am

Author: DOS386

Posted: Thu Aug 28, 2008 2:21 am

OK ... thread is 4 years old nevertheless, didn't contain much clarification so far, not even corpus delicti was attached, so finally answering

This image gets 3 times BIGGER when resized down by factor 2

Code:

************************************************************

Lanczos resize paradox (smaller bitmap, bigger file) :

************************************************************

04A10BD8B75E4EA1E6DE4B685CCCF545
OPTBIG.PNG 17'892

F4338B9E08E97160148E3927A1816703
OPTSMALL.PNG 40'620

************************************************************

Truecolor 3x8bpp BMP :

BIG.BMP 720'054 1'338 colors 600x400
SMALL.BMP 180'054 707 colors 300x200

Obviously, the "small" BMP must be 4 times smaller
than the "big" one, except the 54 bytes of BMP header.

Saving as PNG using NCONVERT 5.00 (XNVIEW must give the
very same result since both contain the very same LIBPNG) :

BIG.PNG 23'028
SMALL.PNG 69'613 More than 3 times BIGGER !!!!!

Maximum lostless PNG optimization using PNGOUT and
DEFLOPT (OPTIPNG irrelevant here, lost against PNGOUT) :

OPTBIG.PNG 17'892
OPTSMALL.PNG 40'620 Still 2.27 times BIGGER !!!

Additionally we can see than an optimized PNG can be
1.7 times smaller than "standard" PNG.

************************************************************

Download: http://freefile.kristopherw.us/uploads/temp/lanczos.zip

Why does the file size grow ? Because the image has "special" content, the FreeDOS fish at the top has >> 256 colours, while the ASM stuff below just 2, resizing rises the amount of colours below to 256 (all grey), so the lower part will compress badly and grow massively in size, while the negligibly small fish can't save too much

This is a special case however, and I deliberately brewed the image as-is to maximize the shock , OTOH resizing down and saving as PNG using PNG optimizers is still the best way to reduce image size, resizing by factor 2 should reduce the file size by factor 4 in average.

> the PNG format allows lossy

NO, as already found out.

> And with the compression ratio similar to Zip according

Better than ZIP, because of the filters.

Quote:

resizing gives no benefit at size there (KB) , this seems illogical.
- Any explanation, please

Maybe LibPNG of XNView was not very good at that time promoting the evil effect ... retest with PNGOUT is the first thing to do next time

Corrupt jpegs, thumbnail extracted...

XnTriq — Thu Aug 28, 2008 2:00 am

Author: XnTriq

Posted: Thu Aug 28, 2008 2:00 am

Hi Conkers,

thanks for your patience.
It took some time for me to get all the facts together.

Bad news: I wasn't able to fix your photo.
Good news: I'm no expert, just an XnTriq.
In other words: There's still plenty of hope

I consider this posting a preliminary report.

After you had sent me a full-size version of the photo I began replacing the header as explained by Calvin Hass.

ImpulseAdventure (Fix your Corrupted JPEG Photos! � Comments � 2008-04-18) wrote:

As a first method of trying to fix your corrupted images, it's always worth a shot and is easy to do.

In advance of this feature, here's what you can try doing:

Open up the damaged photo (corrupted header) in the hex editor
Open up another photo taken with the same camera, and with the same orientation in another window of the hex editor
Identify the start of the real (not thumbnail) scan data -- the easiest way to do this is open up the damaged file in JPEGsnoop and look for the OFFSET line under the heading Marker: SOS. Note down this hex number (eg. 0x00002C5F).
Repeat the same process with the good photo (eg. 0x000030DB)
Now, in a copy of your corrupted photo file, use the hex editor to delete everything from 0x00000000 to 1 less than the offset noted in step 3 (ie. 0x00002C5E).
In the good version of the photo, copy everything from 0x00000000 to 1 less than the offset noted in step 4 (ie. 0x000030DA).
Back in the copy of your corrupted photo file, use the hex editor and paste (insert) what you copied, right at the start of the file (position 0x00000000). Save as a different file name.

When you reopen the modified version of the damaged file, you should see that the thumbnail now represents the "good file" you were working with. If you only had a header corruption, then the damaged image may now be brought back to life!

In case you'd like to follow along with the steps outlined in the tutorial, I've compiled a list of freeware hex editors (as well as text editors with hex editing capabilities):

Brother Technology: AptEdit Lite
HHD Software: Free Hex Editor Neo
Marcin Dudek: ICY Hexplorer
Jan Fiala: PSPad
CoderTools: TotalEdit

Please don't forget to always work with backup copies of your files when using these programs (even if you don't plan to make changes).

For this method you'll also need �another photo taken with the same camera, and with the same orientation�. I downloaded a few from dpreview.com and dcresource.com.

Having tried all kinds of combinations (incl. bare headers w/o any metadata) unsuccessfully, I decided to examine the image once more with JPEGsnoop v1.2.0 (22/Jan/2008) & v1.2.1 β3 (09/Apr/2008). This time I enabled the Detailed Scan Decode option (Options � Scan Segment � Detailed Decode...) before hitting Ctrl+R (File � Reprocess File).

Code:

*** Decoding SCAN Data ***
OFFSET: 0x00001726
Scan Decode Mode: Full IDCT (AC + DC)

[...]

*** ERROR: @ 0x0002EE09.4, num_coeffs>64 [66]
*** ERROR: Bad scan data in MCU(120,24): Lum DC CSS(1,0) @ Offset 0x0002EE0A.2
MCU located at pixel=(1928,192)
*** ERROR: @ 0x000EEE10.5, num_coeffs>64 [65]
*** ERROR: Bad scan data in MCU(95,130): Lum DC CSS(1,0) @ Offset 0x000EEE11.2
MCU located at pixel=(1528,1040)
*** ERROR: @ 0x0016EE00.1, num_coeffs>64 [68]
*** ERROR: Bad scan data in MCU(89,195): Lum DC CSS(1,0) @ Offset 0x0016EE01.0
MCU located at pixel=(1432,1560)
*** ERROR: @ 0x001AEE07.3, num_coeffs>64 [66]
*** ERROR: Bad scan data in MCU(29,222): Lum DC CSS(1,0) @ Offset 0x001AEE08.2
MCU located at pixel=(472,1776)

This more verbose output indicates scan errors in the bitstream of the JPEG rather than corruption of its header.
At first I though we were screwed. By then I had already tested a bunch of programs to no avail:

e.World Technology: JPEG Recovery
Recoveronix: PixRecovery
VG Solutions: VG JPEG-Repair
Wim Vanmaele: Programma's � Repair-jPeg
See also: S2 Services Data Recovery Freeware List: JPG and BMP Image Repair.

But a brief consultation with almighty Google reminded me that Calvin had repaired photos which had very similar errors.

ImpulseAdventure (JPEGsnoop - Interesting Uses � Comments � 2007-11-03) wrote:

I'm pleased to report that I managed to recover these images almost perfectly! Your photos were great examples of heavy data corruption, which in turn helped me refine the fix methodology. What I found interesting, however, is that the corruption appeared to have some periodicity within the image, but not so much within the file stream.

ImpulseAdventure (Fix Corrupt JPEG Photos!) wrote:

Fixing Corrupt Photos

During the development of JPEGsnoop (a JPEG analysis tool), I began to question whether it was at all possible to fix images that have had errors in the scan segment (JFIF SOS) bitstream. After significant analysis and tool development, I am happy to report that I am now able to correct many of these photos!

Unique Correction Technique!

While there are dozens of software utilities available on the web that advertise that they fix or recover corrupt JPEGs, I am not yet aware of any that actually correct scan bitstream errors (as shown in the samples below). In nearly all cases, these programs will recover the files from deletion (stitching file clusters together) but you may still be left with a damaged JPEG image!

I believe my technique to be unique and hence the reason I decided to post this page and share my services. Photos can often be fixed with virtually no degradation to the original image!

New version ?

art12345 — Wed Aug 27, 2008 10:37 pm

Author: art12345

Posted: Wed Aug 27, 2008 10:37 pm

And please add the future of "original size" in context menu when you are in full screen mode. It would be nice if this feature can be assign to the button.

XnView in ContextMenu in Vista

rra — Wed Aug 27, 2008 9:38 pm

Author: rra

Posted: Wed Aug 27, 2008 9:38 pm

There seems to be a special 64-bit version,
do you happen to have the 64-bit Vista ?

Ren�

[BUG]profil icc utilis� comme destination

fouinix — Wed Aug 27, 2008 5:18 pm

Author: fouinix

Posted: Wed Aug 27, 2008 5:18 pm

fouinix wrote:

Et pour l'application du profil en mode diaporama, est-ce que c'est r�alisable pour les prochaines versions?
Merci

up!

1.94.2 : PNG pics showing black screen in full screen mode

RGBA — Wed Aug 27, 2008 4:33 pm

Author: RGBA

Posted: Wed Aug 27, 2008 4:33 pm

oops66 wrote:

Of course not, it's also interesting to solve it !

Yeah, its kind a challenge, but impossible without every needful specific info of details during an Observation.
Especially, when theres no chance to see anything what's going on or related to interplay, you know..
Don't take it as a personal affront to you. Really not, S.H.Bouwhuis. I have to say sorry, if this is your opinion.