4.5.1 keeps crashing...
Hi,
Well, I must say that there´s something really wrong about 4.5.1 pro !
4.5 pro worked quite nicely and without any major problems, but this new 4.5.1 keeps crashing all the time and I can´t get my work done.
So is there still a download link where I can get the 4.5 pro version ?
Edit: Found the link...
Well, I must say that there´s something really wrong about 4.5.1 pro !
4.5 pro worked quite nicely and without any major problems, but this new 4.5.1 keeps crashing all the time and I can´t get my work done.
So is there still a download link where I can get the 4.5 pro version ?
Edit: Found the link...
0
-
4.5.1 keeps crashing for me as well - 2-3 minute uptime and then Vista will throw up a do you want to find a solution box.. 😡
System - Vista 64 Ultimate - SP1 (has latest updates from MS)
CPU E6850
Latest Nvidia drivers
8GB RAM
the drive where the photos are has 32GB of space left0 -
The crashes I encountered where related to insufficient memory (at least that is what 4.5.1 reported before crashing)
Thankfully I got the program running after I reconfigured the OS:s (win xp, sp3)memory usage...
Still, we are just talking about a raw converter ! I mean, how much memory does it need to run smoothly ??
To give an example, I haven´t had any problems with photoshop...which is quite a big memory hog...0 -
Have you tested the ram in your computer? That could be a possible crash cause.
Steve0 -
I have 2G ram...and it´s working fine. And like I said - if it´s enough for photoshop, I can´t imagine why C1 would need more 🤓
Furthermore, usually there are only 10-20 files (eos 5D) per folder...so it´s hard to believe that with 2G ram C1 couldn´t handle it.
A 100, maybe 200 hundred files per folder could cause the crash...but 10-20 😕
Any way, all´s working fine now...
My only complaint are:
If I apply clarity tool, curves, vignetting etc...the image processing seems to take forewer (10 to 20 seconds). But with just the basic adjustments (exposure, contrast, levels, etc) processing is quite fast...
And strangely...(eos 5D) vertical shots won´t focus (images looks soft) and the effect of clarity-tool won´t show, unless I zoom a notch with the mouse wheel 😕
Instead, when viewing eos 20D vertical shots...all works well ! This is a very annouying feature and I sure hope that PO would kill the bug...sooner the better.
So I think this has something to do with image resolution ❓0 -
Yep! My keeps crashing too! Completely nut! Won't even open at the minute without immediately crashing 😡 0 -
[quote="Vesa_Ekholm" wrote:
If I apply clarity tool, curves, vignetting etc...the image processing seems to take forewer (10 to 20 seconds). But with just the basic adjustments (exposure, contrast, levels, etc) processing is quite fast...
It is probably the clarity tool, perhaps the vignetting, I doubt the curves slow things down much (as the whole rest of the processing is based on value mapping through non-linear equations). But the clarity tool probably requires the comparison of each pixel to its neighbors rather than just picking a point in the grid of raw pixels and figuring its output color. Vignetting has each pixel being processed slightly differently from the one before and after so a simple loop with fixed values doesn't work.
Really though, is 20 seconds all that bad? Capture One is asynchronous you can be working on the next photo while the last is processing, or if you add them to the batch while it is paused you can just have them all done at once while you go off too check e-mail or something.[quote="Vesa_Ekholm" wrote:
And strangely...(eos 5D) vertical shots won´t focus (images looks soft) and the effect of clarity-tool won´t show, unless I zoom a notch with the mouse wheel 😕
Instead, when viewing eos 20D vertical shots...all works well ! This is a very annouying feature and I sure hope that PO would kill the bug...sooner the better.
So I think this has something to do with image resolution ❓
It actually has to do with zoom level. The 5D having more pixels than the 20D will be at a lower zoom when sized to Fit, and even a lower zoom level when a portrait orientation photo is being displayed on a landscape formatted monitor.
Phase One seems to be aware of the issues with previews at different magnification levels and seem to have tried to fix it in 4.5.1 (from the release notes, "Better sharpness when in "Zoom to Fit" mode"). But maybe didn't anticipate the very small scaling presented by the 5D portrait photo on some monitors.
By the way, what layout are you using? I have Tools right, and Browser left. That gives me a bit more height for photos in the middle so my portraits get close to the same Fit as my landscapes on a 16:10 widescreen monitor.0 -
[quote="martin" wrote:
Yep! My keeps crashing too! Completely nut! Won't even open at the minute without immediately crashing 😡
My guess is that you have a corrupted install.
I would suggest uninstalling the program, and then cleaning your machine of the residual directories left in the user folders.
Try using the Windows search to find folders with "Capture" or "Phase" in their name--there are a lot of them. Have a look inside each to make sure it doesn't look like anything important (like image settings). Then delete (or to be extra safe--just in case you're Recycle Bin can't hold them all--move to a back up folder). Finally, re-install the program and see if it behaves any better.
I was having a couple weird errors until I found the Phase One folder under ProgramData in Vista and cleaned it up.0 -
[quote="Christopher" wrote:
[quote="Vesa_Ekholm" wrote:
Really though, is 20 seconds all that bad? Capture One is asynchronous you can be working on the next photo while the last is processing, or if you add them to the batch while it is paused you can just have them all done at once while you go off too check e-mail or something...............Phase One seems to be aware of the issues with previews at different magnification levels and seem to have tried to fix it in 4.5.1 (from the release notes, "Better sharpness when in "Zoom to Fit" mode"). But maybe didn't anticipate the very small scaling presented by the 5D portrait photo on some monitors...................By the way, what layout are you using? I have Tools right, and Browser left. That gives me a bit more height for photos in the middle so my portraits get close to the same Fit as my landscapes on a 16:10 widescreen monitor.
Hi Christopher,
Well, you´re absolutely right... 15-20 seconds isn´t anything I couldn´t live with. I quess it´s just that...since I didn´t have anything else to complain about, had´t to say somethin 😂
I do mainly nature photographing and usually that´s all about waiting, so I´m not really in any hurry while sitting beside my computer...
Read the release notes too and hoped PO would have fixed that issue with portraits...sadly, that wasn´t the case. But, I have every confidence that PO solves the problem in future updates...
And yes...I´ve been using the same layout as you...0 -
Hi everyone, especially to Vesa_Eckholm,
I´m fighting also against permanent out of memory crashes. How did you reconfigure your OS to solver the problem?
I´m running a 4GB RAM System, should be enough memory all the time. Processor is an Intel QuadCore.
Since I upgraded from 4.5 to 4.5.1 working is nearly unpossible.
Best regards
Marc0 -
Well Marc...sorry to say, but never mind what I did...since it started again !! 🤬 Just about to throw my computer out of the window, with this **** C1 ❗️
How is it possible that everything works, but this damn raw conversion software... How hard can it be ?!?!
If anyone has any idea what´s going on with this, I´d be glad to know...
- notsohappypocustomeranymore0 -
One post suggested to test your memory (I believe Memtest86 is a good program for that). Have not heard from you guys you did do that already. Just to start troubleshooting. 0 -
Hi Paul,
Haven´t tested my memory yet...but I´ll do it right away !
Thanks,0 -
I've had the same problem with all v4's. Memory is tested and ok. 0 -
Memory tested and there seems to be no major errors... 0 -
Hmmm, lets do some math.
The 5D is 4368x2912 or a total of 12,719,616 pixels. I'm assuming that Capture One handles color internally as a single precision float point number. That will be 32-bits per color channel. So for 3 channels at 4 bytes each that becomes 152,635,392 bytes (145 MB) for each photo in memory, and that's not including any other language overhead, nor the thumbnail or preview.
.Net has automatic garbage collection. That means when an object goes out of scope (no longer used) it gets freed. But if Capture One isn't destroying the image objects as you move from one to the next, or of the .Net framework doesn't think its memory should be freed yet, after loading 20 images you already be using almost 3 GB of RAM.
I too had OOM crashes on my old computer with 2 GB of RAM when just stepping through a directory of 30D photos. Now my new machine has 32 GB running Vista 64, and I've not had a crash yet. But that's just silly. Something needs to be done with the memory management.0 -
Just came back from shooting session outside...imported images and what do I get ??? Crash, after crash, after crash !!! There´s not enought memory...or so it says 🙄
No really, how is it possible that everything else works...and C1 states that there´s not enough memory ❓ Let´s face it...the flaw is not in my computer, but in C1 ❗️
PO released an unfinished, untested program...and the users are the ones who take the beating. Right now, I can´t get anything done with my images !
So thank you very much...and yes, I´m quite angry and frustrated 😡
PS: And hey PO ! I´ve tried Adobe Lightroom...it has bells and whistles too, so many gadgets I cant´t even count them, but it worked...and NEVER crashed.
The only thing is, that I didn´t like. I like C1, I like the image quality it makes. If only it would work...0 -
OK, next step in troubleshooting is the virtual memory setting. It is best to revert to the Windows default in case you have changed it. 0 -
Sorry Paul, but there are some english terms that I dont´t understand...and my XP speaks finnish.
Can you explain to me what does virtual memory mean ? 🤭
Edit: Same as scratch disk ?
Edit2: Okay, now I think I know what you mean... Well, I´ll try that too...0 -
Well, no help to the matter there either...
Had to (again) switch back to 4.5 pro...it doesn´t crash nearly as often as 4.5.1.
So I quess I´ll wait for the next update...hopefully the answer to all of this lies there...0 -
hello again,
we will not test our memory because we do not have any trouble in any other system.
ok, there seems to be no solution at this time. In the meantime I downgraded to 4.1.1 and we are more or less able to work with the system. That means, we know how to work that C4 won´t crash. But 4.1.1 is a poor alternative in a professional environment.
I had some contact with a support girl in Germany - forget it. It looks like she didn´t have any idea at all. All the support links she sended didn´t have anything to do with the bug we reported. Completely different issues....
I´m really fed up with this banana software. Has anyone an idea what we can use instead of C4? Bibble? next version looks not bad. Before C4 we have been really Capture One fans, but the releases Phase One is delivering at the moment - they should pay money to us! These guys from phase one are very lucky that they do not live next door to me.
Regards
Marc0 -
Does Phase One listen us? (or peaple that open a support case) ? 0 -
I've stopped down to v4.1.2 because v4.5.1 crashed without warning after 3-5 minutes, and v4.5 crashes, but allows me to send an error report, and v4.1.2 still crashes, but just not as much as 4.5.. its quite annoying when trying to edit 800-1200 wedding photos.. 0 -
You might have noticed a knowledgebase article on the Phase One web site, Ulf mentioned today in another post. Might help you as well. Worth a try.
http://www.phaseone.com/HOME/Content/Su ... 20-%20Main0 -
[quote="Paul_E" wrote:
You might have noticed a knowledgebase article on the Phase One web site, Ulf mentioned today in another post. Might help you as well. Worth a try.
http://www.phaseone.com/HOME/Content/Su ... 20-%20Main
Thanks for that link: at least the opening error message is gone on my install. Can't say if it has improved stability, though.
regards,
Bernd0 -
... 4.6 is much more stable now and a big imp
But after working a while, we get this old "out of memory" crash. The problem is, if you close the software, you loose the whole batch of pictures which are not processed at this time and you have to reselect them after a restart. Not quite amazing!
And we are busy in wedding photography, so we are dealing with thousands of pictures in every job.
So the only solution seems to be, to let the image core process run until the complete batch is processed. If you have a long batch to develop, you can not go on with your work for an hour or more....
It seems to me as if the crash appears after we did some lens corrections. But we are not shure at this time.
Is there anyone here with an idea?
Regards
Marc0 -
Marc,
Why don't you stop the processing when you want to do other things with your computer or close it down? You can start it any time you like later on.0 -
Hi Paul,
thank you, this could be a temporarily solution. We can try to split in working on the pictures and after that start processsing. But I am not quite sure if this will help.
Working with the software the last hours we are quite shure now, the problems with the out of memory crash result from lens corrections. Every time you correct e.g. a 17mm picture with the lens correction distortion slider you can watch the used memory by CO running up the hill. The software has definitely a problem with its memory management.
By the way, we never run out of memory. The task manager reports in every moment still enough memory.
So we will have a try and test your idea (I suppose it will take weeks until phase one will deliver a patch).
Regards,
Marc0 -
Marc,
Valuable information about the effect of lens correction. I do hope you informed Phase One through a support case.
Although your computer may not run out of memory, the application can and crash. Therefore, another tip is to restart CO4 after correcting numerous images of offload occupied memory and before starting processing. You can monitor the amount of memory CO4 uses during making adjustments with the Task Manager. When it reaches 2 GB limit, it may crash I think.0
Post ist für Kommentare geschlossen.
Kommentare
28 Kommentare