Slow reaction in C1

Juerg1

• August 16, 2012 13:49

I am using a windows PC win 7 64 bit with a total of 16 GB Ram and a fast internal HDD (so my laptop is certainly not that slow).

Recently in C1 6.4.3 I have noticed a slow reaction of C1 when making certain adjustments. I noticed this especially when using the brush within the local adjsutment tool. It usually takes 1 to 3 seconds until the red color is displayed on the sreen after the bushes are made. And recently I also recognized a kind of a slow reaction when dragging some of the sliders left or right (i.e. exposure adjustments).

Can someone lead me towards the checks I can made in the computer system or in C1 software to figure out where such low performance come from?

I do have no viruses and I often defragment my disks as well as clean the garbages using CCleaner tools.

thank you.

0

• 

  SFA

  • August 20, 2012 10:21

  Hi,
  
  My systems, both desktop and notebook, are far below the specification of your machine so I see longer delays before the appearance of the brush mask display. However the speed does seem to depend very much on the size of the brush and the amount of feather being used. I conclude that it is proportional to the complexity of data selection being made (from a large number of pixels) and the softwware then making decisions about how to choose which pixels are to be changed and by how much in relative terms.
  
  It would be interesting to know a little more about the design concepts of the selective local adjustments. Having the use of another editor (not LightRoom) that has long offered local adjustments but that creates them in a very different way (not using a "brush") it is interesting to compare the different approaches and the perception of performance in completing the task. There seems to be little difference in most cases.
  
  In the past I have compared the performance of different systems fulfilling a similar editing task when one application seemed to be much faster to respond than the other. More often than not there has been little if any difference in the time taken to complete the task. Indeed sometimes the 'slow' system has been the faster system to complete the task. But it looked slow on screen.
  
  How could that be?
  
  Well, you have to see what is really happening on screen. "Slow" systems tend to do nothing much in terms of visual screen changes (maybe and icon and possibly some image updates at certain points in the process) until they complete. "Fast" systems will often having constantly changing screen updates keeping the screen busy in order to look like something is happening but still take the same amount of total elapsed time. Other systems fall between the two extremes - they update the screen image during a process but not constantly. In many cases any icon or process bar advising that processing is active will disappear (implying the process is complete) some time before the final version of the new rendition actually hits the screen.
  
  All of that does not mean that a slow screen response or, as I sometimes find using a mouse, an erratic response is not frustrating for the users. Delevopers will know this and usually seek way to refine the process over time. However in my situation I suspect that upgrading the hardware would give me more than anything the developers could realsitically provide. Your situation may be different.
  
  What are you using as in input device? Trackpad, mouse or editing tablet?
  
  Grant Perkins

  0

Post is closed for comments.