>From [EMAIL PROTECTED] Wed Mar 22 10:14:12 2006
Return-path: <[EMAIL PROTECTED]>
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Wed, 22 Mar 2006 09:53:52 +0000
Received: from [194.200.237.129] (helo=helios.sciencephoto.co.uk)
by austin.sciencephoto.co.uk with esmtp (Exim 4.43)
id 1FM02J-0004H4-7i
for [EMAIL PROTECTED]; Wed, 22 Mar 2006 09:53:52 +0000
Received: from studio.imagemagick.org ([64.34.164.5] helo=imagemagick.org)
by helios.sciencephoto.co.uk with esmtp (Exim 3.16 #3)
id 1FM0LM-000391-00
for [EMAIL PROTECTED]; Wed, 22 Mar 2006 10:13:32 +0000
Received: from redux.imagemagick.org (localhost.localdomain [127.0.0.1])
by imagemagick.org (8.12.11/8.12.11) with ESMTP id k2MARuAv011730;
Wed, 22 Mar 2006 02:29:35 -0800
Received: from helios.sciencephoto.co.uk (helios.sciencephoto.co.uk
[194.200.237.129])
by imagemagick.org (8.12.11/8.12.11) with ESMTP id k2MARp2J011724
for <[email protected]>; Wed, 22 Mar 2006 02:27:54 -0800
Received: from [194.200.237.140] (helo=[194.200.237.140])
by helios.sciencephoto.co.uk with esmtp (Exim 3.16 #3)
id 1FM06A-00033g-00
for [email protected]; Wed, 22 Mar 2006 09:57:50 +0000
From: "Dermot Paikkos" <[EMAIL PROTECTED]>
To: [email protected]
Date: Wed, 22 Mar 2006 09:57:16 -0000
MIME-Version: 1.0
Message-ID: <[EMAIL PROTECTED]>
Priority: normal
X-mailer: Pegasus Mail for Windows (4.31)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Subject: [magick-users] extraneous bytes error - one possible fix
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: [EMAIL PROTECTED]
List-Id: ImageMagick User List <magick-users.imagemagick.org>
List-Unsubscribe:
<http://studio.imagemagick.org/mailman/listinfo/magick-users>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <http://studio.imagemagick.org/pipermail/magick-users>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://studio.imagemagick.org/mailman/listinfo/magick-users>,
<mailto:[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-Spam-Score: -3.1
X-Spam-Report: Spam detection software, running on the system
"austin.sciencephoto.co.uk", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
[EMAIL PROTECTED] for details.
Content preview: Hi, This post started as a request for help but has
ended up as a FYI post. I have quite a few jpegs with "extraneous bytes
before marker 0xed". [...]
Content analysis details: (-3.1 points, 7.0 required)
pts rule name description
---- ----------------------
--------------------------------------------------
-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
[score: 0.0000]
-0.5 AWL AWL: From: address is in the auto white-list
Hi,
This post started as a request for help but has ended up as a FYI
post.
I have quite a few jpegs with "extraneous bytes before marker 0xed".
The images can be opened in PS, IrfanView and browsers so the
corruption is not fatal but, mostly as an exercise, I wanted to try
and remove the error.
I could convert the files to remove the error but that would apply
the encoding again and would lead to some, albeit minute,
degradation of the image.
What I wanted was to do is open the files in a hex editor, find the
marker, delete x number of bytes before the marker and save the
image.
Trying to find the hex value was a little tough. After doing a lot of
searching for 'ed' in Hex edit mode of WinVi32, the most obvious
candidate looks like a section that reads like
00 00 00 00 ff ed 7d
Where 00 goes back about 30 lines. So the marker sequence to find was
"ff ed 7d". In the 3 cases I looked at the extraneous bytes were null
or 00.
So to remove the extra bytes, highlight the first null characters
prior to 'ff ed' back to the first occurrence of 00 in that sequence.
Delete the highlighted section, save the file with a new name. Open
it in a graphics package and run identify to check that the image is
sane. If your happy, overwrite original corrupted file with your new
version.
The only real benefit I have found in doing this is that graphics
packages (namely PS) will open the file a little quicker. As far as I
can tell this process has not tampered with any of the other file
attributes such as ICC/IPTC/EXIF profiles and the preview image
remains intact.
Away, HTH.
Dp.
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
