Why ignoring -o option when use -jpegcrop?

Discussions on NConvert - the command line tool for image conversion and manipulation

Moderators: helmut, XnTriq, xnview

Post Reply
andrushka
Posts: 1
Joined: Wed Dec 23, 2009 10:16 am

Why ignoring -o option when use -jpegcrop?

Post by andrushka »

Why ignoring -o option when use -jpegcrop and overwrite source files? With -crop option is worked fine, but slow. :bugconfirmed: ?
User avatar
DOS386
Posts: 291
Joined: Sun Jun 11, 2006 2:43 pm

Re: Why ignoring -o option when use -jpegcrop?

Post by DOS386 »

andrushka wrote:Why ignoring -o option when use -jpegcrop and overwrite source files?


I don't see any blocker here, apparently for some "internal" reasons :-( , could be improved ;-)
With -crop option is worked fine, but slow.
But also lossy :-(

Possible implementation problem with lossless JPG transformations: http://newsgroup.xnview.com/viewtopic.php?f=35&t=19014
There is indeed no WinZIP under my rock.
User avatar
helmut
Posts: 8704
Joined: Sun Oct 12, 2003 6:47 pm
Location: Frankfurt, Germany

Re: Why ignoring -o option when use -jpegcrop?

Post by helmut »

As written in another article, the direct manipulation of the lossless JPG operations is a problem in XnView (GUI), because it works differently and I guess there's users who crop and loose their original files by accident. The solution for XnView (GUI) would be a backup copy mechanism, which is a good idea, anyway.

The solution for nconvert seems even simpler to me:
Make a copy of the file, rename the copy to the specifed output filename, and then apply the lossless operation.

Anyway, this issue should be solved soon to avoid more people loosing part of their images due to a wrong usage.
Post Reply