<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Jeffrey&#8217;s &#8220;Metadata Wrangler&#8221; Lightroom Plugin</title>
	<atom:link href="http://regex.info/blog/lightroom-goodies/metadata-wrangler/feed" rel="self" type="application/rss+xml" />
	<link>http://regex.info/blog</link>
	<description>Not a photo blog, but sometimes I play one on TV</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:25:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Vanderbeck</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-38371</link>
		<dc:creator>John Vanderbeck</dc:creator>
		<pubDate>Mon, 01 Mar 2010 19:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-38371</guid>
		<description>Hi Jeffrey,

Wanted to first say thank you for adding the ability to strip keywords.  It has been a huge help to me.  I&#039;ll be sending a donation your way soon.

I also wanted to say that with this functionality in place, you can do something really cool with your plugins!  You can now use internal tags to affect the export of your photos to services like Flickr, but then have those internal tags stripped during the export.  So you get the automated control over the export without the tags actually going out.  It rocks!  For example, on Flickr my default copyright level is Copyrighted, but I sometimes upload photos that I set to Creative Commons.  I can now set a keyword in Lightroom called &quot;license_cc&quot; and in your Flickr exporter I have it set to mark any images with that keyword as Creative Commons license.  But then in the Metadata Wrangler I have it set to STRIP that keyword.  Net effect is that the Flickr exporter sees it and assigns the license, but then the wrangerl removes the keyword so I get the license on Flickr but not the keyword.  Cool!

&lt;span class=&#039;jfriedl&#039;&gt;About &#8220;&lt;i&gt;You can now use internal tags to affect the export of your photos to services like Flickr&lt;/i&gt;&#8221;, you can do that without this plugin... just right-click on the keyword in the Keyword List (in Library) and unselect the &quot;include on export&quot; option. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Hi Jeffrey,</p>
<p>Wanted to first say thank you for adding the ability to strip keywords.  It has been a huge help to me.  I&#8217;ll be sending a donation your way soon.</p>
<p>I also wanted to say that with this functionality in place, you can do something really cool with your plugins!  You can now use internal tags to affect the export of your photos to services like Flickr, but then have those internal tags stripped during the export.  So you get the automated control over the export without the tags actually going out.  It rocks!  For example, on Flickr my default copyright level is Copyrighted, but I sometimes upload photos that I set to Creative Commons.  I can now set a keyword in Lightroom called &#8220;license_cc&#8221; and in your Flickr exporter I have it set to mark any images with that keyword as Creative Commons license.  But then in the Metadata Wrangler I have it set to STRIP that keyword.  Net effect is that the Flickr exporter sees it and assigns the license, but then the wrangerl removes the keyword so I get the license on Flickr but not the keyword.  Cool!</p>
<p><span class='jfriedl'>About &#8220;<i>You can now use internal tags to affect the export of your photos to services like Flickr</i>&#8221;, you can do that without this plugin&#8230; just right-click on the keyword in the Keyword List (in Library) and unselect the &#8220;include on export&#8221; option. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Vanderbeck</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-38086</link>
		<dc:creator>John Vanderbeck</dc:creator>
		<pubDate>Wed, 03 Feb 2010 16:32:44 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-38086</guid>
		<description>I&#039;m sorry, my fault for not being clear.  I know I can set certain keywords to NEVER be exported in a global manner, but I use them for various internal purposes so I need them to export in most cases.  However when exporting to specific areas, like Flickr for example, I need to strip certain keywords.   I have been doing it manually but when I heard about this plugin I had hoped it would allow me to automate it.

&lt;span class=&#039;jfriedl&#039;&gt;I thought it would be easy to add, but I kept running into things (and adding more features), so it took two solid days, but I&#039;ve just pushed &lt;b&gt;v58&lt;/b&gt; that allows you to do this, and more. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry, my fault for not being clear.  I know I can set certain keywords to NEVER be exported in a global manner, but I use them for various internal purposes so I need them to export in most cases.  However when exporting to specific areas, like Flickr for example, I need to strip certain keywords.   I have been doing it manually but when I heard about this plugin I had hoped it would allow me to automate it.</p>
<p><span class='jfriedl'>I thought it would be easy to add, but I kept running into things (and adding more features), so it took two solid days, but I&#8217;ve just pushed <b>v58</b> that allows you to do this, and more. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Vanderbeck</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-38084</link>
		<dc:creator>John Vanderbeck</dc:creator>
		<pubDate>Wed, 03 Feb 2010 15:03:04 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-38084</guid>
		<description>Is there any way I can strip SPECIFIC keywords, if present, while retaining the rest of the keywords?

I use some keywords internally for organization that just look silly when present on images that I export to publish in places like Flickr.

