Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!news.cgarbs.de!news.addix.net!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail
From: human <noreply@elfavo.com>
Newsgroups: comp.compression
Subject: Re: removing predictable crap from poor quality jpegs
Date: Tue, 03 May 2011 18:32:42 +0200
Organization: humanity
Lines: 11
Message-ID: <4DC02E2A.78B80C34@elfavo.com>
References: <877ha8xeex.fsf@bazspaz.fatphil.org> <4DBFECD7.A3180162@elfavo.com> <eZA*OAaCt@news.chiark.greenend.org.uk> <4DC028EF.4A9DE7BD@elfavo.com>
NNTP-Posting-Host: port-92-195-180-235.dynamic.qsc.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: online.de 1304440282 5527 92.195.180.235 (3 May 2011 16:31:22 GMT)
X-Complaints-To: abuse@einsundeins.com
NNTP-Posting-Date: Tue, 3 May 2011 16:31:22 +0000 (UTC)
X-Mailer: Mozilla 4.78 [de] (Windows NT 5.0; U)
X-Accept-Language: de
Xref: x330-a1.tempe.blueboxinc.net comp.compression:209

> For sequential mode only 0-63 is allowed ...

in the scan script.
In the SmartScale case (as used in your initial approach)
the 63 as Se parameter is overriden automatically inside
the JPEG code by the block size derived value, and
"excessive" progressive scans are also adapted (reduced)
automatically in this case.

ciao
human