{"id":1946,"date":"2012-02-17T22:00:40","date_gmt":"2012-02-17T13:00:40","guid":{"rendered":"https:\/\/regex.info\/blog\/lightroom-goodies\/ipad-howto2"},"modified":"2012-02-17T22:00:40","modified_gmt":"2012-02-17T13:00:40","slug":"ipad-howto2","status":"publish","type":"page","link":"https:\/\/regex.info\/blog\/lightroom-goodies\/ipad-howto2","title":{"rendered":"My Lightroom-to-iPad Workflow: Now a Lot More Refined"},"content":{"rendered":"\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/crop-for-iPad-burninglyrics.png\" width=\"570\" height=\"492\"\nclass=\"raw\"\nid=\"icrop_for_iPad_burninglyrics\"\/>\n<div style='line-height:40px; margin-top:20px; margin-right:30px'><span class='caption'>From Lightroom To iPad<br\/>&mdash; Take Two &mdash;<\/span><\/div>\n<\/div>\n\n\n<p class='h'>Introduction<\/p>\n\n<p>Three months ago in &#8220;<a class='pt' href='\/blog\/lightroom-goodies\/ipad-howto'>How To Best Export\nLightroom Images to an iPad, iPhone, Etc.<\/a>&#8221; I wrote about my old workflow in getting my portfolio photos from Adobe\nLightroom to an iPad. The setup and flow was <i>much<\/i> more complex than one might think it needed to be, mostly due\nto limitations and bugs with iTunes, but also due to some limitations in the Lightroom plugins I was using. I was happy\nto have eked out the best quality iTunes allowed, but the whole process felt horribly clunky.<\/p>\n\n<div style='margin-top:0; padding-top:10px; text-align:center' class='img_right'>\n<img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-PhotoManagerPro.png\" width=\"400\" height=\"533\"\nclass=\"raw\"\nid=\"iiPad_workflow_PhotoManagerPro\"\nstyle=\"padding: 2px; margin:0 20px 10px 20px; border:solid 1px #444\"\/>\n<br\/><span class='caption'>Portfolio on my iPad<\/span>\n<br\/>in this case, with the <a\nhref='http:\/\/itunes.apple.com\/us\/app\/photo-manager-pro\/id393858562?mt=8'>Photo\nManager Pro<\/a> app\n\n<\/div>\n\n\n<p>I've now solved many of the problems I ran into then, in part by making major updates to the plugins I use in\nLightroom, and also by abandoning Apple's &#8220;Photos&#8221; app in favor of a <a\nhref='\/blog\/2012-02-14\/1944'>third-party photo-viewing iPad app<\/a>.<\/p>\n\n<p>The overall workflow is now smoother and faster in most every respect.<\/p>\n\n<p>In this post I'll talk about Lightroom setup, photo selection and processing, and exporting photos to the iPad. I'll\nframe the presentation in the context of the app I use on my iPad, but the bulk of the discussion is relevant for any\nLightroom-to-device workflow.<\/p>\n\n\n<ol>\n<li><a href='#lr-setup'>Initial Lightroom Setup<\/a><\/li>\n<li><a href='#album-setup'>Album Setup<\/a><\/li>\n<li><a href='#image-selection'>Image Selection and Preparation<\/a><\/li>\n<li><a href='#publishing'>Getting Images to the Device<\/a><\/li>\n<li><a href='#dropbox'>Publishing From Multiple Computers<\/a><\/li>\n<\/ol>\n\n<p>By the way, the example photo in the mock-up above is from\n<a href='\/blog\/2012-02-03\/1936'>this post<\/a>\non a festival rite at the Heian Shrine in Kyoto, Japan.<\/p>\n\n<style type=\"text\/css\">\n  p.h { font-weight:bold; font-size:120%; margin-top: 60px }\n<\/style>\n\n<p class='h' id='lr-setup'>Initial Lightroom Setup<\/p>\n\n<p>Setting up Lightroom first involves installing these plugins:<\/p>\n\n<ul>\n\n<li><p><a href='\/blog\/lightroom-goodies\/collection-publisher'>Collection Publisher<\/a> &mdash;\ncontrols the overall workflow, and allows arrangement of photos into albums for the target device.<\/p><\/li>\n\n<li><p><a href='\/blog\/lightroom-goodies\/crop-for-ipad'>Crop-for-iPad<\/a> &mdash; <i>(optional)<\/i>\nallows for device-specific crops to be applied on the fly during export, for selected images that don't have the same\naspect ratio as the target device's screen, but would look better when filling it.<\/p><\/li>\n\n<li><p><a href='\/blog\/lightroom-goodies\/metadata-wrangler'>Metadata Wrangler<\/a> &mdash; <i>(optional)<\/i> allows you to strip selected metadata from the exported copies, either to save space or to preserve privacy.<\/p><\/li>\n\n<li><p><a href='\/blog\/lightroom-goodies\/gps'>Geoencoding Support<\/a> &mdash; <i>(optional, not needed for Lr4+)<\/i>\nif you want to be able to geoencode images, and the target device can display the geoencoded location (and you want to be able to do that).<\/p><\/li>\n\n<\/ul>\n\n<p>Once installed, perform the initial setup of the Collection Publisher publish service. There are a bazillion sections\nto configure, but most are straightforward and unsurprising, so this will go quickly...<\/p>\n\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-top.png\" width=\"849\" height=\"304\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_top\"\/><\/div>\n\n<p>The second section, &#8220;Publish Tree&#8221;, indicates where image copies intended for the target device will be kept on your\nlocal system. (Personally, I use a <a href='https:\/\/www.dropbox.com\/'>Dropbox<\/a> folder, for reasons that I discuss\n<a href='#dropbox'>below<\/a>.)<\/p>\n\n<p>The next six sections of the dialog are standard for most any Lightroom export; I'll quickly go over the settings I use...<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-01-FileNaming.png\" width=\"580\" height=\"120\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_01_FileNaming\"\/><\/div>\n\n<p>Because I might have two renditions of the same image (e.g. color and black &amp; white versions), I want to make sure they're\ndifferentiated, so my standard file-naming rule for all my Lightroom exports is one that combines the file name and the copy name:<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-FilenameCopy.png\" width=\"409\" height=\"216\"\nclass=\"raw\"\nid=\"iiPad_workflow_FilenameCopy\"\/><\/div>\n\n\n\n\n<p>The output should be an sRGB JPEG of fairly nice quality, but due to memory and processing concerns on the target\ndevice, should not be too high. (If you're not familiar with exactly what this means, you'll find this useful: &#8220;<a\nclass='pt' href='\/blog\/lightroom-goodies\/jpeg-quality'>An Analysis of Lightroom JPEG Export Quality\nSettings<\/a>&#8221;.)<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-02-File-Settings.png\" width=\"580\" height=\"180\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_02_File_Settings\"\/><\/div>\n\n\n\n<p>In choosing the pixel size of the exported image, take into account the maximum size that the target device (or the\ntarget app on the target device) can handle natively. Choosing a size larger than that just wastes memory and processing\npower as the app will have to downsize images on the fly or upon load, and choosing a size smaller means that you can't\nzoom up as much as is supported.<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-03-Image-Sizing.png\" width=\"580\" height=\"92\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_03_Image_Sizing\"\/><\/div>\n\n<p>At the moment I've got my rule set up for &#8220;long edge to 2,000 pixels&#8221; because it should be reasonable for most apps\nwhile I test; later once I've settled on an app and know its specs, it'll be a simple matter to update this setting\nappropriately and republish my portfolio.<\/p>\n\n<p>I leave sharpening at &#8220;standard for screen&#8221;...<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-04-Output-Sharpening.png\" width=\"580\" height=\"61\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_04_Output_Sharpening\"\/><\/div>\n\n<p>I don't have Lightroom remove any image metadata, and I don't do any watermarking...<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-05-Metadata.png\" width=\"580\" height=\"146\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_05_Metadata\"\/><\/div>\n\n<p>... but a bit below, I'll pick and choose what metadata I want to retain and remove.<\/p>\n\n<p>The next sections come from some of the plugins installed in Lightroom, and added to the export via the section in the lower\nleft of the Publishing Manager:<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-postprocess-list.png\" width=\"205\" height=\"246\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_postprocess_list\"\/><\/div>\n\n<p>In Lr3 I include the geoencoding &#8220;Shadow Injector&#8221;, though this is no longer required for Lightroom 4:<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-06-Geoencoding.png\" width=\"580\" height=\"228\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_06_Geoencoding\"\/><\/div>\n\n<p>Then in this next monster section courtesy of my Metadata Wrangler plugin, to reduce space I strip all but\nexplicitly-desired metadata. I leave in basics of the exposure, the geoencoding stuff, copyright, and the like...<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-07-Metadata-Wrangler.png\" width=\"580\" height=\"2619\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_07_Metadata_Wrangler\"\/><\/div>\n\n<p>Then I have the &#8220;crop-for-iPad&#8221; plugin settings...<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-08-Crop.png\" width=\"580\" height=\"533\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_08_Crop\"\/><\/div>\n\n<p>As each image is exported, this section defines whether an on-the-fly device-specific crop will be done to the\nexported copy, and if so, what kind, and from what part of the image.<\/p>\n\n<p>The first area of this section indicates the target aspect ratio (the width\/height ratio of the target device). The\nplugin includes data on a number of devices from Apple, Amazon, Blackberry, HP, HTC, Motorola, Samsung, and more, but\nyou can also choose &#8220;custom&#8221; and enter your own width and height.<\/p>\n\n<p>The &#8220;<b>Crop Control<\/b>&#8221; area is where you indicate, with keywords and a default, whether a crop should\nbe taken for each image, and if so, from what part of the image. You can set things to your taste, but as illustrated\nabove, if a photo has the keyword &#8220;iPadNoCrop&#8221;, no crop is taken. If it has the keyword\n&#8220;iPadCropRight&#8221;, a device-best-fitting crop is taken from the right. And so on. If none of the keywords\nmatch, I've chosen to have it take a crop from the center.<\/p>\n\n<img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/crop-for-iPad\/keywording.png\" width=\"291\" height=\"282\"\nclass=\"raw img_right\"\nid=\"ikeywording\"\nindexhint=\"noindex\"\nstyle=\"margin-left:4em; margin-top:0; margin-right:0\"\/>\n\n<p>As illustrated at right, I've made a &#8220;Keyword Set&#8221; for use in the Library's &#8220;Keywording&#8221;\npanel that makes it easy for me to apply these. (The &#8220;PORTFOLIO&#8221; and &#8220;AnthonyBest&#8221; keywords are\nused in my workflow to indicate which photos to send to the iPad in the first place, as we'll see later in this\npost.)<\/p>\n\n<p>You can guess from the &#8220;iPhoneCropLeft&#8221; keyword that I have a matching set of keywords for the copies I\nsend to my phone, via another publish service set up almost identically to the one we're setting up now, but because the\niPhone's screen had a different aspect ratio, it may need different crops, and so that publish service uses a different\nset of keywords, and, of course, a different target folder.<\/p>\n\n<p>When using these kinds of keywords, it's cleaner to keep them internal to your Lightroom setup, so don't forget to\nedit each keyword (by selecting &#8220;Edit&#8221; from the keyword's context menu in the Keyword List panel) to\ndeselect &#8220;Include on Export&#8221;.<\/p>\n\n<p><b>A note about the crop:<\/b> the crop done by the plugin is <i>lossless<\/i> (does not reduce the quality at all)\nbecause the plugin uses the <a href='http:\/\/www.ijg.org\/'>Independent JPEG Group<\/a>'s most-excellent\n&#8220;<b>jpegtran<\/b>&#8221; program. The alternative is to convert the JPEG to pure image data, perform the crop, then\nreconvert back to a JPEG, all of which necessarily reduces the quality. So, it's gratifying that there's a lossless\nsolution available, but one technical side effect of how bits are fiddled under the hood is that a &#8220;bottom&#8221;\nor &#8220;right&#8221; crop might actually be shifted as many as 15 pixels away from the bottom edge or the right\nedge.<\/p>\n\n\n<p style='margin-top:40px'>Now we're back with additional sections from the overall Collection Publisher publish service. I want the images to\nbe regenerated (republished) if I change certain things...<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-09-Trigger.png\" width=\"580\" height=\"178\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_09_Trigger\"\/><\/div>\n\n<p id='renaming'>This next section on image renaming is the most complex of the entire setup:<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-10-Renaming2.png\" width=\"580\" height=\"182\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_10_Renaming2\"\/><\/div>\n\n<p>Lightroom's built-in file renaming seen earlier isn't powerful enough to do what I want, so I use this optional processing\nin the Collection Publisher to achieve my goals, which for my general portfolio images are:<\/p>\n\n<ol><li><p>An overall sort based on aspect ratio, such that all Landscape-oriented (wider than tall) photos are grouped\ntogether, and then all Portrait-oriented photos (taller than wide) are grouped. I want this so that someone flipping through my photos\nwon't have to keep flopping the device around to adjust for each photo's orientation.... they'll merely have to rotate the device\n     once when passing from one orientation to the other.<\/p><\/li>\n\n     <li><p>Within each group, I want images to be random. I don't want photos from one shoot or one season to get\n     clumped: even spectacular photos can get monotonous if all of the same ilk.<\/p><\/li>\n\n<\/ol>\n\n<p>The file-renaming rules in this section are the\n\n<a href='\/blog\/lightroom-goodies\/template'>standard template tokens<\/a> that my plugins use for all kinds of things,\nand in this case I use the sequence:<\/p>\n\n<p style='margin-left:3em'><b><tt>{AspectRatio=X,Y,Z}{UUID:Length=5}__{FILENAME}<\/tt><\/b><\/p>\n\n<p>The first token, <b class='nobr'>{AspectRatio=X,Y,Z}<\/b>, starts off the\nfilename with an &#8220;X&#8221;, &#8220;Y&#8221;, or &#8220;Z&#8221;\ndepending on whether the image is portrait, square, or landscape,\nrespectively. Being at the start of the image filename, this groups files\n(when sorting by filename) by aspect ratio.<\/p>\n\n<p>The next token, <b class='nobr'>{UUID:Length=5}<\/b>,\nessentially becomes five random characters. This causes a sort based on filename to be random within each group, yet maintains the overall grouping.<\/p>\n\n<p>Then there are two underscores, and finally the filename computed by the\nLightroom-standard file-naming section we saw earlier. I add this just so\nthat I can maintain the ability to know which image it is just by looking\nat the filename.<\/p>\n\n<p>The end result of this are filenames that don't look pretty,<\/p>\n\n<pre style='margin-left:3em'>\nXF4DC1__JF7_100620.jpg\nXF889C__JF7_101972.jpg\nXFB839__JF7_103866.jpg\nXFFB90__JF7_080212.jpg\nY4E322__JF7_077785.jpg\nZ00903__JF7_078691.jpg\nZ016C6__JF7_099880.jpg\nZ02EB6__JF7_083189.jpg\nZ039A4__JF7_040249.jpg\n<\/pre>\n\n<p>but they sort as I like: images are grouped by aspect ratio, and random within each group. If the display app allows\nsorting by image date as well, I can toggle between a random and a chronological display.<\/p>\n\n<p>So, that's it for the publish-service settings.<\/p>\n\n<p class='h' id='album-setup'>Album Setup<\/p>\n\n<p>After saving the initial publish-service settings, I'm left with a publish service with one default collection\nnamed &#8220;at root&#8221;. I don't need it, so I delete it.<\/p>\n\n<p>I then create a smart publish collection for each album I want on my iPad, which in my case at the moment is just\none for general nice pics (&#8220;Portfolio&#8221;), one for pics of my kid (&#8220;Anthony&#8221;), and one filled with shots\nof <a href='\/blog\/2012-01-23\/1932'>the Japanese archery event<\/a> I photographed last month (&#8220;\u901a\u3057\u77e2&#8221;).\nThe create dialog for each looks like:<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-create-collection.png\" width=\"690\" height=\"333\"\nclass=\"raw\"\nid=\"iiPad_workflow_create_collection\"\/><\/div>\n\n<p>Each is set so that it's its own album in the export folder hierarchy, and each is populated via keyword matching. In\nthe example, any image with &#8220;PORTFOLIO&#8221; as a keyword is included in the &#8220;Portfolio&#8221; collection, which becomes the\n&#8220;Portfolio&#8221; folder on local disk, and eventually on the target device.<\/p>\n\n<p>And that's it for setup.<\/p>\n\n<p class='h' id='image-selection'>Image Selection and Preparation<\/p>\n\n<p>The most difficult part of this entire process is selecting images to\ninclude in my portfolio, or, putting it more accurately, picking images not\nto include, since the gut instinct is to share everything. The few that\nmake the cut are directed to each album by assigning the relevant keywords\nthat I used in the various publish-service smart collections.<\/p>\n\n<div style='margin-top:0; padding-top:10px; text-align:center' class='img_right'>\n<img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-crop-preview.png\" width=\"466\" height=\"700\"\nclass=\"raw\"\nid=\"iiPad_workflow_crop_preview\"\/>\n<br\/>Crop Preview Tool\n<\/div>\n\n<p>As I add each photo, I need to decide whether to have it appear on the\ntarget device with a full-screen crop, and if so, which crop. On a Mac, my\ncrop-for-iPad plugin features a handy tool, shown at right, via the <span\nclass='nobr'>&#8220;<b>File &gt; Plugin Extras &gt; Preview Crop<\/b>&#8221;<\/span>\nmenu. It allows one to cycle through the possible crops for a given device,\nand optionally apply the keywords required to achieve the crop.<\/p>\n\n<p>A few notes about the crop-preview tool:<\/p>\n\n<ul><li><p>\n\n     It works on OSX only.<\/p><p>In order to build it, I take advantage of some\n     undocumented side effects I discovered in\n     Lightroom's plugin infrastructure, but they don't happen to work on\n     Windows. It's neither something good about OSX nor bad about Windows, just the way the luck fell.\n\n<\/p><\/li><li><p>\n\n     Clicking on the image cycles through the three crops (top\/middle\/bottom in the example).<\/p><p>\n     I'd like to have made it so that you click where you want the image or the crop, but I couldn't\n     figure out a way to make it work. Lightroom's plugin infrastructure is pretty limited in all areas,\n     but particularly with UI-related things.\n\n\n<\/p><\/li><li><p>\n\n     You can configure the color and opacity of the mask (shown blue in the example), as well as the color\n     of the border (shown yellow). I normally use a black mask, to mimic the black surround of the iPad.\n\n<\/p><\/li><li><p>\n\n     It's super convenient when the crop-preview command is mapped to a keyboard shortcut.\n     Choose &#8220;Keyboard&#8221; in &#8220;System Preferences&#8221;, then add an Application Shortcut with a Menu\n     Title of three spaces followed by &#8220;Preview Crop&#8221;. (The leading three spaces are required for it to work\n     because Lightroom adds them to get an indented presentation in the Plugin-Extras menu.)\n\n    <\/p><p>\n     I leave &#8220;Application&#8221; set at &#8220;All Applications&#8221; because I swap often between Lr3 and Lr4 (and for some things\n     I'm still testing even with Lr2).\n\n\n<\/p><\/li>\n\n<\/ul>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-cropkeyboardshortcut.png\" width=\"668\" height=\"397\"\nclass=\"raw\"\nid=\"iiPad_workflow_cropkeyboardshortcut\"\/><\/div>\n\n<p class='h' id='publishing'>Getting Images to the Device<\/p>\n\n<p>Any time I make a change to the service (add or remove photos, or edit\nphotos or their intended device-specific crops), I need to republish to\nlocal disk, then get the resulting images to the iPad.<\/p>\n\n<p>The former is easy, and it the same for any publish service: select the collections and hit the &#8220;Publish&#8221; button.<\/p>\n\n<p>Getting the images to the device is a separate step, and depends strongly on the device and the app used on the device.\nFor Apple's &#8220;Photos&#8221; app that I gave up on, you'd just publish to the same folder that iTunes syncs photos from, and you're done.\nBut for all the esoteric troubles mentioned\n<a href='\/blog\/lightroom-goodies\/ipad-howto'>in my earlier writeup<\/a>, I don't use the &#8220;Photos&#8221; app any more.<\/p>\n\n<p>If the app supports FTP, as <a\nhref='http:\/\/itunes.apple.com\/us\/app\/photo-manager-pro\/id393858562?mt=8'>Photo\nManager Pro<\/a> does, you can use the handy FTP client built into the Collection Publisher, near the bottom\nof the Publishing Manager:<\/p>\n\n<div class='ic'><img loading=\"lazy\" decoding=\"async\" src=\"\/i\/lr\/iPad-workflow-dialog-11-FTP.png\" width=\"580\" height=\"215\"\nclass=\"raw\"\nid=\"iiPad_workflow_dialog_11_FTP\"\/><\/div>\n\n<p>This allows a full sync... send new or changed photos, and delete ones\nthat are on the device but no longer in the publish tree. Prior to building\nthis, a full sync was a nightmare because I couldn't find anything to do it\nin one shot. Now it's a breeze.<\/p>\n\n<p>Another photo-viewer app that supports FTP is <a\nhref='http:\/\/itunes.apple.com\/us\/app\/widephotoviewer\/id392680077'>WidePhotoViewer<\/a>,\nbut there's a bug in Lightroom that stops this plugin from syncing to it\nproperly. The developer is looking into a workaround for me.<\/p>\n\n<p>If you're an app developer and you add FTP sync to your photo-display\napp, drop me a note and I'll include a mention of it here.<\/p>\n\n<p style='margin-bottom:60px'>Some apps allow Dropbox integration, and in that case you can just set\nyour publish root to a Dropbox folder, then access it from the app.<\/p>\n\n\n<!--TECH-->\n<div class=\"robots-nocontent\" style=\"border: 2px solid #FF8080;\n            float: right;\n            padding: 0 1em 1em 1em;\n            margin: 10px 0 1em 1em;\n            display: inline;\">\n<p style='white-space: nowrap'><b>My Tech-Related Photography Posts<\/b><\/p>\n<ul style='margin:0; font-size:80%'>\n  <li><a href='\/blog\/lightroom-goodies\/ipad-howto2'>My Lightroom-to-iPad Workflow<\/a><\/li>\n  <li><a href='\/blog\/lightroom-goodies\/'>Lightroom Goodies<\/a> (lots of plugins)<\/li>\n  <li><a href='\/blog\/photo-tech\/color-spaces-page1\/'>Digital Image Color Spaces<\/a><\/li>\n  <li><a href='\/blog\/other-writings\/online-exif-image-data-viewer\/'>Online Exif (Image Data) Viewer<\/a><\/li>\n  <li><a href='\/blog\/photo-tech\/focus-chart\/'>Jeffrey's Autofocus Test Chart<\/a><\/li>\n  <li><a href='\/blog\/photo-tech\/calendar\/'>Photoshop Calendar-Template-Building Script<\/a><\/li>\n  <li><a href='\/blog\/lightroom-goodies\/ipad-howto'>How to Prepare Photos for an iPad<\/a><\/li>\n  <li><a href='\/blog\/photo-tech\/nef-compression\/'>A Qualitative Analysis of NEF Compression<\/a><\/li>\n  <li><a href='\/blog\/2007-08-24\/554'>Tripod Stability Tests<\/a><\/li>\n<\/ul>\n<p style='font-size:85%; margin:10px 0 0 0'><a href=\"\/blog\/photo-tech\/\">more<\/a>...<\/p>\n<\/div>\n<!--\/TECH-->\n\n\n<p style='margin-top:0' class='h' id='dropbox'>Publishing From Multiple Computers<\/p>\n\n\n\n\n<p>At the moment, my photo archive is split among three different Lightroom\ncatalogs (photos older than about a year in a  Lightroom  catalog on my desktop,\nwith recent images in a Lightroom 3 catalog on my laptop, and the most-recent\nimages in a Lightroom 4 catalog on my laptop), and I'd like to be able to publish\nportfolio pictures from any of them to a common hierarchy.<\/p>\n\n<p><a href='http:\/\/dropbox.com\/'>Dropbox<\/a> is perfect for this. It syncs a\nfolder tree back and forth among multiple computers so changes in one are\nreflected in all the others. So I can add and remove photos on the desktop,\npublish them there, then do the same on my laptop and in the end I have all the\nphotos for the iPad on both machines. Then from either I can do the FTP sync to\nthe target app, and only the changes are sent over. It's a smooth workflow.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Three months ago in \"How To Best Export Lightroom Images to an iPad, iPhone, Etc.\" I wrote about my old workflow in getting my portfolio photos from Adobe Lightroom to an iPad. The setup and flow was much more complex than one might think it needed to be, mostly due to limitations and bugs with iTunes, but also due to some limitations in the Lightroom plugins I was using. I was happy to have eked out the best quality iTunes allowed, but the whole process felt horribly clunky.<\/p> <p>I've now solved many of the problems I ran into then, in [...]","protected":false},"author":1,"featured_media":0,"parent":864,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/1946"}],"collection":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/comments?post=1946"}],"version-history":[{"count":0,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/1946\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/864"}],"wp:attachment":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/media?parent=1946"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}