Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Export to JPEG occasionally produces corrupt files

RichardT
I have been getting this problem intermittently with both Capture One 7.x and 8.x.

I am currently running Capture One Pro 8.1 64 Bit - 8.1.0.200 (b7b4efd) on Windows 7 Home Premium with Sp1.

A typical sequence goes like this:

1. Start Capture One using my only catalogue
2. Import some Canon raw images from 7D Mk II, 40D or G1X using "Current Location".
3. Edit the images including sharpening, clarity, exposure, high dynamic range and levels. Sometimes including straightening and/or crop.
4. Colour tag the images I want to export.
5. Set filter for the appropriate colour tag.
6. Either select a single image, or use Ctrl+A to select all the filtered images.
7. Right-click on a selected image in the Browser and select Export -> Variants...
8. Set the Export Location to the appropriate folder.
9. Under Export Naming, set Method to "Text and Tokens" and Format to "Image Name".
10. Set Format to JPEG and Quality to 92 (say).
11. Set Scale to Long Edge (Never Upscale) and 1024 px.
12. Click the Export button.

The operation always produces the "Files Exported" message, there is never any error message.

However, when I try to open some of the exported images in Windows Photo Viewer it displays the message "Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted, or is too large."

The corrupt files are typically 8KB or 12KB in size (valid exported files for these settings are typically 300 - 600KB).

When multiple raw files have been selected, the operation can produce a number of valid JPEG files and a number of corrupt files. Typically about a third might be corrupt, but the ratio varies.

If the export operation is repeated without changing any settings, the same corrupt files are produced.

Sometimes (rarely) I have found that just changing the JPEG quality e.g. from 92 to 90, will cure the problem. However this does not always work.

If I shut down Capture One and restart it, the export operation is usually successful the next time.

Sometimes I have to reboot the PC before I can get Capture One to successfully export all the images.

The problem does not happen all the time. I can go for several days without seeing it at all. The suddenly another day it can start happening again.

After I upgraded to v8 it didn't happen for a while and I thought it had been fixed, however it has since started to happen again.

Unfortunately I can't see any common conditions for when the problem occurs, it just seems random to me.

Is this a known bug?
0

Comments

22 comments

