Repeated Crashes and Freezes with 4.8
It saddens we to write this, after a whole day wasted on loading and reloading - sending numerous crash reports to both Phase and Apple - Is it bugs or an infestation.
I think we need an open policy on what is going on, I know how frustrating it must be to write coding - but it more pressure standing in front of clients on the real end of photography when this software is not fit for purpose.
I beg you, take a breather and come up with solutions the way things are going you'll be on 6.1 before the beginning on June and still not sorted out the crashes.
I have waited along time for a solid follow up to 3 - so a few months more will not be a problem - Just come back with a killer App, not more updated apologies for the real thing...
I think we need an open policy on what is going on, I know how frustrating it must be to write coding - but it more pressure standing in front of clients on the real end of photography when this software is not fit for purpose.
I beg you, take a breather and come up with solutions the way things are going you'll be on 6.1 before the beginning on June and still not sorted out the crashes.
I have waited along time for a solid follow up to 3 - so a few months more will not be a problem - Just come back with a killer App, not more updated apologies for the real thing...
0
-
Hi folks, here is one thing I noticed - just before it crashed it said out of memory - There is about 600 gig available - any thoughts out there?
I only had one image in the folder.
Eddie0 -
Try throwing away your Phase One preferences restarting and see if that works. 0 -
I've had the same problems with CO 4.7 and now 4.8 crashing and freezing the computer. It took me over an hour yesterday with clients looking over my shoulder to finally get Capture One to Open without quiting. I've trashed the prefs, trashed the last folder that i was working on, and trashed the prefs over and over again and for no reason it would open. It has since crashed again about 10 times but for the time being seams to re open OK after restarting the program. I've not had problems with software behaving like this for 15 years, that was normally conflicts with other programs.
I need a real solution, I'm about to upgrage my P25+ and now considering Leaf, one of the reasons I went with Phase was the superior software, right now it's basically unusable, if it wasn't so damaging to my career it would be laughable.
I'd ask for a solution but from looking at previous threeds it seems as if no solution is out there.0 -
I don't mean this as a disrespectful comment but if people are shooting Phase backs and finding that Version 4.xx is crashing when they did not have any issues with V3.7.8 or V3.7.9, then why not just launch V3.xx instead on the same computer?
I'm a lucky one who has no problems with V4.xx so far but I also keep V3.7.x on both Mac and Win XP machines. Just a thought.0 -
using Canon and Phase for the same job so it's not ideal to be switching from 3.7 to 4.8. Can't process 5dII files in 3.7. Believe me, if I never had to use v4 again I'd be very happy. 0 -
JOHN
Just to check, are you crashing when shooting with the Canon or the P25+, or both. Do you have Canon's software installed?
On my Mac, I removed Canon's software to make sure there is no conflict. It is not a problem on Win XP though.0 -
I'm using the phase and canon during the same shoot. Usually tethered with the phase and cards with the canon but not used the canon software nor have I ever installed it.
There is no rhyme or reason for the crashes, it can happen while tethered, or not.0 -
Well.. at least they did work to implement Olympus cameras.
Please understand Phase One does things in priority orders.. and of course some 450 Euro camera to implement is more important than to bring back stability.
This is irony btw..
New cameras supported
o Olympus E-620
- Image Quality improvements
o Enhancements for Leica D-LUX 4
o Color enhancements for Olympus E-30
o Improved colors for jpeg and tiff files0 -
Daniel
Please spare us this kind of comments, conform to Forum Rules.
Eddie
Most of the time, if you are not working in sessions but with folders it will help if you close capture one and delete the default session which can be found in
~/Pictures/Capture One Library/
Delete the file "CaptureOne.col45"
Relaunch Capture One0 -
[quote="Ulf" wrote:
Daniel
Please spare us this kind of comments, conform to Forum Rules.
Eddie
Most of the time, if you are not working in sessions but with folders it will help if you close capture one and delete the default session which can be found in
~/Pictures/Capture One Library/
Delete the file "CaptureOne.col45"
Relaunch Capture One
Dear Ulf - after month and month over waiting for a stable version you have to understand that people are starting to get a little more controverse. I did recommend your backs over years and did actually help you selling more than enough digital backs - and you know what did make the difference. Yes - your software.. Other developers use the same sensors..
But be happy - i will delete my forum account as i can see that phase one is not interested in taking the suggestions in consideration but copying features from other sotware instead of starting to bring back what capture one once was or implementing such things as cameras that are really outside of any professional range.0 -
Thanks Ulf, I will try this.
Eddie - London0 -
Daniel
We are but in this case you have to understand it is not easy balancing requests, your needs and not all users needs. We many of the features you are requesting is in our scope, and are planned.
I know you would like it but we will not give you exact deadline for each of your requests. We are handling this internally and schedule changed based upon different needs that is more urgent, such as for example support for P40+ which was just released.
Rome was not built in a day, and as many people really love Capture One 3.7.x I am pretty sure that the lacks of Capture One 3.0 would not be accepted, the ugly duckling that became a swan.
Already now Capture One 4 rocks in so many different ways, there is more to wish from it but so much has happen from 4.0 to 4.8 and more will continue to happen.
So as I said, we are VERY interested but you have to be a little more realistic in timeline.
Also making crude comments does not help, try to be constructive I have said it before.
It is a user to user forum. If you have something to take up then contact us at Phase One support, it has been said many times before and.. well now it is said again.
I am leaving this discussion to rest here.0 -
I thought it was just me, our set-up (new Intel iMac, Capture 4.8, Phase P45 and Nikon D3X), but I was relieved to see this problem is real and experienced by more than a few.
That said, hoping this problem is rectified... extremely frustrating and embarrassing in front of clients.
Any help is most appreciated.
Peter walker
IGT Photo Studio0 -
Peter
Nikon D3X suffers under the same USB bug in Mac OS 10.5.6 as Canon does.0 -
So it's a Mac OS issue and not C1 4.8?
Any advice or recommendations?0 -
Snow Leopard - that's where we are placing our hopes 0 -
Oh dear, thats the next thing, waiting for C1 to get Snow Leopard compatibility 😉 0 -
I Have the same troubles as you guys.. just tried 4.8 and still freezes or crashes..tried everything from complete OSX instal to re-instal and activation of software...RUBBISH software...tect support say they haven't been able to reproduce the problems..well lucky them..! they also dont have clients waiting for the photographer to get his mac & camera working either... ☹️
phase one....GET IT SORTED...!!!!!0 -
Apple will probably have it sorted in a 10.5.7 update..
4.8 runs in the beta version of Snow Leopard, but this does not mean much thinking back how it was with Leopard was released. Our version at the time worked fine in the beta but not in final.0 -
Guys ------ (Phase One)
Instead of trying to be all things to all men. Can you not just get the program to work (at say roughly 99%) & then worry about adding new features.
Out of interest, is there any dialogue between the people in the room that makes the backs & those in the other room who write C4?
And, do you not feel you have a duty to those who have invested large amounts of money in one of your backs to get the proprietary software running correctly before adding new features?
Just a casual observation from someone about €30k lighter on the bank balance.0 -
Just finished a 3 Day shoot through post using 4.8.
Thought I would give some feedback....
3 Day shoot
Day 1 mild amount of captures on Canon 1Ds MkIII, using 4.7 and aware of 4Gig limit on tether. A few crashes but nothing major.
Day 2 High volume of captures on Canon 1Ds MkIII, C1 4.7 crashing every 5-10 min.
System goes down with a crashed drive... move to Back-up Laptop system, and crashes continue. Shoot continues, crashes occur on startup of application and just randomly.
Calls to Phase One support, and told to go online and start a trouble ticket. Thanks!
I find that deleting the C1 4.7 Preferences gets things more stable. An hour later 4.8 update is released from Phase One. Thanks Support for not mentioning it. 👿
I start a clean install on my original Mac Pro while I get another Mac Pro delivered to get through the day.
Day 3 Original Mac Pro system is back up and running smooth, still have 4Gig limit on tethered. But much more stable then 4.7. But still not even close to 3.7 stability. Still have the occasional random crash.
Post Day: Tools in 4.8 for color correction are pretty nice... although stability is still a problem. Trying to apply color correction to 75 images crashes the application.
I batched queued about 800 images for processing over night and all done in morning.
Continue post: processing images while working on other images causes queue to stop.
I keep having top go back and start the Queue again. Which then gives me duplicate files later.
I started to notice random files showing up in destination folders, even some RAW files moved! I can't figure out how these files got moved, but it is really worrisome.
Sacha0 -
I had tethered shoot 10 hours under very humid room conditions yesterday.
MacBook Leopard 4G RAM, Canon 1Ds MKII, CO4.7 - Over 300 files non stop without crash!
Just installed CO4.8 today, not sure how it will go later. As advised I removed all the files under the Picture directory of CO LiB.
Keep my finger closed!
-Teng Wei0 -
I shot all day yesterday with 5dMkII MacBook Pro 17" OSX 10.5.6 CO 4.7 tethered. I had 10 models to shoot on a yacht in blazing sunshine, crashed every 30-40 frames.
I was restarting Capture One
Switching off camera and ejecting batteries to get it going again.
A couple of questions
Does it make any difference what length, quality etc of USB cable you use.
Is there a quicker way of restarting a crash.
Would 4.8 improve or worsen the situation
Thanks
Alan0 -
[quote="Alan222" wrote:
I shot all day yesterday with 5dMkII MacBook Pro 17" OSX 10.5.6 CO 4.7 tethered. I had 10 models to shoot on a yacht in blazing sunshine, crashed every 30-40 frames.
I was restarting Capture One
Switching off camera and ejecting batteries to get it going again.
A couple of questions
Does it make any difference what length, quality etc of USB cable you use.
Is there a quicker way of restarting a crash.
Would 4.8 improve or worsen the situation
Thanks
Alan
This is discussed here quite frequently, most recently post is viewtopic.php?p=29476#p29476
It is a regarded to be OS X bug, independent from whether you use Capture One or Canon EOS Utility for tethering.0 -
Well, it is not just a Mac issue. I have Constant crashes with 4.8 in Windows XP,.Net Framework 3. Phase one advises running the repair mode on .Net but it still crashes after that. Especially if 400+files. This software has not functioned properly since 3.6.
The problems seemed to continually be the fault of the Operating systems according to Phase1. Suprising since NX, CS3,Silky pix, Rawshooter, Corel, Pro Desktop and every other piece of software I have never crashes under XP. This is the only piece of software that contiually fails. I modfied the code in the old Rawshooter to open D2Xs files and it is faster and never fails. I am not sure what is up with this software but it is swiftly becoming a liability.
Andrew Philip.0 -
[quote="eddie1" wrote:
Hi folks, here is one thing I noticed - just before it crashed it said out of memory - There is about 600 gig available - any thoughts out there?
I only had one image in the folder.
Eddie
We are getting that also.. very very very unstable.. It kinda makes me mad that this program was released and most of us that upgrade to the 1DS Mark III were forced to buy the new program becuase the old Capture one did not support that camera. I do a large qty of shooting and before this was a good program to keep us organized, but now it just a problem.. the output folders is weird and doesn't always send it to the correct job. I am looking a aperture as maybe a fix, now that you can shoot tethered. Anyone else using this program?0 -
Has anyone tested the new 10.5.7 operating system? with Capture one 4.8 to see if the problem of crashing is still there?? 0 -
Hi All,
just came home after testing the new os update of 10.5.7 with capture one 4.8 and a Canon 1ds Mk 3....
and I didn't have one crash all day after shooting 50 different looks...
seems that the problem has been fixed with 10.5.7 update..0 -
Hi,
I've got similar issues with 4.8. After the Mac OS 10.5.7 update it even got worse.
It is almost impossible to get anything done.
The smallest corrections on a file in a session can cause the software to hang and remain that way. I have already restarted my Mac 4 times this morning.
Please Phase One, do something about it.
Mac Pro 8core 3,2Ghz 6Gb RAM should do the works with C1 Pro but not at this moment.
This is costing a lot of money, I am a huge Phase One fan with P65+ on the way but these software failures cannot be tolerated.
Kind greetings,
Bert Balcaen0 -
My girlfriend uses CaptureOne Pro 4.8.1, Mac OSX 10.5.7, and a Phase One P30, tethered to a MacBook Pro via Firewire. We've always had bad experiences with version 4, but today (on a magazine shoot) it hit a new low.
CaptureOne repeatedly crashes. It appears to have a memory leak. We tried trashing preferences. No difference.
I see talk on ths forum of OS-level problems with USB drivers etc having memory leaks. Has anyone demonstrated this, and that the problem occurs with Firewire? Or is it blame-shifting?
From where I sit it looks clearly as if there is a memory leak with CaptureOne.
As an aside, Phase One, do you apply automated testing (continuous integration, unit testing, stress testing etc) to your software?
As a software developer, I suggest you stop adding new features and make it stable. Otherwise people will dump it, and resent your brand. We'd use Lightroom in an instant if it supported tethered shooting.0
Post is closed for comments.
Comments
37 comments