JP2 output file size fault

Bugs found in XnView Classic. Please report only one bug per topic!

Moderators: XnTriq, xnview

Post Reply
Sprintdriver
Posts: 37
Joined: Mon Feb 02, 2009 11:46 pm

JP2 output file size fault

Post by Sprintdriver » Mon Jun 29, 2009 7:10 pm

OS: WInxp sp3
XnView version 1.96.1


Open a 24bpp BMP file and save as JP2.
Go to Options and select "Compression rate: 1 to". Any number higher than 10 will cause the output filesize to increase in size (compared to output file size when number is 10). So - any number above 10 will cause wrong output file size.

Have used XnView for three years now i think and fixed file size is not often used, but here i was trying to get it all into a floppy, and use all space.

User avatar
Drahken
Posts: 884
Joined: Sun Apr 10, 2005 4:29 pm

Re: JP2 output file size fault

Post by Drahken » Wed Jul 01, 2009 9:27 am

There are 2 different plugins to save JP2 files with; the lurawave one & the jasper one (the one that doesn't specify is the jasper one.

I have confirmed this bug with the jasper one. However, the issue isn't that the size goes up after 1-10, it's that the numbers are backwards. If you want MORE compression, then you need to set the number LOWER. This is completely opposite of the way it's supposed to be, and I could swear that I reported this exact thing a year or two ago, but I thought it wound up getting fixed.
Example: A given image saved to 224KB at 1to10. That same image became 336KB at 1to15, and 116KB at 1to5. It should have been 336@ 1to5 and 116@ 1to15.

The lurawave JP2 plugin works normally.

sprintdriver- There are several ways for you to work around this issue until it gets fixed:
1) Try a lower number instead of a higher one.
2) Use the lurawave plugin.
3) Use either the compression ration or quality slider instead of the 1to10 setting.
Oh the feuhrer, oh the feuhrer, oh the feuhrer's nipples bonk!

Sprintdriver
Posts: 37
Joined: Mon Feb 02, 2009 11:46 pm

Re: JP2 output file size fault

Post by Sprintdriver » Wed Jul 01, 2009 10:20 am

Drahken wrote:I have confirmed this bug with the jasper one. However, the issue isn't that the size goes up after 1-10, it's that the numbers are backwards. If you want MORE compression, then you need to set the number LOWER. This is completely opposite of the way it's supposed to be, and I could swear that I reported this exact thing a year or two ago, but I thought it wound up getting fixed.
Ok then. I can live with that since I rarely use that feature. However I found that number 10 give smallest output file size. Any number higher OR lower will result in a bigger file. So it's not possible to compress a file so that output file size is less than 1/10 of original file size. And THAT I cannot live with.

User avatar
Drahken
Posts: 884
Joined: Sun Apr 10, 2005 4:29 pm

Re: JP2 output file size fault

Post by Drahken » Wed Jul 01, 2009 11:47 am

Hmm... For me, going with a number lower than 10 decreased the filesize. Then again, I'm still using the 1.96beta, so that might be why.

Nonetheless, you can still get smaller images by using the quality slider or the specific filesize option, and you can use the lwf JP2 plugin (on which the compression ration setting works as it should).
Oh the feuhrer, oh the feuhrer, oh the feuhrer's nipples bonk!

User avatar
Drahken
Posts: 884
Joined: Sun Apr 10, 2005 4:29 pm

Re: JP2 output file size fault

Post by Drahken » Thu Jul 02, 2009 8:45 am

I found the other thread I was thinking of: http://newsgroup.xnview.com/viewtopic.php?f=36&t=10878
Oh the feuhrer, oh the feuhrer, oh the feuhrer's nipples bonk!

Post Reply