Date Votes
  • SFA
    Have you verified the catalogue recently?

    One option might be that there is an internal "corruption" somewhere in the database that sometimes comes into play and sometimes does not. When it does you may not get all of the edits deployed as you expect them to be deployed.

    Beyond that ... can't help much I'm afraid. I don't use catalogues and I "Process" rather than "Export".

    However I don't recall ever seeing a problem like the one you describe.



    Grant
    0
  • RichardT
    [quote="SFA" wrote:
    Have you verified the catalogue recently?

    One option might be that there is an internal "corruption" somewhere in the database that sometimes comes into play and sometimes does not. When it does you may not get all of the edits deployed as you expect them to be deployed.

    Beyond that ... can't help much I'm afraid. I don't use catalogues and I "Process" rather than "Export".

    However I don't recall ever seeing a problem like the one you describe.



    Grant


    Thanks Grant, I verified the catalogue (not done that before) and it reported that it was corrupt, so I selected the Repair option.

    I will monitor the situation to see if the problem occurs again.

    I compared a corrupt file with the corresponding valid file and the corrupt file appears to be truncated. Looking at a corrupt file in Notepad++, the last readable content is a chunk of XML that ends with "</x:xmpmeta>".

    Regards,
    Richard
    0
  • RichardT
    Sadly, verifying the catalogue did not fix the problem.

    I tried exporting 5 images - all OK.
    I then tried exporting an image that had been giving problems earlier (but which had eventually been successfully exported).

    First attempt produced a 12KB corrupt file.
    Shut down Capture One and restarted.
    Second export attempt also gave 12KB corrupt file.
    Rebooted PC and tried again.
    Third export attempt also gave 12KB corrupt file.
    Tried different JPEG Quality settings including 80% and 100% - all gave 12KB corrupt files.
    Tried exporting as TIFF - gave 220KB corrupt file.
    Tried exporting as JPEG with Quality 93% - success!
    Tried exporting as TIFF again - success!

    Weird!

    Regards,
    Richard
    0
  • SFA
    Richard,

    I would try running the verify again, perhaps a few times, to see if anything changes.

    FWIW some time back with V7 I had a session that kept doing odd things when editing - apparently randomly. I visually scanned the images but there were about 2500 so not something I sat down to do carefully at that point.

    Eventually I stumbled across a thumbnail that was clearly corrupt. I tried to regenerate it but got the same result. So I deleted the edit variant for that file and created a new one from scratch and the problem never recurred.

    In terms of a database that may end up with bad links for one reason or another there is not much practical difference between a session and a catalogue so it may be worth making a visual scan of the thumbnails to see if they look OK. If any don't they may possibly point to some sort of internal bad pointer and that in turn might be the source of seemingly random problems.

    I suspect it is is easier to go digging into the code in the session files than it is in a catalogue but with luck the visible symptoms may still provide some clues.


    HTH.



    Grant
    0
  • Paul Steunebrink
    Disable OpenCL for processing?
    0
  • RichardT
    [quote="Paul_Steunebrink" wrote:
    Disable OpenCL for processing?


    Thanks for the suggestion, Paul.

    I just tried re-exporting the image that was giving problems on Saturday.

    With OpenCL for processing set to Auto, the export produced a corrupt 12KB file.
    With OpenCL for processing set to "Never", the export produced a valid 463KB JPEG file.

    I repeated the above tests three times and the results were consistent.

    I will keep my eye on other exports to see if the problem has been solved completely.

    thanks,
    Richard
    0
  • SFA
    Interesting.

    I thought 8.1 had pretty much resolved any problems with GPUs and Windows did not seem to suffer anything like as much as Mac anyway.

    Which graphics card do you have and which driver for it?


    Grant
    0
  • RichardT
    [quote="SFA" wrote:
    Interesting.

    I thought 8.1 had pretty much resolved any problems with GPUs and Windows did not seem to suffer anything like as much as Mac anyway.

    Which graphics card do you have and which driver for it?


    Grant


    Graphics card: NVIDIA GeForce GTX 550 Ti
    Driver: 314.22

    I realise this driver is quite out of date, but I had lots of problems with later versions causing my PC to lock-up. It was so frustrating as the PC had to be powered down and I was losing work. I rolled back to 314.22 and the lock-ups stopped happening.
    0
  • SFA
    [quote="RichardT" wrote:
    [quote="SFA" wrote:
    Interesting.

    I thought 8.1 had pretty much resolved any problems with GPUs and Windows did not seem to suffer anything like as much as Mac anyway.

    Which graphics card do you have and which driver for it?


    Grant


    Graphics card: NVIDIA GeForce GTX 550 Ti
    Driver: 314.22

    I realise this driver is quite out of date, but I had lots of problems with later versions causing my PC to lock-up. It was so frustrating as the PC had to be powered down and I was losing work. I rolled back to 314.22 and the lock-ups stopped happening.


    Hi Richard,

    My Notebook does not have this problem - the GPU is so low powered it is ignored! I presume therefore the driver is of no significance for me ....

    However I do recall that at some point early in my ownership there was a driver update for the GPU that entirely trashed the functionality and I had to roll back to an earlier version.

    I think it might be worth trying the latest and greatest driver - you can always roll back if you think it necessary but there have been a lot of advances in recent times so it's worth a try.


    IMO.



    Grant
    0
  • RichardT
    [quote="SFA" wrote:
    Hi Richard,

    My Notebook does not have this problem - the GPU is so low powered it is ignored! I presume therefore the driver is of no significance for me ....

    However I do recall that at some point early in my ownership there was a driver update for the GPU that entirely trashed the functionality and I had to roll back to an earlier version.

    I think it might be worth trying the latest and greatest driver - you can always roll back if you think it necessary but there have been a lot of advances in recent times so it's worth a try.


    IMO.



    Grant


    Hi Grant,

    I have followed your suggestion and installed Nvidia driver 347.09 .

    Immediately afterwards I noticed that Capture One was reacting very sluggishly, taking about 10 seconds just to repaint its main window; and it also wouldn't respond to any mouse clicks! However, after rebooting, it started behaving normally again.

    Since then I have re-enabled OpenCL for processing and have not had any corrupt exports.

    So far I've not had the PC lock-up. If it continues to behave itself it looks like the problem could be resolved.

    Thanks,
    Richard
    0
  • SFA
    Hi Richard,

    That sounds positive.

    I always tend to re-boot at least twice after an sort of significant driver install - especially things like GPU drivers just to make sure that temporary files and internal lookup tables, presets and so on (where there may be some) are most likely to have updated properly.

    There are so so many variables in terms of bits of code or conversion data and look up tables and other stuff in our machines these days that it really is quite a miracle that anything works at all!


    Grant
    0
  • dave211
    Im having the same issue, but from the Sony version and the full version (both Pro).
    GPU acceleration is turned off because it stops any Exporting with an error, but drivers are all up to date (as is Windows 8.1 64 bit)
    It only seems to happen with JPG's.
    I thought it was because i was exporting to a Google Drive folder but ive never had this issue with LR, and its quite random

    Looks like i might have to go back to LR at this rate as it doesnt seem to be a common issue so cant imagine it will be a priority fix.
    0
  • SFA
    [quote="dave211" wrote:
    Im having the same issue, but from the Sony version and the full version (both Pro).
    GPU acceleration is turned off because it stops any Exporting with an error, but drivers are all up to date (as is Windows 8.1 64 bit)
    It only seems to happen with JPG's.
    I thought it was because i was exporting to a Google Drive folder but ive never had this issue with LR, and its quite random

    Looks like i might have to go back to LR at this rate as it doesnt seem to be a common issue so cant imagine it will be a priority fix.


    When you say it only happens with jpgs do you mean when you are processing jpg within C1 or processing RAW files to jpgs as output from C1.


    If the latter can you tell us about your Output Process Recipe settings.

    For completeness ... I did have a situation some time back when a GPU driver update caused problems with an external monitor. Obviously nothing to do with OpenCL! The driver update was "not good" so I had to roll things back one step and wait for a better driver release that fixed the problem before making the update stick.

    Such things are not uncommon and are outside the control of the application developers in most cases though if no other solution is forthcoming they may be able to engineer a specific work around. However this is a cost for them both for development and the continuing need to consider and maintain the "fix" as time goes on. As such patches of that nature are very unwelcome and potentially disruptive at some point in the future.

    I have Win 7 so can't comment Win 8.1 - other than the recent update to 8.1 on my phone was interesting.

    Grant
    0
  • dave211
    Sorry, to be clear, this is happening when process raw files from either my Canon 5Dmkiii or Sony a6000.
    They go to a Goggle drive folder on my E: drive, CO is on my C: drive.

    Ive tired with all configurations of Hardware acceleration on and off, both for display and output.

    Ive worked this way for a few years with LR and never had this issue. In fact i had to go and re export around 15 images last night with LR as it was taking 2-3 attempts sometimes to get the JPGs out of CO.

    Im at work at the moment so cant remember all the settings, but as far as i can recall all ive changed from the default settings are size = 1600px on the long edge, JPG quality at 100%. sRGB and target folder set to the above.

    Thanks.

    Dave.
    0
  • SFA
    Hi Dave,

    As a general comment I think C1 might be working a little closer to the edge of technology than LR right now but I don't know for sure.

    However C1 is 64bit only for a reason and I read recently that LR will become 64bit only with it's next major release. I'm not sure what that may be telling us in this context but no doubt we will find out quite soon.

    From your information I would not think you are doing anything strange unless (guessing) some of the images are heavily cropped and and exceeding the 200% expansion capability - but as you have not mentioned that it seems unlikely.

    On the face of things you are doing pretty much what I have done many times without problems although my E: drive output folder is not a watched folder feeding cloud storage (which I take it your is, correct?).

    What happens if you output to a different folder on E:? (Or indeed somewhere else entirely?)



    Grant
    0
  • dave211
    Thanks Grant.

    Im not doing much cropping, just a bit off the sides when using lens correction. Nothing heavy at all.

    I tried exporting to a folder outside of Google and that seemed to be ok. 28 images all at 1920px on the long edge. Saying that, none of these were edited, i just selected a load and output them.

    One strange thing i noticed the other night was that some of the corrupt images looked ok on my PC using Faststone to view them, but on Google they were corrupt. I know this points to maybe Google but its not happened in over 3,000+ images uploaded using LR.
    I wonder (and its a wild guess) if CO is writing the JPG's in a different way to LR, so Google starts uploading the first bit and not the whole image. PNG''s work perfectly using the same folders etc.

    Ill keep an eye on things, for now im going back to LR for convenience, but ill play around with CO when i get time. There is a lot to learn anyway so i wont rush in to using it exclusively.

    Dave.
    0
  • SFA
    [quote="dave211" wrote:

    I wonder (and its a wild guess) if CO is writing the JPG's in a different way to LR, so Google starts uploading the first bit and not the whole image. PNG''s work perfectly using the same folders etc.



    The same thought has crossed my mind. The copy to Google starting too soon - almost like there is no lock file when writing the image? I have no idea how the Google watch folder works though.

    I would suggest a Support Case would make sense. I think you have enough information to describe the problem well enough for a supporter to be able to work out what is going on.



    Grant
    0
  • dave211
    To be honest i tihnk im going to leave it and go back to LR
    It sounds like it will drag on for a while, as it doesn't seem to be a widespread issue, and ive just noticed there is no lens profile for my E mount 18-105.
    All in all i love the output but not the extra work im going to need to put in, at least at the moment.

    Thanks anyway.

    Dave.
    0
  • SFA
    [quote="dave211" wrote:
    To be honest i tihnk im going to leave it and go back to LR
    It sounds like it will drag on for a while, as it doesn't seem to be a widespread issue, and ive just noticed there is no lens profile for my E mount 18-105.
    All in all i love the output but not the extra work im going to need to put in, at least at the moment.

    Thanks anyway.

    Dave.


    In your own interest, since you like the output, you should register relevant Support Cases with Phase One.

    The Support Case system is, we are told, the basis of all (or at least most) management decisions that guide the direction the product will take - at least in so far as general user input is concerned.

    Having used such a system in my own work a couple of decades ago I understand why that should be and commend it to the user base.


    Grant
    0
  • dave211
    Yeah, i might do that if i have time. The issue then will be having to go through testing stages etc, that i dont really have time to do at the moment.

    I noticed a new update came out the other day, ill give that a go first.
    0
  • WPNL
    I'm strugling with this also...
    I've checked the logs and this draws my attention, can it be related to this?
    There's a lot of -->
    2015-04-06 18:15:49.845> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
    2015-04-06 18:15:49.845> (ERROR) Execution of Filter failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
    2015-04-06 18:15:49.845> (ERROR) Execution of Filter failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
    2015-04-06 18:15:49.845> (ERROR) Execution of Filter failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
    2015-04-06 18:15:49.845> (ERROR) Execution of Filter failed : CL_MEM_OBJECT_ALLOCATION_FAILURE

    OpenCL info:
    2015-04-06 18:37:52.148> OpenCL initialization...
    2015-04-06 18:37:52.351> OpenCL : found platform NVIDIA CUDA, OpenCL Version : OpenCL 1.1 CUDA 7.0.29
    2015-04-06 18:37:52.382> OpenCL Device : GeForce GTX 970
    2015-04-06 18:37:52.382> OpenCL Driver Version : 347.88
    2015-04-06 18:37:52.382> OpenCL Compute Units : 13
    2015-04-06 18:37:52.554> OpenCL : Loading kernels
    2015-04-06 18:38:07.959> OpenCL : Loading kernels finished
    2015-04-06 18:38:07.959> OpenCL : Benchmarking
    2015-04-06 18:38:08.100> OpenCL : Initialization completed
    2015-04-06 18:38:08.100> OpenCL benchMark : 0.216128
    0
  • Peter Hugger
    I guess I'm a bit of a thrill seeker, but I've been running Capture One on Windows 10 Tech Preview.
    It has been running fine without any issues.
    I recently decided to update my Nvidia Graphics card driver to the latest version.
    Capture One would no longer process JPEGs or TIFFs - it only output a corrupt 8k file
    I read the suggestions in this thread and downgraded my video drivers to an older version.
    v350 -> v347 (2 months older)
    Everything is working fine again now.


    Best regards,
    PCH
    0

Post is closed for comments.