&lt;span class=&#039;jfriedl&#039;&gt;Keywords that you never want to publish should just have the &quot;include on export&quot; flag turned off. Right click on a keyword in the Keyword List, and &quot;Edit keyword&quot;. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Is there any way I can strip SPECIFIC keywords, if present, while retaining the rest of the keywords?</p>
<p>I use some keywords internally for organization that just look silly when present on images that I export to publish in places like Flickr.</p>
<p><span class='jfriedl'>Keywords that you never want to publish should just have the &#8220;include on export&#8221; flag turned off. Right click on a keyword in the Keyword List, and &#8220;Edit keyword&#8221;. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KPa</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-37710</link>
		<dc:creator>KPa</dc:creator>
		<pubDate>Tue, 29 Dec 2009 13:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-37710</guid>
		<description>Uh. Silly me, now I feel stupid... back to &quot;reading the friendly manual&quot;. But anyhow, this added the information, atleast to me and hopefully also someone else.

Only difference would be that by having this feature in the export plugin one could have different filtrations depending on the purpose of the export simply by choosing export presets accordingly.</description>
		<content:encoded><![CDATA[<p>Uh. Silly me, now I feel stupid&#8230; back to &#8220;reading the friendly manual&#8221;. But anyhow, this added the information, atleast to me and hopefully also someone else.</p>
<p>Only difference would be that by having this feature in the export plugin one could have different filtrations depending on the purpose of the export simply by choosing export presets accordingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KPa</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-37708</link>
		<dc:creator>KPa</dc:creator>
		<pubDate>Tue, 29 Dec 2009 07:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-37708</guid>
		<description>Hi,

First of all, thank you for making such a usefull add-ons for Lightroom. Without plugins the LR would not be my choice of the post-processing software.

The Metadata Wrangler is very handy controlling the amount of the information one wants to publish with the exported pictures. Regarding that, I have a wish for an extended feature. I do not know if it&#039;s feasible to implement with current approach, but asking never hurts, it adds information instead :) 

So, would it be possible to partially filter keywords attached to exported pictures? Like when you have hierarchical keywords used in Lightroom, you could either select the hierarchies to be included or excluded. For example, one could define export to filter out all keywords under category &quot;people&quot; and &quot;addresses&quot; in order not to accidentally publish name or exact location of the subject. Or, just tag keywords under groups &quot;country&quot; and &quot;animals&quot; to the included in the export.

Do you think such a feature would be feasible?

&lt;span class=&#039;jfriedl&#039;&gt;It may be feasible, but it&#039;s not likely something I&#039;d do, since you can already mark individual keywords in Lightroom to be exported or not. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>First of all, thank you for making such a usefull add-ons for Lightroom. Without plugins the LR would not be my choice of the post-processing software.</p>
<p>The Metadata Wrangler is very handy controlling the amount of the information one wants to publish with the exported pictures. Regarding that, I have a wish for an extended feature. I do not know if it&#8217;s feasible to implement with current approach, but asking never hurts, it adds information instead <img src='http://regex.info/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>So, would it be possible to partially filter keywords attached to exported pictures? Like when you have hierarchical keywords used in Lightroom, you could either select the hierarchies to be included or excluded. For example, one could define export to filter out all keywords under category &#8220;people&#8221; and &#8220;addresses&#8221; in order not to accidentally publish name or exact location of the subject. Or, just tag keywords under groups &#8220;country&#8221; and &#8220;animals&#8221; to the included in the export.</p>
<p>Do you think such a feature would be feasible?</p>
<p><span class='jfriedl'>It may be feasible, but it&#8217;s not likely something I&#8217;d do, since you can already mark individual keywords in Lightroom to be exported or not. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: André Weigel</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-37508</link>
		<dc:creator>André Weigel</dc:creator>
		<pubDate>Wed, 09 Dec 2009 10:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-37508</guid>
		<description>Thank you, for this great LR-plugin !</description>
		<content:encoded><![CDATA[<p>Thank you, for this great LR-plugin !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-37502</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Tue, 08 Dec 2009 18:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-37502</guid>
		<description>where do you store the presets in metadata wrangler?
i&#039;m working on osx 10.5.8 and would like to use the same presets on my laptop.

&lt;span class=&#039;jfriedl&#039;&gt;There&#039;s no easy way to import/export them, though now that I think about it, Metadata Wrangler settings (not presets) are saved when you create a Metadata Preset, so you can select a M.W. preset, create an Export preset, and repeat. Then copy the Export presets to the new computer and cycle through a load, save M.W. preset sequence.  It&#039;s a bit kludgy, but then, you&#039;re the first person to ask about this in the couple of years the Metadata Wrangler has been out. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>where do you store the presets in metadata wrangler?<br />
i&#8217;m working on osx 10.5.8 and would like to use the same presets on my laptop.</p>
<p><span class='jfriedl'>There&#8217;s no easy way to import/export them, though now that I think about it, Metadata Wrangler settings (not presets) are saved when you create a Metadata Preset, so you can select a M.W. preset, create an Export preset, and repeat. Then copy the Export presets to the new computer and cycle through a load, save M.W. preset sequence.  It&#8217;s a bit kludgy, but then, you&#8217;re the first person to ask about this in the couple of years the Metadata Wrangler has been out. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Lewis</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-36886</link>
		<dc:creator>Trevor Lewis</dc:creator>
		<pubDate>Fri, 16 Oct 2009 16:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-36886</guid>
		<description>Perl.exe keeps crashing.

I am using the latest version of MetaDataWrangler   (metadatawrangler-20090903.53.zip ) in Lightroom 2 v 2.5 (64 bit) on a machine running Windows 7 Ultimate 64 Bit and I cannot export without getting a message for every file saying that perl.exe has failed to run.   If  I go to the Win directory in the installed plgin dir and try to run perl.exe directly it also crashes.

Any ideas?

Regards 
Trevor

&lt;span class=&#039;jfriedl&#039;&gt;I&#039;ve not heard other reports of problems on Win7, but I&#039;ve also never tested it there. (I still run XP.) Could yous end details about the crash (what kind of crash?) via email? &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Perl.exe keeps crashing.</p>
<p>I am using the latest version of MetaDataWrangler   (metadatawrangler-20090903.53.zip ) in Lightroom 2 v 2.5 (64 bit) on a machine running Windows 7 Ultimate 64 Bit and I cannot export without getting a message for every file saying that perl.exe has failed to run.   If  I go to the Win directory in the installed plgin dir and try to run perl.exe directly it also crashes.</p>
<p>Any ideas?</p>
<p>Regards<br />
Trevor</p>
<p><span class='jfriedl'>I&#8217;ve not heard other reports of problems on Win7, but I&#8217;ve also never tested it there. (I still run XP.) Could yous end details about the crash (what kind of crash?) via email? &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chandra</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-36756</link>
		<dc:creator>Chandra</dc:creator>
		<pubDate>Thu, 01 Oct 2009 15:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-36756</guid>
		<description>I think this problem will happen on any operating system with BitDefender. You can download antivirus evaluation and try this. Like I said there is no hang  problem with newer version of perl. Will you be able to update your package with newer version of Perl, if this is a possibility.

Thanks
Chandra

&lt;span class=&#039;jfriedl&#039;&gt;You probably just need to add an exception for perl or Lightroom or something. Like I said, plugins downloaded from my site have no viruses (and, FWIW, no one else has ever reported anything like this), so it&#039;s not something I&#039;m inclined to add very high up on my already-impossibly-long todo list. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>I think this problem will happen on any operating system with BitDefender. You can download antivirus evaluation and try this. Like I said there is no hang  problem with newer version of perl. Will you be able to update your package with newer version of Perl, if this is a possibility.</p>
<p>Thanks<br />
Chandra</p>
<p><span class='jfriedl'>You probably just need to add an exception for perl or Lightroom or something. Like I said, plugins downloaded from my site have no viruses (and, FWIW, no one else has ever reported anything like this), so it&#8217;s not something I&#8217;m inclined to add very high up on my already-impossibly-long todo list. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chandra</title>
		<link>http://regex.info/blog/lightroom-goodies/metadata-wrangler#comment-36742</link>
		<dc:creator>Chandra</dc:creator>
		<pubDate>Tue, 29 Sep 2009 03:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://regex.info/blog/lightroom-goodies/metadata-wrangler/#comment-36742</guid>
		<description>I have metadatawrangler-20090903.53 version. If I have the BitDefender 2010 antivirus installed on my machine which has Vista 64 bit Ultimate, the Perl.exe does not work. It just hangs. I tried just typing the perl.exe which comes with the package on the command prompt and it hangs.  I tried putting the Perl.exe as exclusion in the antivirus, still it did not work. If I uninstall the antivirus software then the Perl.exe that comes with the package works.

With the latest  version of Perl.exe and antivirus still there on my machine, the Perl.exe works on a command prompt. I tried replacing the Perl.exe that comes with the plugin with the new version, then it complains about something else, atleast it does not hang. So I think the version that comes with the plugin does not work the BitDefender antivirus software. Can this issue be fixed.

&lt;span class=&#039;jfriedl&#039;&gt;I have neither Vista nor BitDefender so I can&#039;t test, but there are no viruses in my plugin, so if BitDefender is having an issue with it, it seems &lt;i&gt;they&lt;/i&gt; have a problem to address. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>I have metadatawrangler-20090903.53 version. If I have the BitDefender 2010 antivirus installed on my machine which has Vista 64 bit Ultimate, the Perl.exe does not work. It just hangs. I tried just typing the perl.exe which comes with the package on the command prompt and it hangs.  I tried putting the Perl.exe as exclusion in the antivirus, still it did not work. If I uninstall the antivirus software then the Perl.exe that comes with the package works.</p>
<p>With the latest  version of Perl.exe and antivirus still there on my machine, the Perl.exe works on a command prompt. I tried replacing the Perl.exe that comes with the plugin with the new version, then it complains about something else, atleast it does not hang. So I think the version that comes with the plugin does not work the BitDefender antivirus software. Can this issue be fixed.</p>
<p><span class='jfriedl'>I have neither Vista nor BitDefender so I can&#8217;t test, but there are no viruses in my plugin, so if BitDefender is having an issue with it, it seems <i>they</i> have a problem to address. &mdash;Jeffrey</span></p>
]]></content:encoded>
	</item>
</channel>
</rss>
