Anyone using Photo Mechanic?
I use Photo Mechanic for culling and rating images before converting with Capture One. Set up properly C1v6 shows the star rating and some colour tags. It works both ways. The star ratings don't refresh automatically in C1v6 but as soon as focus is moved to the next image up they pop.
The problem is that this is not working for me with C1v7 regardless of preferences set. I've raised a support case and they were very quick to respond and request images and xmp files. Supports last reply confused me slightly and I've asked for clarification but I think they were saying nothings wrong. Well its very wrong on my set up. Is anyone else using Photo Mechanic and having this problem?
The problem is that this is not working for me with C1v7 regardless of preferences set. I've raised a support case and they were very quick to respond and request images and xmp files. Supports last reply confused me slightly and I've asked for clarification but I think they were saying nothings wrong. Well its very wrong on my set up. Is anyone else using Photo Mechanic and having this problem?
0
-
Based on my experience, C1 7 is not compatible with PM. C1 can read the star rating from PM initially when importing but it can't write any changes back to the XMP file. And when you try to sync, C1 will erase all changes made in PM by writing 0 stars to the XMP file. 0 -
[quote="SamC" wrote:
Based on my experience, C1 7 is not compatible with PM. C1 can read the star rating from PM initially when importing but it can't write any changes back to the XMP file. And when you try to sync, C1 will erase all changes made in PM by writing 0 stars to the XMP file.
Thanks for your response Sam the galling thing is that at the moment I have C1 6 and PM happily talking to each other.0 -
I use FastPictureViewer to do a similar sort of thing that you talk about, and I write similar "sidecar XMP files" and it appears Capture One 6 and 7 are doing OK with them.
Yeah, just tested... seems OK.
FastPictureViewer allows you to change the format of the XMP metadata to mesh better with the next image processor along the line (they have Lightroom, iView, IDimager etc. formats). I don't recall changing the way I write the XMP file between upgrading CO6 to CO7. But maybe CO7 is enforcing something more strictly in the XML schema?
I have ALWAYS had trouble syncing metadata more than once in Capture One though.
If I decide to ever re-rate images, I basically hope I haven't made any adjustments, and start a new session so I can start over.
Otherwise, you might get the spinning "Auto-loading Metadata Pinwheel of Patience".0 -
Hi, I am very interested in finding some second party software in which I can make selects (star ratings) AND add a crop to the images, such that the rating and crop gets written to the XMP file, so that Capture one will read it, one I "Load Metadata" in capture one. Will Photo Mechanic or fast picture viewer do this. 0 -
[quote="NNN634405634999443050" wrote:
Hi, I am very interested in finding some second party software in which I can make selects (star ratings) AND add a crop to the images, such that the rating and crop gets written to the XMP file, so that Capture one will read it, one I "Load Metadata" in capture one. Will Photo Mechanic or fast picture viewer do this.
Rating yes, crop no.
Whatever program can do crop to XMP, CO7 won't read it from XMP.0 -
Since it doesn't seem possible that an XMP sidecar file can communicate a crop as part of its data to whatever program you are using to process raw files, is it possible to write that kind of data (crop) to an XML file, and is it possible to save out the metadata (including the crop) from a RAW file to an XML file. I'm not a tech genius but from what i've read, XML files can communicate info between systems pertaining to how they should operate, act, read, write, etc ... ?? I may be reaching here, but does anyone have any ideas to that end? 0 -
If capture one would cache more images in memory (in background) it would be a lot faster for culling and external applications would be less needed. 0 -
True, but when you are shooting 80 shots in a day, the problem is that you have to shoot so fast that it's virtually impossible for anyone to make selects in between shots without holding up the next shot, and thus slowing down the entire shoot throughout the day. So even if C1 could generate previews fast enough that you could cull your selects, you wouldn't have time in between shots to do so. At least not on this kinds of monster e-commerce shoots where you are shooting 80 - 100 shots a day. 0 -
To raise a point in reference to the original topic; I think part of the problem is that C1 is SO proprietary that it rarely functions seamlessly with other apps. Who knows, would it be wild to think that perhaps the people at Phase One deliberately bug each successive generation of C1 in order to prevent users from creating workflows that don't entirely rely on C1 infrastructure. Much like Apple. 0 -
[quote="NNN634405634999443050" wrote:
True, but when you are shooting 80 shots in a day, the problem is that you have to shoot so fast that it's virtually impossible for anyone to make selects in between shots without holding up the next shot, and thus slowing down the entire shoot throughout the day. So even if C1 could generate previews fast enough that you could cull your selects, you wouldn't have time in between shots to do so. At least not on this kinds of monster e-commerce shoots where you are shooting 80 - 100 shots a day.
Please try the "Auto pause" feature from Camera -> Auto-select new capture -> Auto-pause
This way a new capture will not interrupt a customer looking through the pictures.0 -
[quote="Christian Gr" wrote:
[quote="NNN634405634999443050" wrote:
True, but when you are shooting 80 shots in a day, the problem is that you have to shoot so fast that it's virtually impossible for anyone to make selects in between shots without holding up the next shot, and thus slowing down the entire shoot throughout the day. So even if C1 could generate previews fast enough that you could cull your selects, you wouldn't have time in between shots to do so. At least not on this kinds of monster e-commerce shoots where you are shooting 80 - 100 shots a day.
Please try the "Auto pause" feature from Camera -> Auto-select new capture -> Auto-pause
This way a new capture will not interrupt a customer looking through the pictures.
Great idea, I worry that it might crash c1 running on an older OS, ???
Also, I feel like with that many shots (and it goes quick) you will quickly end up significantly behind the shot count by several shot numbers. I do like the idea of using that feature; never really used it before.0 -
[quote="NNN634405634999443050" wrote:
[quote="Christian Gr" wrote:
[quote="NNN634405634999443050" wrote:
True, but when you are shooting 80 shots in a day, the problem is that you have to shoot so fast that it's virtually impossible for anyone to make selects in between shots without holding up the next shot, and thus slowing down the entire shoot throughout the day. So even if C1 could generate previews fast enough that you could cull your selects, you wouldn't have time in between shots to do so. At least not on this kinds of monster e-commerce shoots where you are shooting 80 - 100 shots a day.
Please try the "Auto pause" feature from Camera -> Auto-select new capture -> Auto-pause
This way a new capture will not interrupt a customer looking through the pictures.
Great idea, I worry that it might crash c1 running on an older OS, ???
Also, I feel like with that many shots (and it goes quick) you will quickly end up significantly behind the shot count by several shot numbers. I do like the idea of using that feature; never really used it before.
It shouldn't crash, but if it does, please do tell us through a support case.
Whether or not it can keep up, depends on many factors. The camera connection speed, disk I/O speed and CPU speed.
My best advice is to try it out, and then identify the slowest link, replacing if possible.0 -
how do you get more then 2 rulers to show up in the grid? 0
Post is closed for comments.
Comments
13 comments