Old bug from v11 still in v20
I reported last year on the forums that V11 crashes when I start typing metadata like the heading or description of a photo.
That was with Olympus Pen-F and Nikon D800 raw files.
I downloaded now the v20 trial and I still experience the bug ☹️ .
With the first keypress in the field, Capture One hangs up (it stays unresponsive) and I have to kill it in Task Manager.
Tested now with Nikon Z7 Jpeg file.
As a work around I process my files with Exiftool before I import into Capture One, but it remains a mission to make changes or corrections after import into a session: I have to remove the photo from the session, change with exiftool, and re-import into the session.
To replicate the issue, open a session, import a Nikon raw file, and expand the Metadata tab. Scroll down to "Headline" or "Description" and try to type something in there. When the first key is pressed, Capture One freezes up.
Operating system is Windows 10, 64-bit. v1903,
Computer: i7 processor, RAM 24Gb.
That was with Olympus Pen-F and Nikon D800 raw files.
I downloaded now the v20 trial and I still experience the bug ☹️ .
With the first keypress in the field, Capture One hangs up (it stays unresponsive) and I have to kill it in Task Manager.
Tested now with Nikon Z7 Jpeg file.
As a work around I process my files with Exiftool before I import into Capture One, but it remains a mission to make changes or corrections after import into a session: I have to remove the photo from the session, change with exiftool, and re-import into the session.
To replicate the issue, open a session, import a Nikon raw file, and expand the Metadata tab. Scroll down to "Headline" or "Description" and try to type something in there. When the first key is pressed, Capture One freezes up.
Operating system is Windows 10, 64-bit. v1903,
Computer: i7 processor, RAM 24Gb.
0
-
Is this only with Olympus and Nikon files?
If so that is extremely illogical and it's not something I can recall seeing discussed (indeed nothing even like it) ever.
Did you previously report this problem to the Capture One Support Team?
If so, how did that report progress?
Grant0 -
I just tried it as noted above, and it worked with no problem.
Nikon D810 RAW file, Computer running Win10.0 -
Yep, worked for me. I have Win10 1809 and am using D700 NEF files.
What did support say?0 -
SFA wrote:
Is this only with Olympus and Nikon files?
No problems here with Olympus E-M1 Mk II or E-M1X files on a Win 8.1 box.0 -
It's effecting you from V11 to V20, could it not be something to do with your system?
Have you tried on another comp?0 -
I mentioned the issue with Olympus and Nikon files as that is the cameras I own. I cannot say whether the issue is with other camera files as well. I mentioned it to give as complete info as I can.
Regarding reporting the issue and progress on it: When the software starts after a crash, it automatically prompts for a crash report to the developers. I sent these off quite a couple of times last year on V11. I expected to receive a confirmation email or to find it fixed with a free maintenance release. Never got any response from Phase One, so I later gave up filling them in and developed the work-around in the original post. Now with V20 I also sent 2 of these messages off.
Regarding trying on another computer: I do not think it is a problem isolated to just one system. I switched to a new computer end of 2018 or early 2019, and the issue with v11 repeats on the new computer as well. I never upgraded to V12. V20 trial is installed on the new computer, together with V11.
Given other threads in this forum like "Still full of bugx ☹️", my experience with bugs in this software is not unique.0 -
NN635065702198330154UL wrote:
I mentioned the issue with Olympus and Nikon files as that is the cameras I own. I cannot say whether the issue is with other camera files as well. I mentioned it to give as complete info as I can.
Regarding reporting the issue and progress on it: When the software starts after a crash, it automatically prompts for a crash report to the developers. I sent these off quite a couple of times last year on V11. I expected to receive a confirmation email or to find it fixed with a free maintenance release. Never got any response from Phase One, so I later gave up filling them in and developed the work-around in the original post. Now with V20 I also sent 2 of these messages off.
Regarding trying on another computer: I do not think it is a problem isolated to just one system. I switched to a new computer end of 2018 or early 2019, and the issue with v11 repeats on the new computer as well. I never upgraded to V12. V20 trial is installed on the new computer, together with V11.
Given other threads in this forum like "Still full of bugx ☹️", my experience with bugs in this software is not unique.
Your experience may or may not be unique but it is rare. Most users are not affected.
You need to know that the system crash reports are useful and are analysed in temrs of the number of times similar reports are sent in but they are never considered to be requests for personal support. In effect they are treated as Anonymous problem reports.
For the personal report you seem to need given the nature of your problem you should use the "Submit a request" option that can found near the top of most pages in the Support section of the Web site. (Note that until very recently the process for requesting personal support was slightly different but the effect the same.)
That will start a personal support dialogue with the C1 Support Team that should help you resolve the problem. It is most likely to be something quite obscure in the data somewhere and if it has existed across more than one version update is unlikely to be solved be a simple re-install of the system.
Do you use C1 catalogs or sessions?. (I note you mention session but just want to clarify that you are not referring to a period of editing as a "session".)
Does the problem only effect the IPTC metadata fields - or perhaps only some of them?
If you create a new session or catalog and add just one new image to it does the problem still exist?
HTH.
Grant0 -
NN635065702198330154UL wrote:
Regarding reporting the issue and progress on it: When the software starts after a crash, it automatically prompts for a crash report to the developers. I sent these off quite a couple of times last year on V11. I expected to receive a confirmation email or to find it fixed with a free maintenance release. Never got any response from Phase One, so I later gave up filling them in and developed the work-around in the original post. Now with V20 I also sent 2 of these messages off.
The automated crash reports are not the same thing as putting in a personal request for help from the support team. You can do that here.
https://support.captureone.com/hc/en-us/requests/new
Ian0 -
NN635065702198330154UL wrote:
Regarding trying on another computer: I do not think it is a problem isolated to just one system. I switched to a new computer end of 2018 or early 2019, and the issue with v11 repeats on the new computer as well. I never upgraded to V12. V20 trial is installed on the new computer, together with V11.
Given other threads in this forum like "Still full of bugx ☹️", my experience with bugs in this software is not unique.
Bugs affect every software but sometimes they're the result of particular combinations or even don't lie in the software itself. If yours was an endemic system problem, we all would be affected. You say you switched to a new system but probably you set it the same way as the older one. I mean, everyone has his own habits. I use to treat all my computers the same way, to install the same utilities and programs, to set them the same way and so on, so maybe there's something in your system handling that produce it. Maybe another program or driver that creates a conflict.
As others told you, you have to open a support case.0 -
NN635065702198330154UL wrote:
(...)
Given other threads in this forum like "Still full of bugx ☹️", my experience with bugs in this software is not unique.
That is not the point. It is not your experience with bugs, but your experience with the software on your computer. It is not relevant whether this is a bug or an isolated incident.
This point is you need support, you need help. Contacting the support department is the first step.
Note: crash reports are in general not followed up with feedback. Supports case are.0
Post is closed for comments.
Comments
10 comments