A few more observations, now that I also use it on a 15" Retina MacBook.
They must be a bit schizophrenic...
While most keyboard shortcuts translate easily between Windows and OS X, just by substituting CTRL with CMD, for copy & paste it is a disaster.
Windows: CTRL-C & CTRL-V not matter what the subject is, settings or text.
Mac: CMD-C & CMD-V for metadata text, SHIFT-CMD-C & SHIFT-CMD-V for image settings
and in contrast to the rest of the shortcuts, this can not be redefined.
Utterly idiotic.
I finally understood how to properly configure the output image naming:
In the recipe, one can specify s sub-folder and a sub-name.
The sub-folder, relative to the image source is used without a problem.
But the sub-name is ignored. One has to use the token subname in the output name tool to activate the sub-name in the recipe. I have no idea what those guys are smoking, but it definitely is not something I ever want to try....
Similarly, when using the download function to copy images from the card, there is a job name that can be specified for the file name. But there is now way to use that in the directory name, why?
Why do I have to scroll in a small text filed to put in my project name?
The generation of masks from the color editor is still wonky (v 9.01). Lets hope they fix it in the next update.
In a previous post I mentioned that on Windows I could not select scripts for post processing. On Macs it is basically the same stupidity, only if it is named .app it is selectable in the menu.
In contrast to the brain dead Lightrooom catalogs, one can copy a project directory easily between machines and resume working on the other box. If the images are there already on both boxes, just syncing the C1 settings directory is sufficient...
cheers
afx