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. ⚠️

5.1 crashes often when editing image name in thumb browser

Permanently deleted user
Support case also opened.

I've found if I edit the image name in the capture one thumbnail browser (click on image name under thumbnail, edit text) that there is a very consistent crash - not for every edit, but for at least every 2-3. On restart everything works fine and the edits stick.

WinXP SP3
0

Comments

12 comments

Date Votes
  • Permanently deleted user
    To add to this. If I open 5.1 standard and start editing image names, no problem. But if I make some IPTC edits (specifically to the 'source' field), then edit the image name or the next image name it crashes. The IPTC data area whites out with a big red X across it.

    I did open a support case and am getting support with a closer look, I provided the crash log file and the all CO log files.

    Just curious, can anyone else recreate?
    0
  • Drew Altdo
    Alex,
    Are your files in some location that could possibly have a permissions conflict? An improperly formatted external drive?
    Sounds like, when Capture One tries to rename the Sidecar Files (Setting, Proxie, Focus Mask) the software hits an access hicup and quits. If you move the files to the Local boot Drive and repeat the practice does it act the same?
    0
  • Permanently deleted user
    The image files (Canon 30D RAW CRW's) are on the same C: drive as the OS and programs (i.e capture one) drive. Generally most of my image files reside on an external HDD, but I've never tried to edit their names before. I just happen to be working from files on my local drive now and for unrelated reasons had the need to rename them from the thumbnail browser, which I had never tried before from any version of capture one.

    I can try and determine exactly what the repeatable sequence of events is. It is likely edit iptc data and switch to the next image and change it's name or it is rename image name, edit iptc data, then switch to next image and crash...

    After the crash on re-start of CO all the edits including iptc and file name change are there. Nothing appears to be lost. The only oddity is that CO is starting up with the same (but not first in directory) image as default, which is not one of the images being edited or one that had been edited recently. Normally CO start up with the last image that was being worked on. I also note looking at .cop, .cos, .cof and the .CRW file that there are no residual files left (i.e. ones that still have the previous image name)

    I have never had a crash like this editing any of the other image settings and switching between images. It is only when I started editing iptc AND changing the image name did I first experience a crash. I have not tried editing non-iptc settings then the image name to see if that causes a problem.

    Thanks for the questions.
    0
  • Drew Altdo
    Alex,
    Just curious... what happens if you pack the file as an EIP first, then edit and rename?
    0
  • Permanently deleted user
    I have to try that and a few other tests (to be sure I know the exact sequence that results in crash) later tonight in about 2-3hrs. Have you looked at the log files I uploaded for the support case or is that being handled by Jakub?
    0
  • Permanently deleted user
    OK, here is one small interface nuance that may be of interest as it does not seem fully 'right.'

    I click on the file/image name under the thumbnail to edit it, the name changes to an edit box (black text on white background and the filename extension .CRW is not shown) - during this I have the metadata tab visible (so I can manually change filename to reflect a part of the iptc data)

    Then I edit the text, say add -XXX to the end of the image file name.*

    Then instead of hitting enter key I mouse click on the next adjacent thumbnail, my edits are accepted and the edit box changes back to grey text on black background. That newly selected thumbnail is now highlighted (bold white box around thumbnail) but the oddity is that meta data is still showing for the previously selected thumbnail - this remains no matter how often I re-select the same new thumbnail by re-clicking on it. Only if I select a different image will it show the correct meta data for that newly selected image.

    *However if I hit 'enter' after editing the image/file name then select the next image with a mouse click the correct metadata for the newly selected image is shown.

    I don't know if this is related to the crash, but even if it isn't it is a UI anomaly that probably should be fixed.

    Also note if I have a different tab open (such as the color tab, for white balance) the behavior is not the same and is what I would expect, the new white balance for the image selected with a mouse click is immediately shown even if I don't hit 'enter' after editing the image name. So there is something different happening with the metadata tab vs. other image settings.

    (also by the way *censored word* was 'exexex' where 'ex' is the letter.)
    0
  • Permanently deleted user
    The crash also occurs if i first pack images to .eip then edit meta data (in this case the 'source' field) and edit the file name and click to the next image (which has also been packed to .eip)

    Here is exactly how to cause crash. Edit the IPTC 'source' field. Edit image name, don't hit 'enter', click on next image to select it: Crash.

    But if I edit the 'source' field, then edit the image name, hit 'enter' before I click on the next image: NO Crash
    0
  • Permanently deleted user
    Any comment on these findings or the updated support case from the same time?
    Thanks!
    0
  • Permanently deleted user
    I don't consider this resolved either here on in my support case. Is this and the new information I provided still being considered?
    0
  • Drew Altdo
    Alex,
    Your case is currently in the hands of the test department. They can be a bit slow to respond but they are looking into your findings.
    0
  • Permanently deleted user
    Thanks Drew! That is all I needed to hear, no hurry, just wanted to ensure my latest inputs were in the loop and it appears they are.
    0
  • Permanently deleted user
    Phase One Tech Support notified me that they could reproduce this error in 5.1, but that it is no longer in 5.1.1. I also can not reproduce in 5.1.1

    Issue closed. Thank you!
    0

Post is closed for comments.