p.3 #2 · Capture One - importing and editing problems
The Capture One support team has replied. They suggested that I should delete the user.config file. I did so, and the problem remains.
I tried regenerating previews: the problem remains.
tntcorp1 wrote:
during the sw install, were you prompted to customize or choose the layout of the workspace?
I don't think I have the browser thumbnails mixed up with the main edit window. I can place the browser thumbnails left, below or to the right - this shows that I'm moving the browser and no other part of the workspace.
p.3 #3 · Capture One - importing and editing problems
Termite wrote:
The Capture One support team has replied. They suggested that I should delete the user.config file. I did so, and the problem remains.
I tried regenerating previews: the problem remains.
It’s disappointing that they didn’t ask you to send them a copy of a generated .cop preview file so they could see what resolution it actually is. These files appear to be in a proprietary image format. Presumably the engineers at Capture One have a tool to inspect them, but the support person you got wasn’t an engineer. I’m unsure why the software industry thinks this is acceptable – if I take my car to the dealer with a problem, I expect a mechanic to look at it, not the receptionist.
Can you A/B test:
• your computer?
• your graphics card, if you can’t change the whole computer?
• your monitor? A 4K television should work, although there may be practical problems moving the computer close enough, and you will need an HDMI connection.
I know it’s reporting that it’s generating them in high res, but clearly it’s not. Perhaps one part of Capture One decides on the resolution to generate, but then the bit that actually does the generation asks the monitor what resolution it has and gets back a stupidly low value. There are many monitors out there that don’t respond to such “EDID” queries correctly.
And, have you tried with a new, empty catalogue? At least on macOS, the .cop files are actually in the catalogue. (A bad design, IMO, since they get needlessly backed up.)
p.3 #4 · Capture One - importing and editing problems
Meanwhile, I have received some other suggestions from Capture One support, but the problem remains.
I don't rule out some kind of mistake on my part. Perhaps this stubborn problem is just one small setting gone wrong, but I don't know what to do.
melcat wrote:
And, have you tried with a new, empty catalogue?
Yes, several times. Also, I have checked the size of the raw files in the CO catalog; they are ~20 MB, as they should be.
I'm not sure what you mean by A/B testing. The same raw files open in full resolution in Lightroom and Photoshop, so the graphics card and other components seem to work fine.
p.3 #5 · Capture One - importing and editing problems
Termite wrote:
I'm not sure what you mean by A/B testing.
I mean changing one thing at a time while keeping everything else the same. Maybe in Swedish it’s more like “controlled tests”. So, if I think the monitor might be sending back incorrect EDID information, an A/B test is to change the monitor and nothing else. If I were also to change the software in the test to Lightroom I couldn’t be sure that Lightroom didn’t have a workaround for a monitor bug, that Capture One doesn’t have.
The same raw files open in full resolution in Lightroom and Photoshop, so the graphics card and other components seem to work fine.
Suppose Windows has two different OS calls to get the monitor resolution. Suppose that Call 1 works but Call 2 doesn’t with this particular monitor, graphics card and driver. Now suppose Lightroom uses Call 1 – it will generate the correct previews.
But now suppose the Capture One engineer who wrote the settings dialogue used Call 1 to display the resolution: you look at it, and say it’s OK to use the monitor resolution, and Capture One writes into its config to use the monitor resolution. But another Capture One engineer wrote the code to actually generate the previews, and they use Call 2 to retrieve the monitor resolution. And Call 2 is buggy in this driver and sends back 320 × 500. It exactly matches your bug, and it’s why it would be nice to know exactly what resolution those .cop files are.
p.3 #6 · Capture One - importing and editing problems
I’ve had a poke around inside one of my catalogues at a .cop preview file. The Unix "file" utility says it is a JPEG XL file. Wikipedia says that is an open file format, that the normal extension is .jxl, and that macOS Sonoma can display it. Encouraged, I made a copy of it with a .jxl extension and tried to open it. Apple Preview and Apple Safari, under Sonoma, couldn’t. But Affinity Photo could, although it saw only the thumbnail. However, its metadata panel said the image is 5120 × 3413. The long side exactly matches the monitor resolution, so this seems to be correct.
You can find these files under the Caches/Previews subdirectory (folder) inside the catalogue (assuming the catalogue layout is the same on Windows as on macOS), and then subdirectories by year, month, day. Copy one out somewhere and change its extension to .jxl. Then try opening that in Photoshop, Windows Explorer and whatever else you have to find the resolution. If it is stupidly low, you have proof the preview generation is wrong, and that is definitely a Capture One bug if it isn’t as shown in the preferences. If it is correct, it is some kind of display problem.
p.3 #7 · Capture One - importing and editing problems
melcat wrote:
I mean changing one thing at a time while keeping everything else the same.
Got it - but I only have one laptop and no other screens, so not much possibility of A/B testing with other equipment. All I can say is that all other programs are working at the right resolution.
Capture One is a little more tricky than I thought. Raw files are copied to a folder which I have created on my desktop, but the .cop files of the same images are located in another folder: Images/Capture One catalog/Caches/Previews ...
I opened the .cop file like you described, and it's 3840 x 2560 pixels, the right resolution for my screen. In Lightroom the same raw file displays as it should.
Back to square one, I guess. Though it feels more like square zero.
Hm, one more thought: should the .cop files folder be in the same main folder as the catalog with the raw files? Could that be the problem?
p.3 #8 · Capture One - importing and editing problems
Termite wrote:
Hm, one more thought: should the .cop files folder be in the same main folder as the catalog with the raw files? Could that be the problem?
It shouldn’t matter. I have the catalogues in a different directory from my images, on the same volume. Plenty of people put the catalogue on a fast internal SSD and the images on a slower drive. On macOS, the catalogue is just a directory with a .cocatalog extension.
I wonder whether Capture One is running out of GPU memory for display. The usual advice for that is to reboot the machine, make sure nothing else is running, and then start the program again.
p.3 #13 · Capture One - importing and editing problems
@melcat: it's exactly what the op is experiencing; e.g. the wrong file is being displayed in the preview screen. and a preview refresh didn't help because low res thumbnails remained in the preview screen.
i don't shoot fuji, if the camera has applied a film simulation, capture1 automatically applies the corresponding picture profile during import. perhaps this could be a factor.
p.3 #14 · Capture One - importing and editing problems
Hello all,
Sorry for not replying earlier. Windows, Capture One and my graphics card are all updated. I did the latest update today, and I still have the same problems.
The Capture One support team has promised to get back to me with new solutions; I will let you know what happens.
tntcorp1 wrote:
if you send me a raw fuji file, i can try importing it, as long as my version supports your camera.
pm me and i can give you my email.
I don't think there's anything wrong with my raw files, since they open as they should in Lightroom, but a PM is on the way.
Also try importing a large jpg and a different raw file. See if they both do the same thing.
Previews are set to the correct size (the same as my screen resolution). Importing a jpeg gives me the same problem. I also tried switching the colour profile - the problem remains.
p.3 #17 · Capture One - importing and editing problems
Have you tried running C1 as an Administrator? You should (I think) have Admin privs as the User but I believe running a program as an Admin might be a little different.
Start icon
Find the PS icon and right click on it
Select More
Select Run as administrator
p.3 #18 · Capture One - importing and editing problems
mcbroomf wrote:
Have you tried running C1 as an Administrator? You should (I think) have Admin privs as the User but I believe running a program as an Admin might be a little different.
I tried it right now, and I still have the same problem.
I am in contact with Capture One support, but so far they have not managed to solve the problem.
