Repeated Crashes and Freezes with 4.7
I've had repeated crashes and system freezes with 4.7 Pro on Mac 10.5.6. This is something of a first. Has completely frozen my system, I don't believe that this has ever happened before since moving to Mac OS X, vaguely reminiscent of Mac OS 9. Odd and troubling behavior. Crash report sent in. Totally unexpected coming from CO Pro.
0
-
I too have been having freezes, hangs, SPD (Spinning Pizza of Death) with 4.7.
I've had to reboot a couple of times, and had several hangs/SPDs when I've tried to work with lots of images. My current shoot is 900+ images big and 4.7 seems to be REALLY unhappy about dealing with it. I've the brand new PB17 with 2.93MhZ processor so I'm not prepared to blame the Mac!0 -
It's been a very long time since I've felt compelled to downgrade software, but I'm downloading 4.6.2 as I type this. I like the sound of 4.7, but the first 24 hours of taking it for a spin have forced me backwards. I had a series of crashes and hangs today. 4.6x running on 10.5.6 never crashed at all, to the best of my recollection, and was a stable piece of software. What a shame. No changes with my system except for the C1 upgrade. I guess I'll sit this one out, at least until 4.7.1 comes along. 0 -
[quote="Ron" wrote:
It's been a very long time since I've felt compelled to downgrade software, but I'm downloading 4.6.2 as I type this. I like the sound of 4.7, but the first 24 hours of taking it for a spin have forced me backwards. I had a series of crashes and hangs today. 4.6x running on 10.5.6 never crashed at all, to the best of my recollection, and was a stable piece of software. What a shame. No changes with my system except for the C1 upgrade. I guess I'll sit this one out, at least until 4.7.1 comes along.
I find it very strange when I read posts about C1 V4.xx crashing. From V4.6x onwards, I have not had a crash at all. I cannot remember accurately about earlier versions of V4.xx but if I did have any crash it was also very rare. I'm also having the same experience with Win XP. I think I'm must be a very lucky person because quite a few people are posting about crashes.0 -
I too have had to revert back to version 4.6.2 - never had to do that with previous versions of C1 - hopefully they will unravel the reason/s why from all our crash reports and get the program back to a usable state. 0 -
[quote="David" wrote:
I too have had to revert back to version 4.6.2 - never had to do that with previous versions of C1 - hopefully they will unravel the reason/s why from all our crash reports and get the program back to a usable state.
Hopefully you have reported more details in a support case with Phase One.0 -
I was told that it was probably because there was another C1 program running underneath, that shouldn't be, and that I should restart the Mac if it happens! That was the extent of the support.
I'm just hoping that they are working on a fix. Having said this, I've worked three projects through today and yesterday and not one crash. I think they are smaller shoots. The one with repeated crashes had 900+ images in one album. I know it should be able to handle this, they don't say anywhere it's unstable over 300/500/800 images, or 2Gb, or 4 Gb or whatever, but they probably never tested it to that (pro) level.
So I'll keep going as I like some of the stuff over 3.7 which is from where I upgraded. I hate to go back!0 -
Are these shoots that crash done with P1 backs or are they shot with 3rd party cameras? 0 -
Canon 1DsMkII, 5D MkII, and Leica M8 & 8.2.
None of them any trouble with 3.7.
Importing via Lexar Pro SD card readers [FW800]0 -
My guess it is not frozen but since there is a lack of a progress bar when updating sessions files and settings files etc this is what you experience.
This have to of course be changed.
Try to rename your current session, default this is ~/Pictures/Capture One Library
Rename this to ~/Pictures/Old Capture One Library
And open Capture One 4.7 again.
This should do the trick.0 -
Thanks ULF, but my issue is the program just shut down repeatedly. It quit all on its own. Or it did with that big number of image files. It's not done this (or frozen all day today).
But I hear you about the progress bar missing, this is a huge headache. I also miss it during the building of the web browser (for contact sheet). Nothing worse than not knowing if it's happening or not.
While I have you...
I'd quite like the clarity slider to go into the negative. It's just a nice way to soften some landscape images, it gives them a lovely quality when the light's a little harsh.
Also, in the contact sheet, I'd like to put my business name in the first title space, then, instead of one frame for description, I'd find it really handy to have spaces to name the agency or art director, the client's name, the date, and location. if this is too tricky, then at least allow us to have line breaks, so we can use paragraphs to give the client the information they need more clearly than we can right now.
Finally, it would be great to be able to manually sort the images in Contact Sheet somehow (in LightRoom 2 you can do this by sending the files to a favourites folder, the only place you can sort manually). It would really help to be able to group shots in categories so the client or art director can easily edit.
Thanks!
Happy with the product though, teething problems that's all, slowly finding my way around the program. I tried version 3.x and didn't buy, it didn't feel right, this seems to be a much more 'Pro' product.
John
www.netgoose.co.uk0 -
[quote="Ulf" wrote:
My guess it is not frozen but since there is a lack of a progress bar when updating sessions files and settings files etc this is what you experience.
This have to of course be changed.
Try to rename your current session, default this is ~/Pictures/Capture One Library
Rename this to ~/Pictures/Old Capture One Library
And open Capture One 4.7 again.
This should do the trick.
Simply start to provide a stable version and stop ignoring us all. Do you think we are all stupid. I am not going to rename all sessions and clear preferences of all my shoots each time you feel to make the softwear even more unworkable.
4.7 is more crashing than ever. It is freezing and mostly even the bug report is freezing that i cant send them.. and it would ahve been a lot.0 -
Can we assume, from the fact that this thread is not many times as long as it is, that most people are not experiencing the same issues with significant instability in 4.7 that some of us have run into? I've seen isolated posts on other forums, and most of those who are having problems are having repeated problems, but no avalanche of crash reports. What might be the common thread for those of us on 10.5.6 that can't get it to work for us doing routine database chores without crashes or hangs? 0 -
My problem with 4.7 is that when processing 1DsIII files, 4.7 appears to have of it's own accord, dropped both the camera profile and picture style. It's pretty weird watching all your previews turn dark and green right before your eyes. Oh, and the freaking noise reduction is still on when it's set to Zero until you move the sliders up and back again.
The folks at Phase keep saying that they're listening and responding but it just doesn't seem like they're really hearing.
What is happening for me is that after I jump through all the hoops i get great results. it's just that there are so many little steps that I have to double-check for every file i process that the workflow advantage has practically disappeared.0 -
Here is a support question I sent and the reply I got.
I have just started using the 5D Mark II I downloaded C1 Pro 4.7 today I did an intensive photo shoot where I was downloading shots in a rapid sequence tethered to my Macbook Pro Intel. Things would go along fine and then the files would stop downloading and the program would come to a halt and the spinning ball would come on. Nothing would stop this except by shutting down and force quitting the software. When I tried to shut off the camera it told me that is was downloading files but it never stopped and those files were neither on the card or computer.
I am also noticing that the preview is taking longer than I have experienced in the past with my 1Ds Mark II.
Any advice or help would be appreciated.
the reply......
Hi Lanny,
Unfortunately the problem that you are experiencing here is caused by drivers from Apple that do not release RAM (the same issue happens with EOS utility as well). If you open Activity Monitor while you are shooting you will see that a process called Image Capture Extension is using more memory on every shot and eventually it will use up all your RAM, when this happens the crash will occur. Until Apple addresses this issue in a system update my recommendation is to monitor the memory usage of Image Capture Extension and quit the process before it crashes the software and the images in the buffer are lost. After killing the process, just reconnect the camera so that it starts again.
Additional questions
I'm not sure if more RAM in the Macbook Pro will help. I sent back that question to Support but have not heard back at this time. I will try to talk to someone at the Mac store to see if they have any ideas. To have to shut down the camera and restart at a specific time may be difficult in the middle of a shoot but I don't know what else to do at this point.0 -
[quote="Lanny" wrote:
Here is a support question I sent and the reply I got.
I have just started using the 5D Mark II I downloaded C1 Pro 4.7 today I did an intensive photo shoot where I was downloading shots in a rapid sequence tethered to my Macbook Pro Intel. Things would go along fine and then the files would stop downloading and the program would come to a halt and the spinning ball would come on. Nothing would stop this except by shutting down and force quitting the software. When I tried to shut off the camera it told me that is was downloading files but it never stopped and those files were neither on the card or computer.
I am also noticing that the preview is taking longer than I have experienced in the past with my 1Ds Mark II.
Any advice or help would be appreciated.
the reply......
I can relate to this, we were putting the DsMarkIII and CO4.7 through some intensive tests, tethered on two separate but similar MacPro machines (dual quads one with 2.66, the other at 3 Ghz and 8 GB of RAM in both, both running 10.5.6.
We would be taking frame after frame as we would do on a fashion shoot, sometimes running up to 300+ frames...
With out warning we would stop receiving the captures, the buffer in the viewfinder of the camera would read busy, and the workstation would lock up... sometimes we could recover by Force Quitting the software, once we quat, and powered down the camera, the camera would "record the images" forever if we let it, it did this for an hour before I unplugged from the tower, and the number counted down like it was putting the images somewhere, but they are nowhere to be found.
The preview is a deal breaker, in versions 3.x there was no down time between frames, and now in 4.x-4.7 the area where the preview should be goes blank as the next frame is loaded. In short, we see the first image for a split second, it hardly renders itself into focus before disappearing, and we're left looking at the blank screen while the second frame flashes, renders, then disappears, then the third, fourth etc, (many of the frames we are taking we don't even get the chance to view until the Photographer has stopped shooting and, if the software doesn't lock up, all the images are transfered through the tethered USB 2 cable. Then we have to go back through them.) So we are left looking at the blank screen waiting for the next capture, more than we are looking at the actual image itself. This would be very disappointing for any Art Director we would work with and is very hard to explain.
I haven't tried monitoring the Activity of the Image Capture extension, but I will.
This would be difficult to explain to the Director on set, but if it is the only workaround, and if it works we will do it.
This post may be useless . . . but if we are all hoping it will get better, hopefully it does.0 -
Re the reply Lanny got from Phase this looks like it might explain my experience recently. I have to ask though why is this not listed in known issues? Why do we have to discover these problems for ourselves in shoot situations? Why does Phase One not spell out in bold that due to erroneous memory handling in OSX Capture One should be relaunched after "X" number of exposures so we're not muddling through this in already stressful enough situations? And then we're expected to file a support case to tell them what they already know. What a waste of time and goodwill.
Dave0 -
I would like to confirm the behavior described in this thread. The software will lock up after a couple hundred frames and become unresponsive. Force-quitting the application has a 50% chance of requiring a reboot of the entire system. The DS1 MKIII hangs too, losing all images in the buffer. They do not appear in the card. This is repeatable across different workstations with ample RAM >6GB. OSX 10.5.6, Intel MacPro.
The possible workaround of quitting C1 4.7 after a certain number of frames -might- get us through a high speed fashion shoot. We reboot our machines periodically at convenient times anyway.
However, the problem of preview rendering kills this software for us. There is No Reason that the art director needs to be looking at an empty preview window half the time. In C1 3x. the preview would appear, sharpen, and then PERSIST until the next frame replaced it. Despite the time lag, the old software gave the AD time to see the image and make a judgment. In 4.7, the preview appears, sharpens, and then disappears leaving a blank window for a second until the next frame appears. I have had an AD insist that we stop the shoot and revert to C1 3x and the DS MkII. All the high end equipment and software features in the world are not enough to placate an annoyed AD who may decide to shoot somewhere else next time.
What this means is that we have an $8000 camera sitting in the closet because our client can't do her job with C1 4.7.
So hows this for an idea:
Write a driver for C1 3x that works with the new DLSRs that currently only work in C1 4.7 and OS X 10.5.6. Once Phase One has allowed us to get back to work instead of troubleshooting the application, we can truly determine if the new whiz-bang features of C1 4 are worthwhile.0 -
[quote="Jon" wrote:
So hows this for an idea:
Write a driver for C1 3x that works with the new DLSRs that currently only work in C1 4.7 and OS X 10.5.6. Once Phase One has allowed us to get back to work instead of troubleshooting the application, we can truly determine if the new whiz-bang features of C1 4 are worthwhile.
Unfortunately this would not only take a substantial amount of time to implement, it would not really solve the crashing problem. In order to tether a Canon or a Nikon camera we have to use software provided by the manufacturer (SDK). Both of these SDK tie-in with the OS quite a bit and thanks to a bad driver we have this wonderful crashing problem when all the Ram is used up (as do EOS utility and Nikon Capture). If we were to use the same new SDK with the old software the result would be the same. Of course the old SDK which works great does not support the newer cameras.
Of course this does this not happen with Phase One backs (since we don't rout our tethering through image capture). Also since the camera releases images from the buffer faster and shoots a bit slower, (or as I like to say is better paced), the images you see in Capture One are more current with what is being shot. Compare this to shooting Canon where the art director is often 10-20 images behind what the photographer is shooting and it can be a much better experience.
I can echo the complaints about the the previews not appearing until the full preview has been processed, it's never good for the Art director to see nothing and I have alerted R&D to the problems that this causes.0 -
[quote="Jon" wrote:
[quote="Jon" wrote:
So hows this for an idea:
Write a driver for C1 3x that works with the new DLSRs that currently only work in C1 4.7 and OS X 10.5.6. Once Phase One has allowed us to get back to work instead of troubleshooting the application, we can truly determine if the new whiz-bang features of C1 4 are worthwhile.
Unfortunately this would not only take a substantial amount of time to implement, it would not really solve the crashing problem. In order to tether a Canon or a Nikon camera we have to use software provided by the manufacturer (SDK). Both of these SDK tie-in with the OS quite a bit and thanks to a bad driver we have this wonderful crashing problem when all the Ram is used up (as do EOS utility and Nikon Capture). If we were to use the same new SDK with the old software the result would be the same. Of course the old SDK which works great does not support the newer cameras.
Thanks for responding. I understand that you are bound by the limits of the operating system and manufacturer SDK. Your explanation above makes sense.... for OS X 10.5.6 Leopard. However, I would be willing to downgrade my OS to 10.4.1x Tiger, which will happily connect to the Ds1 MkIII (we have just tested this). The only reason we are using Leopard (which breaks a lot of other things as well) is because C1 4.7 won't work in Tiger, and only C1 4.7 will tether to the Ds MkIII. It is the 10.5.6 Leopard OS which contains the bad driver. Enabling C1 3x to work with the new Ds MkIII also enables us to use 10.4.1x Tiger and get around the whole driver problem. Everyone following this thread is hoping that Snow Leopard fixes this image capture driver problem, but who knows when what will be or what, in turn, Snow Leopard will break.
Of course this does this not happen with Phase One backs (since we don't rout our tethering through image capture). Also since the camera releases images from the buffer faster and shoots a bit slower, (or as I like to say is better paced), the images you see in Capture One are more current with what is being shot. Compare this to shooting Canon where the art director is often 10-20 images behind what the photographer is shooting and it can be a much better experience.
Having a shorter lag time between capture and preview on screen would be nice, but most ADs learn to get used to that, provided they trust that they are in fact seeing ALL the frames.
I can echo the complaints about the the previews not appearing until the full preview has been processed, it's never good for the Art director to see nothing and I have alerted R&D to the problems that this causes.
Thank you. C1 3x was not exactly "Art Director Friendly", but C1 4.7 is downright hostile to ADs. They need to be considered too, since we don't shoot in a vacuum.
0 -
[quote="Jon" wrote:
[quote="Jon" wrote:
[quote="Jon" wrote:
So hows this for an idea:
Thank you. C1 3x was not exactly "Art Director Friendly", but C1 4.7 is downright hostile to ADs. They need to be considered too, since we don't shoot in a vacuum.
How about this for an idea? Ignore Capture 4 for starters.
Set up & get the lighting right. Check it on screen a la what was called a polaroid in the old days. Make sure your client is happy with he/she sees & the you, as the photographer, get on with what your good at which is taking pictures. Don't let the client constantly look at the bloody monitor - it just slows everything down destroys any spontaneity and energy. In fact don't even join the camera up to the computer. Let your client trust your abilities & you, your 'gut reaction'. Shoot away, you never know you might get what used to be called a happy accident or even something special as it's not been contrived by a committee trying to merge bits from 50 different frames into 1. Then every so often, download & once you've checked all's OK, allow the client to have a quick look. None of my a/ds get to look at anything before I have and then only as thumbs.
This constant looking at the monitor seems to be destroying photography. Why not just CGI the whole lot. Then at least you wouldn't have to worry about C4 freezing or tethering issues.
It's also one less wire trailing across the floor for some muppet to trip over & trash your camera. Radio slaves, the best thing invented.0 -
Happy accidents are a lovely idea David, unfortunately the same can't be said for the other kind and I don't know many ad's who are prepared to gamble either way in this economy. Anyway you can't turn back the clock I agree you can easily bog down if you're checking the monitor after every frame but there's also other benefits to reliable tethering--everything's disked as you go no uploading later whatever, it's a reasonable expectation that it should work.
Cheers,
Dave0 -
Still continues to crash. Today three or four times, probably more than in all prior use with CO Pro, and I've been using it since v1. Crash reports duly sent in, if this part of the program is functional. Odd and cumbersome. 0 -
Hello,
I just downloaded the latest version of Capture 4.7 (I'm running a 2 x 3.2 GHz Quad-Core Intel Xeon Mac with 6 GB RAM using OS X 10.5.6.) I also have my computer crashing numerous times. It also freezes during batch processing. The files I'm trying to work are IIQS files created in Capture One Pro 3.7. Do I have to revert to the old software? Is it just that this new version is buggy and not stable on this version of OS X? Please help!
David0 -
For those of us here who are having REPEATED, FREQUENT software hangs and unexpected quits, Phase One recommends deleting your preferences before applying any update to their software. We have found that a clean install of any update does indeed reduce the number of unexpected quits and spinning rainbow wheels.
The problem of the driver memory leak will still remain, however, requiring the user to kill the "Image Capture Extension" process. This is not strictly a Phase One problem, but seems to the be main theme of this thread. We are currently looking for a workaround for this and the Vanishing Preview problem to get us through the next couple of shoots.0 -
Since I last posted I have spoken to Apple who suggested trashing the caches in both of the library folders. I have upped the RAM in my macbook pro to the max which in my case is 4gb. I did a shoot this morning and mid way through the program hung up and I had to restart the computer and C1. C1 seems to take forever to start up. I think it looks for the last session and loads that session. What I have been doing is waiting for the old session to load then close it and start a new session. I wonder if there is a way to have the program just open to a blank new session.
I hate that I have to explain that this software I am using just quits. Quite honestly I don't think there is an easy way to tell when this is going to happen. It was suggested to check the activity monitor but I have a lot to look at just to get the shoot done
(people's expression lighting etc.) without having to watch the RAM count.
I really wish I knew how to write software. I would design a program that does nothing but tether and preview. I'm sure it is more complicated than that but that's just my frustration speaking.
I will be forever indebted to anyone who can solve this problem.0 -
I am a phase back user, I have just shot one image on a P back and started work on the image preparing to process - Just adjusting the image sharpening on screen - moved around the image and programme crashes over and over again - Yes like many of you here I'm using the new Mac 2.93 Quad-Core Intel with 8 gig of Ram.
The time has come to be honest with the loyal clients... If you are having technical problems with this programme in it's latest version - then either hold back til tested rather than leave the user in a very vulnerable situation at a time of recession - when a client asks why are you using a product that does not work - I say loyalty, he said can you afford loyalty at the expense of losing clients.
Back to 3.7.9 I went, everything was back on track in seconds...
I personally love the [u]potential[/u] of 4, but will it survive the lack of support from a very brutal industry?
Eddie (P Back user since 2004)0 -
[quote="eddie" wrote:
I am a phase back user, I have just shot one image on a P back and started work on the image preparing to process - Just adjusting the image sharpening on screen - moved around the image and programme crashes over and over again - Yes like many of you here I'm using the new Mac 2.93 Quad-Core Intel with 8 gig of Ram.
The time has come to be honest with the loyal clients... If you are having technical problems with this programme in it's latest version - then either hold back til tested rather than leave the user in a very vulnerable situation at a time of recession - when a client asks why are you using a product that does not work - I say loyalty, he said can you afford loyalty at the expense of losing clients.
Back to 3.7.9 I went, everything was back on track in seconds...
I personally love the potential of 4, but will it survive the lack of support from a very brutal industry?
Eddie (P Back user since 2004)
Which version did you try it on? Did you try CO 4.8? It includes a number of bugfixes.0 -
Still crashing in 4.8 - did a complete re-install followed the help pages 1164 / 1589 of knowledge base. Still no luck.
I remember this used to happen early on in 3.5ish in colour editor. You would be moving a slider then it would crash.
This time it is is the sharpening palette - if i crop and move it crashes / generally feels very unstable.
If anyone out there can offer advice I would be glad to hear it.
Eddie London.0 -
Eddie,
did you completely clean up all traces of C1 Pro before re-installing, and I mean all.0 -
Hi Henry, yes to the best of my knowledge - followed the instructions to the letter. Why, can't there be software that removes everything for us to save having to look all over the place and maube missing something - I'm sure you used to get un-install software for reasons we have discussed, so stop any oversights.
If there may be a rhyme or reason to these crashes keep happening - someone please give the application a chance and tell the rest of us.
Eddie0
Post is closed for comments.
Comments
37 comments