CO 7.1 is the buggiest ever!
I only go back to 6.4.4 with CO and have loaded each version since. 7.0 had its share of problems, but 7.01 and 7.02 seemed to remedy quite a few ... at least on my system. But I still suffered some crashes and freezes from time to time. So I downloaded 7.1. Mistake. I'm back to 7.02. End of story.
- Steve
- Steve
0
-
Totally different experience on my end…7.1 has been flawless thus far. Try it again and make sure in your preferences that your hardware acceleration is set to NEVER on both drop down menus. If its set to AUTO change to NEVER. Restart software and give it a try. 0 -
Id also recommend a clean install of the 7.1...
http://www.phaseone.com/en/search/artic ... nguageid=10 -
[quote="NeilBurgerDigitalTechChicago" wrote:
Id also recommend a clean install of the 7.1...
http://www.phaseone.com/en/search/artic ... nguageid=1
I totally agree with this.
I have recently installed two Samsung Pro SSDs and 16Gb Ram into my 2012 MacBook Pro, done a full, clean install of ML 10.8.2 and all applications including Capture One Pro 7.1.
I have been using CO Pro 7.1 heavily over the last few days with tethered shooting from a Canon 1DX, importing from CF cards, processing many hundreds of raws etc and so far, fingers crossed, everything has been very stable - and very fast.
Surprisingly, CO Pro 7.1 now closes down almost immediately - I don't know if this is due to the SSD drives? Before the upgrade to my hardware, it took many seconds to close down and occasionally crashed during shut-down for no apparent reason.
All I need Phase One to do now is remove the REALLY ANNOYING automatic Lens Adjustments added to imports coming in which I have to constantly remember to remove before I even start working on the images. It should be OFF by default.
Regards0 -
[quote="ianmac" wrote:
[/quote]
All I need Phase One to do now is remove the REALLY ANNOYING automatic Lens Adjustments added to imports coming in which I have to constantly remember to remove before I even start working on the images. It should be OFF by default.
Regards
+ 1 A hearty endorsement of this remarkably perspicacious observation0 -
If they are reading this thread let me add one other pain. Its the "copy from last" box. This one box, until I discovered it, almost cost me clients. What it does is build on each correction you make. So if you dont know about the copy from last box, it will cause you to end up with images that are already maxed out on adjustments before you even process it.
Every time you set up a session you need to set that box to "defaults" or you will be in big trouble. If I want to copy from last Ill use the copy adjustments and let it go as I want it. Never understood this box.0 -
[quote="Tosy" wrote:
If they are reading this thread let me add one other pain. Its the "copy from last" box. This one box, until I discovered it, almost cost me clients. What it does is build on each correction you make. So if you dont know about the copy from last box, it will cause you to end up with images that are already maxed out on adjustments before you even process it.
Every time you set up a session you need to set that box to "defaults" or you will be in big trouble. If I want to copy from last Ill use the copy adjustments and let it go as I want it. Never understood this box.
Where is that Box?0 -
[quote="Tosy" wrote:
If they are reading this thread let me add one other pain. Its the "copy from last" box.
...
Never understood this box.
This box is in the Next Capture Adjustments tool and works during tethering only. It allows you to apply adjustments you make earlier in the shoot - to get the right impression on screen - automatically on consecutive shots.
I think that 99% of the tethered shooters use this setting, hence it is made the default.0 -
Paul,
Thanks for the reply. Is there a way to make "default" the default setting?
I shoot tethered all the time. Simply, Id like to make that the default setting.
thanks0 -
[quote="Tosy" wrote:
Is there a way to make "default" the default setting?
I shoot tethered all the time. Simply, Id like to make that the default setting.
Not directly no, but indirectly yes.
You can make a session (or catalog), set this setting and optionally others as well and leave that session alone as a template.
Each time you need a new session, duplicate the session folder, rename the session folder plus the session file inside that folder and you're set.0 -
"CO 7.1 is the buggiest ever!" - i would nominate the infamous version 4. something that had an update that outright corrupted Canon files as the buggiest ever.
/end of unconstructive post0 -
[quote="Edward51" wrote:
"CO 7.1 is the buggiest ever!" - i would nominate the infamous version 4. something that had an update that outright corrupted Canon files as the buggiest ever.
/end of unconstructive post
As time has passed the problem surely changes.
If you go back a few years developers would likely be using tools that had a reasonably long development history and might be expceted to work say 90% of the time. Use something in the 10% and you may run into problems.
Cut some poor code back then ... well, yep, culpability might be down to the developers.
However the more recent era of software tool development - the core stuff the end user developers use to carve code that we all access rather than the stuff hidden below - is perhaps a little less robust than people think. This is likely to be espcially true for "Open" software development. Sometimes this development offer huge potential advantages but with the risk (some might suggest benefit) that the code is not the responsibility of a single quality control organisation. I use that phrase broadly and without implying faith in controls.
Long term the benefits may be enormous. Short term the challenges may be extreme in some circumstances.
It's always much more difficult to hit a moving target, let alone score the bullseye.
My thoughts, for what they are worth.
Grant Perkins0
Post is closed for comments.
Comments
11 comments