How to invoke the Adobe Bridge CC - Photo Downloader on any arbitrary folder

As you have seen in my post Digital photography workflow I use the photo downloader from Adobe bridge as the corner stone of my workflow. Sometimes, I am in a rush and I need to take a copy of what is in the memory card and keep it somewhere for safekeeping until I have time to process it. What I have to do then is once I am ready, copy the folder content that was stored for safekeeping into a new cleaned up memory card and start bridge to download the images.

Here is a technique so that you do not need this copy back (which can be slow if you are copying 32 GB of images back onto a memory card).

Let assume that you have copied the memory card content to a folder say

h:\backup\memory card from houston trip

what you need to do is to look into Windows Explorer for a drive letter not in use in your computer at the moment. Lets say this is drive P:. You type the following command at a command prompt:

subst p: "h:\backup\memory card from houston trip"

This will create a drive P: with the content of the original memory card. Then you type the following long command line (for Adobe Bridge CC, not sure if older version work the same) where P: represent your newly created drive with the subst command above:

"C:\Program Files\Adobe\Adobe Bridge CC (64 Bit)\photodownloader\Photodownloader.exe" module=photodownloader params mode=direct devType=volume priDevId="P:"

And voila! You should then see the familiar Adobe Bridge CC - Photo Downloader window. That's all folks.

Comments

Handling multipart form data in Spring 3.1

Introduction Multipart mime encoded is a format used to transmit binary and arbitrary data in 1 single HTTP request transaction. In this post, I will describe how to create and process multipart form data using Spring 3.1, the leading industry standard java application framework for creating Java web application. I will start the discussion from the user perspective by talking about two main use cases and will expand it by describing how these two use cases translate into 7 possible application system use cases. Use Cases Here are some use cases of this feature: A browser submits or uploads a file to a web server using an HTML page. This is by far the most common use case of the multipart form data feature. A multipart is required because the form data and the file are both included in the request body. A java program (a java application or servlet instance) sends multipart form data to a web server (most likely a web service). This is

Tutorial on how to write and run a javaFX 11 Spring Boot program using Eclipse

Since the decoupling of javaFX from the JDK (see http://openjfx.io ) it has become somewhat of a challenge to use javaFX with the new module capability since java 9. This tutorial is a brief roadmap between a java 8 javafx to the java 11 version. All code for this sample resides in https://github.com/marioja/javafx and can be imported into eclipse and should run as is. You can also do this manually following these instructions. First you need to use an eclipse that supports the java 11 execution environment (Eclipse 2018-12 at the time of this writing). Then you need to make sure you have a java 11 jdk installed(11.0.2 at the time of this writing). I downloaded openjdk11 and unzipped into a folder on my home directory (user profile on windows). Lets call this directory jdk-11.0.2. You should add the eclipse -vm argument in the eclipse.ini file to select jdk-11.0.2. Start eclipse and create a brand new workspace (one that does not exist). I called it javafx-tutorial. If

Put your WARs on a diet with Maven: Maven and skinny wars!

I have seen a lot of confusion and misunderstanding on what is and why use a java enterprise concept called skinny war . In simple terms , a skinny war is a WAR where some of its dependencies are moved from the WAR module WEB-INF/lib to the EAR lib folder . This post is specifically written to deal with skinny wars and does not explain or go into details which jars must be in the WAR class loader and which one do not have to . It is assumed that the reader is familiar with this concept and the concept of the WAR class loader versus the application class loader . Suffice it to say that typically, JAR that must be scanned by CDI usually belongs in the WAR class loader . Web fragments and jars with tag libraries are other candidates . Also, all test and provided scope artifacts must be specified in the WAR module as having maven remove them from the WAR does not make sense as they were never to be put there and having them in a deps POM file does not work . They will not be e

Mario Jauvin's blog

Search This Blog