C1 v5.2.1 LCC problems
To Whom Can Help,
I am currently running v5.2.1 and use the LCC option daily. I've always had problems when processing files using this feature (the LCC will often drop even when packing the files as an EIP). I've come to accept this flaw and will take the additional time to reprocess those files.
[NOTE: The LCC will drop for, seemingly, a variety of reasons. Starting and stopping of the Processing Queue, renaming of images after shooting and/or having images in the Browser but still loading a style.]
Recently, I processed some files for a coworker and came across a more discreet problem. When locating my coworker's files on our server (using the LIBRARY TAB in my C1 software), I noticed the LCC was not attached. Luckily, we shoot a white card as part of our process and I was able to create a new LCC profile and apply it to the images I needed to process. Once we have processed out the images, we create small JPEGs from the processed files to make sure the LCC "sticks". If you thumb through the files quickly, it appears as if the LCC option worked. Upon further review, I noticed the RGB values drop 10 points on about 10% of the images. This sounds like a complete drop of the LCC option but because we run into that problem daily, we know that the RGB value difference between an image with and without the LCC option is far greater than 10 points.
If anyone knows why this happens or how we can fix it, I'd be greatly appreciative. If not, the only option moving forward would be creating images without the use of the LCC option.
I am currently running v5.2.1 and use the LCC option daily. I've always had problems when processing files using this feature (the LCC will often drop even when packing the files as an EIP). I've come to accept this flaw and will take the additional time to reprocess those files.
[NOTE: The LCC will drop for, seemingly, a variety of reasons. Starting and stopping of the Processing Queue, renaming of images after shooting and/or having images in the Browser but still loading a style.]
Recently, I processed some files for a coworker and came across a more discreet problem. When locating my coworker's files on our server (using the LIBRARY TAB in my C1 software), I noticed the LCC was not attached. Luckily, we shoot a white card as part of our process and I was able to create a new LCC profile and apply it to the images I needed to process. Once we have processed out the images, we create small JPEGs from the processed files to make sure the LCC "sticks". If you thumb through the files quickly, it appears as if the LCC option worked. Upon further review, I noticed the RGB values drop 10 points on about 10% of the images. This sounds like a complete drop of the LCC option but because we run into that problem daily, we know that the RGB value difference between an image with and without the LCC option is far greater than 10 points.
If anyone knows why this happens or how we can fix it, I'd be greatly appreciative. If not, the only option moving forward would be creating images without the use of the LCC option.
0
-
I can't say I've ever heard of such a thing but if you create a support case we'd be interested to know more. However, one thing about your description sticks out as a possible reason for all the trouble you've reported with the LCC... [quote="NN164622UL" wrote:
When locating my coworker's files on our server...
Since the LCC would be stored on the Local Machine (where Capture One is installed) and the RAW files on a server, their ability to flawlessly find each other is greatly diminished. If you apply LCC's, Edit and Process on a local drive (the same that Capture One is installed on) is the LCC still a headache?
Aside from that I guess I'm a bit surprised by your post, only because I use LCC frequently and haven't had, or come to accept, issues in any aspect. Sure I have suggestions for improvement, but no conflicts when it comes to processing or application.0 -
This is what "import" in the LCC drop down menu is for.
LCC-profiles are stored in two locations:
1.) in the settings folder of the respective session (session folder -> capture one -> settings50)
2.) ~/library -> application support -> capture one -> lcc profiles
If there is an lcc profile in a session but the respective lcc profile is not stored on the local drive (~/library/application support ...) you can import the said lcc profile simply by using the "import" command from the LCC drop down menu. The lcc profile be copied to the local folder then.0 -
Hey Guys,
Thanks for the response. Drew: You said, "Since the LCC would be stored on the Local Machine (where Capture One is installed) and the RAW files on a server, their ability to flawlessly find each other is greatly diminished."
According to the USER GUIDE in v5.2.1 and the earlier v5.2.0 (in Capture ONE > Help> Capture One User Guide), it says the "Enhanced Image Package, is a convenient way of packing your master file for a true Capture One user based workflow. The image file will be seen exactly as you created it. The original untouched RAW file will be packed with your setting file, ICC and LCC profile." It goes on to say "When the .EIP is opened by Capture One on your clients computer the .EIP will be exactly the same quality and look you created – as the .EIP merely is the original RAW file and the relevant settings files. The .EIP is cross platform, so you do not have to worry about PC/MAC issues."
If this is true, I should of seen the same image that my coworker created, right?
Later you asked, "If you apply LCC's, Edit and Process on a local drive (the same that Capture One is installed on) is the LCC still a headache?" Unfortunately, this isn't an option for us. We shoot roughly 1200 images a day and process throughout the night. We fill up space pretty quickly and have to move our EIPs to a server almost daily. We also rotate computer stations monthly.
For us, the bigger issue is archiving. If we are already running into problems with this and it's only a month or two after taking the photograph, what will happen if have to pull something from tape a year from now?0 -
The issue with EIP is ... it's not compatible.
EIPs created with prior versions of C1 are not compatible with the current version of C1 and EIPs created with V6 won't be read correctly by older versions.
EIP might be a good idea... but...0 -
[quote="thowi" wrote:
🤓
The issue with EIP is ... it's not compatible.
Is this based on opinion or experience?0 -
[quote="Drew " wrote:
at a certain time you've changed something... if I remember correctly. I think with V4.6 (or 4.8 )... EIPs created prior to that version where not compatible anymore (re LCC). But as I don't use EIP I don't remember exactly which version it was. Somewhere I have 3 EIP files (containing LCCs) created with 4.5 or 4.6 (or so)... and the LCC setting doesn't work anymore (the setting is checked, but the color shift is not corrected).[quote="thowi" wrote:
🤓
The issue with EIP is ... it's not compatible.
Is this based on opinion or experience?0 -
[quote="Drew " wrote:
[quote="thowi" wrote:
🤓
The issue with EIP is ... it's not compatible.
Is this based on opinion or experience?
Drew,
I'm having the same issues with LCCs not staying in the EIPs, so I opened a support case regarding this same issue (Case #79397) to which PhaseOne replied:
"Hi Mike,
Please be sure you are using Capture One 5.2... earlier versions of Capture One may not have had the full LCC implementation in EIP.
Best regards,
Phase One support"
Unless I'm missing something, EIP files are clearly not standard among different versions. 🤓
And on top of all of this, I can always redo the LCC on my old files, but right now I'm having problems with files that were shot yesterday on the same version of CaptureOne 5.2.1- the manual says that the LCC files should travel within my EIPs so that my clients can see exactly what I do. This isn't happening.0 -
[quote="mikepucher" wrote:
"...Please be sure you are using Capture One 5.2... earlier versions of Capture One may not have had the full LCC implementation in EIP..."
Unless I'm missing something, EIP files are clearly not standard among different versions. 🤓
EIP is standard. What changed is the LCC's integration with EIP. The format has not changed, we simply improved it as it was pointed out that an "All inclusive File Format" without an associated LCC is not exactly "All" inclusive. An EIP created way back when can be accessed opened and used today just as it was then with nothing lost, only gained.0 -
[quote="Drew " wrote:
[quote="mikepucher" wrote:
An EIP created way back when can be accessed opened and used today just as it was then with nothing lost, only gained.
Drew… download this EIP (from May 2009):
http://www.captureintegration.com/downl ... 10fall.eip
(source: http://www.captureintegration.com/tests/phase-one/ )
When you are opening the EIP in C1 the LCC setting is checked but color cast is not corrected.
You have to unpack the EIP (NOT in C1… rename it to ZIP and unpack it on the desktop or so), go to the extracted settings folder and copy the LCC setting file to the local LCC profiles folder. Restart C1. First now you can use the LCC profile (LCC->Legacy).
So the good news is C1 actually can read the LCC setting file. It just doesn't do so straight from the EIP.0 -
From the above posts, it sounds like there are still issues with LCC. The question moving ahead: what is Phase One going to do to resolve this issue without breaking what the users have already created (and please don't say upgrade to v6)? 0 -
[quote="Mat Fretschel" wrote:
not exactly with LCC.
From the above posts, it sounds like there are still issues with LCC.
Only with LCC in conjunction with EIP.0
Post is closed for comments.
Comments
11 comments