<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.5.1" -->
<rss version="0.92">
<channel>
	<title>ImageIngester Blog</title>
	<link>http://imageingester.com/wp</link>
	<description>News about ImageIngester and other digital photography products</description>
	<lastBuildDate>Wed, 08 Oct 2008 23:58:09 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>New LRViewer Version 1.3.02 for Windows; new Redistribution Kit</title>
		<description>This new version fixes a bug that prevented viewing of Lightroom 2 images. Also, the Redistribution Kit has been updated to support Lightroom 2.

Update: The newest Windows version is now 1.3.03; the earlier version left a debugging file around. </description>
		<link>http://imageingester.com/wp/?p=30</link>
			</item>
	<item>
		<title>New ImageIngester Version 3.2.04 adds minor feature and fixes bugs</title>
		<description>The details:

	 Ingestion Notes now preserved across executions (but not saved in any preset) 
	 Bug fix: On OS X, the preset name wasn't shown in the title of the File Handling Details panel. 
	 Bug fix: The macro {@filename} appearing in metadata presets was erroneously replaced by the new file name ...</description>
		<link>http://imageingester.com/wp/?p=29</link>
			</item>
	<item>
		<title>New LRViewer version supports Lightroom 2 catalogs</title>
		<description>Version 1.3.01, just posted. (Metadata file group is no longer supported.) </description>
		<link>http://imageingester.com/wp/?p=28</link>
			</item>
	<item>
		<title>New web-page facility to export keywords from LR to II</title>
		<description>
It's
here.

This web page doesn't explain how to do it, it does the work for you. Note that II doesn't support hierarchical keywords, so any such keywords in LR will be flattened to a single level. </description>
		<link>http://imageingester.com/wp/?p=27</link>
			</item>
	<item>
		<title>ImageIngester User&#8217;s Manual updated for Version 3.2</title>
		<description>
Updated for the new preset design and for the disc-burning features. </description>
		<link>http://imageingester.com/wp/?p=26</link>
			</item>
	<item>
		<title>New ImageIngester 3.2.03 for Windows fixes preset bug</title>
		<description>
Settings from the File Handling Details panel weren't always effective when the panel was closed, although they were stored in the preset. Now fixed. </description>
		<link>http://imageingester.com/wp/?p=25</link>
			</item>
	<item>
		<title>New ImageIngester Version 3.2.02 with new preset design</title>
		<description>
This version is incompatible with previous versions.

Here's what's new:


New preset design. Click here for details.

Incompatibility: Master Presets no longer copied from IIPv2.

Incompatibility: Master Presets from IIPv3.1 use Default for Destination, File Handling, Metadata, and Keywords presets.

Many minor bugs fixed.

 </description>
		<link>http://imageingester.com/wp/?p=24</link>
			</item>
	<item>
		<title>Proposed New ImageIngester Preset Design</title>
		<description>
The Current Version 3 Preset Design


ImageIngester Version 3 was designed so that all preset values other than Photographer, Content, and Rights are saved in the Master Preset. For Metadata, the names of the Photographer, Content, and Rights presets are saved, not the individual values. This design means that:


The Master Preset ...</description>
		<link>http://imageingester.com/wp/?p=23</link>
			</item>
	<item>
		<title>New ImageVerifier Version 1.2.02 for OS X and Windows</title>
		<description>
What's new:


New option to store hashes for TIFFs even though the structure check calls them invalid. (IV's TIFF checker often reports valid TIFFs as invalid because the TIFF format isn't standardized.) [New for Windows; previously appeared in 1.2.01 for OS X]

New option to limit number of subprocesses. Useful if you ...</description>
		<link>http://imageingester.com/wp/?p=22</link>
			</item>
	<item>
		<title>New ImageVerifier Version 1.2.01 for OS X</title>
		<description>
What's new:


New option to store hashes for TIFFs even though the structure check calls them invalid. (IV's TIFF checker often reports valid TIFFs as invalid because the TIFF format isn't standardized.)

New option to limit number of subprocesses. Useful if you have multiple CPUs and/or cores and don't want IV to ...</description>
		<link>http://imageingester.com/wp/?p=21</link>
			</item>
</channel>
</rss>
