Crash / Lockup on Import and/or CF Card Detection
Running 4.6 on Leopard 10.5.6. Have both 3.7.9 and 4.6 installed. When I open 4.6 and either hit import OR the app detects a CF card connected the application locks up. Everywhere I click the app beeps at me. I can't quit; option is grayed out along with many other choices in different drop-down menus. I'm forced to Force Quit via the Finder. What's up?
0
-
I would like to suggest you to update to 4.6.3 for a start. 0 -
[quote="Paul_E" wrote:
I would like to suggest you to update to 4.6.3 for a start.
Hi Paul. I upgraded. Same problem. And it's unbelievably slow. Everything. And I get this weird double screen redraw where the image looks great and sharp and then "settles in" to this softer look. I keep trying to use 4Pro and I keep experiencing painful problems that interrupt my production flow. I've seen other users complain about 4.5 being slow, but 4.6 doesn't seem any better. All of the 4.6's that is, .0, .1, and .3.0 -
What Mac, what raw files are slowing you down? 0 -
[quote="Paul_E" wrote:
What Mac, what raw files are slowing you down?
Hi. Thanks. One New Macbook Pro 10.5.7 and a 2x3GHz Intel Mac running 10.5.7. I noticed it with both my P25 files and Canon .cr2 files (1Ds Mark II). I want to use 4.6 for all the controls, but my production is getting killed. Can't do it. Thanks for any help. Oh, the Input problem only on the Mac Pro. Incidently, I used the import function last night on a shoot on the Macbook Pro, and it was fine. Huh. Thanks.0 -
As for Capture One being slow after upgrading to 4.6.3, it is because Capture One regenerates the proxy files (cache files). It will only seem slow until these are all regenerated. It will happen each time you visit a folder that you haven't visited before with 4.6.3.
Regarding the importer bug, you can try to delete/rename your settings file after quitting Capture One. It resides in <username>/Library/Preferences/com.phaseone.captureone.plist
When you restart CO, it will generate a fresh settings file and the problem should be fixed.0 -
Good tips Mikkel. As for Sean, you seems to be an early adopter of OS X updates (10.5.7 not released yet as far as I know) 😉 0 -
Thanks. Will try those suggestions. And yep, my error: 10.5.6. So I understand the regeneration of cache: If I have say 5 folders with 120 images each (corresponds to numbered CF cards) then to generate the image I should select the folder and let them generate, then, say, move on the the next folder? What about the lag time between making an adjustment on an image (color balance or exposure)? There is a lag between my mouse click (selecting the option) and the app's receiving the option. I'm comparing the workflow with 3.7.9 which is very fast and satisfyingly responsive. Not to be expected with 4.6.3? Thanks again for all your imput. 0 -
[quote="Sean" wrote:
Thanks. Will try those suggestions. And yep, my error: 10.5.6. So I understand the regeneration of cache: If I have say 5 folders with 120 images each (corresponds to numbered CF cards) then to generate the image I should select the folder and let them generate, then, say, move on the the next folder?
Yes.What about the lag time between making an adjustment on an image (color balance or exposure)? There is a lag between my mouse click (selecting the option) and the app's receiving the option. I'm comparing the workflow with 3.7.9 which is very fast and satisfyingly responsive. Not to be expected with 4.6.3? Thanks again for all your imput.
Well, that depends on your hardware, but if it is busy generating cache files, it will very likely slow adjustments down.0 -
Update: So far removing that .plist file has solved most of the trouble. 1) the app is functioning more to the speed of 3.7.9 and 2) the import function did not crash the app. I'll keep working with it today; I've got a bunch of exporting and gallery proofs to run, so I'll put it to the test. But thanks VERY much so far. This has really helped me. 0 -
Mikkel and Paul. Thanks! Man, I was able to fly through my work today. When Phase rocks it's great. Seems that clearing the .plist files are good thing to do. Not to be excessive, but would you recommend clearing those out from time to time. I did note that when I opened it in a text editor prior to deleting it was nearly 3 times as much data there. Thanks again! 😄 0 -
[quote="Sean" wrote:
Mikkel and Paul. Thanks! Man, I was able to fly through my work today. When Phase rocks it's great. Seems that clearing the .plist files are good thing to do. Not to be excessive, but would you recommend clearing those out from time to time. I did note that when I opened it in a text editor prior to deleting it was nearly 3 times as much data there. Thanks again! 😄
I wouldn't recommend clearing it unless you have problems. It is after all personal preferences that should be retained.0
Post is closed for comments.
Comments
11 comments