[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NSImageCompressionFactor
|
From: |
Riccardo Mottola |
|
Subject: |
Re: NSImageCompressionFactor |
|
Date: |
Tue, 20 May 2014 16:16:52 +0200 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 |
Hi,
Lundberg, Johannes wrote:
I mean, it works but that becomes always 0 = the best jpg quality.
I fear you are right, I just tried using PRICE, this is what I get:
-rw-r--r-- 1 multix staff 451980 May 20 16:17 linhof_00.jpg
-rw-r--r-- 1 multix staff 411706 May 20 16:16 linhof_100.jpg
-rw-r--r-- 1 multix staff 411706 May 20 16:17 linhof_25.jpg
-rw-r--r-- 1 multix staff 411706 May 20 16:17 linhof_75.jpg
it is not even true that values higher than "1" ield 0, because 0 would
have a terrible quality. Here the difference seems to be very small
instead, only 0 is really bigger and looks like 100.
Riccardo
- NSImageCompressionFactor, Lundberg, Johannes, 2014/05/14
- Re: NSImageCompressionFactor, Riccardo Mottola, 2014/05/21
- Re: NSImageCompressionFactor, Lundberg, Johannes, 2014/05/21
- Re: NSImageCompressionFactor, Fred Kiefer, 2014/05/27
- Re: NSImageCompressionFactor, Riccardo Mottola, 2014/05/28
- Re: NSImageCompressionFactor, Fred Kiefer, 2014/05/30