batch queue portability?

Hi,

I have a question regarding processing files on separate machines. If I set up a session on one machine, with exposure corrections/renames, etc, and I start batch queue to process files, I want to be able to continue processing this session on another computer. If I simply move the session (via the original external capture drive) to another computer, the batch queue does not follow. I realize this allows the queue (which may encompass multiple sessions) on the original machine to continue processing multiple sessions as long as they are still on the computer.

Theory:

(For simplicity, this assumes session folder is setup and remains on an external drive, which is accessed by multiple computers. The session folder is not copied to/from this drive to the source/destination computers. Same version of C1Pro on all machines.):

Send images for processing to batch queue in c1p. Disable batch queue in C1pro. Delete any processed jobs from queue. Go to: user folder>library>application support>phase one>batch queue on source computer and copy this folder to the portable drive to install on the destination computer in corresponding location (no images remaining to be processed on destination computer prior to overwrite). Open session on new computer, enable queue.




•Should this work? I have not yet tested this, I will later (probably not today).•

The batch queue folder contains a Batch Job List.xml file. Is this simply a list of what job #s need to be run, with no information on the jobs in particular? Is it portable & connected to the session, or can it run only on source computer?

There are .job files which I assume refer to the individual image files, but these .job file names on the machine I'm looking at do not match any image file names in the process queue list within open C1Pro, nor any file names on hard drive. Do these .job files contain all of the information about processing parameters for the individual images that is not otherwise saved to the individual session? Will the images be processed with any scale/profile/icon/watermark, etc that were chosen on the source computer when they were sent to queue. If the destination computer does not have the same output destination (ie, srgb jpg, tiff rgb, etc...) enabled (or even setup), will destination computer nonetheless process according to the parameters chosen for output on source computer when sent to queue?

If destination computer is simply a process drone, and I want source comp to reflect current process status (and I have not done any further work subsequent to porting the queue): after processing complete on destination computer, move queue folder back to source computer (if nothing has been concurrently added to source batch queue), or delete original batch queue on source computer (in C1, or just trash the queue folder?

If I want to start a new batch queue (for a new session) on source machine, and do not want to return the original batch queue that I have previously ported to destination computer, what is the best way to do this? Should I delete all the images from the batch queue within C1? Erase the batch queue folder, and let C1p write a new, empty one (will it?)?

Has anybody done this? Any problems doing it?

Feature request: *batch queue export*. Have option to tie queue either to 1: boot computer (as it is now), which is great for multiple sessions/background processing, or to 2: individual sessions, which would make processing off-site, or by different computer/tech sometimes easier. Make batched .job names match the image files that they reference. Should I be asking for feature requests in the forums like this, or what is the current m.o. ? I have some others...

Thanks,
MrJesse