Black Previews on 7.1
I have "upgraded" to C1 v7.1.
Excellent - its not crashing on every import now but...
In session mode, when I browse some folders, I have now up to 50% of my preview thumbnails showing as a black image. If I create a clone using "New Variant", the correct original preview shows up - it does not if I select "Clone Variant". This of course means I lose all adjustments for the image. I have tried selecting the image(s) and using the file menu option FILE->Regenerate Previews, but this does not seem to do anything. Does anyone know what is causing the problem I am having and how can I fix it?
Just about at the end of the line with C1 as I am losing too much time and productivity with one issue after another.
Excellent - its not crashing on every import now but...
In session mode, when I browse some folders, I have now up to 50% of my preview thumbnails showing as a black image. If I create a clone using "New Variant", the correct original preview shows up - it does not if I select "Clone Variant". This of course means I lose all adjustments for the image. I have tried selecting the image(s) and using the file menu option FILE->Regenerate Previews, but this does not seem to do anything. Does anyone know what is causing the problem I am having and how can I fix it?
Just about at the end of the line with C1 as I am losing too much time and productivity with one issue after another.
0
-
This has come up in the past and the advice offered has been to do with turning off the use of OpenCL.
If you use the search facility you will find a list of posts referred to and hopefully you can pick those nearest to your situation to check for possible resolutions. Bear in mind that OpenCL is a developing standard and interaction between the varioous pieces of softeware and hardware involved may take a while yet before everything can be excpected to be "stable".
As I recall from some advice posted earlier C1 does not always make use of OpenCL and this might well explain the seemingly odd matter of some of your previews being OK and others not OK. Some adjustments to an image automatically mean that all processing is done in the CPU with no inolvement of the graphics card and therefore no OpenCL use.
Whether this is the full story in your examples remains to be seen but setting "Use OpenCL" to "Never" should help you to identify if any other factors are involved. However, based on your observations about creating variants the pattern you have identified seems to fit with the OpenCL problem diagnosis.
Worth a test. I would be interested to hear about the results.
Grant Perkins0 -
Hi Grant,
thanks - I already have the preferences for Use OpenCL set to "Never" since the release of v7 as it was so unstable with it on. This "black problem" has only occurred for me since I upgraded to V7.1 Most of the time, I cant even get to the preference settings as the general tab displays correctly maybe 5% of thee time - I have reported this - something to do with the 15" retina dimensions.
Any other thoughts?0 -
[quote="LANEWAY" wrote:
Hi Grant,
thanks - I already have the preferences for Use OpenCL set to "Never" since the release of v7 as it was so unstable with it on. This "black problem" has only occurred for me since I upgraded to V7.1 Most of the time, I cant even get to the preference settings as the general tab displays correctly maybe 5% of thee time - I have reported this - something to do with the 15" retina dimensions.
Any other thoughts?
Hi Mark,
Yes I read your comments on the other post shortly after made the suggestions here.
Going back to basics - as I tend to do when I remember to ... more to prompt ideas than to expect an instant result!
Common factors:
What is common between the black and the non black previews?
Different camera?
Different in camera resolution for the files?
Any other in camera settings that may not be supported?
Different processing engine? Are any of the files from an earlier version (5/6?) or an earlier release of 7?
Different preview resolution set when the preview files were created? (Not sure if the preview size would be something carried over by cloning bit not by a new variant. Easy to check I guess.)
More likely possibilities perhaps, in view of the variant result differences;
SOmething to do with one or more of the adjustments applied?
I would be thinking maybe in terms of local adjustment, or perhaps colour or maybe a style, preset or lens correction (that may be something indocated by file similarity assessment of course.)
Maybe an output profile set somewhere?
At the back of my mind is a thought that says we had something very like this a short while back but I can't remember which thread it was in.
I'll try another search and see what comes up.
Grant0 -
Hi Grant,
good thoughts. I had a look, but the "black previews" are right next to frames that are working correctly. All same camera (Canon 5DmkIII) and no specific lens. All images are version 7 engine and all were imported in versions previous to 7.1
None of the images appear to have star ratings or any adjustments showing, but I am not sure that they were like this or I have lost the adjustments and ratings & etc. There will be 1 or more black frames between a series of almost identical frames, So - seems to be random - not very helpful.
Interesting update: I loaded the directory into the new Media Pro 1.4 and the image raw previews show correctly. If I select them all and press command-B for rebuild items, then the larger previews show up (I have Media Pro set to show bigger previews) except that the previews go black that are black in C1. This could be just because Media Pro is using the same V7 code.
Mark0 -
The easiest workaround is the following:
1. Import all pictures
2. If the "black previews" appear, save the catalogue and close it.
3. Close COne
4. Open COne
5. Open the catalogue
6. All previews should now be displayed
7. Missed ratings and other data are now visible and selectable
saludos redondos -
tom0 -
Thanks Thomas, will try that. Also, just had a response from Technical Support which suggested moving the white balance slider - I reset the WB to "As shot" which showed the preview again. There is obviously a bug in the rendering code which I have asked for a timeline for a fix as I dont have the time to invest in fixing the thousands of images. We will see. 0 -
Hi Mark,
I checked the WB issue with different raw-files from different Nikons, Canon 5D MKII, Leica M8, Sony Nex3, and Panasonic G1.
The presets differ with every different camera,that means, that the WB presets are related to the camera type. Every model is provided with different values in K and tint.
Nikons - D50, D80, D200, D300, D700, D3 are in a Range between 5100 K to 5500 K with a variety in tint ranging from -8 to +5.
5D Mk II is 5150/5
Leica M8 is 5200/0
...
Another hint might be, that some models offer settings that are called Incandescent/daylight - white: D700 eg uses values 4853/-1.9.
I made a series with a D300 & Nikkor 180/2.8 ED - a friend used a D700 & Nikkor 180/2.8 ED.
Fortunately both lenses were seemingly from a similar series. The recorded WB values to the same subject from the same angle of view at the same time differ in values that cannot be measured in Mired - D300 measured 2690 K, while D700 measured 5050 K. Take care that these are the values that are read out by COne, which does not necessarily mean that these are the "correct" values. The pictures look nearly the same in COne and in Nikons Capture NX2 - despite the indicated different values!
---
I am not sure if COne reads out "some" values or makes guesses or interpolations. So check out the pictures with Canons DPP if you have installed it and do a cross check. I did this with NX2 and there the daylight settings are exactly 5200 K for both files D300 and D700, but applying the predefined values in COne indicated different values, while the pictures have a similar look and curves.
Maybe COne does the same as Adobe with ACR. Adobe never licensed the the Nikon SDK's but tries to get the values that cannot be read out by reverse engineering the settings.
---
Having detected this, I would not bet that the results may differ even if the values are completely different. From having detected this I still refuse to believe in those values - numbers are just numbers and even if they are "indicated" different, the results might be equal :-==)))
---
... and btw: COne does not indicate the ISO values of all different files! it's just "ISO: ---"
saludos redondos -
tom0 -
Besides my last long post:
Why don't you just batch the WB values of your need to every collection of pictures? This does not take that long - it might be one or two cups of coffee or tea?
saludos redondos -
tom0
Post is closed for comments.
Comments
8 comments