Capture one crash
this is my privat video which shows how C1 8 crash under using the best imac 27" Hardware and Yosemite 💡
show me please how can i upload the video hear ?
show me please how can i upload the video hear ?
0
-
Host the video elsewhere (YouTube?) and post the link to it here. 0 -
You'd be better off contacting our Support team 😊 0 -
i want to shear this video hier only for register user , i already send the crash reports to phase one
in this video you can see live how and ware C1 crashes happened.
just tray this on your Imac with the following work sequences.
1. open C1 and deactivate or activate the GPU in setting.
2. open your catalog and chose a picture for editing with a RAW format .
3. pic the spot remove brush and pick on some places in image.
4. go to local adjustment and select a clone or heal layer for adjusting,
5. zoom to a place with about 100-250 % or moor and brush a image Area .... at this moment C1 crash !
using the Spot brush with the Adjustment brush to a Image makes C1 to crash0 -
Just for interest I have tried this using Windows 7 and while the system response is slowed (at 300 or 400 % especially) I have not yet made C1 crash. That suggests there must be something specific that creates the failure rather than a basic and generic flaw in the code.
HTH someone somewhere.
Grant0 -
sorry but Window 7 is not same like Apple ! 0 -
[quote="CAPTURE NIKON D700" wrote:
sorry but Window 7 is not same like Apple !
Very true.
Grant0 -
I have followed the same sequence: spot removal first and healing brush afterwards without any crash.
I am on a test machine MBP 17" Early 2011 16Gb RAM OSX 10.10 CO 8.01 (Open CL is off).0 -
Ok, i traid this 3 time again and got only one crash !
pleace tray this ..
bevor you gais select the Picture to edit, aktivate the filter surch funktion just like " show me all RAW Pictures" then
begin with the steps, give me your feedback please
thanks0 -
[quote="CAPTURE NIKON D700" wrote:
Ok, i traid this 3 time again and got only one crash !
pleace tray this ..
bevor you gais select the Picture to edit, aktivate the filter surch funktion just like " show me all RAW Pictures" then
begin with the steps, give me your feedback please
thanks
Uhhhmm, created a support case already?0 -
As your have seen that this is not something that happens every time in your catalog have you also tried creating a completely new catalog to see if the same things happen then?
If not it would perhaps help you to try that.
The reason is that catalogs (and session databases) are basically files that keep a record of all the parts of and image edit process, preview, thumbnails and everything else. Part of what they do is create an index and link record for all othe components that make up the edit. If for some reason - any reason and maybe not even related to something you were doing at around the time the problem appeared or even the program you were using - the links may go "bad". If that happens many of them may still work well but a few may not and so they cause random problems.
If you create a completely new clean catalog (or session) and then try the same types of edits on NEW versions of the source files (i.e. you do not want to copy in existing edits from the other catalog or session at that point of the test) you have an opportunity to quickly discover whether or not the same actions result in the same problem appearing. If they do then there would seem to be something in the code for that feature that initiates the problem. If the problem is not repeatable or not consistent for the same images it would suggest that the problem exists somewhere else and make take a little more work to discover where that might be.
The additional benefit is that you can then try running a check on the old catalog to see if any errors are identified. If the problem still persists once you have done that then at least you can carry on with new work in the new catalog while the Support Team investigates the problems with your old one as reported in the Support Case.
HTH.
Grant0 -
Yes ...now i found it how c1 crash to 90 % under Imac and Yosemite, i send always reports to Phase one.
but i would bee happy if they let mir hear to post my video about it 😄
the problem happens always when you first activate the filter search option in C1 " RAW or Keywords ..." and then
edit a picture to your select by using 3 to 6 Spot correction on a different location on image, then you zoom to about 150-200 % and add the Heal or clone location adjustment to your image.0 -
Yosemite is not yet supported. Crashes and quirks are to be expected on this unsupported OS. 0 -
[quote="Paul_Steunebrink" wrote:
[quote="CAPTURE NIKON D700" wrote:
Ok, i traid this 3 time again and got only one crash !
pleace tray this ..
bevor you gais select the Picture to edit, aktivate the filter surch funktion just like " show me all RAW Pictures" then
begin with the steps, give me your feedback please
thanks
Uhhhmm, created a support case already?
see my post I just wrote about this bug. It is real and it exists.0 -
[quote="alececco" wrote:
[quote="Paul_Steunebrink" wrote:
[quote="CAPTURE NIKON D700" wrote:
Ok, i traid this 3 time again and got only one crash !
pleace tray this ..
bevor you gais select the Picture to edit, aktivate the filter surch funktion just like " show me all RAW Pictures" then
begin with the steps, give me your feedback please
thanks
Uhhhmm, created a support case already?
see my post I just wrote about this bug. It is real and it exists.
That is why you should report it in a support case.0 -
This happens to me as well, and I can replicate it.
If I create a new heal layer, select draw mask, the moment I click anywhere to draw the program crashes.
I've also sent the crash report.0 -
[quote="NN635513306989742303UL" wrote:
This happens to me as well, and I can replicate it.
If I create a new heal layer, select draw mask, the moment I click anywhere to draw the program crashes.
I've also sent the crash report.
Just a crash report or did you create a Support Case?
I would suggest the Support case would be more helpful to you and the Support Team who may need to look at a number of detailed examples before they can be certain where any problems are coming from.
Grant0 -
Uhhhmm, created a support case already?[/quote]
see my post I just wrote about this bug. It is real and it exists.[/quote]
That is why you should report it in a support case.[/quote]
Dear Paul, thank you for your suggestion. You will happy to know that after many email exchanges with support they finally were able to replicate the problem. We eagerly await a fix0 -
[quote="alececco" wrote:
Uhhhmm, created a support case already?
see my post I just wrote about this bug. It is real and it exists.
That is why you should report it in a support case.[quote="alececco" wrote:
Dear Paul, thank you for your suggestion. You will happy to know that after many email exchanges with support they finally were able to replicate the problem. We eagerly await a fix
Happy to know that faith is restored in the support department and R&D department. 😉0
Post is closed for comments.
Comments
18 comments