Image name limitation
Is there a limit to the number of characters for a image file name. Sometimes my character count can exceed 150 characters. Windows and other programs don't seem to mind but C21 is crashing when I scroll through my catalog. I know this likely isn't the problem but I've tried about everything else including reinstalling windows and nothing seems to help. The program seems to crash when I scroll through an area with these especially long file names, so I thought I would give this potential trouble vector a shot. Thanks in advance for any ideas an input.
-
Don't know, hardly believe anybody here would. Just a few thoughts: You have the images in the catalog (or session?), so at least some part of C1 accepts long names, without checking or rejecting longer names over a specific limit, e.g. importer. That does not necessarily mean that other parts of C1 run flawlessly (browser, scrolling/preloading logic or datastructure) under all circumstances. btw, does the scrolling speed matter?
Try verifying the catalog / or session.
Try to exclude the images or rename them to verify or falsify your assumption about long names.0 -
Nick,
In addition to BeO's suggestion, you might want to check the log files to see if they give any clues about what is happening just before the crash. Even if the logs are unable to provide specific failure identification they might show that the problem can be made to occur consistently. That information, consistency or not, might offer some guidance.
0 -
C:\Users\your user name\AppData\Local\CaptureOne\Logs
0 -
Probably irrelevant but no harm in enabling Win 10 long file name support and see what happens?
https://www.itprotoday.com/windows-10/enable-long-file-name-support-windows-10
I see C1 adds 50 or so characters to the file name to name it's thumbnail files.0 -
Could be yet another openCL issue.
Try turning hardware acceleration off in preferences,
close C1, delete the ImageCore folder and restart C1.
C:\Users\User_Name\AppData\Local\CaptureOne\ImageCore0 -
Thank you for all of your responses.
I have:
verified the catalog dozens of times (all ok)
turned on/off hardware acceleration
looked at the crash reports and they do not show any anomalies although
scrolling speed does not seem to matter.
New Info
Through experimentation I found a series of images that, if I select (click on) them C1 immediately crashes. Strangely, if I scroll down in list mode, C1 crashes when I come into the area of the suspect images without selecting any image. Then a white screen with a red "X" appears in the browser window.
I'm willing to delete these files from the catalog but I do not know how to without selecting them which I can't because it crashes the program. . Any help with that? Thank you.
0 -
white screen with a red "X" appears in the browser window
I think this backs my assumption that one component (the browser in this case) cannot cope with long file or path names, or too many of them, but others (e.g. importer) could.
I'm willing to delete these files from the catalog but I do not know how to without selecting them which I can't because it crashes the program.
Hm, maybe the crash won't happen for offline images? I mean if you delete, move or rename them on the file system level.
0 -
Thanks BeO. I tend to agree with you there is an issue with one of the modules. Additionally gb noted C1 adds characters to the file name which could easily put some of my image names over the standard (I think) 255 character limit.
What I did do was create a new catalog and imported all of the images except for the "known offenders". I then renamed them and imported them separately. I'm still doing some integrity checks to be sure everything imported correctly but I haven't had any crashes so far but this is very early days. I guess I may never know if it was the file name issue or a corrupt file that was not imported (or was corrected during the import). I'll update this post when I have more news or a higher confidence level the issue is resolved. I also have a ticket open with C1 and will be interesting to see what they have to say. Thankls again for eveyone's suggestion. BTW...gb I did change Windows to accept long file names.
0 -
Nick,
The system would need to be able to deal with long file names (and maybe some other aspects of the processing needs) in its work areas with memory and temporary file handling.
Also, for at least some portability between operating systems, the lowest level of compatibility may be adopted by default.
Whether these matters are influential in this case I have no idea but it would be something to bear in mind.
The log files may offer some clues about what is happening but whether they can be understood at that level by anyone except the developers is an open question.
0 -
SFA wrote:
Also, for at least some portability between operating systems, the lowest level of compatibility may be adopted by default.
Good point. In case C1 will have a clear advantage on Macs over Windows, be it performance, stability or whatsoever, which might possibly be the case in far future, and if I'm in the market for a new buy at that time, I will be considering a cross-os operation of C1. Provided that C1 will still be with me then.
0
Post is closed for comments.
Comments
10 comments