Crashing on batch import for .RAF files
Alright folks, it's come to this. I need help with getting this fixed.
It started two days ago. I'm suddenly unable to import groups of .RAF files into either catalogs or sessions. I will do my best to cover everything I've done to troubleshoot the issue.
The .RAF files are in various folders. When I try to import the folder and it's files into the catalog/session it crashes the program, usually while generating previews. Occasionally, it will blue-screen my computer when it crashes. If I then reopen CO20 and select the album containing the upload, the preview generation starts and the program crashes again.
Looking at the event log, it tells me that random files can not be opened, suggesting the file may be damaged or otherwise unable to load.
Log data file line:
" 2020-07-13 12:43:21.837> CProxyFileBase::checkHeader: unable to open proxy file [I:\Photography\2020_Catalog\Cache\Previews\2020\7\13\0\DSCF2603.RAF.cop]"
Event Log Description:
"Unable to create proxy, for image I:\Photography\2020_Active\2020-01_X_RAW\DSCF2603.RAF. The image file may be damaged or otherwise unable to load."
So, I've done some experimenting. I've gone to each of these files and loaded them in individually. No problems. They will import individually and can be edited. furthermore, i was able to open them in Photoshop Camera Raw without issue.
I experimented with CO20 trying to upload small numbers of files at a time. 1 file import = ok. 5 files imported = ok. 10 files imported = ok; 15 files imported = crash. Again, crashing while generating previews.
I've deleted the 20 catalogs and sessions and tried to start with new catalogs/session. No difference.
I've completely unistalled CO20 and reinstalled it. No difference.
I rolled back to the last update version (the one before the most recent, when i wasn't having this issue). No difference.
I performed a memory diagnostic scan on my computer memory; no issues found.
I performed a CHKDSK scan on the harddrive; no issues or bad sectors found.
I copied the files to another blank SSD drive and tried to import; still crashed.
So here is what I'm thinking now, but I don't know why this would all this sudden be a problem when it never was before and rolling back versions didn't help...
***Maybe it's that i'm importing from a different drive than CO20 is installed on and that the Catalog is on the external drive that I'm importing from ??
***Maybe its that I have custom profiles on the .RAF files (fujifilm always for recipe adjustments in-camera). maybe that's causing issues. I have an XPRO3 and some of my profiles have adjustments to the "Contrast" setting, which is fairly new. Again, this was not an issue until two days ago.
Has anyone run into this before, or know whats going on? I'm open to any suggestions at this point because the program is basically unusable like this.
Cheers - Jonathan
-
I don't have a solution but there are a few things you could try.
Is it only raf files, have you tried other file types? Do jpegs import correctly?
In a session it is possible to just browse the disc or copy the files into the Capture folder with windows explorer, have you tried this and then opening a file for edit in C1? Look at the System Folders section under the Library tab, you should at minimum be able to browse the files there.
Have you tried importing different batches of raf files (just in case one is corrupt).
Have you performed a HDD check, to make sure that there is no error on the disc stopping C1 reading files.
I think the log files are kept in c:\users\user name\appdata\local\captureone\logs. You could clear out the logs (suggest move somewhere else just in case) then run C1, import some files, after the crash look at the log files they may give some ideas to the fault.
I would suggest that you put a support request in.
0 -
Jonathan,
Two thoughts come to me.
Firstly that Fuji recently introduced some new Film simulations that are not yet present in C1. Might you be using those? I'm not sure what would happen if C1 was trying to set an as yet not available simulation to an imported file had you used in in camera but normally I would not expect a blue screen crash.
Secondly ...
I had something similar a long tame ago - C1 V6 or V7 iirc - but not on import.
One particular session of about 3k images would crash about every 10th image being edited for no obvious reason.
In this case all of the imports were completed with no errors. The crashing on edit at first appeared to be rather random as I jumped around looking at the shots but when settled down to work through them it became apparent that the "about 10 imagesbetween crashes" rule was quite consistent.
Around half way through and getting somewhat frustrated I happened to spot a single thumbnail that was showing signs of being corrupt. Attempting to regenerate it failed giving the same corrupt result. After a few more experiments and some under the hood digging I concluded that one of the file fragments involved in the representation and management of that "file" at the Windows system level seemed to have an incomplete identifier for file system use and therefore could be associated with other file groups. It seemed to related to a .cos file - so a settings file holding edit data in C1 terms.
The result would have been that when that fragment was picked up and built into a string of data in certain situations the type of information would have been wrong for the field being processed and therefore the program would crash at a system level. It wold have been so obscure as a problem for an application code level that there would be no likely way to trap it even if the possibility was considered as a processing risk.
The nature of the bad reference number - basically a long string of digits that ended in a sequence of several zeros when it really should have had non-zero numbers - meant it came into play about every 10 images when passing through the files in order of import (pretty much file name order in effect.)
Once I had discovered this I delete the file and reimported it and all was well. The edits applied at import had gone but that was of no consequence and had to happen anyway because it was the edit file that had been created in a way that caused the problem - which was why the thumbnail was corrupt.
Now, since you have already eliminated sessions and catalogues and re-imported it suggests that you could have a similar problem but in a different file - one that persists even when the imports have been deleted and repeated.
Might provide a clue to files that are repeatedly problematic - maybe not always for the same file on import.
My inclination would be to ensure, firstly, that any temporary files from earlier earlier times that may have been orphaned and not cleaned up by windows are eliminated.
Beyond that it's difficult to know what to suggest - unless the log files show that the problems occur with the same files every time. In which case it may be possible to identify a potential common factor for those files.
Also, assuming you are on Win 10 with auto updates, it may be worth checking whether the problems started at around the same time as an update was applied. Such things could be simply coincidence or course but given the recent track record of Win 10 updates it might be sensible to at least consider the possibility that a Win update could be a factor.
Finding a pattern may be the key to this sort of problem. Annoying and time consuming of course but perhaps unavoidable.
There are some things to check in the Application data side of things and maybe the Userconfig file but that's not somewhere you would want to dive in blind (or at all!) without first trying to find some sort of pattern about when the failures arise.
HTH.
0 -
SFA, It does feel like some sort of file corruption issue, although the film simulation aspect is an interesting path to follow. I wonder if creating a session and then browsing to the files via the file folder directly (through the Library tab) would highlight any troublesome files...
0 -
Mark,
I think this may be more related to something in one of the appdata settings, the related userconfig file or, possibly, the film simulations but if those then it's behaving in an odd way.
Too much to dive in randomly with much hope of anything but a lucky find.
Need to look at the log files to seek some ideas for what to look at and for.
0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare