syncing color tag changes
Hi,
working in a multi user environment where capture are taken on one machine, edited, tagged with a color and packed as EIP. They are then transferred to another computer where processing occurs. I am using rsync to transfer the files, and forcing a hash check and including the .cop, .cos and .cof files and preserving the folder structure. In other words, everything capture one sees on the "capture" station is being synced -- bit for bit -- to the "processing" workstation.
trouble scenario:
if i mark the file red, pack as EIP. It transfers fine and color tag is the same on both machines.
If, AFTER, i have already packed and set the color label, i change the color, i.e. from red to blue, the update to the color tag is not updated in C1 on the "processing" station.
If however, i quit and restart capture one, the tag is now back in sync -- i.e. the updated blue.
How can i force this to happen, or make it happen without forcing it, with our restarting C1?
thanks!
working in a multi user environment where capture are taken on one machine, edited, tagged with a color and packed as EIP. They are then transferred to another computer where processing occurs. I am using rsync to transfer the files, and forcing a hash check and including the .cop, .cos and .cof files and preserving the folder structure. In other words, everything capture one sees on the "capture" station is being synced -- bit for bit -- to the "processing" workstation.
trouble scenario:
if i mark the file red, pack as EIP. It transfers fine and color tag is the same on both machines.
If, AFTER, i have already packed and set the color label, i change the color, i.e. from red to blue, the update to the color tag is not updated in C1 on the "processing" station.
If however, i quit and restart capture one, the tag is now back in sync -- i.e. the updated blue.
How can i force this to happen, or make it happen without forcing it, with our restarting C1?
thanks!
0
-
Have you tried 'regenerate thumbs' , I think it's under File . I had a very similar problem and that worked for me. 0 -
You need Capture One to re-read the adjustments after your change. It does not do this dynamically. Regenerating the previews might help (it is basically not a preview issue but it apparently reads the adjustments again as well). Restarting the application will also do as you noticed. Changing folders and return to the originating one does probably help too (not tested).
The bottom-line is that Capture One was not designed to do this, so you always have to come up with a workaround.0 -
Could you not have Capture One create a sidecar XMP and then do a full sync to that XMP file on the other machine?
If all else fails, with the external XMP file you can always use the "Reload Metadata".0 -
tried all of the sidecar options, but nothing worked without restarting c1.
when i reloaded the metadata, it actually dropped all of the info and was blank.
feature request,
would love it, if in the future, all of that info, metadata, adjustments etc were zipped up neat and tidy in the EIP, and that when changes were made to an already packed EIP the file's modification time would be updated, thus allowing the most current version of that particular file to trigger a sync
--side note: pretty surprised that performing and md5 hash check to the source EIP did not trigger a sync, are adjustments made after packing not actually being written to that file?
is there a white paper out there on how the EIPs are actually "zipped" up?0 -
Bumping this as I'd love to hear and answer to this. [quote="NN634868622653107646UL" wrote:
tried all of the sidecar options, but nothing worked without restarting c1.
when i reloaded the metadata, it actually dropped all of the info and was blank.
feature request,
would love it, if in the future, all of that info, metadata, adjustments etc were zipped up neat and tidy in the EIP, and that when changes were made to an already packed EIP the file's modification time would be updated, thus allowing the most current version of that particular file to trigger a sync
--side note: pretty surprised that performing and md5 hash check to the source EIP did not trigger a sync, are adjustments made after packing not actually being written to that file?
is there a white paper out there on how the EIPs are actually "zipped" up?0 -
I've tried this workflow in the past and I've gotten the impression that Capture One caches your settings into the session. So if you externally change that data capture one doesn't re-read it. Enabling this ability in Capture one, to live update metadata as it changes would RADICALLY improve the super high volume and time sensitive work that many of us do. 0 -
[quote="Corey Riggle" wrote:
I've tried this workflow in the past and I've gotten the impression that Capture One caches your settings into the session. So if you externally change that data capture one doesn't re-read it. Enabling this ability in Capture one, to live update metadata as it changes would RADICALLY improve the super high volume and time sensitive work that many of us do.
Corey,
That sounds like a suggestion that would be a good candidate for creating a support case so that it gets official recognition and consideration by the C1 development team.
That said I'm not sure the application architecture is really likely to have any components that are intended for what is, in effect, a multi-user network environment and there could be a whole load of issues around record locking needs if a traditional database processing approach was to be taken.
Grant0 -
[quote="SFA" wrote:
[quote="Corey Riggle" wrote:
I've tried this workflow in the past and I've gotten the impression that Capture One caches your settings into the session. So if you externally change that data capture one doesn't re-read it. Enabling this ability in Capture one, to live update metadata as it changes would RADICALLY improve the super high volume and time sensitive work that many of us do.
Corey,
That sounds like a suggestion that would be a good candidate for creating a support case so that it gets official recognition and consideration by the C1 development team.
That said I'm not sure the application architecture is really likely to have any components that are intended for what is, in effect, a multi-user network environment and there could be a whole load of issues around record locking needs if a traditional database processing approach was to be taken.
Grant
I've brought it up several times with different people at Phase One. It's "not supported" and there isn't any way to know if they are interested in pursuing this feature.0 -
I've tried using xmp sidecars to sync rating too. And last time I tested it wasn't reliable. That was 6 months ago. Maybe it's better now. 0
Post is closed for comments.
Comments
9 comments